Restaurant Menu QR Code Generator — Table Tents, Takeout, Catering

Use a dynamic QR ($5/month Lite plan) for restaurant menus by default. Menu URLs change — you migrate from a website to Square to Toast, switch from PDF to HTML, add an online ordering layer, or rebuild the website. Each change breaks a static QR encoded to the old URL. Dynamic codes survive every platform migration via dashboard update.

Verify the menu URL is mobile-readable before printing the QR. Open the URL on your phone, scroll the full menu, tap an item, check that body text is at least 16pt and headings are visible without zooming. A QR pointing at a desktop-only menu is a bad first impression that loses the table to the restaurant next door.

Avoid PDF menus for table-tent QR distribution. PDFs zoom badly on phones, force pinch-and-pan navigation, and rarely reflow text. If your menu is currently a PDF, host it as HTML (the platforms — Toast, Square, Owner.com — do this automatically) or convert to a responsive web page before generating the QR.

Print at minimum 4 cm × 4 cm on table tents (arm's-length scan at 40–60 cm), 5 cm on counter signage, 8–12 cm on window vinyl (sidewalk scan from 3–8 feet). The 10:1 rule applies: code width ≥ scanning distance ÷ 10, with 1.5× safety margin for dim restaurant lighting and older audience phones.

Use matte lamination on table tents — never glossy. Glossy lamination reflects overhead pendant lights and table candles directly into the camera lens, killing scan attempts at the exact moment the diner is engaged. Matte lamination is also more durable against the grease and condensation that table tents face nightly.

Pair the QR with explicit CTA copy: 'Scan for menu,' 'Scan to order,' 'Scan for wine list.' Naked QRs on table tents convert at half the rate of QRs with adjacent prompt copy. The CTA resolves the moment-of-decision friction; diners scan for a known purpose, not on speculation.

Run separate QRs for distinct intents rather than a single 'find everything' QR. Menu, wine list, takeout menu, catering, gift cards — each gets its own QR with its own label. Per-intent QRs convert at 2–3× the rate of shared landing-page hubs. Two QRs on the table tent beat one QR linking to a navigation page.

For multi-location restaurant groups, generate a separate QR per location even when the menu URL is the same. The per-location dynamic QRs let you measure scan volume by storefront, which tells you which locations the printed asset is paying off at and which need different placement or copy.

Test the full flow before scale-printing. Scan with an iPhone and an Android, load the menu, tap an item, and verify the experience. A misconfigured menu platform or broken image link surfaces immediately in the test scan and prevents the reprint of 500 table tents.

For takeout bag stamps and to-go signage, design the QR to scan through plastic bag wrap and steam. Use error correction H (30% recovery), print at 5 cm minimum, and use food-safe ink. A QR that smudges after 20 minutes in a humid takeout bag is a QR that does not exist.

Avoid combining menu, online ordering, reservations, gift cards, and feedback into a single 'one QR rules them all' page. Each intent has its own conversion path; combining them onto a navigation page drops completion by 50–70%. Print three smaller QRs on the table tent rather than one QR linking to a hub.