Event ticketing: features, fees and selection
Ticketing connects sales or registration with available capacity and admission. A single class has different needs from a series with reserved seats and a box office. Start with the processes you actually need. A system price alone does not show the total cost of setup, payments and support.
Sales, registration or admission checks?
Paid tickets need payment handling and clear settlement. Free registrations still need capacity limits, confirmations and possibly waiting lists. Existing sales may need only admission checks or an integration. Explain that distinction before comparing features and prices.
| Situation | Agree in the offer |
|---|---|
| Sell tickets | Sales, payments, fees and settlement. |
| Free registration | Capacity, confirmation and any extras. |
| Existing ticketing | Import, integration and responsibilities. |
Capacity, prices and seats
Give the number of events or sessions and total expected tickets or registrations. This distinguishes one large event from many small sessions. Passes, time slots and categories need coordinated capacity to avoid offering the same places more than once.
Reserved seats need a reliable seating plan, existing or created. General admission, standing and assigned seats are different configurations. Prices with currency, concessions and free categories help estimate fees. A brief overview is enough initially; a finished seating plan is not required.
Website and sales channels
The shop may work through a link or embed in your website. Check design, languages, payments and confirmations. Sales outlets, box-office work and special invitations add processes. Unneeded features do not help the audience or sales team.
Admission, devices and offline operation
Decide whether phones suffice or scanners and staff are needed. Multiple entrances require access permissions, re-entry rules and device coordination. Offline operation may need prior synchronisation. Check simultaneous offline use and subsequent reconciliation. A scanning app cannot prevent every possible misuse.
Compare all ticketing fees
Models may charge per ticket, a revenue percentage or both. Setup, managed operation, devices and modules may add costs. Agree who pays. Passing fees to buyers does not make the service free overall; it changes who bears the cost.
Distinguish complimentary tickets at a paid event from an entirely free event. Payment or delivery methods may also have different charges. Compare the total for your volume and price mix rather than just the advertised percentage.
| Item | Comparison question |
|---|---|
| Sales fee | Fixed amount, percentage, minimum and payer? |
| Setup and operation | Self-service or commissioned support? |
| Admission | Are devices, staff and training included? |
| Changes and cancellation | Processing, refunds and retained charges? |
Settlement, data and support
Agree payouts, reports and responsibility for customer queries. Check import and integrations before commissioning work with an existing solution. Agree roles, access, export and deletion for personal data. Guest lists and buyer records are unnecessary in an initial enquiry.
Test the flow before launch
Test selection, confirmation and scanning. Include mobile devices, sold-out categories and invalid or used tickets. Identify contacts for launch and the event. Agree postponement communication and refund handling; automation and fee-free refunds are not included by default.
Frequently asked questions
How much does event ticketing cost?
Volume, ticket prices and scope determine cost. Compare sales fees, setup, devices and support together.
Is ticketing free for free events?
It depends on the model and extras. Complimentary tickets at a paid event may be treated differently.
Can the shop be embedded in my website?
Many solutions offer embedding or a link. Check design, payments and technical requirements.
Do I need a finished seating plan?
Not for the initial enquiry. State whether assigned seats are needed and a plan exists.
Can admission checks work offline?
Depending on the solution. Agree synchronisation, multiple devices and loss of connection explicitly.
Do I need to upload buyer data?
No, not initially. Describe the system and required connection without guest lists or credentials.
