QR menus for restaurants: how they work and when they pay off
A QR code on the table can be a PDF nobody reads, or an extra waiter who never tires. The difference is what happens after the scan.
In short: a QR menu is a code printed on the table; the guest scans it with their phone camera and the menu opens in the browser, with no app to install. There are two kinds: a view-only menu, and one that takes the order and sends it to the till and the kitchen. The first saves printing menus; the second changes how the floor works.
The two kinds, and which you need
| View-only menu | Ordering menu | |
|---|---|---|
| What the guest sees | Items and prices | Items, prices, options and an “order” button |
| Where the data comes from | Often a separate file or site you update by hand | The POS itself |
| An item runs out | Stays visible until you edit it | Disappears the moment it is marked unavailable |
| Effect on waiters | Almost none | Less time writing, more time serving |
If the menu lives apart from your system you will forget to update it, and a guest will order at last month’s price. The rule: one source of prices.
What does the restaurant actually gain?
- The second order: coffee after the meal, dessert, another drink — often lost because the waiter is busy. With a scan they take seconds.
- Fewer mistakes: the guest picks “no garlic” themselves, so no mishearing and no bad handwriting.
- Rush hour: pressure on waiters eases when the room is full.
- No reprinting menus at every price change.
And the drawbacks, honestly
- Some guests prefer a waiter who explains and recommends — especially in family and fine-dining places. Do not drop the paper menu; make QR an extra option.
- The guest needs internet on their phone; offer guest Wi‑Fi.
- Without controls you may get a prank order. That is solvable, as follows.
How to stop prank orders
- Start with manual acceptance: every order shows at the till and is approved before it reaches the kitchen.
- A code per table, not one code for the venue, so you know where each order came from.
- A cap on order value.
- Accepting hours: no orders while you are closed.
- Regenerate the code if it is photographed and shared; the old one stops.
Once you trust the flow, move to automatic acceptance for tables that already have an open bill: the guest really is seated, and their add-on order goes through without waiting.
Steps to switch it on
- Make sure your items are in the system with names, photos and options — the menu mirrors them.
- Generate a code per table and print it on a small stand or a waterproof sticker.
- Choose manual acceptance, and set the hours and the cap.
- Train the cashier on the “incoming orders” screen.
- After two weeks, review: how many orders came by QR, and how many were second orders?
In Sahl
Sahl’s QR menu reads items, prices, options and photos from the POS itself, with three acceptance modes, a cap, accepting hours and a dedicated price list if you want one, and any table’s code can be paused or regenerated. An accepted order goes to the kitchen display like any other. It is part of the restaurant module at no extra charge.
Frequently asked questions
Does a guest need an app to scan a QR menu?
No. The phone camera reads the code and opens the menu in the browser.
Does a QR menu replace waiters?
No. It takes writing off their hands and catches add-on orders, but welcoming, advising and serving remain human work. Offer it alongside the paper menu.
Do guests pay through the QR menu?
In Sahl the order is sent from the phone and payment happens at the till or with the waiter, so the whole bill stays in the POS.