Billetto

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.

How the money moves: payment methods offered to buyers (cards, PayPal, SEPA direct debit, invoice, local methods), whether the organiser connects its own payment account or the platform collects as merchant of record, when the revenue is paid out (continuously, before the event, or after it), the per-ticket and payment fees and whether they can be passed on to the buyer, refunds of single tickets and of a cancelled event, ticket transfer and resale, and chargebacks.

0 — No payment of any kind; the product only collects free registrations.

3 — Online card payment through the platform; payout timing, fee model, refunds or buyer-paid fees are basic or not described.

5 — Several payment methods including cards and PayPal or SEPA, the fee per ticket stated with the option to pass it to the buyer, the payout schedule stated, and refunds of single orders and of a cancelled event issued from the product.

8 — A choice between the organiser's own payment account (Stripe, PayPal, Mollie or similar) and platform collection, payouts before the event stated with their conditions, invoice and bank transfer for business buyers, partial refunds and refund policies set per event, ticket transfer or resale by buyers, and chargeback handling explained.

10 — Full control of the money: the merchant of record named for each set-up, payout timing and any reserve held published, every fee itemised per order, refunds, transfers and resale with the organiser's rules enforced, and the cancellation process for an event documented end to end.

How ticket revenue reaches the books correctly: the VAT rate set per ticket or product (reduced rates for concerts and culture, exemptions for education and seminars), gross and net prices shown, invoices to buyers in the organiser's name with consecutive numbers, business buyers with company name and VAT ID, reverse charge for cross-border events, cancellation invoices and credit notes, the platform's own fee invoice, e-invoicing, and exports to DATEV or named accounting systems.

0 — No receipts or invoices; the organiser has to produce every invoice outside the product.

3 — An order confirmation or simple receipt per booking; VAT rates, invoices in the organiser's name, business buyers or accounting exports are basic or not described.

5 — VAT rate configurable per ticket, invoices generated in the organiser's name with its tax details and consecutive numbers, company name and address captured for business buyers, cancellation invoices on refund, and a sales export as CSV or to at least one named accounting system.

8 — Several VAT rates in one order, net prices for business buyers, VAT IDs validated and reverse charge applied, e-invoices (XRechnung or ZUGFeRD) for public and business buyers, a DATEV export with booking data, the platform's fee invoice separated from ticket revenue, and whether the platform sells as agent or in its own name stated.

10 — Tax handled per country: VAT rules for events in several EU countries documented with the place of supply, invoices and credit notes stated as compliant with national invoice law, a reconciliation of payouts, fees and ticket revenue per event, and a GoBD-compliant archive or audit export.

What happens at the door: a check-in app that scans tickets on phones or scanners, offline scanning and several devices at once, entrances and time slots, check-in lists by name, badge printing with attendee data and QR code, box office and on-site sales with card terminals, walk-in registration, session and room check-in at conferences, attendance certificates, and live attendance figures.

0 — No check-in; tickets cannot be validated at the event.

3 — Tickets with a QR code and a guest list to tick off by hand or in a simple app; offline use, several devices, badges or on-site sales are basic or not described.

5 — A free check-in app for iOS and Android that scans tickets on several devices at once, works offline and syncs, a searchable guest list, and live check-in numbers in the dashboard.

8 — Badge printing with attendee data and QR codes, access rules per entrance, session or day, box office sales on site with a named card terminal, walk-in registration, dedicated scanner hardware supported or rented, and attendance certificates for courses.

10 — On-site operations at scale: self-service kiosks or turnstile integration, session check-in feeding continuing-education credits, cashless or on-site payments reconciled with online sales, and the hardware, offline limits and failover documented.

Who the ticket buyer belongs to: whether the organiser is the controller of attendee data and the platform its processor, or the platform a controller in its own right; whether buyers must create an account on the platform; whether the platform markets other events to the organiser's buyers or lists the event on its own marketplace; consent for the organiser's newsletter collected in the checkout; messages to attendees; attendee data exportable at any time; and deletion and anonymisation after the event.

0 — The organiser receives no attendee data at all; the platform keeps the buyer relationship entirely.

3 — A guest list visible to the organiser; who is controller, the platform's own marketing to buyers, export or deletion are basic or not described.

5 — Attendee data exportable by the organiser at any time, the organiser named as controller with a data processing agreement offered, buyers able to book without a platform account, newsletter consent for the organiser collectable in the checkout, and messages to attendees from the product.

8 — A white-label set-up in which buyers see only the organiser, the platform stated not to market other events to the organiser's buyers (or the opt-out explained), the platform's marketplace listing optional, deletion and anonymisation of attendee data after the event configurable, and attendee data synced to a named CRM or via API and webhooks.

10 — The organiser owns the relationship and can prove it: the controller and processor roles documented for every data flow, no platform account or platform marketing by default, retention set per event and enforced, and a complete export of orders, attendees and answers that a successor tool can import.

Who the contracting entity and the parent company are, where attendee, order and payment data are hosted, and who the subprocessors are (hosting, payment providers, email delivery, analytics, support). Independently sourced by the sovereignty pipeline; attendee lists show who goes where and when, and a conference list holds names, employers and dietary or accessibility answers, so the whole chain counts, not only the database.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (payments, email, analytics, support) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, a self-hosted or on-premises option or data export and deletion documented, and certifications published with their scope rather than implied.

Whether an organiser can compute the real cost of an event from public pages alone: the fee per ticket or per registration (fixed, percentage or both), payment processing fees, whether fees are charged to the organiser or added to the buyer's price, free events, subscriptions or credit packs, payout and refund fees, add-ons (seating, white label, badges, box office), hardware rental, minimums and term, and VAT on the fees.

0 — No public prices at all; every organiser is a sales call.

3 — A starting price or "free for free events" exists, but the fee for paid tickets, payment fees or who pays them is unclear.

5 — The fee per ticket and the payment processing fees are public with the main inclusions, but at least one commonly needed piece (refund fees, white label, seating, box office, hardware) is unpriced or "on request".

8 — Every fee published with its rule (per ticket, percentage, cap), the share paid by buyer and organiser stated, add-ons and hardware priced, payout and refund fees listed, and VAT treatment of the fees stated.

10 — Complete price computability: the cost of an event derivable for a given ticket price, ticket count and payment mix, with every add-on, hardware, support and payout fee and the cancellation and data-return terms published.