Three Jobs, One Square: Auditing the QR Codes Sitting on Your Tables
Photo: Erik Cleves Kristensen, CC BY 2.0, via Wikimedia Commons
Walk into almost any US restaurant in 2026 and there's a QR code waiting on the table. It arrived during the pandemic as a menu workaround and never left, because it turned out to be useful. Also because nobody has had a spare afternoon to reconsider it.
Here's the thing about that square: it stopped being a menu a long time ago. Most of them now do three separate jobs at once, and only one of those jobs is the one you think you assigned.
Job one: getting people to the food
The overt job. A diner sits down, scans, and expects a menu in under three seconds. If the code points at a PDF that takes nine seconds to render on a crowded cellular network, the server gets asked for a paper menu — assuming there is one.
This is where most QR programs quietly fail. The code was generated in 2021, printed on 400 table tents, and pointed at a PDF that lived on someone's personal Dropbox. The link still works. The experience is miserable.
Quick wins:
- Ditch the PDF. Mobile-friendly HTML menus load faster and are readable without pinching.
- Test on cellular, not Wi-Fi. Stand in the dining room during service and scan it.
- Check the current menu. Nothing erodes trust like a QR code that opens last spring's prices.
Job two: steering the review
Many restaurant codes route to a Google review page, a Yelp listing, or a short survey before the check arrives. That's a legitimate use — a diner with a full stomach and a phone in hand is an unusually willing reviewer.
But the routing matters. If the code dumps someone straight into a review form with no context, most people back out. If it lands on a short page that asks one friendly question and then offers a review button, response rates climb.
A common mistake: pointing the table code at a review platform you don't actively monitor. If a one-star review lands and nobody replies for three weeks, the funnel you built is now working against you.
Job three: the one nobody mentions
Here's where it gets less comfortable. Many QR codes carry tracking parameters — the utm_source, utm_medium, and utm_campaign strings appended to the end of a URL. These aren't malicious. They're how the marketing team knows the table code outperforms the window decal.
But those strings can get long, and they can carry more than campaign names. Some setups attach identifiers that follow a diner across sessions. Others route through a third-party redirect or a link shortener that logs every scan.
None of this is illegal, and most of it is standard analytics. It's still worth knowing what's attached to the square on your table, because a diner who scans a menu and gets a cookie consent wall didn't sign up for that.
The stale-link problem nobody owns
Ask a restaurant owner who owns the QR code program and you'll usually get a pause. The printer made the table tents. The web person set up the landing page. The POS vendor provided the ordering link. The review platform has its own dashboard.
Four vendors, zero accountability. That's how a code ends up pointing at a decommissioned ordering page for eight months while everyone assumes someone else checked.
Assign one person. Put it on the monthly closing checklist next to the walk-in temperature log. That's the entire fix.
Strip the URL down before you print again
If you're reprinting table tents — or even if you're just re-examining the ones you have — do an honest pass on the destination URL.
What to remove:
- Redundant tracking. One
utm_sourceis plenty. Chains of eight parameters look like spam to some scanners and slow the redirect. - Legacy redirects. If the link hops through two shorteners to get to the final page, collapse it to one.
- Dead subdomains. Point everything at your real domain wherever possible.
What to keep:
- A readable path.
yourrestaurant.com/menubeats a string of random characters, and diners who see the URL before tapping trust it more. - A single hop. One short link to one destination.
Build the fallback before Friday night
Every QR code should have a human-readable backup printed next to it. Not because the code will break — though it might — but because some phones scan poorly in dim light, and some people just prefer typing.
A short, memorable URL underneath the square solves three problems at once: accessibility, older devices, and the diner who simply doesn't want to open a camera app.
It also gives you an escape hatch. If the ordering system goes down mid-service, you can redirect the short link to a simple page saying "order at the counter tonight" and nobody has to reprint anything.
If you're the one holding the phone
A quick word for diners, since you're the other half of this transaction.
- Look at the URL before the page loads. If a restaurant's code opens something that isn't the restaurant's own domain or a recognizable ordering platform, back out.
- Decline the cookies if you just want the menu. A PDF doesn't need location access.
- Notice the fallback. A restaurant that printed a readable URL next to the code usually also tested the code.
The square on the table is a small piece of infrastructure doing a lot of work. Give it twenty minutes of attention a quarter and it'll keep doing all three jobs without embarrassing anyone.