QR code ordering for guests who would rather not wait to catch an eye

Where QR ordering fits, and where it does not

The honest answer is that it fits the places where guests already feel slightly ignored. A busy café at 8:30 on a weekday, where the queue stalls because people read the board at the till. A pub garden on a warm evening, where the walk from the bar is long and the staff cannot see who wants another round. A food court, where the customer sits far from the stall and has no intention of queuing twice. A hotel pool, where nobody wants to get up.

It fits less well where the conversation with the server is part of what people pay for. A tasting menu, a wine list that needs explaining, a neighbourhood place where the owner takes every order and knows every regular. In those rooms a view-only QR menu for reference is plenty, and the ordering can stay with the person.

Many restaurants land somewhere in between: ordering on the terrace, paper inside; ordering at lunch, servers at dinner. Because the code does not change, you can switch ordering on and off by time of day without reprinting anything.

Setting up table codes

Give every table its own code rather than one code for the room. It costs a few more minutes of printing and saves you from every order arriving as “unknown table”. Number the cards visibly, use a holder that does not slide off, and print a spare set, because cards get spilled on.

Test the codes under the lights you actually serve under. A code that scans at noon by the window can fail at 9pm under a warm bulb on a glossy card. Matte card, a 3 cm code or larger, and a white margin fix most scanning problems. The free QR generator produces print-ready files and has sizing notes.

Handling the guest who wants to pay another way

Some guests will not want to pay online, and some will not have a phone. Keep the ordinary path open: a server takes the order and payment through your POS. This is not a failure of the system; it is why the floor team is still there. The order screen will show the QR orders and the servers will know about the others, and on most nights the mix sorts itself out.

Training the team for the first week

The first week is about habits, not software. Tell every table the code is there, because a card on a table reads as decoration until someone mentions it. Agree who watches the order screen during service and who runs the food, so an order for table 9 does not sit accepted and unread while both people assume the other saw it. Keep the check-back: a guest who ordered from their phone still wants to be asked whether the food is right, and that visit is where the second order gets prompted. And give the floor team a line for the guest who scanned the wrong card: “No problem, I will have it sent to the right table,” then fix it at the screen.

Keeping the menu honest

QR ordering is unforgiving about stock. On paper, a server can say the lamb is finished. On a phone, a guest will order the lamb, pay for it, and then be told. Make switching an item off part of the pass routine: when the last portion goes out, the person calling the pass marks it sold out from their phone. It takes five seconds and prevents the single most common complaint about ordering from the table.

The same goes for prep times during a rush. Set them realistically on the order screen so the guest who orders at 1:10 is not expecting food at 1:15 on a full terrace. A longer honest time beats a short broken one.