The angle problem
A table tent leans back, and a seated guest looks down at it. That combination photographs the code from above at a slant, which foreshortens the pattern.
- Keep the tent's face at roughly 60 to 70 degrees from the table, not the near-flat lean most stands default to
- Position the code in the upper half of the face, closest to the reader's eye line
- A5 or A6 tents want a 4 to 5 cm code, which is larger than most designs allow for
- Weight the base. A tent that slides when someone leans in is a tent that gets pushed to the far end of the table
- Matte finish, because restaurant lighting is warm, low and directly overhead, which is the worst combination for gloss
Three moments, three offers
Print a two-sided or three-panel tent and let the guest pick:
- On arrival: the menu and the WiFi code. WiFi is what makes the tent worth looking at in the first place, and it is the one code guests thank you for.
- During: ordering and reordering, which is where table-side ordering pays for itself. The table ordering explainer covers how the table identity gets attached to the order.
- At the end: paying, tipping, and the review code. Never lead with the review; a review request before the food arrives reads as desperate and gets the wrong rating.
One code per table
It costs slightly more to print and it changes what you can see:
- Orders arrive with a table number attached, which is the entire point of table-side ordering
- Feedback becomes traceable to a section, which means to a server and a shift
- You learn which tables turn slowly and which parts of the room never get scanned, which is a seating-plan insight nobody had before
What guests hate, and how to avoid it
QR menus earned a bad reputation for good reasons, and most of them are fixable. The menu mistakes guide lists them in full, but the three that matter here:
- A PDF is not a menu. Pinching and zooming on a phone at a dinner table is why people ask for paper. Use a mobile page.
- Keep printed menus available. The code is a convenience, not a filter on who gets to eat.
- Do not demand an app, a login or an email before showing the food.
Keep it current without reprinting
A dynamic code lets the same tent show today's specials, switch to the brunch menu at eleven, and become a holiday-hours notice in December. Table tents are printed in the hundreds, and every reprint avoided is real money.
Design a table tent QR code in 4 steps
Fix the angle and size
60 to 70 degrees from the table, code in the upper half of the face, 4 to 5 cm across, matte finish.
Split the tent by moment
Menu and WiFi on arrival, ordering during, payment and review at the end. One face per moment.
Give every table its own code
Table identity attaches to orders and makes feedback traceable to a section, a server and a shift.
Point it at a mobile page, not a PDF
A pinch-and-zoom PDF is the reason guests ask for paper menus back.
Frequently asked
How big should a QR code be on a table tent?
4 to 5 cm on an A5 or A6 tent. It is scanned from arm's length at a downward angle, which needs more size than a flat surface at the same distance.
Should the table tent show the menu or ask for a review?
Both, on different faces. Menu and WiFi on arrival, review at the end. A review request before the food arrives gets a worse rating than no request at all.
Is one QR code per table worth the extra printing?
Yes, if you take orders by scan. Table identity attaches to the order automatically, and feedback becomes traceable to a section and a shift.
Why do guests dislike QR menus?
Because too many are PDFs. A pinch-and-zoom document on a phone at dinner is worse than paper. A mobile-first menu page removes almost all of the objection.
Do we still need printed menus?
Yes. The code is a convenience for the guests who prefer it, and paper stays available for everyone else. Treating the code as the only option is what generates complaints.
Read next
Need a different QR type? Browse all 48 QR types on the home page.
