QR code check-in for events looks like a door problem: guests arrive, staff scan a code, the line moves. In practice the door is the last step of a chain that starts with the registration form. If the form collects one email for a group of five, if two people end up holding the same seat, or if the counters work from separate lists, the scanner only shows those mistakes in front of the queue.
This guide is for teams that run conferences, forums, exhibitions, training days and corporate or innovation events. It covers the workflow from form to door, the questions to ask when you choose an event registration and check-in system, and how we handle each step in EBMS, the event registration and check-in platform that MOHA built and used for Vietnam Innovation Day 2026.
Why the door depends on the form
A QR code is a container. The standard behind it, ISO/IEC 18004, defines how data is encoded, how big the symbol can be and how errors are corrected. It says nothing about whether the person holding the code is the person you approved, whether their seat is still theirs, or whether this session accepts their ticket type. Those answers come from your registration data.
Almost any phone can scan a QR code, so scanning is rarely what goes wrong. What matters is whether every code points to one named guest, one ticket type and one seat, and whether every scanning device reads and writes the same guest list.
Three things break QR check-in more often than the scanner does:
- Shared codes: one person registers a group, receives one code, and five people try to enter on it.
- Double-booked seats: the seat plan lives in a spreadsheet, two guests are told they have C7, and the conflict surfaces in the hall.
- Split lists: counter 1 and counter 2 each work from their own export, so a guest can be checked in twice and the organizer cannot tell who has arrived.
All three start upstream, in registration and seating. Fix them there and the door becomes the easy part.
The workflow from registration form to the door
1. Set up the event before you open the form
Decide the structure first: offline or online, one session or several days, which time zone, and whether this event is part of a series. In EBMS you also set the date when registration opens, so the form goes live on schedule rather than when someone remembers to publish it. Event content can be in Vietnamese, English, Korean, Chinese and Japanese, which matters when international delegates register alongside local ones.

2. Registration: no forced accounts, one place per named guest
Asking guests to create an account before they can register adds a password to something they will do once. EBMS does not require one. Guests choose a ticket and a seat, fill in their details and receive the ticket by email.
Group registration is where shared codes come from, so set it up on purpose. In EBMS the organizer can require the name, phone, email and organization of every person in a group. Each place then belongs to one named guest, and each guest gets their own QR code. The person who filled in the form does not hold everyone's tickets.
Two other registration features save work later:
- You can put your own survey questions in the form, or ask for a profile at sign-up. For customer conferences, trade events and product launches, you learn who is coming before the day, and the answers stay with the guest list for the next event.
- You can turn on approval. Every registration then waits in a review queue until you accept it, which suits government conferences and invitation-only forums.
3. Seating: draw the hall once, lock every booked seat
If your event has assigned seats, the seat map is part of registration, not a separate document. In EBMS you design the map yourself: zones with names and codes, rows, seats per row, and colors by tier. If you do not need assigned seats, the booking page can show a photo of the hall instead, or no map at all.
The rules that prevent conflicts are simple. Capacity comes from the seats on the map, so you never sell more places than the hall holds. A booked seat is locked, so no seat is sold twice. If a guest has to move at the last minute, you move them on the map and the ticket follows the seat code. Maps can be saved as hall templates for later events, and one event can use several halls.
4. Tickets: one code per guest, structured so staff can read it
In EBMS each ticket type (VIP, delegate, general, or whatever you name it) is tied to the zones it covers. When the event is published, EBMS generates the ticket stock from each zone's capacity. You can also import the stock from a file. A 48-seat VIP zone becomes 48 VIP tickets.
Every guest gets their own QR code, and the ticket code follows a type-zone-number structure, so a staff member can read "VIP" or "DB" at a glance without scanning anything. Tickets can be free or paid, with price and VAT set per type, and you can download the whole ticket stock.
If you print codes on badges, think about wear. Denso Wave, the company that created the QR code, explains its four error correction levels: level M is the usual choice, while levels Q and H suit codes that may get dirty or damaged. A code shown on a phone screen faces different problems, mostly screen brightness and cracked glass, which is why a manual fallback matters at the door.
5. Check-in: sessions, several counters, one dataset
A one-day conference often has more than one door moment: morning registration, an afternoon session, a dinner. In EBMS you split the day into check-in sessions, and each session sets which ticket types it accepts. A dinner session can accept VIP tickets only, while the afternoon accepts every ticket.
Guests get in three ways:
- Staff scan the code on the guest's phone at a counter.
- Guests scan a QR code placed at the door or on a kiosk themselves, with no staff needed.
- Staff look the guest up and confirm by hand when the guest forgot the code or their phone.
Several counters can work at once. Every scan lands in the same guest list and the result updates on every device, so the door and the organizer see the same numbers. That shared dataset is what stops double check-ins and lets the event lead answer "how many delegates are in the hall?" without calling each counter.

6. Reports: attendance figures while guests arrive
Scanning also leaves data behind. EBMS groups reports into attendance, revenue, partners and operations. Attendance covers total registrations, check-ins by session and by counter, the check-in rate (checked in divided by registered) and no-shows. You can filter by event and date range, view by day, week or month, compare several events side by side and export to Excel for your own report or for leadership.

What to check when choosing an event registration and check-in system
Feature lists are long and look alike. These questions say more about how a system behaves on the day, and we give the EBMS answer to each.
- Do guests need an account to register? An account is friction for a one-time sign-up. EBMS: no account; guests receive the ticket by email.
- Can one person register a group, with a separate code for each guest? EBMS: yes, with name, phone, email and organization per person if you require it, and one QR code per guest.
- Is the seat map part of booking, and are booked seats locked? EBMS: you design the map or use a hall photo; capacity comes from the map; booked seats are locked.
- Can several counters and self-scan points work at once on one guest list? EBMS: yes, counters, self-scan and manual lookup all write to the same dataset in sync.
- Can check-in rules change by session? EBMS: each session sets the ticket types it accepts.
- What do the reports show, and can you take the data out? EBMS: attendance, revenue, partners and operations, with event comparison and Excel export, plus a download of the full ticket stock.
Ask one more: how payment works today, as opposed to what is planned. Our answer is below.
Example: Vietnam Innovation Day 2026 on EBMS
Vietnam Innovation Day 2026 had many ways to take part, and each needed its own form, rules and guest list. On EBMS, each one ran as a separate event: the opening ceremony, the forum, booths, sponsorship, accommodation, private meetings and company visits. The organizing team approved, followed and reported on all of them in one place.
The system recorded 237 registrations across 8 registration forms (figures from EBMS on 08/10/2026).
The structure is what other organizers can reuse. A programme like this is really several events under one name. Sponsors, booth exhibitors and delegates booking accommodation answer different questions and need different approvals. Running each as its own event keeps the forms short and the approval queues separate, while the reports can still compare them side by side.

Run your next event on EBMS
Registration, seat maps, QR tickets, check-in at several counters and reports in one system.
Where EBMS stops today
You should know the current limits before the event, not during it.
EBMS supports paid tickets with price and VAT, but payments are currently confirmed by bank transfer. An online payment gateway is on the roadmap. For free and invitation-only events this rarely matters. For public paid events with many individual buyers, build the transfer confirmation step into your timeline.
There is no mobile app for organizers yet. Organizers and check-in staff use EBMS in the browser on phones and tablets, and an organizer app is on the roadmap. We do not give dates for either.
Partner services: a second source of revenue
Some events bring in partners who want to reach attendees. EBMS lets partners list services that go with the event. The platform approves them, so only approved services appear. Partners then run campaigns to the event's registrants and manage their promotion budget from a wallet, with receipts and campaign reports. The organizer gets another source of income and keeps control of which partners appear.
Running your first event on EBMS
We work with your team from the first conversation to the report after the event, in five steps:
- Discovery: your needs, event types, scale, halls and how you want to check guests in.
- Setup: your organization, hall templates and a sample event.
- Training for the organizing team and the check-in staff.
- A dry run: test registrations, print tickets and rehearse check-in.
- Event day: support on the day and a report handed over afterwards.
Protect the dry run in your schedule. Rehearsing check-in with the real ticket stock and the real devices is how you find a counter without a charged tablet or a session that rejects the wrong ticket type.
Why MOHA can write this
MOHA builds EBMS and ran Vietnam Innovation Day 2026 on it. Seat locking and multi-counter sync are the same problems we deal with in booking software; we covered the engineering side in scalable ticket booking system architecture and in our own MOHA Booking Solution for salons, clinics and car washes.
See EBMS on your next event
If you run conferences, forums, exhibitions or training days and want registration, seating, QR tickets, check-in and reports in one system, see the full feature list on the EBMS product page, then book a demo of EBMS. We can run it on a sample event, or write to [email protected] to discuss your event.


