Ten thousand phones, one job each
A full house arrives in forty minutes and every one of them has a phone. A code at the gate opens the ticket, one on the seat brings a beer without missing a song, and one at the stand shifts merch before the encore.
- Faster gates: the ticket opens on the phone before the queue moves
- Food and drink to the seat number, paid on the phone
- Set times, map and cloakroom that you update on the day
The codes that run a night
Each does one thing, each is dynamic, so the running order or the map changes on the day without a reprint.
Ticket / entry
Sends patrons to their ticket in the wallet app before they reach the gate. Fewer fumbled screenshots, faster lines.
Order to seat
Food and a drink to the seat number, paid on the phone. Runners come to them; nobody misses the support act queuing at the bar.
Merch
The full range and sizes on the phone while they queue, so they pay and collect instead of deciding at the counter.
Set times & map
Doors, support, headline, curfew and where the toilets are. Update it if the running order shifts on the day.
Cloakroom
Bag drop and a collection ticket on the phone, so there's no paper stub to lose on the floor.
Doors at 7
One night, gate to load-out.Where it goes, how big, what breaks it
Where venue codes fall over
We'd rather you printed two good codes than ten that nobody scans.
Champion — $39.99/mo
A venue runs codes across every gate, bar, seat zone and the merch stand, and the box office, bars and security all need in. Champion's larger code count, team sharing and custom domains fit a multi-space venue running a different show every night. A single small room might manage on Creator ($19.99).
Concert venues questions
The ones owners actually ask us before they print.
A dynamic code is just a redirect. The load sits on the page it points to, so host that on something that scales. In practice the bottleneck is mobile data in the room, not the code.