# One-code group ticket: setup and gate preflight

Use controlled test orders only. Keep buyer names and full QR/ticket codes in the ticketing system.

- **Event / ticket type:** ____________________
- **Provider and group-code setting:** ____________________
- **Planned people per group:** ______  **Expected ticket types:** ______
- **Buyer-message owner:** ____________________  **Gate exception owner:** ____________________

| Controlled case | Expected code and entitlement count | What buyer received | What gate displayed / recorded | Pass or follow-up |
| --- | --- | --- | --- | --- |
| Several tickets of one type |  |  |  |  |
| Mixed ticket types, if sold |  |  |  |  |
| Entire group arrives together |  |  |  |  |
| Only part of group arrives |  |  |  |  |
| Same code presented again |  |  |  |  |

Before launch, compare the issued-ticket record, buyer instructions, inventory record and check-in result. On Ticket Tailor, the **one-QR issuance option** and the optional **Check in orders as a group** device setting are separate controls. The latter shows order items for selection when a ticket from that order is scanned, even if it is not group-coded. The operator still chooses which tickets to mark. Do not infer that one QR combines different ticket types or that scanning alone admits everyone.

**Open mismatch / owner / next check:** ___________________________________________