Every restaurant knows the ritual. Prices change, the fish supplier moves, a dish comes off — and suddenly you're reprinting, re-laminating and hand-correcting menus with a marker. A QR code menu ends that cycle. Guests scan a code on the table and always see the current version, because there is only ever one version. What follows is an honest look at what changes when you switch, what it costs against printing, and the one technical mistake that quietly turns printed codes into dead ends.
The reprint ritual costs more than the printing
The invoice from the print shop is the part you can see. The rest hides in the week around it. Someone rebuilds the file. Someone proofreads it and misses the one typo that matters. The order goes out, the batch arrives on a Thursday, and by the following Tuesday your butcher has put eighty cents on the ribeye. So the new menus get a sticker, or a line through the price, or nothing at all — and your floor staff spends the next three months apologising at tables.
The second cost is the inertia it creates. Because reprinting hurts, you stop making small changes. The seasonal dish that would have sold beautifully in April waits for the next print run. The dessert nobody orders stays on the card another year. A printed menu quietly turns every menu decision into a budget decision, and that is the genuinely expensive part.
What a QR code menu actually improves
Marketing aside. Here is what actually changes — the things you notice in the first month:
- Price changes go live in seconds, from your phone, standing at the pass. No reprint, no sticker, no marker.
- Sold out at eight on a Saturday? Mark the dish unavailable and it greys out live for every guest with the menu open.
- New dish, new description, new price: entered and visible before the next table scans.
- All 14 EU allergens and dietary badges sit on the individual dish, so the answer is on the menu instead of in a folder behind the bar.
- Guests who don't speak your language switch the menu to theirs — AI translations you can hand-tune string by string, on the Premium plan.
- Scan analytics show how many people opened the menu, roughly where and when, also on Premium.
- Multi-currency: prices converted automatically, or set by hand per currency, for the tourist tables.
None of it requires an app. Guests point a camera, a web page opens, they read it. That is the entire interaction, and it is why this lands at the table more easily than owners expect.
The mistake that dead-links printed codes
Almost nobody checks this before sending 300 table tents to print: most QR menu tools encode your menu's web address directly into the code. That works perfectly — until something about the address changes. You rename the menu for the new season. You reorganise and the path shifts. You buy your own domain, because a restaurant with a proper domain looks like a restaurant that intends to stick around. And every printed code on every table, window and flyer now points at nothing.
yourmenu.app encodes a permanent short link instead. The code carries a fixed identifier, and the identifier points at wherever your menu currently lives. Rename it, restructure it, move it to your own domain on Premium — the code you print today keeps working. If you take one practical thing from this article, take this: before you print anything, ask your provider what is actually inside the code.
Allergens are not a nice-to-have
EU Regulation 1169/2011 requires the 14 mandatory allergens to be declared for non-prepacked food, and that includes the dishes you serve. In Germany the LMIDV implements it: written documentation has to exist, and oral information is only permitted when that written record is available on request and a notice tells guests so. In practice, someone has to keep a document current. With a printed menu that document is a second document — the folder behind the bar, last touched in March. On a digital menu it is the same document as the menu: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame, sulphites, lupin and molluscs, tagged per dish and current the moment the dish is. Allergen tags are part of the free plan here, not an upsell.
What guests actually want
Nobody installs an app to read a menu. Nobody enjoys pinch-zooming a PDF that was designed for A4 and then squeezed onto a phone screen. Guest expectations are boringly simple: open fast, read without squinting, compare prices down a column, spot the vegetarian dishes without reading every line.
That is the whole brief for a good QR code menu — a fast, mobile-first web page with readable type, clear prices and dietary badges you take in at a glance. It is also exactly why PDFs make such poor QR menus. A PDF is a picture of a document. A menu page is a document.
The cost math, honestly
We won't pretend to know your print quote. Do this instead: pull last year's numbers. Count the print runs — the seasonal changes, the price corrections, the two reprints after supplier increases, the lunch card, the drinks list, the laminated specials board. Add design or agency time if you pay for it. Add the staff hours spent proofreading and hand-correcting. Divide by twelve.
Against that sits this: yourmenu.app is free forever for one complete menu — permanent QR code, allergen tags, unlimited instant updates, no credit card. Premium is $19 a month and adds multiple menus, AI translations, a custom domain, scan analytics and priority support. For most restaurants the honest answer is that the free plan is already enough, and the monthly comparison isn't close. What people end up paying for is a second menu or a second language, almost never the QR code itself.
The two objections worth taking seriously
"My guests are older and won't scan." Some won't, and that is fine. Keep four or five printed copies at the host stand. You no longer need one per table, so printing is a handful of pages rather than a run of eighty, and you print them yourself from the current menu whenever they get scruffy. The QR code covers the majority, the paper covers everyone else. It was never either-or.
"The signal in my back room is terrible." Fair, and testable before you commit anything: walk to the worst table and scan. A QR menu is a lightweight web page rather than an app download, so it copes with a weak connection far better than a PDF does. Even so, no web page loads with no connection at all. If the dead zone is genuinely dead, guest wifi with the password on the table tent solves it, and the printed copies cover the rest.
Getting started
The start is deliberately unglamorous. Type your menu in, or upload a photo or PDF of the old one and let the AI extraction draft the sections, dishes, prices and descriptions for you to correct. That gets you to a reviewable menu in minutes instead of an evening of typing. Your menu lives at your-name.yourmenu.app. Print the code, put it on the tables, and make your first price change from your phone just to feel how it lands.
That first change is what convinces people. You edit a price standing in the kitchen, the menu on table six is already right, and the reprint ritual is simply over. Start on the free plan — one full menu, your permanent QR code, no credit card — and move to Premium only when you genuinely need a second menu or translations.