An event ticketing platform should be chosen on four criteria, not on price: the real fee withheld per ticket, the ability to integrate access control through an API, ownership of attendee data, and technical resilience during sales peaks. Everything else (page design, seating maps, discount codes) matters, but you’ll find it everywhere. Whoever gets this choice wrong finds out on event day, at the gates.
What a ticketing platform actually does
A ticketing platform is the system that publishes the sale, collects the money, issues the entry credential and delivers the list of expected attendees. Those are four separate functions, and no platform does all of them equally well.
Organizers tend to judge it as a sales storefront (how nice the checkout page looks) when the real problem comes later: how that list gets into the system that opens the gates, who updates it when sales continue until an hour before doors, and what happens if the venue’s connection drops at peak arrival.
The four models on the market
| Model | How you pay | Suits | Main limitation |
|---|---|---|---|
| Public marketplace | Fee on sales, often paid by the buyer | Public events looking for visibility | The relationship with the buyer stays with the platform |
| Subscription software | Monthly or per-event fee | Organizers with a recurring calendar | Fixed cost even in months with no events |
| Corporate event registration platform | Subscription or per-attendee cost | Congresses, conventions, invitation-only events | Not well suited to public sales with peaks |
| Organizer’s own custom system | Development plus maintenance | Large recurring events | Upfront investment and in-house technical responsibility |
There’s no best model in absolute terms. There’s the model that fits the format: a festival selling 20,000 tickets in three days needs to hold up under load, while an 800-person congress needs profiles, per-session quotas and personalized badges.
Fees: where the real cost hides
The percentage on the homepage is rarely the one you’re left with at the end. It’s worth rebuilding the numbers line by line:
- Service fee. The percentage on the ticket price. Clarify whether the organizer or the buyer pays it, because in the second case it raises the perceived price and affects conversion.
- Payment processing. Cards, digital wallets, bank transfers and installment payments all cost differently. In some markets installments make up half of sales and cost twice as much.
- Payout timing. Some platforms only pay out after the event. If your cash flow depends on presales, that contract detail is worth more than a percentage point of fees.
- Cost of free tickets. Many plans charge a fixed fee even on zero-value credentials: press, staff, guests. At an event with thousands of invitations, that line adds up.
- Refund costs. If the event is postponed, who pays back the fees already withheld.
A practical rule: ask for a written simulation based on your real scenario (number of tickets, average price, share of free tickets) and compare the net amount, not the percentage.
Integration with access control is not a detail
This is where useful platforms separate from the ones that become a problem. Access control is the system that checks at the entrance that the credential is valid, hasn’t already been used and matches the right zone. To work, it needs the up-to-date list.
The three possible approaches, in order of robustness:
- Real-time API integration. Every sale is reflected immediately in the access system. It’s the only acceptable option if you sell until the gates open.
- Periodic sync. Lists update every few minutes. It works if sales close the night before.
- Manual file export. Acceptable only for small, closed-list events. Every manual export is a point of human error.
The topic deserves its own chapter, and it has one: we went into detail on how to integrate access control with your ticketing platform and what to ask the provider before assuming both sides talk to each other.
A second point almost no contract covers: what happens without a connection. If the access system depends on the network to validate, a fiber outage at the venue stops entry. Offline validation solves the problem, but it has to be designed beforehand, not improvised at the gate.
Who owns attendee data
On this point it pays to be explicit during negotiation. A platform can consider itself the owner of the relationship with the buyer and only return aggregated statistics, or it can recognize the organizer as the data controller and allow a full export.
The difference shows at the next edition: without your own database, every year you start buying an audience from scratch. It also shows when you change provider, and the data has to be returned and deleted.
At a minimum, put in writing: purpose of processing, legal bases, retention periods, sub-processors and server locations, and the procedure in case of a breach. We’ve written a dedicated guide on handling all this from the organizer’s side: event attendee data privacy.
Resale and fraud: what the platform can do
No tool eliminates resale, but the right combination makes it unattractive. Named tickets, a purchase limit per ID or card, a dynamic QR code that regenerates at intervals, single validation and an official resale channel at a controlled price. The condition that makes it all work is always the same: ticketing and access control have to share the same registry in real time, otherwise the same code can get in twice through two different doors. We cover this in more depth in how to prevent ticket resale and fraud.
Eight questions before you sign
- What net amount do I receive for each 50-euro ticket (or the equivalent in your currency), all costs included?
- When are funds paid out, before or after the event?
- Do you have documented APIs for integration with an external access system?
- Can I export the full attendee list at any time?
- What volume of simultaneous sales can you handle, and what data backs that up?
- What happens if the event is postponed: who refunds the fees?
- What anti-fraud tools do you offer and how do they work with named tickets?
- Who answers the phone on event day, in what language and with what response time?
The answers to these eight questions, in writing, are worth more than any demo.
Mistakes you pay for on event day
Selling through several channels without a single registry. Opening presales without testing the entry flow with real devices. Finding out at the last minute that the printed badges aren’t in a format the reader recognizes. Forgetting that free credentials (staff, suppliers, guests, press) are often 10% of the people on site and need the same discipline as paid tickets.
With more than 150,000 attendees accredited, the recurring lesson is always the same: the bottleneck is never the sale, it’s the gate.
How to proceed
Choose the platform after you’ve defined how you want people to get in, not before. If you’d like a technical assessment of your current ticketing setup and how it integrates with access, tell us about your event and we’ll tell you what holds up and what needs to change before presales open.