QR Codes for Restaurants: The Complete 2026 Playbook

The menu QR is the only place dynamic codes are genuinely required for a restaurant. Every other code has a stable destination URL.

Menu URL: changes (or should change) anytime the menu changes — prices, items, seasonal specials. Dynamic is correct because you cannot reprint every table tent every time a price moves. If you use a static QR encoding the menu page URL directly, you can still update the menu CONTENT at that URL — but if you ever change the menu's URL (CMS migration, new domain), every table tent is dead. Dynamic insulates you from that.

WiFi credentials: change rarely (every 6–12 months for the guest network on a security rotation). Static is fine — when you rotate the password, you reprint the table tent. Costs $5 in printing per rotation.

Review link to Google Business Profile: stable URL. Static is correct.

Loyalty signup URL: usually stable. Static is correct unless you frequently change loyalty platforms.

The cost of using dynamic for everything: ~$5/mo for the Lite plan (handles 25 dynamic codes). The cost of using static for everything except the menu: $0. The cost of using static for the menu specifically: every menu URL change requires reprinting every table tent, which costs more than $60/year ($5/mo × 12) at any restaurant with more than 5 tables.

The right configuration: dynamic for the menu QR, static for everything else. EZQR's free tier handles unlimited static codes; the Lite plan at $5/mo monthly billing handles the one dynamic menu QR plus 24 spares. Total annual cost: $60. See the dynamic-vs-static engineering guide for the broader trade-off.

The menu QR is the highest-stakes restaurant QR. Most guests scan it within 60 seconds of being seated; failures here ripple through the entire dining experience.

Design: 1 to 1.5 inches square on a standard table tent. Below 1 inch, scan rates drop on older phones in dim restaurant lighting; above 1.5 inches, the QR dominates the design.

Color: black on white is the safe baseline. Brand colors are fine if the dark module color passes 4.5:1 WCAG contrast against the background — see our color guide for the safe palette. Avoid yellow on white, light grey on white, or pastel-on-pastel — they fail under restaurant lighting even when they look fine in the design file.

Quiet zone: four module widths of solid light space around the entire QR. Designers regularly bleed graphics or restaurant logos into that border and break the scan rate. Reserve the space in the table tent layout.

Dynamic redirect: the QR encodes a short URL (e.g., ezqr.com/r/abc123) that forwards to your current menu page. When the menu changes — seasonal items, price updates, kitchen 86s — you update the destination URL once and every table tent in the restaurant reflects the change instantly. No reprinting.

Destination page: the page behind the QR must be mobile-optimized. Most off-the-shelf menu plugins for WordPress and Squarespace render fine on phones; some don't. Test the menu page on an iPhone and a mid-range Android in landscape and portrait before publishing. Slow load times (over 3 seconds) lose 40% of scanners before the menu shows.

Placement: front-facing on the table tent so guests don't rotate it. "Scan to view menu" text immediately above or below the QR. For multi-section menus (food, drinks, dessert), one QR per section actually loses traffic to the food menu — use one combined QR with a tabbed menu page instead.

Sharing your WiFi password via QR code is safer than writing it on a whiteboard, but only if you set up the guest network correctly first.

Never encode the main business WiFi password into a public QR. The QR data is technically readable by anyone with a QR decoder app — they don't have to scan-and-connect, they can extract the credentials and authenticate from anywhere. If your main network has access to the POS system, the kitchen display, the security cameras, or the back office, that is a serious breach.

Set up a dedicated guest network on the router. Modern small-business routers (Ubiquiti, Cisco Meraki, even consumer-grade ASUS or Netgear) support guest networks with one toggle. The guest network is isolated from the main network — guests can reach the internet but not your internal systems.

Encode the guest network credentials in the QR using the standard format: WIFI:T:WPA2;S:GuestNetworkName;P:GuestPassword;;. WPA2 or WPA3 encryption; never WEP. The WiFi QR guide covers the full format including escaping special characters in passwords.

Rotate the guest password every 60–90 days. Each rotation requires reprinting the table tent — keep that in the operations cadence. Static QRs (encoded credentials directly) need new prints; dynamic QRs (pointing to a credentials landing page) only need the landing-page update, but they require the guest to be online first, which defeats the purpose.

Label the QR clearly: "Scan to connect to guest WiFi" works. Avoid "Scan for WiFi" without context — guests sometimes think it'll connect their phone to free outside WiFi rather than yours.

For restaurants with multiple guest networks (one for the dining room, one for the bar, one for the patio), separate QRs per network simplify troubleshooting. "This QR is for the dining room WiFi" vs "the patio network is on its own QR" gives staff a clearer answer when guests have connection issues.

Review-driving signage is the single highest-ROI QR placement in most restaurants. The post-meal moment of satisfaction is the only window in which guests are reliably willing to write a review — once they leave, the rate collapses.

Destination: link directly to your Google Business Profile review form. The URL format is g.page/yourbusiness/review or you can use the Place ID format from Google Maps for Business. Direct-to-review is critical — linking to your business page generally and asking guests to navigate to the review section loses 70%+ of intent.

For Yelp, link to the business page directly (Yelp doesn't expose a direct review URL the same way). For TripAdvisor, similar — link to the business page; the review CTA is a tap away. For OpenTable, the review prompt arrives via email post-reservation, so the QR is less critical there.

Placement: the highest-converting placement is the check presenter, beside the bill or on the inside of the folio. Guests are paused, satisfied (hopefully), and in the right emotional state. Second-best: the exit door at eye level on the way out. Third: table tent alongside the menu QR.

Messaging: "Loved your meal? Tell us on Google" outperforms generic "Leave us a review" by 2–3×. Be specific about the platform and connect it to the emotional moment.

Trackable variant: separate dynamic QRs per zone (bar, booth, patio, private room) reveal which sections drive the most reviews and which need attention. If the patio drives 80% of reviews from 20% of guests, the patio staff and table experience are doing something the indoor section isn't — diagnose and replicate.

Avoid: incentivizing reviews with discounts or rewards. Google's terms of service prohibit it; flagged reviews get removed and your profile gets penalized. The QR is a frictionless ask, not a transactional one.

Loyalty programs convert at higher rates when enrollment happens during the visit rather than in the post-visit email. A QR code on the check or receipt captures the moment of intent.

Destination: link to the loyalty program signup form. Whether you run a custom loyalty platform (Toast Rewards, Square Loyalty, Punchh) or a simple email-list signup, the QR routes to the relevant landing page. Pre-fill what you can — if your POS captures the table number or check number, pass it as a URL parameter so the loyalty record ties back to the visit.

Incentive structure: "Scan to join and get 10% off your next visit" outperforms generic "Scan to join" by a wide margin. The incentive doesn't have to be steep — even $5 off or a free side item is enough to flip the enrollment decision for most guests.

Form minimalism: ask for the absolute minimum at signup — name, email, and (optionally) phone. Birthday, preferences, dietary restrictions can all come later. Every additional field on the signup form drops conversion 5–10%. The full profile happens over time as guests interact with the loyalty program.

Dynamic codes for loyalty: useful if you A/B test enrollment incentives ($5 off vs free side vs free drink) and want to attribute signup rate to each variant. Use one dynamic QR per variant; the scan-by-scan data ties enrollment back to the incentive.

Static codes for loyalty: fine for established programs where the enrollment flow is locked. The destination URL is stable; reprinting on the rare occasion of a platform change is acceptable.

Follow-up sequence: every loyalty enrollment should trigger an immediate welcome email or text with the first-visit offer. Hot leads cool fast — a 6-hour delay halves redemption rates.

Online ordering QRs make sense for fast-casual, ghost kitchens, and quick-service restaurants. They rarely make sense for full-service dining, where the server interaction is part of the value proposition.

For QSR / fast-casual:

The ordering QR sits on the table or the counter, linking to the mobile ordering interface. Guests scan, browse, customize, pay, and the order appears in the kitchen system. Labor cost on order-taking drops; ticket sizes often increase (no time pressure to decide; more visible upsells).

Dynamic codes are correct here. The ordering interface evolves — menu changes, promotion banners, COVID-era pivots like contactless takeout — and you can't reprint table tents every change. Dynamic QRs let you adjust the destination flow without touching the print.

For full-service:

Most full-service operations explicitly avoid order-via-QR because the server interaction drives ticket size and tip percentage. The order-via-QR experience feels like fast-casual; full-service guests are paying for something different.

Hybrid model that works: server still takes the order, but a QR on the table routes to "add to your order" — desserts, after-dinner drinks, takeout for tomorrow. Captures the impulse purchases servers might miss in a busy section without disrupting the service interaction.

Vendor selection for ordering: integrate with your POS. Toast, Square, Clover, Lightspeed all have native QR-ordering integrations or partner apps. Avoid standalone ordering platforms that don't sync back to your POS — the dual data entry kills the operational win.

For the multi-location / chain context, the logistics industry page covers per-location QR variants that route through location-specific ordering systems while sharing brand assets.

Restaurant lighting is variable and usually dimmer than office lighting. Table tents take wear from spills, cleaning chemicals, and guest handling. Spec the print for the worst case.

Substrate: glossy coated paper or laminated cardstock. Direct-thermal labels fade under fluorescent lighting in 4–6 months — avoid for table tents. Standard 14-point coated cover stock with a 1.5-mil laminate handles 12+ months of guest handling and routine cleaning.

Lamination: matte lamination beats glossy lamination for QR scanning. Glossy creates glare under overhead lighting at certain angles, which breaks scans intermittently. Matte stays scan-reliable.

Size: the QR portion of the tent — not the whole tent — at 1 to 1.5 inches square. The surrounding tent design can be any size that fits the table.

Color: black-on-white or dark-on-white. Brand colors are fine if the dark module color passes 4.5:1 WCAG contrast — navy, forest green, burgundy, deep teal, charcoal all work on white or cream. Pastels and light colors fail.

Error correction: level Q (25% recovery) as the default. Level H (30%) if you embed a small restaurant logo in the center of the QR.

Quiet zone: four module widths of solid light space around the entire code. Designers regularly bleed graphics or restaurant logos into the quiet zone and break the scan rate.

Print run: order a one-piece proof from the print shop before authorizing the full batch. Print shops typically charge $5–15 for a single-piece proof. Scan it under actual restaurant lighting on three phones (one older, one mid-range, one current flagship) before approving the batch.

Replacement cadence: budget for a replacement run every 12–18 months. Even with quality lamination, edges delaminate slowly; once the QR pattern is exposed to spills and cleaning chemicals directly, scan rates drop.

For outdoor patio tents, upgrade to UV-resistant lamination — standard indoor lamination yellows in direct sun within 4–6 months. The packaging guide covers the broader print-substrate decision.

Per-zone scan data surfaces optimization opportunities that gut instinct misses. Generate a unique dynamic QR per zone (bar, booth, patio, private room) and watch the data for two months.

Menu scan velocity by zone. If the bar's menu QR is scanned 3× more often than the dining room's, the bar's table mix may be more transient guests who don't know the menu. The dining room may have more regulars. Affects menu design and promotion strategy.

Review-rate by zone. Track which zones produce the most reviews per cover. Patio at peak season usually leads. Private rooms often surprise high. Inside dining rooms in winter often surprise low. Use the data to allocate staff training and table-team mix.

Loyalty enrollment by zone. Where do guests sign up most? Usually the booths near the bar, where the conversation is louder and the guests are more engaged. Less often in the deuces in the back corner. Reflects ambient energy more than location.

Time-of-day scan patterns. Lunch scans skew toward menu views (efficient ordering); dinner scans skew toward WiFi and review. Reflects different psychology. Lunch guests are working, dinner guests are relaxing.

The vendor for this is any dynamic QR generator with per-scan event data. EZQR, QR Tiger, and Uniqode all deliver. The trackable QR generator comparison covers the scan-data fidelity differences.

For restaurants in a chain or multi-location group, per-location plus per-zone data ties scan velocity to revenue. Location A has 2,000 menu scans/mo and $X revenue; Location B has 800 scans/mo and $Y revenue. The scan-to-revenue ratio surfaces which location's menu is converting well and which one isn't.

A trackable menu QR is only useful as long as the code is alive. The biggest hidden risk in restaurant QR deployments is the vendor's cancellation policy.

Flowcode deactivates dynamic codes 30 days after subscription cancellation. For a restaurant that subscribes during a busy season and cancels during a slow season, every printed table tent goes dead 30 days after the cancellation. Guests scan and see a dead URL. The reprint cost and reputation damage outweigh the saved subscription cost many times over.

QR Code Generator (qr-code-generator.com) deactivates dynamic codes on cancellation per their published ToS. Same risk pattern.

Bitly QR Generator applies a retention policy that has different rules for free, paid, and cancelled accounts. The ambiguity is the issue — the policy can change without warning.

EZQR keeps dynamic codes redirecting indefinitely after cancellation. The redirect infrastructure is funded by active subscribers, not by deactivating past customers' codes.

QR Tiger keeps codes active after cancellation per published ToS.

Uniqode keeps codes active per current ToS — but verify in writing because the Beaconstac → Uniqode rebrand broke other policies for legacy customers.

The practical workflow for any restaurant printing 50+ table tents:

1. Verify the cancellation policy in writing from vendor support before generating the dynamic menu QR.
2. Save the support response.
3. Test the cancellation flow on a trial account — generate one dynamic code, cancel the trial subscription, scan the code 35 days later, confirm it still works.
4. If the test code dies, switch vendors before printing the production batch.

The permanent QR code guide covers the vendor-by-vendor cancellation policies in detail, and the subscription traps guide covers the broader patterns to watch for.

After working with hundreds of restaurant operators and watching the same patterns repeat, here are the failure modes that show up most often.

Encoding the main WiFi password into the public QR. The QR data is readable by anyone with a decoder app. If your main network has access to POS, kitchen displays, or security cameras, that's a security breach. Always use a dedicated guest network on an isolated VLAN.

Using static codes for the menu. Every menu URL change forces a full table-tent reprint. Static codes only make sense if the menu URL is permanently stable, which is rare. Dynamic is the right default for menus; static is the right default for everything else.

Skipping the contrast test under restaurant lighting. A brand-colored QR that looks fine in the design file fails 30% of scans under dim restaurant lighting. Print one sample and scan under actual restaurant lighting (not office lighting) before committing to the full batch.

Cancelling the dynamic-menu subscription mid-year. Vendors with deactivation-on-cancel policies kill every printed table-tent menu QR 30 days after cancellation. Verify the policy before printing and avoid Flowcode for this use case specifically.

One QR for everything. A single QR linking to a "scan for menu, WiFi, and reviews" hub page forces guests to navigate to find what they wanted. Separate QRs per job (menu, WiFi, review, loyalty) convert at 2–3× the rate of a shared hub.

Watermarked QR codes on guest-facing tents. A free QR generator that stamps its logo on the code looks unprofessional on a customer-facing table tent. Use watermark-free tools (EZQR free, QRCode Monkey free) for all guest-facing print.

Reprinting on uncoated paper. Uncoated stock absorbs ink and softens module edges. Even the same QR design fails more often on uncoated than on coated paper. Spec coated 14pt cover stock with matte lamination as the default.

No clear call-to-action near the QR. A QR with no text next to it converts at half the rate of one with "Scan to view menu" or "Scan to connect to WiFi" adjacent. The label is not optional.

Every restaurant should be running at least three QRs per table: a dynamic menu QR, a static WiFi QR, and a static review QR. Most should add a loyalty enrollment QR on the check presenter; some should add an ordering QR if the concept is fast-casual or quick-service.

For the toolchain: EZQR handles the full restaurant stack on monthly billing — free for the unlimited static codes (WiFi, review, loyalty, back-of-house), Lite at $5/mo covers the dynamic menu QR with scan analytics. Codes survive cancellation indefinitely, which removes the time-bomb risk every alternative has.

For the design: 1–1.5 inch QRs on coated cardstock with matte lamination, error correction level Q, brand colors that pass 4.5:1 WCAG contrast. Adjacent label text. Quiet zone preserved.

For the operations: rotate the WiFi guest password every 60–90 days, update the menu URL whenever the menu changes, audit review-rate-per-zone monthly, refresh the table tents annually.

For the verification: print one proof, scan on three phones under actual restaurant lighting, confirm before the batch. Verify the vendor's cancellation policy in writing before printing 50+ tents.

For the deep-dive on each piece, see the restaurants industry page, the trackable QR generators comparison, and the permanent QR code guide.