Requirements

What must be in place before an event can sell access.

The three requirements

If attendee functionality is disabled under Settings → POM Events → General, there is nothing for a purchase to enroll into.

The WooCommerce side

Before linking anything, WooCommerce itself must be usable:

• a working payment method;
• tax and currency configured;
• a checkout page that completes;
• an order confirmation (thank-you) page that renders — this one matters more than usual, because enrollment happens there;
• order emails configured, since WooCommerce's emails are the only ones a buyer receives.

Test a complete purchase of any product before involving events.

The product

Any published product can be associated with an event. Practical requirements:

• Published. A draft product cannot be added to the cart.
• Purchasable, with a price.
• In stock, if you manage stock.
• Simple, for the most predictable behavior. The event button works with a single product identity, so variable products with several variations are not the natural fit — see Multiple products and one event.

Customer accounts

Enrollment attaches to the order's customer account. That has one consequence worth deciding before launch:

• with guest checkout allowed, an order may have no customer account attached, and the resulting attendee record has nothing to identify it;
• with accounts required at checkout, every buyer becomes a customer and enrollment is unambiguous.

For paid events, requiring an account — or at least strongly encouraging it — makes the attendee list reliable.

What POM Events does not add

• No ticket types, seat numbers or passes.
• No per-attendee data collection at checkout beyond what WooCommerce already gathers.
• No refund automation.
• No capacity synchronization with WooCommerce stock.

That last one matters: event capacity and product stock are two independent limits. If both are set, they can disagree. See Refunds, cancellations and attendee status.

Before selling your first event

• [ ] WooCommerce is active and a test purchase completes end to end.
• [ ] The thank-you page renders after payment.
• [ ] Order emails reach the buyer.
• [ ] The POM theme is active.
• [ ] Attendee functionality is enabled.
• [ ] The product is published, priced and purchasable.
• [ ] A decision has been made about guest checkout.
• [ ] The event's capacity and the product's stock do not contradict each other.
• [ ] Someone owns checking paid orders against the attendee list.

Then continue with Connect products to an event.