The QR menu has a bad reputation, and it has partly earned it. But the problem was almost never the QR code: it was a scanned PDF, heavy and landscape, forcing the customer to pinch-zoom with two fingers while the waiter stood there waiting. That isn't a digital menu. It's a bad scan with a code on top.
Done well, a digital menu solves three real operational problems. Done badly, it's the first bit of friction a customer meets when they sit down.
What does the business gain from a digital menu?
Changing prices without reprinting. Fish goes up, you adjust the price that morning. No binning 400 menus, no waiting for next season. This alone pays for a digital menu within a year.
Marking what's off, the moment it runs out. No more "we're out of that today" three times a service.
Knowing what people look at. This is what almost nobody takes advantage of: a digital menu leaves data behind. Which dishes get opened most, which get looked at but not ordered, the order people browse in. That's margin intelligence a paper menu will never give you.
Translating properly. In Tenerife that isn't optional. A menu that detects the phone's language and shows itself in English or German sells more than one with a shaky translation in small print underneath.
Handling allergens at a glance. In digital form, each dish can carry its allergens right beside it without cluttering the menu or making anyone ask for "the folder". It's easier for the customer and saves the floor staff the same conversation ten times a day.
When should you NOT use a QR code?
Here's the part almost nobody says out loud:
- White-tablecloth restaurants with a high average spend. If you're selling an experience, the physical menu is part of that experience. Good paper communicates something a screen doesn't.
- An older clientele. If your customers are past 65, the QR code is a barrier, not a convenience.
- No decent signal. If 4G doesn't reach your terrace and you have no guest wifi, the QR code doesn't work. Full stop.
The sensible answer in most cases is a mix: a physical menu for ordering, a QR code for the other-language versions, the allergens and the specials of the day. Each format does what it's good at.
What separates a good digital menu from a bad one?
| Bad | Good |
|---|---|
| A PDF you have to zoom into | Built for mobile, readable without touching anything |
| Slow to load | Opens in under 2 seconds on weak 4G |
| Requires downloading an app | Opens in the browser, nothing to install |
| Allergens in a separate PDF | Allergens visible on every dish |
| Spanish only | Detects language; ES/EN/DE as a minimum |
| No photos | Real photos on the highest-margin dishes |
| A printed QR that can't be changed | A permanent QR pointing at an editable menu |
That last point saves a lot of grief: a printed QR code should never contain the menu itself. It should point at a web address you control and can change. Otherwise every menu change means reprinting every code.
What decides whether it works
A digital menu is a small website, and the same rules apply: if it's slow, people give up on it. The difference is that here the customer is already sitting at your table, hungry, with the waiter in front of them. Patience is measured in seconds.
At GMB Horizon we build digital menus that load fast, work in several languages and you can edit yourself. If that sounds useful, get in touch.