Operations guide
A mobile QR menu without an app
The simplest journey begins at the table: a guest scans a code, the phone opens a web address and the menu appears in the browser. No installation gets in the way. That visible simplicity still depends on careful choices about placement, links, readability and maintenance.
An app-free QR menu is a mobile web page reached through the phone’s camera or QR reader. The code contains a stable address; the restaurant can change the menu behind that address without printing a new code for every edit.
Book a call
01
The real journey: scan, verify, open, read
The camera recognizes the code and proposes an address. The guest chooses to open it in the browser, preserving familiar phone controls such as back navigation, text enlargement and link sharing. The menu does not need to imitate an installed application to feel direct.
The first screen should confirm the restaurant and expose useful categories immediately. An unclear redirect, account request or intrusive banner introduces doubt at the moment someone simply wants to read.
- The QR opens a recognizable web address.
- The first screen identifies the restaurant.
- The menu asks for neither an account nor an installation.
- Normal browser controls remain available.
02
Table placement is a service decision
A QR works when guests can frame it without moving glassware or leaning awkwardly. The support must suit the room’s light: enough contrast, limited glare and clear space around the pattern. A tiny code hidden under a glass becomes a dining-room problem rather than an abstract technical issue.
Nearby copy explains the action briefly and names a fallback. Staff should know where supports are placed, how to recognize damage and how to offer a physical menu or verbal help to anyone who cannot or does not want to scan.
03
A stable link separates printed material from changing content
The code on the table should point to a durable address controlled by the restaurant or its menu service. Seasonal dishes, prices and availability can change behind that entry point. A dated file or temporary address turns every correction into another print run.
Stability does not remove the need for checks. After an update, someone should open the public link on a phone that is not signed into the editing tool. Existing bookmarks and already printed codes belong in that test.
| Element | Role | Useful control |
|---|---|---|
| Printed QR | Entry point at the table | Scan every print batch before placement. |
| Public address | Durable destination | Review redirects and the HTTPS certificate. |
| Content | Menu, prices and availability | Proofread, publish, then check the public version. |
| Fallback | Access when scanning is unsuitable | Keep it current with the service team. |
04
Readability and accessibility are not finishing touches
The menu should work in portrait orientation with strong text contrast and comfortably separated touch targets. Categories remain understandable without colour alone. Prices, options and allergen notes do not hide behind hard-to-discover gestures, and browser zoom remains available.
Screen readers need ordered headings, named links and real text. Even a sharp image of a menu cannot provide that structure. Dish photographs carry useful descriptions when they communicate information; decorative elements can stay silent.
- A logical heading structure with one main heading.
- Controls that work with keyboards and assistive technology.
- Text size and contrast suited to dining-room conditions.
- No essential information trapped inside an image.
05
Network conditions vary; service still needs a way forward
A basement dining room, terrace or busy mobile network can delay opening. The responsible answer is not a promise of absolute availability. It is a light page, text that appears before media and reception checks at actual tables under service conditions.
Fallback may be an updated physical menu, a restaurant tablet or help from the team. Its presence does not weaken the digital menu. It recognizes that hospitality must continue when a phone is out of power, incompatible or simply unwanted.
06
Maintenance and security are observable habits
The restaurant should know who can edit the menu, how changes are reviewed and how correct content can be restored. The public address uses HTTPS and displays a domain guests can recognize. Editing permissions stay limited to people who need them.
Physical supports also deserve inspection. A sticker placed over a QR can send a scan to another address. Staff can compare the proposed URL with the expected destination and replace altered materials. These practices do not remove every risk; they make anomalies easier to notice and correct.
- Name the people allowed to publish.
- Review prices, availability and allergen notes before release.
- Check the address proposed by codes in the dining room.
- Document how to correct or restore menu content.
✓
For the team
Checklist before placing QR codes on tables
Test the journey with the support, lighting, phones and network conditions guests will actually encounter.
- The code is sharp, high-contrast, unobstructed and low-glare.
- The scan proposes the expected domain before opening.
- The page immediately identifies the restaurant and menu.
- Guests can read without installing an app or creating an account.
- Text appears before heavier photographs or media.
- Menu changes keep the same stable public address.
- Staff know the fallback and keep it current.
- Physical codes and publishing permissions receive regular review.
Prepare the table journey
Review your QR menu in real service conditions
The support, public address and mobile menu can be considered together to identify friction before it reaches the dining room.