Sell the Seat Once, Admit the Guest Fast
Online ticket sales with seat or capacity control, QR codes validated at the gate even without a signal, domestic payment methods, and revenue that reaches accounting without a manual step.
Ticketing is deceptively simple until the day it matters. On an ordinary Tuesday any system works. The test is the hour before a popular event, when hundreds of people are buying at once and hundreds more are arriving at a gate where the mobile signal is poor because everyone is using it.
Two failures matter and they pull in opposite directions. Selling the same seat twice produces an argument at the door in front of other guests. Validating slowly produces a queue, and a queue at an event with a start time is a problem that grows by itself. A ticketing system has to prevent the first without causing the second.
iGlobal builds ticketing with the inventory logic used for stock: a seat or a capacity slot is reserved the instant it is selected, not when payment completes. At the gate, validation runs on the device and syncs afterwards, so admission never waits for a network that is exactly when it is weakest.
What goes wrong at the gate and in the books
Double selling happens when a seat is only committed at payment. Two buyers choose the same seat, both proceed, and one of them finds out at the door. Reserving at selection with a short expiry solves this completely, and it is the sort of detail that only shows up under load.
Duplicate entry is the other side. A screenshot of a QR code can be forwarded, so a code that is merely scanned and visually checked lets two people in on one ticket. Validation has to mark the code used at the moment of scan, and that mark has to be visible to every other device at the gate.
In the accounts the usual problem is timing. Money arrives from a payment gateway in a batch two days later, the ticket was sold on Friday, and nobody reconciles the two. Refunds and cancellations make it worse. The event finishes with a revenue number that takes a week to confirm.
- The same seat confirmed to two buyers
- A forwarded QR screenshot admitting a second person
- Validation stalling when the signal drops at the gate
- Event revenue confirmed a week after the event
What the ticketing solution covers
Seat maps and capacity slots
Reserved seating with a visual map, or capacity-based admission by time slot for venues without fixed seats, with the place held the moment it is selected.
Ticket types, pricing and promotions
Early bird, group, student and member rates, combo packages, discount codes and quantity limits per buyer, all enforced by rules rather than by a person checking.
Gate validation that works offline
A phone or scanner validates the code locally and marks it used immediately, synchronising with the other gate devices as connectivity allows. Admission never waits for the network.
Vietnamese payment methods
Domestic cards, e-wallets, bank transfer with automatic matching and cash at the counter, with the ticket issued the moment payment is confirmed.
Refunds, transfers and name changes
Policy-driven refunds with the accounting entry created automatically, and controlled transfer of a ticket to another name so resale does not become an unmanaged problem.
Live sales and attendance dashboard
Tickets sold by type and channel, revenue, and actual attendance against tickets issued as people arrive, available during the event rather than afterwards.
How we deliver it
-
1
Event model and policy design 1 to 2 weeks
Seat map or capacity model, ticket types, pricing rules and the refund policy written down precisely, because an ambiguous refund rule becomes an argument during the event.
-
2
Build and payment integration 3 to 4 weeks
Sales pages, seat selection, payment gateways and ticket delivery by email and Zalo, tested end to end with real low-value transactions.
-
3
Gate rehearsal 1 week
We test the scanning devices at the actual gate, deliberately with the network disabled, and measure seconds per admission. A gate that takes four seconds per guest cannot clear a thousand people in time and it is better to learn that in rehearsal.
-
4
First event with us present 1 event
We are on site for the first sale peak and the first gate opening, and the revenue reconciliation is completed together the following day.
Who this is for
- Theatres, cinemas and venues with reserved seating
- Tourist attractions and parks selling timed admission
- Conference and training organisers with paid registration
- Sports facilities and clubs selling day passes
Why iGlobal
The seat is held at selection, not at payment
This single design decision removes the double sale entirely. It is the difference between a system that works on a quiet day and one that works on the day that matters.
We rehearse the gate with the network off
Offline validation is tested at your venue before your first event, with admission time measured per guest. A capability nobody has exercised is a claim.
Revenue lands in the accounts by itself
Sales, gateway settlements and refunds post automatically and reconcile against the bank, so the event closes financially within days rather than weeks.
The best balance of cost, quality, and service
No commission per ticket sold, which at volume is the difference that matters most, and the customer data belongs to you rather than to a ticketing platform.
Three ways to do this, compared
| What you are comparing | By hand, on spreadsheets | Off-the-shelf software | With iGlobal |
|---|---|---|---|
| Selling the same seat twice | Two sellers working from one seating chart | Prevented at payment, which is already too late | The seat is held the moment the buyer chooses it |
| Admitting guests when the signal is weak | A printed guest list and a pen | Scanning stops and the queue keeps growing | Validated on the device itself, synced afterwards |
| Knowing what the event earned | Counted up about a week later | Sales are known; settlements and refunds are not | Sales, settlements and refunds reconciled within days |
| Cost across three years | Hidden inside salaries, so it never appears in a budget | A predictable licence per user, plus the work it cannot do | Quoted per phase and reviewed with you before each one starts |
| Who holds your data | Scattered across files, inboxes and personal phones | On the vendor platform, exported on the vendor's terms | Your own database, exportable in full whenever you ask |
| When something breaks | The person who built the file, if they still work here | A ticket queue, often in another language and time zone | A named engineer in Hanoi you can reach the same working day |
The two middle columns describe approaches that genuinely work for some companies. Where they win, they win, and we have tried to say so.
What changes after the first event
The visible change is the gate. Admission measured in about a second per guest means a thousand people clear in a manageable time, and the staff at the door stop being the people who absorb everyone's frustration.
The commercial change is that you learn what actually sold. Ticket type, channel, time of purchase relative to the event and no-show rate are all recorded, and after two or three events the pricing and release schedule can be set from evidence instead of from last year's plan.
The financial change is speed of closing. Because sales, gateway settlements and refunds post themselves, the event's profit and loss is available within days. For organisers running a series of events, knowing the result of the last one before planning the next is worth more than it sounds.
- Admission at roughly a second per guest, signal or not
- No seat ever confirmed to two buyers
- Event profit and loss available within days
- Buyer contact data kept in your own database
Frequently asked questions
What happens if the internet fails at the gate?
Validation continues. Each device holds the valid code list for the event and marks codes used locally, then synchronises when connectivity returns. The one genuine risk is the same ticket presented at two different offline gates simultaneously, which we handle by assigning ticket ranges per gate when we expect poor coverage.
Can we sell tickets at the door as well as online?
Yes, from the same inventory, so the counter cannot sell a seat the website has already taken. Counter sales accept cash and card and print or send the same QR ticket, which keeps the attendance figures complete rather than split across two systems.
How do you prevent ticket sharing by screenshot?
The code is marked used at the first successful scan, so a forwarded screenshot is rejected at the gate with a clear message telling the staff member when and at which gate it was already used. For high value events we can also require a name on the ticket and spot check identity, but the single use mark handles the great majority.
Can it handle a venue with no fixed seats?
Yes, through capacity by time slot, which is the right model for attractions, museums, swimming pools and exhibitions. Instead of a seat the guest buys a slot, the slot has a maximum, and arrival spread is controlled by how many slots you open per hour.
Who owns the customer data?
You do. Buyer contact details sit in your own database and can be used for your next event, which is a material difference from selling through a platform where the audience belongs to the platform. For organisers who run events regularly this often matters more than the commission saving.
Related solutions
Talk to a senior consultant, not a call centre
Tell us what you are trying to fix and we will tell you honestly whether we are the right team for it.