The queue moves before the gate
The queue at the gate is where you lose people on a hot day. A code on the approach sells the ticket before they get there, and the same codes turn every viewpoint sign into the story behind the view.
- Tickets bought on the approach, so the gate queue keeps moving
- Every viewpoint sign carrying the story, in the languages you need
- Feedback caught on the way out, while the visit's fresh
The codes a site prints
One job each, and every one dynamic, so a timed session or a re-signed trail never means a reprint.
Buy / skip the queue
Sends the approach queue to mobile ticketing before the turnstile. Repoint it at the day's timed sessions as they fill.
Viewpoint interpretation
The story of what they're looking at, with audio and other languages behind one code. One per lookout, so it's about the view in front of them.
Wayfinding
The site map, the loop times and where the toilets are: the thing everyone asks staff at the gate. Update the file when a path closes.
Feedback
A short form or your review page. Put it at the exit and the café, not the entrance, where there's nothing to say yet.
A hot Saturday, 11am
What the codes do from the car park to the way out.Where it goes, how big, what breaks it
Where attraction codes fall over
We'd rather you printed two good codes than ten that nobody scans.
Creator — $12.99/mo
A site with a gate, a trail and half a dozen viewpoints runs past what Free covers fast, so Creator's 50 dynamic codes and bulk generation handle the signs, with three custom domains so links carry your site's name. Champion ($39.99) suits a group running several attractions off one account.
Tourist attractions questions
The ones owners actually ask us before they print.
The ones with a payoff do. A short bit of audio about the view beats a paragraph they'd skip. Lead with the 30-second version and let the detail sit underneath for anyone who wants more.