Table-Specific QR Codes: Why Each Table Needs Its Own Code (2026)

August 1, 2026 at 8:50 AMTabres Team

table specific qr codes qr code per table restaurant table qr code scan to order qr code menu

Most restaurants print one QR code, photocopy it forty times, and stick it on every table. That single shortcut is the reason their staff still walk around the room asking "who had the burger?"

Short answer: each table should have its own QR code because the code carries the table number inside the link. When a guest scans table 12, the order arrives tagged "table 12" — no typing, no guessing, no runner holding a hot plate in the middle of the room. One shared code strips that information out, so every order lands anonymous and someone has to put it back by hand. Table-specific QR codes cost the same to make. They just take ten extra minutes to set up once.

If you already have a QR code menu running, this is the upgrade nobody tells you about. Let's go through it properly.

What a table-specific QR code actually is

It's not a different kind of QR code. It's the same black-and-white square. The difference is what's written inside it.

A general menu code holds a link like yourplace.com/menu.

A table-specific code holds yourplace.com/menu?table=12.

That little tail is the whole trick. The guest never sees it. Their phone opens the same menu, looking exactly the same. But now the page knows where that phone is sitting, and every order it sends carries the table number with it.

Same code size. Same scan speed. Same cost to print. The only extra work is generating forty codes instead of one — which, in any decent tool, is forty clicks.

The five things that break with one shared code

I've watched this play out in enough dining rooms to know the pattern. Here's what actually goes wrong.

1. Someone has to type the table number. Most shared-code menus ask the guest to pick their table from a dropdown before ordering. Guests get it wrong constantly. They read the number off the neighbouring table. They pick "12" when they're on "1B". They skip it and hit "continue" twice. Now your kitchen is cooking blind.

2. Orders arrive anonymous. Without a table, an incoming order is just a list of food. A runner carries it out and starts the world's least professional game — walking the floor saying "chicken? chicken?" Guests notice. It reads as chaos even when the food is perfect.

3. Guests can't add to the order. This one costs real money. A table finishes their first round, wants two more beers, and scans again. With a table-specific code, those beers join the open order on table 12. With a shared code, they start a brand-new order that has no connection to the first one — so now you've got two tickets, two bills, and one confused waiter. Many guests just give up and don't order the second round at all.

4. Splitting the bill turns into arithmetic homework. Splitting a bill is easy when the system knows all six people are on the same table. It's impossible when those six orders are six unrelated tickets scattered through the day.

5. You lose every piece of table-level data. Which tables get scanned most? Which corner of the room nobody orders from? How long between scan and payment on a Friday? A shared code answers none of it. Every scan looks identical.

Shared code vs one code per table

	One code for the whole room	One code per table
Guest types table number	Yes, every time	Never
Wrong-table orders	Common	Rare
Add a second round to the same bill	No	Yes
Split the bill by table	Manual	Automatic
Waiter sees the live bill for a table	No	Yes
Per-table scan data	None	Full
Setup time	2 minutes	About 20 minutes
Printing cost	Identical	Identical

That last row is the point. There's no financial reason to use a shared code. It's purely a "we didn't know" decision.

What you get back

Beyond fixing the obvious, table codes unlock a few things that quietly make service better.

Faster turns. Cutting the "whose food is this?" walk saves maybe 20 seconds per delivered plate. In a 40-seat room doing 120 plates a night, that's roughly 40 minutes of walking, every single night. Not glamorous. Very real.
Waiters can check a table without going to it. Open the table on the POS, see what's ordered, see what's owed. No more walking over to ask if they're ready for the bill.
The bill request goes to the right person. Guest taps "bill please" on table 12, and the waiter for that section knows. No more waving.
Section accountability. When every order is tagged to a table, you can finally see how each section actually performs — which matters far more than most owners think when you're trying to fill dead weekday tables.
Better menu decisions. Table-level ordering data feeds straight into menu engineering. You start seeing that the terrace orders cocktails and the back room orders coffee — and you plan for it.

How to set up table QR codes properly

Here's the order I'd do it in on a slow Monday.

Step 1 — Fix your table names before you print anything

This is the step everyone rushes and everyone regrets. Whatever you name your tables now, you'll be living with for years — on the codes, in the reports, on the POS.

Two rules:

Use the names your staff already say out loud. If your team says "window two", don't call it T17. Nobody will remember T17 under pressure. Matching the spoken name kills a whole category of mistakes.
Add a zone letter for anything outside the main room. T1–T6 for terrace, B1–B4 for bar, M1–M20 for main hall. When someone shouts a number, everyone knows where to look.

Leave gaps in your numbering too. If you ever squeeze two extra tables onto the terrace, you want T7 and T8 free — not a full renumber and a full reprint.

Step 2 — Generate one code per table

In any tool worth using, you pick the branch, pick the table, and it builds the link for you. Do it once per table and download them all.

Two things to get right here:

Use dynamic codes. The code should point at a permanent web link you control, never at a file. If you point at a PDF, changing the menu kills every printed code in the room. That's the number one reason QR code menus suddenly stop working.
Keep the branding light. You can drop your logo in the middle and use your brand colours, but keep the contrast strong and don't overdo the logo size — here's how to add a logo without breaking the code.

Step 3 — Print the table number in plain text under every code

If you take one thing from this article, take this.

Every card, tent, or sticker should have the table number printed in human-readable text, big enough to read from standing height. Something like:

TABLE 12 [ QR code ] Scan to see the menu and order

Why it matters: table tents get moved. A guest slides one over to make room for a pizza. A cleaner stacks them all on the bar and redistributes them. Without a visible number, table 12's code ends up on table 3 and now you're sending food to the wrong people with total confidence. With the number printed on it, anyone can put it back in two seconds.

I'd also write the number on the underside in marker. Belt and braces.

Step 4 — Get the size and placement right

Size is simple: for a table card that people scan from about arm's length, 2 x 2 inches (5 x 5 cm) is the practical minimum, and 2.5 inches is safer with a logo in the middle. Full breakdown in the QR code print size guide.

Placement matters more than most people expect:

Avoid glass tabletops and glossy laminate. Overhead lights reflect straight into the camera and the scan fails. Matte finish, always.
Watch your candle placement. Dim, romantic lighting is lovely and terrible for phone cameras. Test your codes at night, not at 11am.
Terrace tables need weather-proofing. Laminated card or vinyl sticker, not paper. And wind — a light table tent outside is a frisbee.
Bar seats and high-tops count as tables. They're the ones everybody forgets.

Step 5 — Scan every single code before service

Not a sample. Every one. Sit at each table, scan with your own phone, and check the screen says the right table.

It takes fifteen minutes for a forty-table room and it catches the two codes that got swapped at the printer. Do it again after any reprint.

The mistakes that actually cost you money

Codes that expire with a free trial. Some generators quietly kill your link once a trial ends. Every printed code in the room dies at once. Check whether the codes stay live forever before you print 40 of them.
One poster at the entrance instead of table codes. Great for the takeaway crowd, useless for table service. Do both, but don't let the poster replace the table cards.
Printing them on the paper menu. If you already print menus, the code goes on the table, not on the menu — otherwise you're back to reprinting every time a price changes.
Forgetting the Wi-Fi. The second question after "what's the menu?" is always the Wi-Fi password. Put a Wi-Fi QR code on the same card — two codes, one piece of cardboard, half the clutter.
No plan for replacements. They get spilled on. Print 15% extra at the start, keep them in a drawer, and you'll never have a naked table on a busy Saturday.

What it costs

Honest numbers for a 40-table US restaurant in 2026:

Vinyl stickers, printed locally, roughly $0.40–$0.90 each in a batch of 50. Cheapest option, great for outdoor and high-top tables.
Laminated table cards, about $1–$3 each depending on size and finish.
Acrylic table tent holders, $2–$5 each, reusable — you slide a fresh printed insert in whenever you change the design.
Print it yourself on card stock with a laminator: under $0.30 a table.

So a whole 40-table dining room, done well, lands somewhere between $20 and $150. One-time. Compare that to what a single mis-delivered steak costs you, and it stops being a decision.

When you honestly don't need table-specific codes

I'd rather tell you this than sell you something you don't need.

Skip them if:

You're counter service — guests order at the till and carry their own tray. A single code on the counter and a couple on the wall is plenty.
You're takeaway or delivery only. There's no table to tag.
You run a food truck or a market stall.
You're a bar where everyone orders at the bar. Though bar-side table codes for the seated area often surprise people with how well they work.

Definitely use them if: you have table service, you let guests order or pay from their phone, you have a terrace with its own flow, or you run more than one branch and want reports you can actually compare.

Frequently asked questions

Do I really need a different QR code for every single table? If guests order or pay from their phone, yes. The table number lives inside the code — that's the entire benefit. If your menu is view-only and waiters take every order, a shared code is fine, though table codes still help when a guest requests the bill.

What happens if a guest moves to a different table? They scan the new table's code, and the order moves with them — most systems let a waiter transfer an open order to another table in a couple of taps. If two tables get pushed together for a group, the orders can usually be merged into one bill.

Can two tables share one code? They can, but you get all the shared-code problems on a smaller scale. The only case where it makes sense is a pair of tables that are always used as one — like two two-tops permanently pushed together in a corner.

Do guests need to download an app? No. A QR menu opens in the phone's normal browser. Any app requirement is a hard stop for guests and you should treat it as a dealbreaker when picking a tool.

How long does it take to set up 40 tables? About 20 minutes to generate the codes, plus printing time. The longest part is naming the tables properly — and that's the part worth slowing down for.

Are table QR codes hygienic? More than a shared laminated menu that ten people touched today. That's one of the real advantages of QR menus over printed ones, alongside the cost of reprints.

Can I track how many people scan each table? Yes, if your menu tool reports scans by table. It's genuinely useful data — you'll spot the corner table nobody uses and the terrace spot that carries your whole summer.

Here's the thing: nobody switches from a shared code to table codes and goes back. The change is small, cheap, and boring to set up — and then one Friday night you notice nobody's walking the room shouting "carbonara?" anymore.

Give your tables real names. Print the number next to the code. Scan every one before you open. That's the whole job, and it'll outlast three menu redesigns.