Research basis
Desk-based product assessment of the published Android documentation. No hands-on testing, paid account access or live-event trial was performed.
What the product is
pretixSCAN is the check-in application for events managed in pretix. The documentation lists Android, iOS and desktop availability; this explainer uses the current Android guide. It documents ticket validation, manual participant search, badge printing and attendance statistics. It is distinct from pretixPOS for sales, pretixPRINT for printing and pretixLEAD for lead acquisition. This is documentation-based coverage, not a hands-on review.
How offline operation works
pretix describes asynchronous scanning as using a local copy of attendee data and synchronising with the server when a connection becomes available. The operational advantage is that the scanner need not stop immediately when the network drops. The trade-off is freshness: another entrance’s latest scan may not yet be known to an offline device. An offline capability should not be described as a guarantee of real-time duplicate prevention across disconnected entrances.
Choose the security profile deliberately
The Android guide distinguishes a full pretixSCAN profile from online-only and kiosk profiles that do not synchronise order data. Offline scanning does not work with the no-order-sync profiles. That is a meaningful choice between local-data availability and keeping attendee records off a device, not simply an on/off preference for convenience. Confirm the exact profile used on each device with the person managing the organiser account.
Plan the exception route
An attendee may arrive without a ticket, with a changed booking or with a ticket already marked used. The guide documents manual search, but a kiosk or restricted profile can limit what the operator can access. Design a separate staffed route for exceptions. Decide what staff may override, who authorises it and how the decision will be recorded. Do not grant every entrance device broad account access just to make one unusual case easier.
What to demonstrate before purchase
Use the intended handset, network and printer. Synchronise a test event, disconnect the device, scan a ticket and then reconnect. Try the same test ticket at another isolated device to understand conflict handling. Check what happens to a booking created after the device went offline. Confirm how local data is removed after the event. These are proposed checks, not results of ETN testing.
Availability and limits
The Android guide specifies Android 7 or newer at the time checked, but device support can change. Hardware rental, printing and the underlying pretix edition are separate purchasing questions. Ask for a documented bill of materials and compatible versions rather than assuming an app download includes the whole entrance setup. See the linked official guide for current prerequisites.
Sources and research basis
Sources checked 2026-10-17. Supplier capabilities and venue specifications are attributed to their published documentation. No first-hand test or visit is implied.