Ticket shop, checkout & registration
How this is scored
How a ticket or a registration is sold: ticket types and categories, member and early-bird prices, discount codes, bundles and add-ons, a shop embeddable on the organiser's own website or under its own domain, custom questions per ticket and per attendee, group and company bookings, capacity limits and waiting lists, reserved seating with a seating plan, recurring dates and course series, several languages, and an accessible mobile checkout.
0 — Not a ticketing or registration tool; tickets cannot be sold and registrations cannot be taken in the product.
3 — An event page on the platform with a few ticket types and a fixed sign-up form; embedding, custom questions, capacity rules or seating are basic or not described.
5 — Several ticket types with prices, quotas and sale periods, discount codes, custom questions per attendee, a shop embeddable on the organiser's website as a widget or link, capacity limits with a waiting list, and a checkout that works on a phone.
8 — A white-label shop under the organiser's own domain and design, reserved seating with a seating-plan editor, add-ons and bundles, group and company bookings with several attendees per order, conditional questions, member prices by code or login, recurring dates and course series, several languages, and the checkout's accessibility stated.
10 — A shop that fits any event: multi-event and season tickets, timed entry and seat holds, a checkout that the organiser can extend (API, custom fields synced to a CRM), an accessibility conformance statement (WCAG level named), and the conversion and drop-off of the checkout reported to the organiser.
The Conference Organiser
Their own-shop story is what I want for the association website: a complete ticket shop embedded as an iFrame with my accent colour and font and my own domain advertised, carrying my categories, discounts and the free seating plan, plus early-bird and flex tickets, event series, multi-day combo tickets, discount codes, personalised tickets with additional fields for my custom questions, and categories protected by an access key that could carry member pricing. We found no public information on one assistant booking several colleagues in a single order, on capacity limits with waiting lists, on conditional questions, on shop languages, or on an accessibility statement for the checkout. 3 4 5 9 10