QR Codes for Restaurant Tables
A table QR code has one job: put the menu in the hand of somebody who has already sat down. The hard part is not the code, which takes a minute. It is that most table codes point at a PDF that was right in March, and the whole thing rots.
Build the menu first
Make a Menu page
In Landing Pages, create a page and pick the Menu template. It is a menu, not a page about your restaurant - courses, dishes, prices, read one-handed on a phone.
Mark the dietary options yourself
Tag dishes v, vg, gf, df or n where you know it. Nothing infers these, on purpose. A guess on a menu page is a guess somebody with an allergy is trusting.
Publish, then make the code
Publish the page, then open the QR code panel in the editor. Download the table tent and print it, or have proper ones posted to you.
Why this one does not rot
The printed code does not encode your menu's address. It encodes a short floatmessage.com link that forwards to whichever page you point it at. Two consequences worth having:
- Edit the menu whenever you like. The page changes; the printed tents are already correct, because they never named the menu - they named the link.
- Swap the menu entirely. Build the autumn menu as a new page, repoint the code, and fifty tents start opening it that evening.
Getting the print right
- Print at 100%, not Fit to page. Fit to page is the single most common reason a printed code scans badly.
- A table tent is read at arm's length, so the A4 fold-over is plenty. A window needs the bigger A5.
- Say what it is. “View our menu” next to the code outperforms a bare square, because people do not scan things when they cannot tell where they go.