Five ways venues get QR ordering wrong

QR ordering is not complicated technology. A guest opens a web page and taps things. When it doesn't work in a venue, the cause is almost always operational — where the code sits, who watches the screen, how the change was introduced to staff.

Here are the five that come up most.

1. Hiding the code

The code goes on a laminated card, the card ends up flat on the table behind the napkin holder, and nobody scans it. The owner concludes guests don't want QR ordering.

Guests never saw it.

Fix: put the code on something that stands up, in the middle of the table, at the eye level of someone sitting down. Add one line of instruction — "Scan to see the menu and order" — because a bare code doesn't tell anyone what it does. Then sit at your own table and check you'd notice it.

2. Sending orders somewhere nobody is watching

Orders arriving by email, or as a notification on the manager's personal phone, work perfectly at 3pm and fail at 8pm. The phone is in a pocket, the manager is dealing with something else, and a table waits forty minutes.

Fix: orders belong on a screen the kitchen is already looking at, with a sound. A kitchen display on a spare tablet by the pass is enough. If your system can't do that, that's a product problem worth solving before you go live.

3. Rolling out to the whole floor on your busiest night

It's tempting — maximum impact, immediate answer. It's also the setup where every small unknown (where the screen goes, who marks tickets ready, what happens with a split table) becomes a crisis in front of a full room.

Fix: start on a quiet weekday, on a handful of tables, with paper still running in parallel. You want to discover the awkward details when there's slack in the system. Expand once a full service passes without anyone reaching for the old way.

4. Not deciding who does what

The most common live failure isn't technical. It's two people each assuming the other marked an order as ready — so the food sits under the lamp while the floor waits for a signal that never comes.

Fix: before the first shift, say out loud who moves tickets through the stages, and who is responsible for checking the screen when it's quiet. It takes one conversation and prevents most of the confusion people blame on software.

5. Forcing it

Removing printed menus, or telling guests scanning is the only way to order, generates complaints far out of proportion to the number of people actually inconvenienced. People tolerate a new option; they resent a removed one.

It also tends to sour staff, who then stop mentioning the code — which quietly kills adoption more effectively than anything else on this list.

Fix: keep both. Most guests will choose their phone because it's faster. The ones who don't are a small number, they're often your regulars, and serving them the old way costs you very little.

A sane rollout, in order

1. Load your menu properly — photos, correct prices, modifiers. This is the real work.
2. Put the kitchen screen somewhere the kitchen can actually see it, and test the volume.
3. Agree who moves tickets and who watches the screen.
4. Print codes for four to six tables. Stand them up, add a one-line prompt.
5. Run a quiet weekday shift with paper still going.
6. Ask staff what was annoying. Fix that.
7. Expand.

None of this is about software. That's rather the point.

Related: do diners actually use QR ordering? · what to check when choosing software