QR Codes for Restaurants: Menus, Reviews, and WiFi That Actually Work

After 2020, every restaurant printed a QR code on the table and called it a menu. Five years on, most of those codes are wrong: faded, too small, pointing at a dead PDF, or wrapped through an ad service that takes 4 seconds to load before the menu shows up.

Here's a practical playbook for getting QR codes right in a restaurant context — without paying for a "QR menu platform" you don't need.

The four QRs every restaurant should have

1. Menu — the most-scanned QR in your venue
2. WiFi — joins the guest network in one tap
3. Review — opens the Google review form pre-filled
4. Reservation / contact — opens vCard or the booking page

Most restaurants stop at #1. The other three each take 30 seconds to make and quietly improve operations every week.

QR menu: the right way

The big mistake is treating the QR menu like a digital file. Treat it like a webpage — fast, mobile-first, and updatable from a phone.

Best options:

1. Your own page — yourrestaurant.com/menu is the gold standard. You control the design, the load speed, the updates.
2. A Google Doc set to "anyone with the link can view" — surprisingly fine for small venues. Mobile-friendly, free, fast.
3. A static site like Notion published page — clean look, easy editing.

What to avoid:

• PDF menus. A 2 MB PDF takes 5+ seconds on a weak signal, opens in a clunky reader, and people zoom in awkwardly. PDFs are for printing, not scanning.
• "QR menu builder" sites that wrap your URL. They charge $20/month, slap an ad on the redirect, and lock your menu in their editor.
• Image-only menus. Hard to update, bad for accessibility, painful on small screens.

Generate the menu QR with Qropi (URL tab), point it at your menu page, and you're done — for free, forever.

Print specs that actually work

Restaurants are dim. Tables are reflective. Phones at arm's length need a target the camera can lock on. Use these specs:

• Size: at least 4 cm × 4 cm. Smaller looks designed; bigger scans reliably from a relaxed sitting posture.
• Error correction: Q (~25%). Tables get wiped with damp cloths constantly. Q absorbs the wear.
• Color: black on white. Brand colors on a hero poster are fine; on the table card, use boring black. Reliability beats branding.
• Quiet zone: leave a 4 mm white margin around the code. Don't crop in.
• Surface: matte laminate, not glossy. Glossy reflects ceiling lights and kills the scan.

Print 20–30% more table cards than you have tables. They get destroyed faster than you'd think.

The review QR: small effort, large compounding effect

A review QR points at a Google Maps URL that pre-opens the review form. The format:

https://search.google.com/local/writereview?placeid=YOUR_PLACE_ID

To get your Place ID:

1. Go to Google's Place ID Finder
2. Search for your restaurant, click the marker
3. Copy the Place ID — it looks like ChIJN1t_tDeuEmsRUsoyG83frY4

Generate that URL as a QR. Print it on the receipt or the bill folio with copy like "Loved your meal? It takes 10 seconds to leave a review." You'll get more reviews than email follow-ups, and they'll be more recent — which Google weights heavily in local rankings.

The WiFi QR: stop reading the password aloud

Generate this from the WiFi tab on Qropi, with these inputs:

• SSID: your guest network (not your main one — never your main one)
• Password: the guest password
• Security: WPA

Print at the same 4 cm size as the menu QR, on a separate card or on the back of the menu card. Modern phones (iOS 11+, Android 10+) join automatically from the camera app.

We covered this in detail in QR Code for WiFi.

The reservation / contact QR

Two options depending on your operation:

• vCard QR — saves your restaurant's name, phone, address, and website to the customer's contacts in one tap. Use this if you take phone reservations.
• URL to booking page — points at OpenTable, Resy, or your own booking widget.

Print this small (3 cm) on the menu cover or napkin holder. Lower scan volume, but high intent — a guest who scans this is asking to come back.

What about table ordering?

Table-ordering QR codes — scan, browse, order, pay, all from your phone — are great for fast-casual and bad for fine dining. Two real concerns:

1. You replace your server's read of the table (drink refill, dessert nudge, allergy questions) with a transactional flow that customers don't want.
2. The platforms charge 3–8% per order on top of payment processing. For thin-margin food, this is real money.

If you want table ordering, run the math against your current ticket size and tip structure. For a 60-seat restaurant doing $80 per cover, 5% adds up to ~$1,200/week in fees. That has to come from somewhere.

Real-world mistakes I keep seeing

• One QR per table laminated to the table itself. Every QR points to the same menu, but they get scratched up over time. Use removable cards instead so you can replace the worn ones.
• A different QR per table for "table number tracking" but no actual ordering integration. The scan does nothing with the table number — it's theater.
• Menu QR pointing at a Linktree. Your customer is hungry. Don't make them choose between your Instagram and your menu.
• No fallback URL printed. Phones occasionally fail to scan in low light. Print the URL in tiny text below the QR as a backup.

TL;DR

• Menu, WiFi, Review, Reservation — four QRs cover 95% of restaurant use cases
• Use static QRs (free) pointing at pages you control, not "menu platforms"
• 4 cm × 4 cm minimum, error correction Q, matte not glossy
• Always use a guest network for the WiFi QR
• Print a tiny URL fallback under the code

Generate all four for free at Qropi — no signup, no ads in the redirect, no monthly fee.