Dependencies

Ticket dependencies allow you to require that one ticket type must be purchased before another ticket type becomes available. This is perfect for add-ons, upgrades, and optional extras.

What are dependencies?

Dependencies create a relationship between ticket types where a "dependent" ticket can only be purchased if a "required" ticket is also in the cart. This ensures attendees purchase necessary base tickets before adding optional extras.

Common use cases

Workshop add-ons - Require a conference pass before allowing workshop ticket purchases.

Meal packages - Require an event ticket before offering lunch or dinner add-ons.

VIP upgrades - Require a general admission ticket before offering VIP upgrade options.

Equipment rentals - Require a workshop ticket before offering equipment rental tickets.

Child tickets - Must accompany an adult ticket. You can set rules like 3 children per adult.

Creating dependencies

1. Open the ticket type that needs a dependency (e.g., the add-on or extra).
2. Enable Dependencies in the ticket settings.
3. Choose which ticket type(s) must be purchased first.
4. Set the dependency as required or recommended (recommended allows separate purchase but shows a warning).
5. Define how many dependent tickets are allowed per required ticket.