How to use WhatsApp QR codes on restaurant tables and menus

What a table QR actually does

A guest scans the code and their phone opens WhatsApp with a chat to your own number and a pre-filled first message — something like “Table 6 — I'd like to order.” They press send; your staff reply from the same WhatsApp they use now.

That's the whole mechanism. It's a fast way to start an order request or a reservation request — not a point-of-sale, not a payment page, not a booking engine. The kitchen and front desk stay in charge; the QR just opens the conversation.

A real situation: twelve tables and a takeaway flyer

A neighbourhood bistro puts a unique QR on each of its twelve tables, plus one on the takeaway flyer it tucks into delivery bags. Guests at a table scan to ask about specials or place an order request; flyer scanners ask about collection.

Because every table and the flyer carry their own code, the owner can see that window-side tables ask after starters more often, and that the flyer quietly drives a third of weekday takeaway requests — then prints more flyers, not fewer.

Adding table and source context

The useful part is context. Encode the table number or placement into each code's pre-filled message and source, so an incoming request already says “Table 6” or “Takeaway flyer” without the guest typing it.

Staff see immediately where the request came from, and you get clean attribution by table, menu, or flyer in your reports.

Routing to the right branch or front desk

If you run more than one location, routing sends each scan to that branch's own WhatsApp instead of a single shared number. You can also point reservation requests at the front desk and order requests at the kitchen line, so the right people see the right requests first.

It's still redirect-only — routing just chooses which of your own numbers the guest reaches.

Set up WhatsApp QR codes for your tables

1. Connect your restaurant's own WhatsApp number (or one per branch). 2. Create a smart link with a pre-filled message that fits the placement — “Table 6 — I'd like to order” or “Reservation request.” 3. Add the table or source as the campaign name so requests are attributed. 4. Generate the QR for each table, menu, and flyer, and print them. 5. If you have branches, route each code to the right number. 6. Publish, watch requests by table and placement, and re-point any code without reprinting when a number or promo changes.

Common mistakes

Calling it an ordering system. It opens an order request in WhatsApp; your team confirms, prepares, and takes payment as they always have. Set that expectation on the table card.

One QR for every table. You lose the per-table attribution that makes this worth doing. Give each table its own code.

Printing the raw number. Point at a smart link instead, so you can change the number or message later without reprinting every menu.

How WA.Direct fits

WA.Direct creates the smart link behind each QR, attaches the table or source context, routes the scan to the right branch number, and tracks every scan and click. The order or reservation request itself happens in your own WhatsApp, handled by your staff — WA.Direct never processes orders, takes payments, confirms bookings, or reads the chat. It gets the guest to the right conversation and shows you which tables and menus drive it.