QR ordering has a bad reputation in some cafés, and usually for a fair reason: somebody tried it, the customer had to download an app or make an account, and half of them gave up and waved at a server instead. The technology was not the problem. The friction was.

This is what a version that works looks like, and what to watch for when you set it up.

The install step is the whole game

Every step between scanning a code and seeing a menu costs you a meaningful share of the people who scanned. An app download is not one step, it is several: a store page, a download on café wifi, an account, a password, a permission prompt. By the time that finishes, a person who wanted a flat white has decided it is easier to catch your eye.

So the rule is simple. Scanning the code should open a menu, in the browser, and nothing else should happen first. No app, no signup wall, no cookie interstitial. Ask for identity later, when the customer has a reason to give it.

The order of operations that works

Scan. The camera opens your menu in a browser tab.
Browse and add. Photographs help here more than they do anywhere else, because nobody is describing the food to them.
Suggest. This is the step most setups skip. A coffee is an obvious pairing with a pastry, and the system can offer it on every order rather than only when the counter remembers.
Identify. Now ask for a number and verify it with an OTP. At this point the customer wants something in return, so they will give it.
Apply rewards. Points or a coupon, if they have one.
Place. The order reaches your counter as one ticket with the table number.

Notice that identity comes fifth, not first. Asking for a phone number before someone has chosen anything is the second most common way to lose them.

What to actually put on the table

One code per table, and print the table number on it. A single generic code means somebody has to type a table number, and they will get it wrong.
Make it big enough to scan while seated. A small code on a tent card is fine at 30cm and useless at arm's length across a two-top.
Say what it is. "Scan to see the menu and order" outperforms a bare code by a wide margin, because a naked QR could be anything.
Keep a paper menu. Some customers will never scan anything, and that is fine. This is a second channel, not a replacement.

The operational changes to plan for

The customer side is the easy half. The half that decides whether this survives its first busy Saturday is what happens behind the counter.

Somebody has to own the screen. An order that lands where nobody is looking is worse than no system at all. Decide whose job it is before you go live.
The alert has to be impossible to ignore. It should keep making noise until a human acknowledges it, not chime once into a busy room.
Sold-out items must be one tap. If marking the last croissant gone takes thirty seconds, nobody will do it, and you will be selling things you do not have.
Expect the first week to be bumpy. Staff will keep taking orders the old way out of habit. That is normal and it settles.

Common mistakes

Treating it as a cost-cutting exercise. If the pitch to your team is that this replaces people, you will get no cooperation, and this does not replace people. It removes the dull part of the job, which is walking to a table to write down a latte.

Hiding the menu behind a login. Covered above, but it is worth repeating, because it is the single most common reason these projects fail.

Letting the menu go stale. A digital menu with last season's prices is worse than a printed one, because customers assume the screen is correct.

Ignoring the data. The most valuable output is not the orders, it is knowing who your regulars are. See how to build a loyalty programme for what to do with that.

What to measure after a month

Scan-to-order rate. How many people who opened the menu actually ordered.
Average ticket, digital versus counter. Suggestions usually show up here.
Repeat rate. The share of orders from someone you have seen before. This is the number that matters most, and it is the one you could not measure at all before.
Items that stopped selling. Easy to spot on a digital menu, invisible on a printed one.

Retova does QR ordering for cafés with no app to install, plus loyalty, customer records and the counter screens to run it. Read how it works for cafés, orbook a walkthrough and we will set it up against your own menu.

QR code ordering for cafés: a practical guide