Event ticketing software: 6 things to check before you pick one
Last updated

An event does not lose money at the till, it loses it in the gaps: the seat sold twice, the ticket screenshot that gets two people in, the scanner that went quiet when the Wi-Fi did. Here are six things to check before you pick ticketing software, with DEV3 Turnstub as the worked example.

1. Can two people ever hold the same seat?
Ask what happens when eight people click the same two seats in the same second. The right answer is one winner and seven clear messages, with nothing half-held. In Turnstub a hold claims the seats under a row lock and a countdown tells the buyer how long they have.

2. Is the hold visible at checkout?
A buyer who does not see a clock will wander off and block the seats. Look for a countdown, a price summary that includes fees and tax, and a promo code field that updates the total.

3. Does a ticket stay one ticket?
A screenshot should not be a second ticket. Turnstub signs every ticket, and the wallet shows a QR image that refreshes every 30 seconds.

4. What happens to a transfer?
A transfer should send a link, show the recipient the event and seat, and retire the old code when it is accepted.

5. Does the gate cope with no signal?
Ask whether the scanner works from a downloaded list when the connection drops, and what it does with duplicates afterwards. Turnstub's scanner app reconciles when it is back online, and the organiser sees the live gate board and a scan log.



6. Are the limits honest?
Turnstub is an install you run as the operator. Card payments and organiser payouts are simulated until you connect a gateway, and seat maps are generated grids with no CAD import or designer for arbitrary shapes. If an old ticket code is scanned offline before a transfer has synced, both the old and the new holder can get in; a two-hour transfer cutoff before the event narrows that gap. There are no turnstile, RFID or wristband drivers, and publishing the two Flutter apps to the stores is your step. The apps were verified only in simulator builds, tests and against the live API, not on a real device or camera; push is simulated and the device token store should be swapped for secure storage before shipping. Say that plainly to your buyers.
Everything between on sale and doors open — seat maps, holds, promo codes, signed tickets, transfers, refunds, payouts and the widget.






