How many ticket tiers should one event have?

Two to four is typical — a member and non-member rate at minimum, with an early-bird or table rate added if it genuinely changes buyer behaviour. More tiers than that usually confuses registrants without adding meaningful revenue.

Should add-ons be shown as separate line items or bundled into the ticket price?

Separate line items — showing the base ticket and each add-on individually (in the cart and on the final invoice or receipt) makes the total transparent and lets a chamber see exactly which add-ons are actually selling, which a bundled price hides.

What happens if an add-on sells out before the main event does?

The add-on should stop being offered at checkout once its own capacity is reached, while the base ticket remains available — treating add-on capacity as independent from event capacity is what makes this possible.

Do sponsor-comped seats count against paid capacity?

They should be tracked against total event capacity (the room only holds so many people) but kept separate from paid ticket revenue in reporting, so the event's actual profit and loss is not distorted by seats that were never going to generate ticket revenue.

How to Run a Chamber Event With Paid Tickets and Add-Ons (2026)

Start with the ticket tiers, not just one price

A single flat ticket price leaves real revenue on the table and often under-serves the member-price expectation at the same time. The standard structure is a member rate and a non-member rate at minimum, sometimes with an early-bird window or a table/group rate layered on top for larger bookings.

Member rate — the discounted price for active members, usually the anchor price members expect.
Non-member (guest) rate — higher, and often the rate that funds a meaningful share of net margin on the event.
Table or group rate — a bundled price for a table of ten, common for galas and dinners.
Sponsor comps — free or discounted seats attached to a sponsorship package, tracked separately from paid tickets so the event P&L stays accurate.

Add-ons are optional extras, priced and tracked separately

An add-on — a wine pairing, a workshop seat bolted onto a conference ticket, a table upgrade — is optional on top of the base ticket, not a separate ticket type of its own. Keeping add-ons distinct from ticket tiers means a registrant can mix and match (a non-member with the wine pairing, a member without it) without the tier list multiplying into a confusing grid.

One checkout, not several

The registrant should pick a ticket tier, tick whichever add-ons they want, and pay the total in a single transaction — seats plus add-ons together. Splitting this into separate purchases (buy the ticket, then separately buy the add-on) adds friction that measurably reduces add-on attach rate, and creates two records to reconcile instead of one.

Track capacity and seats-left accurately

Capacity should be enforced at the event level (total seats) and, where relevant, at the add-on level too (a wine pairing may have fewer seats than the event itself, if the room only holds a certain number for that add-on). Showing an accurate "seats left" figure on the public registration page also creates legitimate urgency — a stale or manually-updated count either oversells the room or understates real availability.

Where Chamberflow fits

Chamberflow's event setup lets a chamber define ticket tiers and add-ons once, and the public signup page handles tier selection, add-on selection, seat quantity, and a single checkout automatically — with capacity enforced live, so seats-left is accurate rather than manually maintained. Payment settles directly to whichever payment account the chamber has connected, not to a Chamberflow-held balance.

How do you run a chamber event with paid tickets and add-ons?