> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://learn.nuwebgroup.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://learn.nuwebgroup.com/_mcp/server.

# How does ticket scanning and validation work at events?

> Learn how ticket scanning verifies admission rights, handles duplicate and invalid tickets, and works with barcodes, NFC, zones and offline devices.

**Ticket scanning and validation check whether a presented ticket grants entry to a particular event, time or venue area.** A scanner reads a barcode, QR code, NFC credential or other identifier, and the access-control system checks its status and applicable rules before admitting or rejecting the holder. Successful validation may also record that the ticket has been used.

**Reading a code is not the same as validating admission.** A phone can decode a QR image without knowing whether the ticket has been refunded, transferred, already scanned or restricted to another entrance. The decision requires the corresponding ticket and access rules.

## What happens when a ticket is scanned?

**A scan turns a presented credential into a validation request against the event's admission records.** The exact sequence depends on the scanning hardware and whether validation is online or offline.

A typical process is:

1. The attendee presents a ticket in a mobile app, wallet, PDF or printed format, as allowed by the event.
2. A camera, hardware reader or NFC terminal captures the credential or its identifier.
3. The access-control application identifies the relevant event, performance, date, zone or entry point.
4. The system checks that the credential exists and satisfies its configured rules.
5. If permitted, the scan is recorded as a successful check-in and relevant usage state is updated.
6. Staff receive a clear success or refusal result, with an operational reason when access is denied.

Validation may check ticket status, allowed entry dates, duplicate-use rules, re-entry policy, assigned zone, seat or ticket category. A ticket for Saturday's show should not be admitted at Friday's performance simply because both have valid-looking QR codes.

An entry system is therefore part of the wider ticketing operation: purchases, refunds, ticket transfers and administrative overrides can change whether the same credential remains eligible for use.

## Why can a valid-looking ticket be rejected?

**A readable barcode can fail validation because the admission entitlement is invalid in the current context.** Staff should distinguish between a bad scan, a valid ticket with a restriction and a genuine duplicate or revoked credential.

Common outcomes include:

| Result                  | Possible explanation                                       | Operational response                                         |
| ----------------------- | ---------------------------------------------------------- | ------------------------------------------------------------ |
| **Unreadable**          | Damaged print, glare or device issue                       | Retry or use an approved lookup method                       |
| **Unknown code**        | Credential not recognised for the event or scanner dataset | Verify event and ticket source; use support workflow         |
| **Already used**        | Ticket has been checked in under single-entry rules        | Check scan history before overriding                         |
| **Wrong event or time** | Ticket is valid, but not for this performance or window    | Direct customer to the correct entry or box office           |
| **Revoked or refunded** | Ticket entitlement was cancelled or replaced               | Verify order status; do not admit on visual appearance alone |
| **Wrong zone**          | Ticket allows main entry but not a restricted area         | Enforce the zone rule or authorised upgrade process          |

A rejection should not force staff to guess. Good systems give staff a reason code or useful context while avoiding unnecessary exposure of the customer's personal information.

## How are QR codes, barcodes and NFC different?

**QR codes and conventional barcodes are optically scanned, while NFC communicates with a compatible reader at close range.** All can carry or reference a ticket credential, but none alone determines whether admission is authorised.

A printed ticket may use a static barcode that remains unchanged. A mobile ticket may use a rotating barcode that reduces the usefulness of screenshots or forwarded images. Ticketmaster, for example, explains that some of its mobile ticket codes refresh periodically and screenshots cannot be used for entry.

NFC can reduce the need to position a phone camera precisely and may support wallet-based tap experiences. It requires appropriate hardware, pass configuration and validation rules; simply adding a ticket image to a digital wallet does not automatically create NFC access.

Each method must work with the venue's operational constraints: device availability, battery life, queues, lighting, connectivity and accessibility needs. A venue may offer several approved ways to present credentials, with clear rules for each.

## How do duplicate scans and re-entry work?

**A ticket's entry policy determines whether a second scan should be accepted.** For single-entry tickets, a second successful entry using the same live entitlement should generally be prevented or flagged. For events allowing re-entry, the system may record entry and exit events and permit another entry under defined conditions.

For a hypothetical festival, a weekend pass may allow one admission on each eligible day, while a VIP credential may also permit entry to a separate area. The system needs to know whether its usage limits apply across the whole event, per day or per zone.

A duplicate warning also needs context. It could indicate attempted fraud, an accidental immediate rescan or a staff member scanning the same attendee at two checkpoints. Staff should have an escalation workflow that does not require bypassing the validation rules casually.

When resale or transfer replaces a ticket credential, the older credential should cease to be accepted according to the platform's rules. A PDF screenshot from the original purchaser must not be treated as proof that the admission right still belongs to them.

## Can ticket scanning work offline?

**Some access-control systems can validate tickets against data stored on a device when the network is unavailable.** Offline scanning can keep gates operating during connectivity loss, but it introduces a synchronisation problem.

If two offline scanners each have an older copy of the admission records, they may both accept the same credential before either learns about the other scan. A later synchronisation can detect the conflict, but it cannot undo entry that has already occurred.

Offline readiness therefore involves more than a switch marked “offline mode.” Operators should understand how much ticket data is downloaded, how revoked or newly issued tickets are refreshed, how duplicate protection works across devices, and what happens after reconnection.

A venue using multiple entrances can reduce risk through operational zoning, clear sync procedures and supervision of exceptions. High-risk events may need stricter rules or alternative connectivity plans. The relevant trade-off is **continuity of admission versus freshness of the validation state**.

## What should venues test before doors open?

**Test the full ticket lifecycle, not just whether a scanner reads a QR code.** Run sample valid and invalid tickets through the actual equipment, supported ticket formats, assigned entrances and staff permissions.

Include tests for the wrong date, a refunded order, transfer or resale, repeated scans, VIP-zone access, sold-out conditions, lost connectivity and device handover between shifts. Check that customer-support teams can find an order without exposing unnecessary data and that staff understand when they are authorised to override a result.

Also plan for operational capacity. If a venue expects 3,000 people over 30 minutes, the average required throughput is **100 admissions per minute** across all open lanes, before allowing for peaks, bag searches and exceptions. That calculation does not imply each scanner can achieve any particular throughput; lane performance must be measured in realistic conditions.

**Reliable access control combines valid ticket data, rules, devices and trained staff.** A fast reader with stale entitlement data or unclear exception handling is not a complete admission solution.

## Related explanations

#### [How do offline ticket scanners work?](/distribution-access/how-do-offline-ticket-scanners-work)

Distribution & Access · Entry and access control

#### [How does venue access control manage restricted zones?](/distribution-access/how-does-venue-access-control-manage-restricted-zones)

Distribution & Access · Entry and access control

#### [What is event access control?](/distribution-access/what-is-event-access-control)

Distribution & Access · Entry and access control

[More in Distribution & Access →](/distribution-access)