Bundles

A bundle sells a set at one price: a table of eight, a ticket-and-shirt deal, a weekend pass with camping. Buyers see the saving against buying the pieces separately — and everything inside arrives as ordinary tickets and add-ons.

What a bundle is

A bundle is a recipe — this ticket type twice, that add-on once — with one price for the lot. It is not a new kind of ticket: buying a bundle issues each item inside exactly as if it had been bought on its own, so every ticket scans, transfers and appears in reports as itself. There is nothing new to teach your door staff.

Building one

Bundles live under Setup → Bundles in the event workspace. Pick the components and quantities, set the one price, and optionally cap how many bundles may sell and how many one order may take.
A recipe can hold up to 20 component lines, drawn from the event’s ticket types and add-ons. Types that need approval, ask the buyer to name a price, are seated, or hide behind an access code can’t be components.
On a multi-date run, a dated component names its date in the recipe — you fix it when building the bundle, so every buyer of “Opening Weekend” gets the same nights.
The form shows the components’ current worth beside your price, so you can see the saving you’re offering as you build. Bundles sort into their own display groups, like tickets and add-ons.

What buyers see

On the event page, a bundle row lists what it contains and what it saves — worked out live from the components’ current prices, so an early-bird step-up changes the stated saving on its own. In the basket and on the order page, each item shows as itself with a “part of” note naming the bundle, and the saving appears against the items it belongs to. Invoices carry the same lines and the same reduction, so the arithmetic a finance team checks always adds up.

Stock & selling rules

Availability is the tightest of the bundle’s own cap and every component’s remaining stock. A bundle can never oversell a component: if the last t-shirt goes to a solo buyer mid-checkout, the bundle sells out with it.
Buying a bundle holds real stock for each component during checkout, exactly like buying the pieces — abandoned baskets release everything.
Discount codes don’t stack on bundle items — the bundle price is already the deal. A code in the same basket still applies to anything bought alongside.
Tax is worked out per component at each item’s own rate, so a zero-rated ticket and a standard-rated shirt in one bundle each keep their correct VAT treatment.

Refunds & changes

A bundle is priced as a whole, so buyer self-service cancellation doesn’t cover its items — refund a bundle order from the console, where whole-order refunds work as they always do. In the checkout basket, removing any part of a bundle removes the whole bundle; changing how many means going back to the event page. A bundle that has sold can’t be deleted — deactivate it to stop further sales while keeping its history.