Unique serialised ticket codes generated in bulk, an offline-capable check-in scanner for the gate, and session codes that repoint as the programme changes.
Bulk ticket generation and the check-in scanner start at Lite. Serialised codes are audited as a batch before export.
ONE LANYARD, FOUR JOBS
EVENTSTicket
160 × 60
Ticket160 × 60
Ticket4/4Programme4/4Venue WiFi4/4Feedback4/4
Ticket codes are scanned once, fast, in bad light, by a volunteer holding a phone. They are generated at EC-Q and audited as a batch so not one of them fails at the gate.
WHAT YOU GET
The gate is the hard part
A ticket code that fails is a queue. Everything here is built around that single failure mode.
Serialised unique tickets
Sequential or random unique codes with collision checking, generated to 100,000 per job, each carrying its own reference for reconciliation.
Batch scanability audit
Every ticket in the run is scored before export and the job summary reports the distribution. Failures are flagged and reissued, not discovered at the door.
Offline-capable check-in
The gate scanner works without a connection and reconciles when it regains one — because venue WiFi fails exactly when the queue is longest.
One-time validity
A ticket marked used cannot be redeemed twice, and duplicate attempts are surfaced to the person on the gate with the original scan time.
Programme that changes
Session and stage codes are dynamic, so a schedule change or a room move updates every printed sign and lanyard card instantly.
Post-event follow-up
Repoint the ticket code after the event to a recording, a feedback form or next year’s sale. The printed ticket keeps working as a channel.
Tickets outlive the subscription
Codes printed for an event keep working after the event, and after the plan ends. What stops is editing and analytics — never the scan at the door.
Every code in the batch is checked
Quiet zone, module count and contrast are measured per code rather than per batch, so one bad serial is found before ten thousand wristbands are printed.
SETUP
From attendee list to gate
A single bulk job produces the whole run.
STEP 01
Upload the attendee list
Or specify a quantity for unnamed tickets. Serialisation and unique slugs are handled for you.
STEP 02
Design once
One template applies across every ticket, with per-row variables for name, seat or tier.
STEP 03
Audit the batch
Every code scored, distribution reported. Nothing exports until the run passes.
STEP 04
Brief the gate
Volunteers open the check-in scanner on any phone. Offline mode is the default, not a fallback.
PRINT PACK
Formats made for this room
Every format is rendered at its own minimum size and decode-tested before export, so a code that fits the layout is a code that scans in the room.
The check-in scanner is offline-capable by design. It validates against a downloaded manifest and reconciles when connectivity returns, so a dead uplink slows nothing.
Can a ticket be used twice?
No. Once redeemed it is marked used, and a second attempt shows the volunteer when and where it was first scanned so they can handle it on the spot.
How small can a ticket code be?
Tickets are scanned at close range, so 20mm is comfortable. We generate them at EC-Q rather than EC-M because a ticket lives in a pocket and gets creased.
Can I reuse the codes for next year?
Repoint them rather than reissue. After the event, ticket codes make good channels to recordings, feedback or early-bird sales for the next edition.
Do attendees need an app?
No. Attendees just show the code; only the gate uses the scanner, and that runs in a browser on any phone.
We’d like to count visits with Google Analytics and see where pages confuse people with Microsoft Clarity. Both set cookies, and nothing loads until you choose. Anything you type stays hidden from recordings.
Change it any time from “Cookie settings” at the foot of every page. Cookie policy