QR code ordering for restaurants: when it works, when it backfires, and how to set it up
QR ordering went from pandemic necessity to permanent fixture — but plenty of venues bolted it on, hated it, and ripped it out. The difference between the two outcomes is almost never the technology. Here's how to tell which camp you'd be in.
Wemu Team
Product
Put a QR code on a table and you've changed the job description of everyone on the floor. Done well, that's a café serving 20% more covers at lunch with the same staff. Done badly, it's a dining room full of people staring at phones while a server hovers uselessly. The technology is identical in both cases — the operating model isn't.
What QR ordering actually changes
| Metric | Typical effect | Why |
|---|---|---|
| Average order value | Up 8–20% | No queue anxiety, full menu with photos, and add-on prompts at the moment of ordering |
| Table turnover | Faster at peak | Ordering and paying stop being bottlenecks that require a staff member's attention |
| Labour per cover | Down | Order-taking and payment-running disappear; staff shift to food running and hospitality |
| Tips | Mixed | A prompted default tip often beats a verbal ask — but only if you set sensible defaults |
| Order accuracy | Up | The customer types it; nobody mishears "no onions" across a noisy room |
Where it works — and where it doesn't
Be honest about your venue before you print a single code.
- Strong fit: cafés, casual dining, bars with table service, food halls, breweries, poolside and beachside venues, anywhere queues form at peak
- Workable: bistros and mid-tier restaurants, if you use QR for drinks and repeat rounds while staff handle the main order
- Poor fit: fine dining, degustation, venues where the server's recommendation is the product, older-skewing clientele in areas with patchy mobile data
The mistake that kills adoption
Removing staff from the floor the day you launch. QR ordering only reduces labour once customers are trained on it. Keep the floor staffed for the first month — the venues that fail are the ones that cut shifts on day one and let confused tables sit unattended.
The setup checklist
- 1Get your menu genuinely digital first — photos, accurate descriptions, allergen notes, and modifiers (extra shot, no onions, sauce on the side). A QR menu that's a PDF scan of a printed menu is worse than no QR at all.
- 2Set up modifiers and upsell prompts properly. This is where the average-order-value lift actually comes from: "make it a large for $1.50" converts far better on a screen than from a rushed server.
- 3Print one code per table, not one for the venue — the order needs to know which table it came from, or you've just built a takeaway counter.
- 4Decide your payment model: pay-now (best for turnover and zero walkouts) or add-to-tab (better for long sessions and bigger rounds).
- 5Configure tipping defaults thoughtfully. Three options with a middle default performs best; aggressive presets generate complaints and one-star reviews.
- 6Route orders to the kitchen display, not a printer nobody watches. The whole point is that the order arrives without a human relaying it.
- 7Train the floor on the new job: food running, checking in, and helping the one table per service that can't get the code to scan.
- 8Keep a paper menu available. Always. It costs nothing and saves the occasional customer relationship.
The details that decide whether people use it
- No app download, ever. If the code opens an app store page, adoption dies instantly — it must open a web page.
- Fast load on bad mobile data. Compress images; assume one bar of 4G.
- Table number visible on screen so the customer knows the order will find them.
- A "call server" button — this single feature removes most of the abandonment that comes from feeling ignored.
- Order status after they pay, so nobody wonders whether the order went through.
What it costs
Standalone QR ordering products typically charge either a monthly fee per venue or a percentage of QR-channel revenue — and the percentage models get expensive fast at volume. The cheaper structural answer is a POS that includes QR ordering natively, so orders land on the same kitchen display and in the same sales reports as everything else, with no integration to maintain and no second system to reconcile at close.
Beyond software, budget for physical codes: printed table talkers or stickers, ideally laminated. Reprinting is the hidden cost — if your provider generates codes that point at a permanent link, a menu change never means reprinting.
Measuring whether it worked
Give it 60 days, then compare QR orders against counter orders on three numbers: average order value, items per order, and covers per staff hour. If QR isn't beating the counter on at least two of the three, the problem is nearly always the menu (thin descriptions, no photos, no modifiers) rather than the channel.
QR ordering, built into the POS
Wemu gives every table its own code. Orders flow straight to the kitchen display, payments and tips settle with the rest of your sales, and it all reports in one place. 7-day free trial.
See Wemu POS →