Every time a supplier price moves, you pay twice — once for the ingredients and once at the print shop. Meanwhile the place across the street taped a small square to each table two years ago and hasn’t printed a menu since.
That square is doing much less than most owners think — which is exactly why it works, and why the versions that fail all fail the same way.
The whole trick is a link
Point a phone camera at a QR code and the phone reads a web address out of the pattern, then offers to open it. That is the entire technology. No app, no chip, no signal coming out of the sticker — it’s a URL printed as a square instead of as text, because nobody at table nine wants to type one.
The menu itself is whatever sits at that address: a proper web page, a PDF, even a photograph of the paper menu. Generating the code is free — plenty of generator sites will turn any address into a printable square in seconds. So the code is the cheap, solved part. Everything that makes a QR menu good or bad lives at the other end of the link.
What diners hate about them
Nobody minds the scanning any more — 2020 taught every phone and every diner how. What people mind is what happens after the scan:
- A PDF that opens at full-page width, so they pinch-zoom and drag sideways to read the appetisers in six-point type.
- “Download our app to view the menu.” Nobody installs an app to order a sandwich.
- A page that demands a name and email before it shows the food.
- A page that crawls on one bar of cellular — old brick buildings do this to phones. If your dining room is a dead zone, the smartest menu page in the world won’t load; fix the signal with proper guest Wi-Fi first.
What works is boring: a fast mobile page. Real text rather than a picture of text, in sections a thumb can flick through, loading in a second or two. Menus built that way collect no complaints at all — diners read them and order, which is the whole job.
The real win — changing prices without reprinting
The code on your tables holds the address, not the menu. Change the page and every code you have ever printed shows the new version instantly — the table tents, the window sticker, the flyer from last spring. You print once and edit forever.
That is where the money actually is. Paper punishes you for changing anything, so prices lag your food costs and the dish that sold out at seven stays on the menu all night, irritating servers and customers in equal measure. A menu that costs nothing to edit lets you raise one price the day your supplier raises theirs, hide the fryer section while the fryer is down, and run a Tuesday special that vanishes Wednesday morning.
Static or dynamic — the trap in free generators
When you generate a code you’ll be offered two kinds, and this is the one decision that can hurt you later.
A static code has your web address baked into the pattern itself. It works forever, costs nothing, and no company can switch it off.
A dynamic code points to the generator company’s redirect service, which forwards each scan on to your menu. It gets sold as the upgrade — scan statistics, an editable destination — but notice what it really means: every code on your tables now belongs to that company. When the free trial ends or the card on file expires, your printed codes die, or worse, start landing diners on an upgrade advert. Restaurants get caught by this constantly. If you generate your own, choose static, pointed at an address you control.
Menus in more than one language
In a tourist area, paper forces a bad choice: print a separate menu for every language and keep them all current, or let visitors guess. A web page just asks. A language switch at the top costs the diner one tap, and the French family by the window reads the same up-to-date menu, at the same prices, as the regulars at the bar.
The translation itself is the part to take seriously. Dish names survive a rough translation; allergy and dietary information doesn’t. If translated menus matter to your trade, have each language read once by someone who actually speaks it — then it’s done, and every future price change reuses it.
The DIY route, honestly
A PDF in a Google Drive share link plus a free static code is a genuinely free QR menu, and it will work tonight. Where it bites:
- It is precisely the pinch-zoom PDF diners hate, framed in Google’s branding rather than yours.
- Replace the file the wrong way and the share link changes — and every printed code on every table now points at nothing. Drive can keep the link stable if you swap the file just so; one wrong click means reprinting the lot.
- No languages, no specials section, no layout designed for a phone.
The step up is a menu page on your own website, which is fine if the site is quick on a phone and easy for you to edit — Wix or Squarespace vs a custom build covers which of those you likely have. Two cautions. A menu page buried three taps deep in your site goes stale, because updating it feels like a chore. And if the site goes down, the menus on every table go down with it — worth skimming what to do when your website is down before it happens on a Saturday night.
What a managed menu service adds
Paying for a menu service buys four things the free route can’t give you: a permanent address of your own that no generator company can hold hostage; a layout actually designed for reading at a table; edits that take a minute, made by you or made for you; and languages handled properly. The pricing model across the industry is a subscription per venue rather than a fee per change — which is the opposite of the print shop, and the reason the maths tends to favour it for any menu that changes more than twice a year.
Handing the menu off entirely
Koadi builds digital menus for restaurants and venues: your menu at your own link, served as a fast page in seven languages, no app for anyone to download. You print the code once; the page stays current. And for everything else that breaks in a restaurant — the POS, the Wi-Fi, the office laptop — you can post the problem free, set a fixed price or take bids from vetted technicians, and the payment sits in escrow until you approve the fix. Remote help covers every US state, evenings and weekends included, and local technicians come on-site when the fix needs hands.