Bundle availability and capacity¶

When you set up a bundle, the bundle's own quantity cap is only one of the limits that controls how many bundles can be sold. The individual ticket caps inside the bundle, and the total capacity of each ticket's home event (the event that owns and issues the tickets), all apply too. Understanding how these interact will save you from unexpected sold-out situations.

How the system calculates bundle availability¶

When a guest tries to buy a bundle, the system checks each ticket inside the bundle individually. For each component ticket, it calculates how many more bundles that ticket can support given its remaining inventory. It then takes the lowest of those numbers as the real available quantity for the bundle.

Example (single component): You have a bundle with one component: a General Admission ticket capped at 400. Your bundle is capped at 500.

• Bundle cap: 500
• GA ticket cap: 400
• Effective bundle availability: 400

Once 400 GA tickets are sold, the bundle is sold out — even though the bundle cap says 500. Any guest who tries to purchase after that point will get an error indicating there is not enough inventory.

Example (multiple components): You have a bundle containing two ticket types: a General Admission ticket capped at 400 and a VIP ticket capped at 200. Your bundle is capped at 500.

• Bundle cap: 500
• GA ticket cap: 400
• VIP ticket cap: 200
• Effective bundle availability: 200

The VIP ticket is the most constrained component, so the bundle's real availability is 200 — not 400 and not 500. Once 200 VIP tickets are sold, no more bundles can be purchased regardless of the other caps.

Setting the bundle to Unlimited does not remove component constraints¶

A common question: "If I set the bundle quantity to Unlimited, does that fix the problem?"

No. Setting the bundle to Unlimited removes the bundle-level ceiling, but the component tickets still have their own caps underneath. In the example above, setting the bundle to Unlimited means the bundle cap is no longer the constraint — but the GA ticket's cap of 400 still acts as a hard wall. The effective availability is still 400.

The only way to allow more bundle sales than a component ticket's cap allows is to raise or remove the cap on that component ticket itself.

Event-level total capacity also applies to bundle purchases¶

Beyond individual ticket caps, events can have a total ticket capacity limit set in the Event Editor. This is a cap on how many tickets can be sold across the entire event, regardless of ticket type.

When a bundle is purchased, the tickets inside the bundle count toward this event-level cap just like any direct ticket purchase would. The system does not treat bundle-sourced tickets differently from individually purchased ones.

Cross-event bundles: whose capacity applies?¶

Bundles can be sold through a different event's checkout. For example, a bundle containing tickets to Event A might be sold through Event B's checkout page.

In this case, Event A's capacity limits are still enforced when the purchase is made. The fact that the checkout belongs to Event B does not change whose cap applies to Event A's tickets.

• If Event A has a total ticket cap of 400, that cap is enforced regardless of which checkout the guest is using.
• Event B's own capacity configuration does not override or replace Event A's cap for Event A's tickets.
• Each event's capacity is checked independently against its own tickets.

Bundles with assigned (reserved) seating¶

When a bundle includes tickets from a reserved seating venue, the specific seats are chosen by you, the host, when you set up the bundle. The guest does not select seats at checkout. They buy the bundle and receive the exact seats you attached to it.

This is the important difference from buying a standalone reserved seating ticket. With a standalone purchase, the guest picks from whatever seats are still open in the venue. With a bundle, the seat assignment is locked in ahead of time and the guest has no selection step.

What the guest sees at checkout. The bundle is added to the cart and checked out like any other product. There is no seat picker, no venue map, no prompt to choose a seat. When the purchase completes, the tickets issued to the guest carry the seat assignments you defined on the bundle.

Mixing reserved seating with general admission in the same bundle. This works the same way. The reserved seating components carry their pre-assigned seats, and the general admission components are fulfilled from the regular inventory pool. The guest is never asked to pick a seat for any part of the bundle.

Planning your bundle inventory. Because each bundle is tied to the specific seats you attached to it, those seats are committed to the bundle the moment you set it up. If you want to sell the "same" bundle covering multiple seat locations, you need to create separate bundles, each with its own pre-assigned seats.

If one of the bundle's seats is sold separately, the whole bundle sells out. The seats attached to a bundle are not reserved exclusively for that bundle — they remain available for individual purchase through the normal seat picker. Because a bundle can only be fulfilled if every seat it contains is still available, selling any one of those seats on its own makes the bundle unfulfillable and it will immediately show as sold out. For example, if a bundle includes Seat A and Seat B and a guest buys Seat A as a standalone ticket, the bundle sells out even though Seat B is still free. If you want to guarantee a bundle stays available, make sure the seats attached to it are not also being sold individually.

Troubleshooting¶