Industry guide
QR codes for sports venues
Seat-back codes with the section, row and seat in the URL turn concession ordering into delivery to the seat. The catch is scale: tens of thousands of simultaneous scans hit whatever the code points at, so use a direct URL to infrastructure sized for kick-off, never a rate-limited shortener.
The seat in the URL
The seat-back code is the venue's best pattern because the code's location is the delivery address:
https://venue.example/order?block=112&row=G&seat=14
One menu and ordering page, tens of thousands of codes, each prefilled with its own seat — generated in bulk from the seating plan and printed once. The fan orders without leaving the action; the runner knows exactly where to go. Seat-backs are read from 40–60 cm, so 4–6 cm of code on a scuff-resistant laminate; seat-backs get kicked, so budget for replacement stickers rather than assuming one print lasts a decade.
The concurrency lesson
A stadium code is scanned by more people per second than almost any other placement — a half-time promotion can put tens of thousands of near-simultaneous requests onto one URL. The code itself has no rate limit; everything behind it does. Coinbase's 2022 Super Bowl ad made this famous when the bouncing QR drove so much traffic the app's landing experience buckled — the same lesson applies inside a venue:
- Link a direct URL on your own domain, never a free shortener with its own rate limits you have never read.
- Serve a static, CDN-cached page at the link target; let the heavy app sit one tap deeper.
- Load-test at expected-peak, not average.
Second screen and season tickets
Concourse and big-screen codes linking match stats, replays or player content give fans a reason to scan beyond food. Big-screen codes follow the same rules as TV codes: large, high-contrast, and held on screen long enough to scan. At the exits, a season-ticket or next-fixture signup code catches the post-win mood — the best conversion moment in sport.
FAQ
How do seat-back QR codes for ordering work?
Each seat's code carries its block, row and seat number in the URL, so the ordering page already knows the delivery address. One page template serves the whole venue; the codes are batch-generated from the seating plan and printed as durable stickers.
Can a QR code handle 40,000 people scanning at once?
The code can — scanning is local to each phone and nothing about the code itself rate limits. The destination is what fails. Point stadium codes at cached, static pages on infrastructure load-tested for peak, and avoid third-party shorteners entirely.
What size should stadium QR codes be?
Seat-backs: 4–6 cm for a 40–60 cm reading distance. Concourse posters: 10–20 cm for 1–2 m. Big-screen codes follow the 10:1 rule against the farthest seats you expect to scan, which usually means occupying a significant fraction of the screen.
Try it — free, no signup
Related
- QR codes for concerts and festivals — The honest truth about static QR tickets, plus on-site codes that work — merch pre-orders in queues, artist follows, wayfinding — and the sunlight problem.
- QR codes for events and conferences — Which QR codes events and conferences actually need, where to put them, what size, and what goes wrong.
- QR codes for gyms and fitness studios — Which QR codes gyms and fitness studios actually need, where to put them, what size, and what goes wrong.
- QR codes for cinemas — One code per film poster linking trailer and showtimes, loyalty at concessions — and why backlit poster cases behave like screens, not paper.