Custom registration fields
Text, email, number, select, multi-select, and checkbox fields. Mark them required or optional. Answers are validated server-side and land in the Excel export.
Publish a branded event page in minutes. Attendees get a QR ticket by email or WhatsApp, sent from the event's own address and written in the event's own timezone. Door staff scan from any browser, or admit delegates straight from the list.
QR Event Pass covers the whole path: the page an attendee lands on, the ticket they receive, and the scan that lets them in. Bring a delegate spreadsheet when you have one; skip it when you do not.
Title, cover, venue with a map, an About section in Markdown, a timezone, sponsors, and a page theme. Choose QR tickets, a delegate list, or both. Preview the public page before it goes live.
A hosted page at /events/your-slug with your own custom fields. Approve registrations by hand if you want to, or let them through. Capacity is enforced atomically, so nobody takes a seat that is not there.
Each attendee gets a ticket page and a ticket image with their QR, attendee number, and sponsor logos, by email, WhatsApp, or both. Failed sends land in a retry outbox instead of disappearing.
Door staff open the scanner in any browser. The QR token is validated on the server and admission is atomic. No QR? Search the name and admit from the list.
Text, email, number, select, multi-select, and checkbox fields. Mark them required or optional. Answers are validated server-side and land in the Excel export.
One QR per attendee, or a single group QR that admits a party. Staff can admit part of a party at the gate when only some of them show up.
Each ticket carries a compact random token that means nothing on its own. The scanner checks it against the server, so a guessed or copied code gets nowhere. Older signed tickets keep working.
Every registration gets a sequential number for its event, like 001. It is printed on the ticket page and image, searchable in the attendee list, included in exports, and used by prize draws.
Registration closes by itself when the guest capacity is reached. The limit holds atomically across public, spot, approved, and delegate entries. The event page stays up, marked full.
Define a main entrance and any number of secondary gates. Each check-in records where it happened, and the dashboard shows admitted counts per area.
Close registration a week before the doors open. The event page stays public with its details until you unpublish it, so nobody hits a dead link.
A browser ticket page and a downloadable ticket image, with an add-to-calendar link, venue details in the event timezone, the attendee number, and sponsor logos.
Excel (.xlsx) export of registrations with attendee numbers, answers, source, and timestamps in the event timezone. An admin view shows every delivery job, its attempts, and its last error.
Conferences with an invited delegate list, open events with public registration, and everything in between. Pick the mode per event; the scanner handles whichever you choose.
Attendees register on the public page and receive a QR ticket. The classic flow.
No public registration and no QR. Import the invited list and admit people by name at the door.
Invited delegates come in from the list, everyone else registers for a QR. One gate handles both.
Download the Excel template, fill in your delegates, and upload it. Rows are checked before they are imported, and imports count against capacity like any other entry.
Staff search by name, email, or attendee number and admit straight from the result. Useful for delegates, and for anyone whose phone died in the queue.
When a delegate arrives with fewer or more guests than listed, staff set how many to admit within the allowed party size, and the count is recorded.
For invite-only and vetted events, registrations can wait for an organizer. A pending registration has no ticket and no QR, so there is nothing to forward or screenshot until you say yes.
Attendee sees a pending confirmation
No ticket, no QR yet
Ticket delivered as normal
Turn approval on for invite-only or vetted events. Leave it off and registrations go straight through.
Review a registration and its answers, then approve it on its own, or select a batch and approve them together.
A declined registration gets a notification, so nobody turns up expecting a ticket that was never coming.
Approval covers registrations from the public page and from the spot-registration poster at the venue.
Not everyone registers in advance. Generate a spot-registration poster from the dashboard, print it, and stand it at the entrance. Walk-ins scan it, fill the same form on their own phone, and receive the same QR ticket. No queue at a laptop, no staff typing names.
The spot link opens when the event starts and closes when it ends. Outside that window it does not resolve, so a photographed poster is useless afterwards.
Spot entries are stored with a spot_registration source and arrive labelled in the Excel export, so walk-in volume is measurable against pre-registration.
Custom fields, capacity, and approval all apply. Once through, the walk-in receives the same QR ticket through the same channels.
Print the poster straight from the browser, or download just the QR PNG to drop into signage you have already designed.
Run the closing raffle from the same dashboard as the gate. Entries come from your attendee list, winners are picked on the server, and the whole thing goes up on the big screen.
Only attendees who have checked in, or everyone registered. Entries are identified by attendee number.
The winner is drawn at random and recorded on the server before the wheel stops. The animation shows the result; it does not choose it.
List the prizes with quantities, and credit a sponsor on each one. The draw works down the lineup.
Every winner is logged. Past winners are left out of later spins. Undo a draw or respin when a winner is not in the room.
Full-screen presentation mode with sound, ready to put on the projector at the closing session.
Give sponsors real placement, not a footnote. Their logos travel with the event everywhere it appears.
Set the look of the public page without a designer, and watch it change as you pick.
Qatar Outlet Exhibition
Fri 14 Nov · 18:00 Asia/Qatar
A ticket email is transactional mail someone is waiting for. It should carry the event's name and address, not a platform's.
Tickets are not sent from a generic no-reply. The display name is the event name and the from address is derived from the event slug on a verified sending domain.
Qatar Outlet Exhibition <qatar-outlet-2026@your-sending-domain>Pick the channels per event. WhatsApp goes out on an approved utility template; email carries the ticket card and the QR. Providers are managed centrally, not per organizer.
Each ticket is a delivery job with attempt counts, the last error, and a next-attempt time. Nothing is dropped silently, and any job can be retried by hand.
Every event carries its own timezone. Times are stored in UTC and rendered in the event's zone on every surface, so a Doha event does not shift because the organizer created it from Chennai or because a server ran in another region.
| Asia/Qatar | UTC+03:00 |
| Asia/Dubai | UTC+04:00 |
| Asia/Kolkata | UTC+05:30 |
| UTC | UTC+00:00 |
The registration window and the event dates are separate fields, and both are read in this zone. Need another region? It is a one-line addition.
Any phone with a camera. Staff open the scanner page, pick a scan area, and start admitting. No app store, no device provisioning.
The token is checked on the server, then admission happens in one database statement. A ticket scanned twice at two gates is admitted once.
Delegates and anyone without their ticket are found by name, email, or attendee number and admitted from the list.
Create check-in staff accounts scoped to the scanner. Live admitted counts per area, no access to event settings or exports.
Organizers request an account and a platform admin approves it. Each organizer gets an event limit and a capacity limit set by the admin.
No. They register in the browser and receive a ticket page and ticket image. Door staff scan with the browser camera. Nothing to install on either side.
Yes. Import a delegate list from the Excel template and admit people by name at the door, or run a hybrid event where the list and QR tickets work side by side.
Check-in staff accounts are scoped to the scanner only. They can find and admit people and see admitted counts; they cannot reach event settings or the exports.
Registration closes automatically at the guest capacity, across every entry route. The public page stays online and shows that the event is full.
The event page stays public until you unpublish it. Registration closes on its own schedule, when the registration window ends or capacity is reached.
Organizer accounts are approved by hand so we can size capacity with you. Tell us about the event and we will get you set up.