QR Table Ordering for a Restaurant or Pub: What to Check

Short answer: The QR code is the easy part. What decides whether table ordering works is whether orders land in your existing till and kitchen printer or screen without anyone re-keying them, whether your real menu (with every modifier and allergen note) fits the system, how paying works, and what staff do when a guest won't or can't use their phone. Ask suppliers the questions below, trial it in one section on quiet shifts, and keep a staffed fallback for good.

How table ordering actually connects

A typical flow, as POS suppliers describe it:

Each table has its own QR code, tied to that table number.
The guest scans it and lands on a mobile ordering page with your menu.
They choose items and modifiers, add notes, and either pay straight away or choose to pay later.
The order appears on your POS and goes to the kitchen ticket printer or kitchen display, already marked with the table.

Square's UK help centre, for example, describes QR codes tied to "ordering stations" so staff know where each order goes, with orders feeding the POS and the kitchen printer or display. Lightspeed's Order Anywhere describes table profiles where guests scan the table's own code, order with modifiers, add a tip, and either pay by card or choose "Pay before leaving". Lightspeed also describes the order showing as pending until the restaurant confirms it.

The question for you isn't whether this is possible. It's whether your setup does it cleanly.

Buyer's questions list

Take this to every supplier demo. Ask them to show you, not tell you.

Integration

Does the order arrive in our current POS as a normal order on the right table, or in a separate tablet someone has to watch?
Does it print or display in the right place (drinks to the bar, food to the kitchen, desserts held)?
If we already have a tab open at the table, does a QR order add to the same bill?
What happens if the POS or internet drops mid-service? Where do orders queue?

Menu and modifiers

Can it carry our full modifier structure: steak cooking, sides swaps, "no onion", half portions, upgrade to large?
Can we mark allergens and dietary tags clearly, and prompt guests to tell staff about allergies?
Can we hide items in real time when the kitchen runs out (86ing), and does that sync from the POS?
Can we run different menus by time (breakfast, lunch, happy hour) automatically?
How are age-restricted items handled, and what does staff confirmation look like?

Payment

Pay as you order, pay at the end, or both? Pubs often want pay-as-you-go; restaurants usually want one bill.
Can a table split the bill or pay for one person's share?
How are tips and service charges shown, and where do they appear in reporting?
Does it support Apple Pay and Google Pay on the ordering page?
Can guests pay by scanning a code on the printed bill, even if they ordered with a server?

Guest experience

Does the page load quickly on a weak mobile signal? Test it in your venue, in the corner with the worst reception.
Is it a web page or does it push guests to download an app? Insist on a web page.
Can a guest order a second round without re-entering their details?
Does the page look like your venue, with your photos and wording, not the supplier's brand?

Costs and contract

Is it part of a plan you already pay for, or an add-on? Square's help page, for instance, lists QR code ordering for Square Online Plus or Premium subscribers.
What are the card fees on table orders compared with your card machine?
How long is the contract, and can you export your menu and sales data if you leave?

The staff role doesn't disappear

Table ordering changes the job; it doesn't remove it. Decide who:

Greets and explains the system ("you can order from the QR code on your table, or I'm happy to take it").
Watches incoming orders for anything odd: a large order from one table, a note that needs a chat, an allergy mention.
Runs food and drinks to the right table, since nobody took the order in person.
Checks on tables that haven't ordered after a few minutes.

Guests who don't want to use their phone

Some guests won't scan: older customers, people with a flat battery, groups who want to chat with staff, anyone who simply prefers it. Keep printed menus and normal table service available, and say so on the table card. A pub that forces QR ordering on a Sunday lunch crowd will hear about it.

Fallback when things fail

Plan for:

No signal or Wi-Fi down. Guests on mobile data may still get through; your POS may not. Know how your system queues orders offline.
Payment provider outage. Switch the page to "pay at the bar" if your system allows it, or switch ordering off temporarily.
Tampered or damaged codes. QR codes carry no visible destination, as Nielsen Norman Group's QR usability guidance points out, so guests can't tell where a code leads. Print a short web address and your venue name beside the code, and check table cards regularly for stickers placed over them.
Kitchen overload. Some systems let you pause ordering or show longer wait times; find that switch before the first Friday rush, not during it.

Rollout plan

Weeks 1–2: set-up

Build the menu with every modifier, allergen tag and time-based menu.
Print table cards with the QR code, venue name, a short URL and "or ask a member of staff".
Train staff on reading orders, refunds and the pause switch.

Week 3: soft launch

Switch on for one section or the beer garden only, on quiet shifts.
Order every menu item yourself through the system, including awkward modifiers, and check what the kitchen sees.

Week 4: review and expand

Look at orders, average spend per table, refunds and errors. Ask staff what broke.
Fix the menu wording guests misunderstood.
Expand to more sections if it's working.

Ongoing

Review modifier errors and "item not available" complaints monthly.
Re-test on a phone after every menu change.

FAQ

Do we need our own app?

No. A mobile web page opened from the QR code is what guests expect; an app download at the table is a barrier.

Will table ordering mean we need fewer staff?

It changes where staff time goes, from order-taking to service and running. Don't plan cuts until you've seen a few weeks of real shifts.

Can we use our website's online ordering for table orders too?

Often, yes. Several systems use the same ordering page for takeaway and tables, with the table number added by the code.

What should the QR card say?

What it does, where it goes, and the alternative: "Scan to order and pay at table 12 — or ask us."

If you're weighing up table ordering and want it joined to your till and menu properly, tell us which POS you use and how your service runs.