Bundled Tickets and Per-Person Check-In

Bundled tickets let organisers sell one ticket that represents several people — for example a Family ticket with 2 Adult + 2 Child seats — and check those people in one at a time at the door, with headcount that matches reality in sales and reports.

This guide is for organisers setting up ticket types, running the door scanner, and reading sales/reports. It does not change how buyers see composition on checkout, PDFs, or email.

Set up a bundled ticket

On a ticket type, define a composition of seat types with a count for each (seller-specific seat types, managed in the ticket-type editor).

Example: Family = 2 Adult + 2 Child.

• Seat types in the composition must belong to your seller
• If the bundle toggle is on, an empty composition is blocked
• Tickets without a composition stay 1-person headcount (backward compatible)
• Legacy tickets keep their previous behaviour

Door scanner: partial check-in

For bundled tickets, the scanner shows a per-seat-type admission card — not a single one-tap for the whole group.

You can:

• See progress such as 2 of 4 admitted
• +1 or undo per seat type (undo stays within 0…composition count)
• Admit all remaining when you want to finish the group in one step

Admissions are applied in order on the client so rapid taps stay consistent.

Single-person tickets are unchanged: one successful scan marks them checked in.

Legacy “used” tickets

Tickets marked used before this feature (or with empty check-in admissions) are treated as fully checked in. Manually marking a ticket used clears any partial admissions.

Sales and reports

Sales and the Reports page show:

• Attendees and Checked in tiles
• Per ticket type: units, headcount, and checked-in counts
• Expandable seat-type splits under a type
• A totals row

Exports:

• CSV / PDF include headcount and seat-type composition
• Ticket sales CSV adds columns for each seat type in use

Large report tables may hit a row cap and show a truncate warning. CSV export waits until seat types are loaded so columns stay aligned.

Fees

Flat processing fees are weighted per person in the bundle (headcount), not per ticket unit. Percentage fees are unchanged. Member-covered tickets also weight flat fees by headcount.

Good to know

• Composition is resolved when you read reports and related views — it is not snapshotted onto each sold ticket. Editing a ticket type’s composition after sales can change past headcount and seat-type breakdowns in reports. Flat fee headcount is snapshotted at charge and is not re-snapshotted if you edit composition later.
• This page does not document:
  • Buyer-facing composition on checkout, PDF, or email
  • Physical seat assignment (for example A1)
  • Refund behaviour beyond keeping the fee snapshot accurate
  • Promo or member pricing changes (orthogonal to composition)
  • A hard max number of seat types per bundle
  • Bulk-editing compositions across many ticket types
  • Any UI that blocks editing composition after sales