QR code ordering: where it helps, and where it quietly hurts

QR ordering had a strange few years. It arrived as a public health measure, got oversold as the future of restaurants, then got quietly resented by diners who felt they were being made to do the waiter's job.

The truth is narrower and more useful than either position: QR ordering is excellent in specific moments and a downgrade in others. The skill is knowing which is which.

Where it clearly works

The second round

This is the strongest case and it is not close. A table has ordered, food has arrived, and someone wants another drink. In a busy dining room that means catching a server's eye, which can take five minutes and often does not happen at all.

That order is frequently lost entirely. QR ordering recovers it, and it recovers it at high margin, because drinks and desserts are where margin lives.

Dessert

Same mechanism. Dessert is a decision made at a low-energy moment, and the friction of flagging someone down is enough to convert "maybe" into "just the bill". Removing that friction is worth real money.

Peak-hour overflow

During your busiest ninety minutes, your floor staff are the bottleneck. QR ordering does not replace them — it absorbs the orders that would otherwise wait for someone to become free.

Large groups

A table of ten is a nightmare to take an order from, and a worse one to split a bill for. Individual ordering from phones solves both at once.

Where it hurts

The first order at a nice restaurant

If someone is paying for an occasion, the server interaction is part of what they are buying. Recommendations, explanations, the sense of being looked after. Replacing that with a QR code reads as cost-cutting, because it usually is.

Anywhere your staff are the differentiator

Some restaurants compete on hospitality. If yours does, removing the hospitality touchpoint to save labour is an odd strategy.

Tables where phones are the problem

A family trying to get their teenagers off screens does not want the menu to be on a screen. Small point, real annoyance.

Older or less phone-comfortable guests

A meaningful share of customers will find this worse, not better. If a QR code is the only way to order, you have excluded them.

The rule that resolves it

QR ordering should always be an option, never the only option.

Restaurants that run QR alongside normal service capture the second-round and dessert upside without giving up the experience. Restaurants that replace service with QR save on labour and pay for it in reviews.

The operational cost of offering both is close to zero — the tickets arrive at the same kitchen display either way.

Practical setup notes

A few things that make the difference between it working and it being ignored:

• One code per table, not one per restaurant. The whole point is that the kitchen knows where it goes. A generic code means someone has to ask.
• Put the code where a phone naturally rests — a table stand, not a laminated sheet under the condiments.
• Photos matter more here than anywhere else. Guests browse a phone menu differently than a paper one; items with images meaningfully outsell items without.
• Do not require an account to order. Every field you add before the first order costs you conversions.
• Make sure sold-out items disappear. Nothing sours a table faster than ordering something that arrives as an apology.
• Tell servers it exists. Guests will ask them how it works. If staff seem unsure, guests abandon it.

What to expect

Restaurants that add QR ordering alongside table service typically see the effect in average order value rather than order count — the same tables spend a bit more, mostly on drinks and desserts they would previously have skipped.

The effect concentrates in casual dining and cafés. In fine dining it is usually smaller, and the experience cost is higher.

If you are unsure, run it on half your tables for a month and compare. That is a cheap experiment and the answer will be specific to your restaurant, which is better than any general advice — including this.