Multiple products and one event

Associated products accepts more than one product. This page explains what that does, what it does not do, and how to handle several price levels.

What associating several products does

It records the relationship between the event and those products.

What it does not do is turn the Get access button into a chooser. The button leads to a single purchase; it does not present the buyer with a list of ticket types on the event page.

So associating five products does not give visitors five options to pick from on the event page.

Patterns that work

One product per event

The simplest and most predictable. One event, one ticket, one price.

Use it unless you have a concrete reason not to.

Price levels as product variations

If your ticket genuinely has levels — full, reduced, member — a variable product with variations keeps them in one catalogue entry and lets the buyer choose on the product page.

To use it, send buyers to the product page rather than through the event button:

1. Disable the event's built-in button on the Attendants tab.
2. Add an additional link pointing at the product page, labelled Buy tickets.
3. The buyer chooses their variation and completes the order there.

The trade-off: a purchase made this way does not carry the event link, so enrollment is manual. That is a real cost, and it is the reason the single-product pattern is preferred.

Separate events per audience

For genuinely different offers — a members' session and a public session — two events with two products is usually cleaner than one event with two prices. Each gets its own capacity, its own attendee list and its own page.

A pass across several events

Sell the pass as a product and enroll holders manually into each event. There is no built-in multi-event enrollment.

What to avoid

Associating several products and expecting a chooser. The event page has one button.

Selling the same ticket at two prices through two products. The two orders look identical afterwards, and reconciliation becomes guesswork.

Relying on product stock as event capacity. They are independent limits and are not synchronized. If both are set they can disagree — and the disagreement surfaces at the door.

Capacity with several products

The event's Available space counts registrations, whatever produced them. A buyer of any associated product consumes a place, and once the capacity is reached, further buyers are enrolled on the waiting list.

If you sell through several products, keep one capacity on the event and manage stock consistently across the products, or turn stock management off and let the event capacity be the single limit.

Naming products for reconciliation

When more than one product can lead to one event, naming is what keeps orders readable:

Spring tasting 14/03/26 — full
Spring tasting 14/03/26 — reduced

Same event, same date, distinguishable at a glance in the order list.

Verify

1. Associate one product and confirm the button leads to it.
2. If using several, confirm which product the button actually uses.
3. Complete a purchase through each route you intend to offer.
4. Confirm which routes create an attendee automatically and which do not.
5. Document the manual step for the routes that do not.