Why QR codes work for restaurants
The pandemic forced QR menus on restaurants; what kept them was the operations maths. A printed menu locks your prices until the next print run - a QR pointing at a page you control lets you change a price, pull a sold-out dish, or swap the whole menu in seconds, with no reprint and no crossed-out specials in marker. Across Canada a large share of restaurants now run scan-to-view menus alongside paper, because the cost and flexibility argument holds on its own, well past the period that started it.
The deeper shift is that every customer touchpoint becomes a digital pathway. The table tent is a menu; the receipt is a review request at peak satisfaction; the takeout bag is a repeat-visit prompt; the social post is an event invite. A modern restaurant QR system is half a dozen small codes working together - menu, Wi-Fi, reviews, owner contact, events - each removing one friction at the moment it matters. The Canadian context shapes it: Quebec language law governs printed materials, PIPEDA applies to any email you collect, and provincial liquor rules constrain how you promote tastings.
The complete restaurant QR system
Menu QR - at every table and on takeout
The core code. The guest scans and sees the current menu with photos, prices, allergens, and descriptions; you update the page and every printed code stays valid. Place it on table tents, inside the menu cover, on takeout-container stickers, on the takeaway bag, and on counter cards for quick service. The full menu QR guide covers hosting options and mobile performance - and you can build one from the generator at the top of this page.
Wi-Fi QR - for guests on their own data
One scan joins the network instead of reading a password aloud across a busy room. Put it on each table beside the menu, at the hostess stand, on bar coasters, and - a genuinely high-impact spot - a restroom-mirror decal. Always run it on a separate guest network, as the Wi-Fi QR guide explains, so the public never touches the network your point-of-sale runs on.
Google review QR - on the receipt
The single highest-ROI code a restaurant prints. The guest has just finished a good meal - peak satisfaction - and the receipt is in their hand. A code by the tip line turns that moment into a review, and review volume is one of the heaviest factors in "near me" ranking. The Google review QR guide covers getting the correct review link and staying within Google's no-incentive rules.
Owner / chef vCard - for catering and VIPs
For revenue beyond covers - catering, private dining, partnerships - a vCard with the chef or owner's name, restaurant, direct line, email, and website, placed on business cards, private-dining menus, catering brochures, and event-vendor packages. See the vCard QR guide.
Phone and event QRs
A phone call QR on closed or holiday signage ("call for hours") and on concierge handouts at nearby hotels gives one-tap contact, and an event QR on tasting, wine-dinner, and holiday promotion drops the date straight into a guest's calendar from a poster, email, or social post.
Quebec language law for restaurants
The Charter of the French Language, strengthened by Law 96, applies to all printed materials in customer-facing areas of a Quebec restaurant. The QR code itself is exempt - it is a symbol, not language - but every word around it, and the hosted menu it opens, must comply.
Where both languages appear, French must be markedly predominant - in practice at least twice the visual weight of the other language - or the material French-only, which is always the safe choice. "Menu · Scannez ici" is compliant on its own; "Menu · Scannez ici" with a smaller English line beneath is compliant if French clearly dominates; "Scan for menu" in English only is not. The hosted menu content - dish names and descriptions - follows the same rule, so a Quebec location should serve French content by default. Non-compliant commercial signage carries penalties starting around $1,500 per offence, escalating for repeat findings, so it is worth getting the surrounding text right the first time. Official guidance is published by the Office québécois de la langue française at oqlf.gouv.qc.ca. Franchises spanning Quebec and the rest of Canada generally keep French-only artwork for Quebec locations rather than relying on a bilingual sign that has to be sized exactly right.
Operational best practices
A short daily check
Once a shift, open the menu code on an actual phone on cellular data - not a back-office computer on Wi-Fi - and confirm it loads quickly and shows today's prices and specials. Verify the Wi-Fi credentials still match if anything on the router changed. Thirty seconds prevents a whole evening of guests staring at a stale or broken page.
Weekly menu updates
Update the menu page or PDF at its address; the code never changes. The only thing you reprint is a separate "today's specials" insert if it carries its own code or text - the main table-tent code is permanent.
Staff training
Every server should know where the code is, what to do when a guest's phone will not scan (read out the short menu address or the Wi-Fi password), and that paper menus exist for guests who prefer them. One staff member per shift should test-scan once at open so a dead code is caught by the team, not by fifty tables.
Common problems and fixes
"The menu loads slowly on phones"
The bottleneck is the menu page, not the code. Run it through a mobile performance check, compress image-heavy menus, and put a content delivery network in front of it. The code can only ever be as fast as what it points at.
"Older guests can't figure out the scan"
Train staff to explain it in one sentence, print the plain menu address as text beside the code, and keep a few paper menus. The code is the fast path for most, not the only path for everyone.
"We get spam to the reservation email"
A public email code exposes the address. Use a dedicated reservations-only address, and put a CAPTCHA or rate limit on any booking form behind it.
"Our Wi-Fi password leaked online"
Public-code Wi-Fi passwords do circulate. Run guests on an isolated guest network, separate from point-of-sale and back office, and rotate that password quarterly - the printed code is cheap to regenerate.
"An inspector flagged our English-only sign"
That is a Charter of the French Language matter. Move to French-only wording, or French markedly predominant, on the signage and the hosted menu. The fines are real and escalate, so correct it rather than contest it.
Mapping the codes to the guest journey
The reason a restaurant ends up with several codes is that each one belongs to a different moment in the visit. Thinking of it as a journey rather than a pile of QR codes is what stops you from cramming five codes onto one table tent where none get scanned.
- Sidewalk: a window or sandwich-board code to the menu, so a passer-by deciding whether to come in can see what you serve before committing - this is a conversion code, not a convenience.
- Seated: the table-tent menu code and, beside it, the Wi-Fi code. These are the two a guest wants in the first two minutes; everything else is clutter at this stage.
- Mid-meal: nothing. Deliberately. A code pushed while people are eating is ignored and makes the table feel busy.
- Paying: the Google review code on the receipt, at the single highest point of satisfaction in the whole visit. Timing is the entire reason it works.
- Leaving / at home: the takeout-bag or container code - menu for next time, or an event code for an upcoming tasting - reaching the guest when they are relaxed and might actually plan a return.
Each surface carries the one code that fits that moment. A guest who scans three codes across a visit barely notices doing it; a guest faced with three codes at once scans none. The journey view is what keeps the system invisible, which is the point.
What it costs and what it saves
The honest accounting matters, because "free QR codes" still has a real cost and a real saving, and they are not the ones owners expect. The generator is free and the codes never expire, so there is no per-code or subscription cost for static use. The cost is operational discipline: someone has to keep the hosted menu accurate, test it on a phone, and make sure the printed surfaces carry the right code in the right place.
The saving is the reprint cycle. A printed menu is a recurring expense every time a supplier price moves or a dish changes - and in practice that means either frequent reprints or a menu that is quietly wrong for weeks. A menu behind a QR moves that change to a web page edit: no print run, no crossed-out lines, no stack of obsolete menus. The review code has a different kind of return - it does not save money directly, it raises the review volume that feeds local search ranking, which is the cheapest customer acquisition a restaurant has. Neither return appears on an invoice, which is exactly why it is worth stating plainly: the spend is attention, not money, and the payoff is fewer reprints and better visibility, not a line item.
Static or dynamic: which does a restaurant need?
A static menu QR - what the free generator above produces - hardcodes the menu address into the pattern. The address never changes, you update the menu at it, and the code works forever with no account. For a single restaurant with one menu page, that is the whole job.
A dynamic QR (a paid plan feature) lets you swap the destination - a different menu by time of day, a seasonal page, an A/B test - without reprinting, which earns its keep for multi-location groups and heavily seasonal operations. A single independent restaurant rarely needs it; stay static.