A ticket scanner performs a very small action.
A customer presents a ticket. The device reads the code. A result appears.
But during a busy event, those few seconds can determine whether thousands of people enter smoothly or end up standing in a queue.
That is why ticket scanning should not be treated simply as a technical task. It is an access-control process involving devices, ticket data, staff, network connectivity and customer behaviour.
The goal is not merely to scan tickets quickly. The goal is to make every valid entry fast, every invalid entry clear, and every exception manageable.
Understand What the Scanner Is Actually Doing
A scanner is not simply checking whether a QR code can be read.
It is normally communicating with, or working from data supplied by, the ticketing system to determine whether that ticket should be accepted.
Depending on the ticketing platform and event configuration, the system may check whether the ticket belongs to the event, whether it is valid for that access point, whether it has already been used, or whether it has been cancelled or otherwise invalidated.
When a valid ticket is accepted, the scan can also change its status so that another attempt with the same ticket can be rejected. Ticketmaster's access-control documentation, for example, describes subsequent entry attempts on an already-entered ticket as being denied.
This distinction is important. The scanner reads the ticket. The access-control system decides what that scan means.
Design the Entry Process Before Event Day
The scanner is only one part of the entrance.
You also need to decide where customers queue, where scanning happens, where exceptions are handled and where customers go if there is a problem.
This matters because a scanner can be technically fast while the overall entrance remains slow.
Imagine a customer reaches the scanner without their ticket open. Another has a ticket that has already been used. A third cannot find the correct ticket on their phone. If the scanner operator has to stop and investigate every case, one difficult customer can hold up everyone behind them.
A better design separates normal entry from problem solving.
Straightforward scans continue through the main entrance. More complicated cases move to a box office or support point where staff can investigate them without stopping the entire queue.
Test Realistic Tickets
Testing should go beyond scanning one valid ticket.
Before doors open, test the situations staff are actually likely to encounter.
Scan a valid ticket. Scan that same ticket again. Test different ticket types and access permissions. Test cancelled or refunded tickets where applicable. Test both digital and printed tickets if both are accepted.
Also test the actual devices and entrance conditions.
Customers may present tickets on phones with low brightness, cracked screens or difficult-to-read displays. The scanner needs to work with the ticket formats your system actually supports.
This is especially important because some mobile ticket systems use security features that mean a screenshot is not an acceptable substitute for the live ticket. Ticketmaster, for example, uses moving barcodes on some mobile tickets and states that screenshots are not accepted for those tickets.
Test the customer journey, not just the technology.
Plan for Connectivity Problems
Network connectivity is one of the most important questions to answer before the event.
Do not simply assume that scanners will continue working if the internet disappears.
Some ticketing systems support offline scanning, but the exact behaviour varies. Ticketmaster's developer documentation, for example, describes scanners switching to an offline mode when the ticket service cannot be reached, validating tickets locally and uploading stored scans when connectivity returns.
Other systems may work differently.
Find out exactly what your platform supports: Can tickets be validated offline? What information is stored on the device? How are duplicate scans handled? What happens when the device reconnects? How are offline scans reflected in attendance reports?
Then test the process before the event. A backup mode that has never been tested is not a reliable operational plan.
Size Scanning Capacity Around Peak Arrival
The number of scanners should not be based simply on the number of attendees.
What matters is how many people are likely to arrive at the same time.
An event with 5,000 attendees arriving gradually may need less entry capacity than an event with 5,000 attendees arriving within a short period before the start time.
Consider the expected peak arrival period, number of entrances, physical queue space and the time required to resolve exceptions.
Scanner capacity also needs to be considered alongside staffing. Ten scanners do not help much if only three trained staff members are available to operate them.
Modern event-entry systems increasingly use attendance and entry data to help organisers understand expected arrival patterns and plan scanner placement and staffing.
Design for the busiest 15 or 30 minutes, not the average hour.
Give Staff a Clear Exception Process
A red or rejected scan is not necessarily the same thing as a fraudulent ticket.
The ticket might already have been used. It might belong to another event or entrance. It might have been cancelled, transferred or otherwise changed. Or there may simply be a technical problem.
Staff should know what the scanner result means and what action to take.
Most importantly, they should know when to stop troubleshooting and move the customer to a support point.
The scanning operator's job is to keep the entrance moving, not to spend five minutes investigating every unusual ticket.
A good access-control operation makes exceptions visible without allowing them to stop normal entry.
Treat Duplicate Scanning Seriously
Duplicate tickets are one of the situations that scanning systems are specifically designed to detect.
If the same ticket is presented multiple times, the system should apply the event's configured access rules rather than allowing staff to make an ad-hoc decision at the gate.
For example, Ticketmaster's external-entry model marks the first valid entry as entered and rejects subsequent entry scans for the same ticket.
This is also why customers should not casually share screenshots or copies of tickets when the ticketing system does not permit them. A copied barcode can create an entry dispute if someone else uses it first.
The scanner is therefore doing more than speeding up admission.
It is helping establish a reliable record of which tickets have actually been used.
Frequently Asked Questions
Q: Can ticket scanners work without internet access?
A: Some ticketing systems support offline scanning, while others depend more heavily on a live connection. The behaviour is platform-specific, so organisers should confirm how offline validation, duplicate detection and later synchronisation work before the event.
Q: What should happen when a ticket has already been scanned?
A: The system should clearly indicate that the ticket has already been used. Staff should follow the event's defined investigation process rather than simply overriding the result.
Q: How many scanners does an event need?
A: There is no universal number. Base the setup on expected peak arrivals, scanning speed, entrance capacity, venue layout, ticket types and the time available to admit the audience.
Q: What should customers do before reaching the scanner?
A: They should have the correct ticket ready in the format accepted by the event. For mobile tickets, it is sensible to prepare the ticket before arriving, particularly where connectivity at the venue may be unreliable.
Q: What should staff do when a ticket does not scan?
A: Check the immediate issue, such as ticket presentation or device operation. If the ticket still cannot be validated, move the customer to the appropriate support point so the main entrance can continue processing other attendees.
If you need additional advice or support, the TicketCRM team is always ready to help with your questions!