Skip to content
AIDC GORequest a quote

Integration & Deployment

Handheld Ticket Scanners for Event Entry: Check-in Rules, Offline Use and Re-entry

By AIDC GO · Published Sep 15, 2026 · Updated Oct 27, 2026 · 2 min read

On this page

Short answer: A ticket scan captures an identifier; the event application decides whether the person may enter. Test entrance rules, current ticket state and offline synchronization together. A readable QR code alone cannot establish valid admission or prevent duplicate entry.

Define the admission result before testing hardware

Record the event, session, entrance and check-in list used by each device. Specify valid entry, wrong session, canceled ticket, already-used ticket and re-entry outcomes. The operator should distinguish these results without relying only on color.

An illustrative conference may admit workshop participants at one entrance and the wider event list at another. A readable main-event ticket can correctly fail the workshop rule. Use controlled test identities and keep the captured value together with the active event and returned status.

Make the offline policy explicit

Ask what ticket data is stored locally, when it was last synchronized and how the application decides when disconnected. The pretixSCAN Android documentation describes a local database and warns that disconnected devices can admit the same ticket before they synchronize.

Define the required data refresh before opening an entrance, the operating rule during a long outage and the conflict-review process afterward. Replacing the scanner cannot resolve stale ticket state held by another disconnected device.

Follow a ticket through exceptions

In a controlled example, device A accepts a ticket online. Device B later loses connectivity before receiving that update and sees the same ticket. Record each device’s last synchronization, local decision and later server result. This explains the duplicate risk without treating either decode as a hardware fault.

For re-entry, test the application’s exit and return rules. If it requires a recorded exit, a second entry without that event should not be treated as a failed scan. Keep rule configuration and synchronization evidence with each result.

Evaluate the complete entrance task

Test representative printed and displayed codes under the actual presentation conditions. Repeat valid, canceled, already-used and wrong-session tickets through the same application path. Include a double scan, entrance change, app backgrounding and connectivity change during submission.

Send ticket media, symbologies, application and OS versions, entrance rules, offline policy and operator feedback requirements with your inquiry. Ask the software provider for supported capture, synchronization and conflict handling. The pilot checklist can extend the test into charging, device assignment and shift handover.

Device options for this task

Compare AIDC GO HX-21 and AIDC GO HX-24 as Android PDA Barcode Scanners. Evaluate representative paper and screen tickets with the selected configuration and the event application’s documented input method.

Devices for this workflow

Related guides

Tell us about your project

Send the application, operating system and where the device will be used.

Request a quote