QR codes for restaurants
Menus, reviews, and Wi-Fi โ one sticker, forever.
The pandemic QR boom was brief and telling. Stickers went on every restaurant table in 2020; most of those stickers are still physically there in 2026, but a good chunk of the links behind them are broken โ pointing at PDFs in abandoned Dropboxes, menus dated March 2021, or 404 pages from web hosts that went under. The hype was 'restaurants will go digital'; the reality was that restaurants went hybrid and mostly forgot to maintain the digital side. What survived the hype cycle is real, but narrower than the original sales pitch. At scale, large chains proved that QR-driven table service works when it's backed by a point-of-sale that treats a scan as an order. McDonald's rolled out in-store QR ordering in the UK starting around 2016 and expanded globally; the benefit wasn't shaving seconds at the counter but the upsell depth and customization data their tablets also captured. Table-service groups with modern POS (Toast, Square for Restaurants, Lightspeed) integrate QR as a direct ordering surface โ the scan is the order ticket, not a menu PDF. That's a tier most independents can't afford and don't need. For sub-chains and independents, three patterns earn their keep in my experience: a menu that actually updates, a review funnel that routes happy guests to Google and angry ones to you privately, and a Wi-Fi QR that saves your bar staff from spelling out a 22-character password at midnight. Everything else you might read โ loyalty punch cards, table-side tips via QR, per-dish story videos โ is optional garnish. Pick the three first, get them right, and ignore the rest until a year of data says otherwise.
A menu that actually updates
The menu pattern fails when nobody owns the updating. A laminated paper menu is at least audited every shift by the servers handing it out. A QR pointing at a PDF is audited only when a customer complains. You need an operator, not a tool. The operational fix: assign one person per shift whose opening checklist includes 'verify the menu URL renders and today's 86 list is reflected.' The technical fix: use a CMS the kitchen already opens โ I've seen Notion pages, Airtable-backed menu sites, and native POS menu editors all work; I've seen Squarespace pages get orphaned within six weeks. The correlation isn't the tool โ it's whether the person who updates 86 lists every day is also the one who touches the menu page. Dynamic QR codes earn their place here cleanly: when your menu source-of-truth moves (and it will), you change the destination once and every table's existing sticker still works. Static QRs pointing at a PDF URL are a trap โ the day your host moves the file, a hundred tables point at a 404 that nobody on the floor notices for two weeks.
A review funnel that routes intent honestly
Google Reviews dominate restaurant discovery in most English-speaking markets. In local-pack tests, a restaurant with 4.2 stars and 800 reviews reliably outranks a 4.8-star spot with 60 reviews. Volume matters almost as much as rating, which means asking for reviews is worth doing โ and the QR on the receipt is the moment of maximum asking-power: right after a customer paid, left a tip, and mentally rated the night. The ethical and effective pattern is a smart link that branches: guests who self-identify as happy land on Google's review deep-link pre-filled with the business ID; guests who say something's wrong route to a private form that pages the manager. Neither path fabricates reviews โ it just gives satisfied guests a shortcut and gives unhappy guests a way to be heard that isn't a public one-star. A receipt QR that only ever routes to Google gets you ratio without recovery, and you'll burn good guests on the review platform when they'd rather have told you quietly.
Wi-Fi QR that staff don't have to read out loud
The Wi-Fi QR is the least glamorous pattern and the most consistently useful one. iOS 11+ and Android 10+ join the network automatically when the camera sees a QR encoding the WIFI: string format โ no typing, no repeating the password at 11pm, no napkin with 'Password: NightOwl!2024' on it. Print the code at the bar, in the menu cover, and on a window decal near the door. If your Wi-Fi password rotates (which it should), a static QR is not the answer โ encode a short dynamic URL that points at a landing page showing the current generated Wi-Fi QR. The printed code on the table never changes; the Wi-Fi QR behind it regenerates when your password does. Small point of advice: don't print the password as readable text beneath the QR. Guests whose phones can't scan will ask โ which is the moment your staff can sell them a drink.
Printing and placement tips
- Laminate or UV-coat every table sticker. Coffee rings and alcohol-based wipes eat uncoated ink within six to eight weeks of daily service โ I've replaced stickers more than I care to admit.
- Size table codes at 3ร3 cm minimum. Guests scan one-handed with a drink in the other; bigger codes scan faster and feel less fussy.
- Audit your menu URL every Monday morning for 30 seconds. Dead links aren't noticed until a customer asks โ and most customers don't ask, they just leave.
Build one now
The free generator handles every pattern above. Upgrade to Pro when you want dynamic destinations or scan analytics on top.
Further reading and sources
- Toast โ Order and Pay (QR table ordering) โ POS with built-in QR order flow
- Square for Restaurants โ Comparable mid-market POS
- Google โ deep-link format for business reviews โ Official guidance for review request URLs
- Wi-Fi QR 'WIFI:' format reference โ ZXing/WIFI string spec
- McDonald's corporate stories โ Context on their digital-ordering rollout