New:Experimental free plan now live for everyonev1.6.0

Ok1Second
Menu
Restaurants & cafés

Dynamic QR codes for restaurant menus

Print the QR code once, change the menu forever. A dynamic menu QR code points at a short link you control, so you can swap in a lunch menu, hide sold-out dishes or move to a seasonal list without touching a single table tent.

Updated 2026-10-06 · 5 min read

One code per table, one menu to rule them all

Reassign a table to a different menu or language in seconds — the printed code stays valid.

Language routing

Route guests to the menu in their language automatically using the visitor's country and browser settings.

See what's working

Scan counts by day, device and country tell you which dishes and specials get the most attention.

Why restaurants switch to dynamic menu QR codes

Static menu QR codes are a trap: the moment a price changes or a dish sells out, the printed code is wrong. A dynamic code embeds a short link instead of the menu URL, so the destination can be edited at any time while the physical code stays identical.

That means reprints only happen when a table tent wears out — never because the kitchen changed the specials.

  • Update prices, allergens and availability without reprinting
  • Serve lunch, dinner and drinks menus from a single code
  • Point the same code at every language your guests speak

Set it up in three steps

Create a code, paste your current menu URL, and print. When the menu changes, open the manager, edit the destination and save — the QR code never changes.

  • Create a dynamic QR code and name it after the table or area
  • Paste your menu link as the default destination
  • Add language or location rules if you run several venues

Where the code goes in the room

Placement decides how a menu code performs more than the design does, because the scanning distance changes from 30 cm to five metres between a table tent and a window decal. A table code scanned from 30 to 50 cm is comfortable at 2.5 to 3 cm square; the same code on the window needs to be several times larger.

Proof it in the room, not on the screen. Print the proof, scan it with two different phones at the real distance, in the real light. Glossy lamination picks up every ceiling lamp, and a code under a candle's glare fails exactly when the room is at its busiest.

  • Table tent: matte finish, a clear space around the code the width of one module
  • Till and counter: keep it at eye level, away from the card reader's screen glare
  • Receipt and check presenter: the right place for the review link and the loyalty sign-up
  • Takeaway bags: good for reordering and delivery, not for the sit-down menu

What the scan data is actually good for

Scan counts answer staffing questions the till cannot. When people pick up the menu, which evenings are dead, whether the lunch board gets read at all: all of that is a scan count per day, and it costs nothing extra to collect.

The useful comparison is before and after. Move a code from the window to the table tent, wait a week, compare. That is how you find out a placement works, rather than guessing from how the room feels.

  • Peaks by hour and weekday to line up staffing and prep
  • Language mix to decide which printed menus are still worth keeping
  • Country mix to see the tourist season arriving before the covers do

Running more than one venue

One code per venue is usually simpler than one code with rules, but the choice depends on what changes. If each site keeps its own menu, give each site its own code and name them clearly, so the manager editing tomorrow's specials is not one dropdown away from the wrong restaurant's page.

For a group spread over several countries, the same printed table tent can serve every site by routing on country, with a default page for anyone the rule does not catch.

  • Name codes after the site and the placement, not after the design
  • Keep one page per site's menu so a local price change cannot leak across venues
  • Group the dashboard by site at month end to compare how each room behaves

Frequently asked questions

Can I use one QR code for the whole restaurant?
Yes. One dynamic code works for every table. If you want per-table reporting, print one code per table — they can all point at the same menu.
What happens to the QR code if my menu moves?
Nothing — you edit the destination URL in the dashboard and the printed code keeps working. That is the whole point of a dynamic QR code.
Can the menu open in the guest's language?
Yes. Add a rule that routes visitors from a country to a specific language page, with a default fallback for everyone else.
Should the QR code open a PDF or a web page?
A web page. A PDF is slow on mobile, cannot be read without zooming, and hides how far anyone got. If the PDF is all you have, at least keep the same file name so the link does not break when it is re-exported.
How big should a table QR code be?
2.5 to 3 cm square for a table tent scanned from 30 to 50 cm. Larger is fine, smaller is not. Print a proof and scan it at the real distance before you send the batch to print.
Do guests need an app or an account?
No. The code opens a page in the guest's normal browser. Nothing to install, no sign-up, no permission prompt before the menu appears.
Can lunch and dinner share one code?
Yes, in two ways. Point two codes at two menus and leave both on the table, or keep one code and swap its destination before each service from the dashboard.

Keep reading

Other solutions

Create your first dynamic QR code

Free to start. One code, editable forever, with scan tracking from the first scan.

Privacy-first analyticsNo per-scan feesEdit links anytimeNo contract