QR Codes for Restaurants
A table-tent QR code that links to a menu is common enough to be invisible at this point. The part almost no generator actually solves is what happens after it's printed: your menu changes, and the code is already glued to fifty tables.
One code, a page you actually control
The business-page QR type builds a single page for your restaurant: name, tagline, a description, your hours, an address with a plain "Open in Maps" link, phone/email/website contact buttons, and a link list you can point at a PDF menu, an online-ordering page you already use elsewhere, or your social profiles. Because it's a dynamic code, every one of those fields can be edited after the code is printed — the QR pattern on the table never has to change.
To be direct about scope: this builds a real, editable business/menu page, not an ordering system, a reservations flow, or a payment page. If your menu link is a PDF you host elsewhere or a link to an existing ordering platform, point the business page at it — the QR code's job is getting someone from the table to the right page, not replacing the tools you already use for the rest.
Seasonal menus, without a reprint
Pair the business page with an expiration date and you get the actual seasonal-menu workflow: set the code to point at your winter menu, set it to expire the day your spring menu launches, and update the destination that same day. Anyone scanning an old printed table-tent after the switch lands on a plain "this has changed" message rather than a menu with prices and dishes you no longer serve — the failure mode you'd get from a static QR code with no expiry at all.
The same mechanism works for a limited-time special: set a scan-count limit instead of a date if you only want the first however-many scans to see a promotion, or use both together.
Knowing whether the table-tents are being used at all
Every scan of a dynamic business-page code is recorded the same way as any other dynamic link — see what's actually tracked. For a restaurant that mostly means one honest, useful question answered: are people at the tables actually scanning the code, or is it being ignored in favor of asking the server for a paper menu? That's a real, low-effort signal worth having before investing more in table-tent design or placement.
Frequently asked questions
Does this build an online ordering system?
No. The business page is a menu/info/contact page you control. If you already use an ordering platform, link to it from the business page's link list — this doesn't replace it.
Can I use one code for all my tables, or does each table need its own?
One code works fine for every table if you just want to link to the same menu. Separate codes per table (or per zone) only matter if you specifically want to know which physical spot scans are coming from — see the multi-placement tracking guide for that workflow.
What happens to the printed code when the menu changes?
Nothing — that's the point. You edit the destination in your dashboard; the printed QR pattern is unchanged and keeps working.
Is the business-page type available on the free plan?
See the pricing page for exactly what's included at each tier.