Skip to main content
A bundle packages existing ticket types and add-ons into a single purchase — a “VIP duo pack”, a “ticket + breakfast” combo. Bundles are listed on Bundles in the event navigation. A bundle grants nothing itself. When someone buys a bundle, they receive each item’s own outcome — a registration for every ticket type in the bundle, and the perks of every ticket and add-on it contains. There is no “bundle perk” and no bundle-level registration.

​
Compose and publish a bundle

1

Create it

Choose Create bundle and name it. Like a ticket type, it is created as a draft.
2

Add contents

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

Choose Publish and confirm. The bundle becomes available as one purchase at checkout.

​
What the buyer gets

Buying a bundle creates one order. Fulfilment produces each item’s outcome:
  • 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 a retired item in the bundle is visible.
  • No nesting. A bundle contains ticket types and add-ons — not other bundles.
  • A bundle has one price of its own, in the event’s currency — the buyer pays the bundle price, not the sum of its items. 0 makes it free. Paid bundles need the Business Unit’s payments connected.
  • Refunds follow policy per sellable — a bundle can cite a refund policy like any other sellable.
Because the bundle grants nothing itself, it stays in sync: change a ticket type’s perks or form and every bundle containing it follows.

Ticket types

The registrations a bundle’s ticket items produce.

Add-ons

The perk-carrying extras a bundle can contain.