QR codes for restaurants: a complete guide

The short version

• Dynamic QR codes let a restaurant change prices or specials without reprinting table cards.
• Static codes are free, but the destination is permanent once printed — risky for a menu that changes.
• A dynamic code lets you edit the linked page and track scans by table without generating a new code.
• Print at least 2×2 inches, and test under dim dinner lighting before rolling out to every table.

Why QR code menus matter for restaurants

A printed menu locks in every price and every dish the day it goes to the printer. A restaurant running a seasonal menu, weekend specials, or a happy hour list needs a way to change what’s on the page without touching the paper on the table.

QR menus solve a second problem: staffing. A server cannot answer “is the fish still on” for forty tables during a Friday rush, but a menu page that updates in real time can. Restaurants building a QR code menu typically use one code per table or section rather than one code for the whole room, because that is the only way to know which tables actually scan, and when.

Build a mobile-first menu page, not a PDF

Most restaurants start by uploading the print menu as a PDF and calling it done. That is the wrong move — PDFs load slowly on restaurant wifi and force diners to pinch and zoom through a scanned image instead of reading text.

• Break the menu into single-column sections by course, not by the original page layout
• Keep the file small enough to load on weak wifi or a phone with a spotty signal
• Use real text for dish names and prices, not a scanned image of the old menu
• Add photos only for signature dishes, not every line item
• Put allergens and dietary tags next to the dish, not buried in a separate PDF

Choose a QR code type that matches how often your menu changes

Free generators produce static codes, which are fine for a menu that never changes but force a full reprint the moment a price or dish changes. For a menu that shifts by season or by week, a dynamic QR code keeps the same printed code while the linked page updates behind it.

• Static QR codes: free and unlimited, but the destination is permanent once printed
• Dynamic QR codes: the printed code stays the same while you swap the linked page
• Test a batch of ten codes before ordering a full run of table cards
• Confirm the link is not set to expire before it reaches every table
• Check the destination page loads in under two seconds on the restaurant’s own wifi

Print and place codes so they survive a dinner shift

• Print at a minimum of 2×2 inches so a phone can scan from arm’s length at the table
• Laminate or seal table cards — spills and grease ruin unsealed paper fast
• Avoid glossy finishes near overhead lights; glare blocks the camera from reading the code
• Stand codes upright on a table tent rather than flat under a plate or napkin
• Test every code under the restaurant’s actual dinner lighting, not office lighting

If a code takes longer than two seconds to scan under dinner lighting, the design is the problem, not the diner’s phone.

Track scans by table, time, and day

Counting scans is what turns a QR menu from a novelty into a tool. Without per-table tracking, a restaurant is guessing at what is working.

• Assign a separate code per table or per section, not one code for the whole dining room
• Watch scan volume by hour to see which shift needs more staff near the door
• Compare weekday scans to weekend scans before changing table card placement
• Flag any table code with zero scans in a week — it may be damaged or hidden
• Use scan data, not guesswork, when deciding which table tents to reprint first

Update menu content without reprinting anything

• Swap the linked page behind the same printed code the moment prices change
• Mark sold-out items on the live page as soon as the kitchen runs out
• Rotate seasonal specials on the same code used for the regular menu
• Keep a backup static link for the rare diner whose phone will not load the live page
• Update the page once, and every printed code in the restaurant reflects it immediately

Train staff to handle scan problems at the table

• Teach servers the phrase “scan to view the menu” instead of “we have a QR code”
• Keep two or three printed backup menus behind the host stand for phones that will not cooperate
• Show staff how to spot a smudged or peeling code before a shift starts
• Explain the difference between a slow phone camera and an actually broken code
• Post one instruction line under the code: “point camera, do not tap the screen”

Menu QR code options for restaurants

A restaurant running specials weekly should default to a dynamic QR code, not a static one. The cost of reprinting table cards every time a price changes adds up faster than the code itself.

Common mistakes restaurants make with QR code menus

• Printing a static code into laminated table tents, then reprinting the whole batch the next time a price changes.
• Uploading the print PDF menu as-is instead of building a page a diner can read one-handed on a phone.
• Placing one code at the entrance only, leaving seated tables with no way to reload the menu mid-meal.
• Skipping scan tracking, so no one knows which table cards get used and which sit ignored.
• Using thin, light-grey code designs that fail to scan under dim dinner lighting — see printing QR codes for contrast and size.