QR table ordering in the UK: get guests ordering by phone
QR ordering only pays off if guests actually use it. A few small placement and menu choices make adoption climb fast.
Guests will happily order from their phone, provided it's obvious what to do and nothing slows them down. The venues with the highest QR adoption have simply removed the small reasons people hesitate.
Make the code impossible to miss
Put the code where hands already rest: table centre, not propped against the wall. Pair it with one short line, “Scan to order & pay”, so there's no guessing about what happens next.
Design the menu for thumbs
Lead with photos and your best sellers, keep categories short, and let guests pay in a tap with Apple Pay or Google Pay. Every extra step is a place to lose them.
“Tables turn faster and the team spends less time taking orders and more time looking after the room.”
The five places adoption quietly dies
The code they can’t find. A laminated card behind the ketchup is invisible. Table-centre, eye height, one per table, plus one at the door for the queue.
The line that doesn’t promise anything. “Scan me” tells a guest nothing about what happens next. “Scan to order & pay, no app” does. The three words that matter most are no app: half the hesitation is fear of a download.
The slow first screen. If the menu takes more than a couple of seconds, phones go back in pockets. Servio’s guest menu is a browser page, not an install, precisely for this moment.
The wall of categories. Guests scroll like they’re flicking, not reading. Best sellers first, photos on the dishes you want to sell, categories short enough to hold in one thumb-sweep.
The card form at the end. Apple Pay and Google Pay turn checkout into one tap. Plenty of guests will abandon a full basket rather than type card details one-handed at a table.
Your team decides whether it works
The strongest predictor of QR adoption isn’t the sticker. It’s the script. If a server says “you can order at the bar or just scan the code, it’s quicker,” adoption climbs within days, because permission came from a person. If the team treats the QR as a rival that steals their tables, guests feel it and default to waving someone down. Brief the floor on what the system is actually for: it takes the transcription off their hands and nothing else. Someone still runs the plates and reads the table. The part that stops is typing orders into a till.
“The three words that matter most are: no app.”
What good looks like, in numbers
Don’t aim for 100%. Counter regulars and cash loyalists are fine as they are. A seated venue doing 30-60% of table orders through QR at peak is winning, and the effect shows up in two numbers you can watch on the live dashboard: average order value (self-paced guests add the extra scoop or the second flat white nobody had time to offer them) and orders-per-staff-hour at your busiest window. If adoption stalls after a fortnight, walk the room as a guest: scan from a seat, order something with two modifiers, pay. Whichever step slowed you down is the one to fix. Our weekend-rush write-up shows what it feels like when all five frictions are gone.
Rolling it out in one week
Monday: print the codes, but put them out at half the tables only, so you have something to compare against. Brief the team on the one-line script and the reason behind it.
Tuesday-Wednesday: watch the halves. The QR tables should show faster first-order times and slightly higher items per order; if they don’t, walk the flow yourself as a guest before blaming the guests.
Thursday: fix the one friction you found, usually the code’s position or a menu photo that’s selling the wrong thing first.
Friday: full floor. Peak service is the real exam, and the team has had four days of low-stakes practice answering “how does this work?”
The weekend after: check adoption by daypart, not overall. Brunch and evening behave like different venues; it’s normal for one to run 60% QR while the other stays counter-led. Optimise them separately.
The one-week shape matters because adoption builds on repeat visits: your regulars need to see the codes twice before they trust them, and your team needs to answer the same question twenty times before the script sounds natural. Venues that “try QR” for one shift and judge it on that have only measured the awkward first hour, before anyone had a chance to get used to it.
Common questions
Do UK guests actually use QR table ordering?
Yes when the prompt is obvious and the menu loads fast. Clear table talkers, a one-line ask from staff, and a familiar browser checkout beat a downloadable app every time.
Where should QR codes sit in a restaurant?
On the table within reach of every seat, not only at the door. Pair each code with a short line such as "Scan to order and pay" so guests know what happens next.
Should QR orders use a separate kitchen printer?
Ideally no. Phone orders should land in the same kitchen queue as till orders so the pass never runs two systems. That is how Servio QR ordering is built.