§ 00 · QR EVENT PASS

Registration, QR tickets, and check-in that hold up at the door.

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.

Under 5 min
Event to live page
2 channels
Email and WhatsApp
3 event modes
QR, list, or hybrid
Per-event TZ
Never the server clock
§ 01 · THE FLOW

Four moves, start to gate

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.

  1. 01

    Publish the event

    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.

  2. 02

    Collect registrations

    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.

  3. 03

    Deliver the ticket

    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.

  4. 04

    Scan at the door

    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.

§ 02 · WHAT IS INSIDE

The parts you would otherwise build yourself

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.

Groups and party size

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.

Server-validated QR tokens

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.

Attendee numbers

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.

Hard capacity

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.

Scan areas

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.

Registration window vs event dates

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 complete ticket

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 exports and delivery ops

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.

§ 03 · NEW · EVENT MODES

QR tickets, a delegate list, or both at one gate.

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.

  • QR

    QR-ticket events

    Attendees register on the public page and receive a QR ticket. The classic flow.

  • LIST

    Delegate-list events

    No public registration and no QR. Import the invited list and admit people by name at the door.

  • HYBRID

    QR plus delegate list

    Invited delegates come in from the list, everyone else registers for a QR. One gate handles both.

Excel template and import

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.

Search and admit without a QR

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.

Adjustable party admission

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.

§ 04 · NEW · APPROVALS

Decide who gets a ticket before one exists

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.

  1. 01

    Submitted

    Attendee sees a pending confirmation

  2. 02

    Pending

    No ticket, no QR yet

  3. 03

    Approved

    Ticket delivered as normal

Optional, per event

Turn approval on for invite-only or vetted events. Leave it off and registrations go straight through.

One at a time or in bulk

Review a registration and its answers, then approve it on its own, or select a batch and approve them together.

Declines are told, not ghosted

A declined registration gets a notification, so nobody turns up expecting a ticket that was never coming.

Public and spot alike

Approval covers registrations from the public page and from the spot-registration poster at the venue.

§ 05 · SPOT REGISTRATION

Walk-ins register themselves. From a printed QR.

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.

  • Only live during the event

    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.

  • Tagged at the source

    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.

  • Same rules, same ticket

    Custom fields, capacity, and approval all apply. Once through, the walk-in receives the same QR ticket through the same channels.

  • Print or download

    Print the poster straight from the browser, or download just the QR PNG to drop into signage you have already designed.

§ 06 · NEW · PRIZE DRAWS

A lucky draw nobody can argue with.

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.

Pick who is in the draw

Only attendees who have checked in, or everyone registered. Entries are identified by attendee number.

Winner decided on the server

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.

A prize lineup

List the prizes with quantities, and credit a sponsor on each one. The draw works down the lineup.

History, undo, respin

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.

Made for the big screen

Full-screen presentation mode with sound, ready to put on the projector at the closing session.

§ 07 · NEW · SPONSORS AND THEMES

The page, the ticket, and the draw all look like your event.

Sponsors

Give sponsors real placement, not a footnote. Their logos travel with the event everywhere it appears.

  • Up to 12 sponsor logos per event
  • A sponsor strip below the event banner
  • Logos printed inside every ticket image
  • Sponsors credited on prizes in the draw
  • Reorder, replace, or remove after the event is created

Event-page themes

Set the look of the public page without a designer, and watch it change as you pick.

  • Solid, gradient, animated, or GIF backgrounds
  • Accent colour and light or dark display
  • A choice of headline fonts
  • A live preview while the organizer edits
  • The same theme carried onto the ticket page
Ticket preview

Qatar Outlet Exhibition

Fri 14 Nov · 18:00 Asia/Qatar

#001
Add to calendarSave image
§ 08 · DELIVERY

Tickets that look like they came from the event

A ticket email is transactional mail someone is waiting for. It should carry the event's name and address, not a platform's.

Per-event sender identity

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>

Email, WhatsApp, or both

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.

A retry outbox, not fire and forget

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.

§ 09 · TIMEZONES

A 7 PM event reads 7 PM everywhere.

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.

Rendered in the event timezone
  • The public event page and the registration window notice
  • The ticket page, the ticket image, and the calendar link
  • The email and WhatsApp message body
  • The organizer dashboard, event list, and scanner
  • The Excel export timestamps
Supported event timezones
Asia/QatarUTC+03:00
Asia/DubaiUTC+04:00
Asia/KolkataUTC+05:30
UTCUTC+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.

§ 10 · CHECK-IN

The gate is the part that has to not break

Browser scanner

Any phone with a camera. Staff open the scanner page, pick a scan area, and start admitting. No app store, no device provisioning.

Validated, then admitted atomically

The token is checked on the server, then admission happens in one database statement. A ticket scanned twice at two gates is admitted once.

Search when there is no QR

Delegates and anyone without their ticket are found by name, email, or attendee number and admitted from the list.

Staff who only see the gate

Create check-in staff accounts scoped to the scanner. Live admitted counts per area, no access to event settings or exports.

§ 11 · QUESTIONS

Before you ask

Who can create events?

Organizers request an account and a platform admin approves it. Each organizer gets an event limit and a capacity limit set by the admin.

Do attendees need an app?

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.

Can I run an event without QR tickets?

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.

Can door staff see attendee data?

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.

What happens when the event is full?

Registration closes automatically at the guest capacity, across every entry route. The public page stays online and shows that the event is full.

What happens after the event ends?

The event page stays public until you unpublish it. Registration closes on its own schedule, when the registration window ends or capacity is reached.

§ 12 · GET STARTED

Run your next event on QR Event Pass.

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.