Restaurant menus
A QR code menu that survives a Tuesday price change
Point a dynamic QR code at your hosted menu page or PDF, put it on the table, and update the file whenever the menu changes. The printed code never needs to change, only the destination.
Most menu QR codes fail for one of two reasons: the code was printed as a static image of a PDF link, so a price change means reprinting every table tent, or the destination is a heavy PDF that loads slowly on a phone held one-handed at the table.
A dynamic code fixes the first problem. Choosing the right destination and the right physical placement fixes the second.
Where to put the code
| Placement | Best for | Watch out for |
|---|---|---|
| Table tent | Sit-down service, wine lists, daily specials | Gets knocked over or sticky. Laminate it and check it weekly. |
| Window decal | Passers-by checking the menu before they come in | Glare washes out contrast in direct sun; use a matte decal. |
| Receipt or check folder | Repeat visits, loyalty pages, review requests | Wrong moment for the full menu — use it for follow-up content instead. |
| Counter or till | Quick-service ordering | Needs to be large enough to scan without holding the line up. |
PDF menu vs mobile web page
A PDF is the fastest thing to produce: export from whatever you already use to design the menu and point the code at the hosted file. The tradeoff is pinch-zooming on a phone, and it's the same PDF for everyone regardless of screen size.
A mobile web page takes more setup but reflows to fit the screen, loads faster on weak restaurant wifi, and lets you show allergen or dietary tags as text customers can search rather than squint at.
Either way, the point of a dynamic code is that you can change your mind later without reprinting. Start with a PDF if you need the menu live today; move to a web page when you have time to build one.
Seasonal and daily changes
- Swap the destination file, not the code, when the season menu changes. The table tents stay exactly as printed.
- For dishes that run out mid-service, edit the page itself rather than the code mapping — that's a content change, not a QR change.
- Keep one code per menu type (lunch, dinner, drinks, kids) rather than one code that tries to hold everything. Diners scanning for a quick lunch shouldn't land on a wine list.
- If you run genuinely different lunch and dinner menus, either re-point the same code on a timer via your own process, or use two codes and swap which table tent is out.
Allergen and dietary information
A QR-linked menu page is a reasonable place to list allergens in full, because you have room that a printed menu doesn't. But don't make allergen information scan-only — regulations in most places require it to be available on request without a phone, so keep a printed allergen sheet behind the counter regardless.
If a dish changes supplier or recipe, update the linked page immediately. Treat the allergen list as the one part of the menu that has to be right the moment it's edited, not batched with the next seasonal refresh.
Takeaway and delivery packaging
- A code on a takeaway box or bag can point at a reorder link, your delivery app profile, or a review page — table-tent menu content doesn't fit the moment.
- Grease and steam degrade printed contrast fast. Use a code with strong black-on-white contrast and test a printed sample after it's been through a hot bag.
- Packaging gets reused for months after a promotion ends, so re-point stale campaign codes to something evergreen (your ordering page) rather than leaving them dead.
Lunch vs dinner scan behavior
Lunch scans tend to be fast: someone wants to see prices and pick quickly before ordering. Dinner scans happen over a longer table conversation, with a return visit to check dessert or wine after mains. Design the linked page so prices and dish names load first, and keep photos below the fold rather than making people scroll past them to see what things cost.
Always keep paper menus
Not every guest wants to use their phone at the table, and not every phone will scan cleanly in low light. Keep a small stock of laminated paper menus for anyone who asks, and make sure staff know to offer one without being asked twice. QR menus save reprinting cost; they shouldn't become the only option.
Common questions
- Should I use a PDF or a web page for a QR menu?
- A PDF is quicker to set up and fine for most restaurants. A web page reflows better on small screens and loads faster, which matters more if your wifi is weak or your menu is long.
- Can I change the menu without reprinting the table tents?
- Yes, as long as the code is dynamic. It encodes a short link, so editing the destination file or page updates every table instantly with no reprint.
- Do I still need paper menus if I have a QR code?
- Yes. Some guests won't or can't scan, and many areas require allergen information available without a phone. Keep a small stock on hand.
- One code for the whole menu or separate codes per section?
- Separate codes for genuinely different contexts — lunch, dinner, drinks — work better than one code holding everything, since guests land exactly where they need to be.
- Where does a QR code scan best on the table?
- Table tents work well for sit-down service because they're at a stable, well-lit angle. Receipts and till-side codes suit a different moment, like reviews or loyalty signups, not the main menu.
Keep reading
- How to create a QR menuA step-by-step setup for restaurants, from file choice to table placement.
- PDF QR codePut a menu, manual or brochure behind a QR code and swap the file later.
- Dynamic QR codesHow editable QR codes work and why they beat static codes in print.
- Google review QR codeSend customers straight to your Google review form.
Print once. Change the destination anytime.
Create a free account, generate your code and edit where it points whenever you need to.