Create check-in lists
In the tickets area, define the lists the event needs and choose which ticket types each one accepts.
Check-in & access
QR check-in and check-out, several lists per event with their own allowed ticket types, and scanner accounts you can hand out and take back in seconds.
In short
Check-in and check-out with QR codes
Several check-in lists per event, validated server-side
Temporary scanner accounts, scoped and revocable
Check-in & access
Answers captured during a scan are stored server-side against that specific scan event, and check-in CSV exports add a column per field key. What the door team recorded is usable the next morning without a transcription step.
How it works
01 02 Add capture fields
Give a list its own extra fields so the scanner asks for exactly what this entrance has to record.
03 Hand out scanner access
Issue temporary scanner accounts, scoped to the event or to individual lists, and revoke them when the shift ends.
04 Scan and export
Check guests in and out, watch the live counts per list and export the CSV when the event closes.
Capabilities
- 01
Multiple check-in lists
An event can run several active lists, each with its own ordering, description and set of allowed ticket types — press, VIP and general admission stop colliding.
- 02
Server-side validation
The scanner sends the check-in list identifier and the backend validates event assignment, active state and permitted ticket types before accepting the scan.
- 03
Temporary scanner accounts
Time- and context-limited scanner access for staff without a full account, restrictable to specific check-in lists rather than the whole event.
- 04
On-site data capture
Each list can define its own extra fields — text, textarea, select and checkbox — that the scanner asks for right after a successful scan.
- 05
Buyer answers at the door
Buyer questions marked as scanner-visible show up with the scan result, which is what makes dietary or age checks workable in a queue.
- 06
Statistics and CSV export
Per list you get scan counts, currently checked-in tickets and a CSV export with dynamic columns for every captured field.
Specifications
- Scan operations
- Check-in, check-out and read-only ticket lookup
- Lists per event
- Multiple active lists with ordering, description and allowed ticket types
- Extra field types
- TEXT, TEXTAREA, SELECT, CHECKBOX
- Temporary access
- Scanner accounts scoped to an event or to specific check-in lists
- Reporting
- Per-list scan statistics and CSV export with dynamic field columns
Use cases
Festivals — Learn more
Several gates, wristband exchange and separate lists for crew, press and day tickets.
Stadiums — Learn more
High-throughput turnstile scanning where a wrong ticket type must be rejected at the gate, not later.
Clubs — Learn more
Door staff on temporary accounts, age verification at the scan and a clean guest count at closing.
FAQ
- Yes. An event can have several active check-in lists, each with its own ordering, description and allowed ticket types, and each with its own scan statistics and CSV export.
- No. Temporary scanner accounts provide time- and context-limited access without a full account, and they can be restricted to specific check-in lists instead of the whole event.
- Yes. Each check-in list can define its own extra fields, and the scanner asks for them immediately after a successful scan. The answers are stored server-side against that scan event.
- No. Staff can inspect ticket information without changing its status; check-in and check-out are explicit operations.
Set up your check-in lists, hand out scanner access and scan your first ticket today.