Use Cases
QR Codes for Restaurant Menus
Menu QR codes became standard in most restaurants during 2020 as a contactless alternative to physical menus, and they've stuck around since — not for health reasons anymore, but because they let a restaurant update prices, swap out seasonal items, or fix a typo without reprinting anything. Done well, they're genuinely convenient. Done poorly, they're the single most common source of "I hate scanning a QR code just to see a menu" complaints. The difference usually comes down to a few specific decisions.
Use a dynamic QR code
This is close to non-negotiable for a menu. Prices change, dishes get 86'd, seasonal items rotate, and happy hour menus shift by day of week. A static QR code locks all of that into the printed table tent permanently — a dynamic code lets you update the destination whenever the menu changes, with the table tents staying exactly as printed. Given how often table materials get replaced anyway (spills, wear, seasonal redesigns), the cost of a dynamic code service is trivial compared to reprinting.
Link to a page built for a phone, not a PDF
The most common failure isn't the QR code itself — it's what it points to. A code that opens a multi-page scanned PDF menu forces a diner to pinch-zoom on a small screen in bad lighting, which defeats the entire point of "quick response." The destination should be a real mobile web page: single column, large legible type, sections that don't require horizontal scrolling. If you don't have a dedicated ordering platform, even a simple single-page site with menu categories as anchor links outperforms a PDF by a wide margin.
Error correction and placement
Table tents and menu inserts get handled constantly — greasy fingers, spilled drinks, general wear — so M or Q level error correction (see our error correction guide) is a safer default than the minimum L level, even though the code itself will be a bit denser. If you're placing a logo in the center of the code, which is common for menu codes since it reinforces the branding, jump to H level, since the logo needs enough redundancy around it to still scan reliably.
Size matters more than people expect at typical table viewing distance — a code smaller than about 1.5 inches per side printed on a table tent becomes noticeably harder for older phone cameras to lock onto quickly, especially with a busy printed background behind it.
Common mistakes
- No fallback for non-scanners. Not every guest wants to use their phone at the table — keep at least a couple of printed physical menus available, or a short printed list of key items, especially for tables with older guests or anyone without a smartphone.
- Codes placed where they get damaged or covered. Laminated table tents that sit flat under plates and cups wear out fast. Standing table tents or wall-mounted codes near the entrance hold up better.
- No context on what scanning does. A bare code with no label creates hesitation. "Scan for menu" next to the code removes any ambiguity about what happens when a guest points their camera at it.