ServicesEvents · Event module
Every attendee badged before the doors open.
Export your registration list, pick a pass or badge layout, and generate print-ready sheets with a unique check-in QR for every attendee — rendered entirely in your browser.
Who this is for
1. Select a registration
2. Document type
4 × 6 in · no photo
3. Live design controls
Rendered in your browser in seconds
Built for how event teams actually work
A unique QR per attendee
Bound to the registration ID column, so every pass scans to the right person.
Runs in your browser
Passes render on your device; attendee photos are never uploaded to a server.
Lanyard-size sheets
Passes and badges laid out many-per-sheet with crop marks.
Pay per record, only when you order
No subscription required just to try it out.
What makes this workflow work
Colour-coded tiers
Drive the band colour and label from a tier column — VIP, Speaker, Crew, General.
Photo only where it's needed
Visitor badges and VIP cards carry a photo; general event passes don't ask for one.
Any registration export
Map the columns from your ticketing tool's .xlsx or .csv once, reuse every event.
PDF or ZIP export
One print-ready PDF of sheets, or a ZIP of individual passes.
What's included
| Capability | KanzioLabs |
|---|---|
| Badges for every attendee from a registration list | Built in |
| Unique check-in QR per attendee | Automatic |
| Lanyard-size sheet layout with crop marks | Built in |
| Cost to try | Free, pay per record |
See roughly what a batch would cost
Billed per record when you place the order. No subscription to start.
KanzioLabs cost
₹0
≈ ₹0.00 / record
Manual badge layout
₹3,600
≈ 20 staff hrs
Estimated saving
₹3,600
that batch
Illustrative only — assumes ~1.5 min of manual work per record at ₹180/hr. Your actual per-record rate is set in your dashboard.
Related document workflows
Ready to badge your next event in minutes?
Create a free account and generate your first batch of passes — no credit card required.
Questions event teams actually ask
Whatever column you bind it to — usually the registration or ticket ID, or a check-in URL built from it. Each pass gets its own code, generated at render time.