QR Codes for Restaurants: The Complete Guide (Menus, Orders, Reviews)

QR codes became table-standard during 2020 and stayed because they genuinely solve restaurant problems: menus go out of date, prices change, allergen disclosures get updated, and reprinting paper menus is slow and expensive. Done right, a restaurant QR system also gives you data you've never had before — which tables generate the most repeat visits, which menu items get viewed most, when peak ordering windows hit.

The three main use cases

1. Digital menus

The baseline. Each table gets a code that opens your menu in a browser. The menu page should be mobile-first (most users will scan with a phone), fast (under 2s to interactive), and easy to update — ideally backed by a CMS your floor manager can edit without a developer.

Best practice: one QR code per table, all pointing to the same menu, but with the table number as a URL parameter. Now you know which tables order what.

2. Contactless ordering and payment

More advanced setup. The QR code opens a web app where the customer adds items to a cart and pays. The kitchen ticket prints with the table number attached. This shifts staff time from order-taking to service, which most operators find net-positive at lunch and net-negative on a romantic dinner — pick your moments.

3. Review and loyalty collection

The most underrated use. Print a small "Loved your meal? Tell us." QR on the check folder that opens directly to your Google review form. Restaurants that do this consistently see a 3-5x increase in monthly Google reviews — which is the single biggest driver of new customer flow for local restaurants.

Placement that actually works

  • Table tents: the standard, but easy to ignore. Works best when the tent has a one-line value prop ("Order from your phone — pay at the table") rather than just "Menu".
  • Etched on the table: durable, beautiful, but you commit to one URL forever. Use a dynamic QR code so the URL can change while the etching stays.
  • Check folder insert: best place for review-collection codes — the customer is already past the meal and forming an opinion.
  • Window decal: useful for "view menu without entering" — works well for tourists deciding where to eat.

Designing the code itself

  • Size: minimum 2cm × 2cm for tabletop, 4cm+ for window decals scanned at a distance.
  • Contrast: dark dots on a light background. Inverted (light on dark) reduces reliability, especially in low restaurant lighting.
  • Quiet zone: keep a clear margin around the code equal to at least 4 modules.
  • Test in low light: the QR code that scans perfectly in your office may fail under candlelight. Always test on-site.

What to track

With dynamic QR codes you can see:

  • Scans per table — surface tables that are positioned poorly (no scans = no one is sitting there comfortably with their phone)
  • Repeat scan rate — high repeat rate suggests customers re-open the menu mid-meal (good signal for dessert prompts)
  • Time-of-day distribution — informs staffing
  • Device share — if 70% of scans are iOS, optimize your menu page for Safari specifically (in-app browsers behave differently)

Common mistakes

  • One QR for the whole restaurant. You lose all table-level data.
  • PDF menus. Slow to load, terrible on mobile, can't be analyzed. Use a real HTML menu.
  • Code with no context. "Scan this" is not a call to action. Tell the customer what happens.
  • Forgetting allergens. Health authorities increasingly require allergen disclosure on digital menus. Build it in from day one.

TL;DR for operators

Use one dynamic QR code per table pointing to a fast, mobile-first HTML menu. Add a separate review collection code on the check folder. Track scans per table, repeat rate, and time-of-day. Update prices and items through a CMS, not by reprinting. Your menu becomes a living surface that gets better every week.