The first wave of QR menus in UK restaurants replaced a laminated card with a photograph of a laminated card. Guests scanned, pinched to zoom, gave up, and asked the server what was good anyway.
A QR menu earns its place when it does something paper cannot: recommend, translate, filter by dietary need, and update the moment a dish comes off. That is the difference between digitising a menu and having a menu that sells.
Allergen information on a printed menu is only as current as the last reprint. On a digital menu it updates the moment you change a recipe, across every table at once, and guests can filter the menu by what they need to avoid rather than scanning footnotes.
For UK operators this removes a recurring operational risk and a recurring printing cost at the same time.
Per-table QR codes let orders arrive with the table number already attached and give you engagement data table by table. A single venue QR works for counter service and takeaway. Most UK venues run both.
Move the sliders to your own numbers. The point is not our figures — it is how little the uplift has to be before the subscription pays for itself.
5% is the conservative default. WowMenu pilot restaurants have reported considerably more, but your own number is the one that matters.
An estimate based on the figures you entered, not a forecast or a guarantee. Actual results depend on your menu, your guests and how the platform is set up.
No. The menu opens in the phone's browser as soon as the code is scanned — nothing to install.
Both are supported. You can run a view-only QR menu, or enable ordering so guests send their order straight to the kitchen display.
Yes, per dish, and guests can filter the menu by dietary requirement. Changes publish instantly across every table.