Compose and publish a bundle
1
Create it
Click Create bundle and name it. Like a ticket type, it is born a draft.
2
Fill the box
On the bundle’s page, add contents with Add a ticket type and Add an add-on, each with a quantity — two General admission tickets and one breakfast voucher makes a duo-with-breakfast pack. A bundle needs at least one item to publish.
3
Publish
Click Publish and confirm. The bundle becomes available as one purchase at checkout.
What the buyer gets
Buying a bundle walks through one order, and fulfilment unpacks the box:- Each ticket type item produces its own registration(s) — counted against that ticket type’s capacity, exactly as if bought separately.
- Each add-on item delivers its own perks.
- Perks come from the items, never from the bundle.
Lifecycle — same as ticket types
Bundles share the standard lifecycle: draft → open ⇄ closed → archived. Drafts are invisible; Close sales / Reopen toggle availability; bundles are never deleted, only archived, and restoring lands on Closed, never Open. See Ticket types for the full rules.Rules to know
- The items’ rules still apply. A bundle cannot sell what its contents can’t: if a ticket type inside is sold out or outside its sale window, the bundle purchase can’t complete for that item. Size the contents’ capacity with bundles in mind.
- Archived items are flagged in the bundle’s contents list (”— archived”) so you notice a box pointing at a retired product.
- No nesting. A bundle contains ticket types and add-ons — not other bundles.
- Free today. A bundle carries no price of its own yet; bundle pricing arrives with paid ticketing.
- Refunds follow policy per sellable — a bundle can cite a refund policy like any other sellable.
Related
Ticket types
The registrations a bundle’s ticket items produce.
Add-ons
The perk-carrying extras a bundle can contain.