What Event Ticketing Actually Costs

By the Kemicard team·3 August 2026·3 min read

Ticketing platforms are rarely compared on price honestly, because the headline number is almost never the number you pay. Understanding where the cost actually sits is the difference between a platform that looks cheap and one that is.

The four places money leaves

• Per-ticket fees. A percentage, a flat amount, or both. On a free event this can be zero; on a paid one it is usually the largest line by a distance.
• Payment processing. Separate from the platform fee and frequently quoted separately, which is how two platforms with identical headline rates end up costing different amounts.
• Who absorbs the fee. Passing fees to the attendee makes your platform cost look like zero and your tickets look more expensive. It is a pricing decision dressed as an accounting one.
• The integration tax. The cost nobody quotes: staff time reconciling the ticketing platform's data with your CRM, every single event, forever.

That last one is routinely larger than the fees for organisations running regular events, and it never appears on a comparison table.

Free is a pricing model, not an absence of cost

Platforms that are free for free events make their money on paid ones, or on payment processing, or on the data. None of that is sinister — it is worth knowing which, because it tells you what happens when your programme grows.

The specific question to ask: what does this cost at ten times our current volume? A model that is comfortable at 200 tickets can be uncomfortable at 20,000.

What actually needs to be in the platform

Feature lists are long and mostly irrelevant. Five things determine whether a platform is workable:

• Tiered ticket types with capacity limits — early bird, member, standard, comp — enforced rather than tracked by hand.
• Check-in that works at the door, including when the network does not.
• Data that reaches your systems without an export step. This is the one that compounds.
• Refunds and transfers as a supported flow, not a support ticket.
• Your branding on the ticket, because the ticket is the last thing an attendee sees before walking in.

Two different products, often confused

A consumer discovery marketplace sells your event to its audience and charges for that reach. A ticketing tool issues and manages tickets for an audience you already have.

If you need discovery, the fee buys something real. If your attendees are your members, customers or staff — which is true of most conferences, member events and corporate programmes — you are paying a discovery premium for an audience you brought yourself.

The case for issuing from your own records

If your attendees already exist as Salesforce records, ticketing from that record removes the integration tax entirely. There is no export, no reconciliation, no second copy of the customer, and attendance lands on the record the rest of your team already uses.

That does not make an external platform wrong — for public ticket sales with genuine discovery value it can be exactly right. It does mean the comparison should include the staff time, not just the percentage. See event ticketing and Kemicard pricing.

FAQ

• Should we pass fees to attendees? Common for public events, poorly received for member events where people feel they have already paid.
• Is a free platform good enough to start? Often yes. The question is what the migration costs when you outgrow it.
• What is the hidden cost people miss most? Reconciliation between the ticketing platform and the CRM, repeated every event.