QR ordering

A QR ordering system that runs the whole table, not just the menu

Most QR codes in restaurants open a PDF. This one opens an ordering system that the kitchen, the counter and the cash desk are all attached to.

In short

QR ordering means every table carries its own printed code. A guest scans it with the camera they already have, the menu opens in their browser, and the order goes to the kitchen attached to that table — with no app to install, no account to create and nobody to flag down. Every round the table orders joins the same visit, so four rounds still end as one bill.

One printed code per table
No app, no login, no guest download
Orders land on a live kitchen board
Every round rolls into one invoice

Book a 20-minute demo See what it costs

What it fixes, specifically

The slowest part of most meals is not the cooking. It is the wait to be noticed — the gap between a guest deciding they want something and your system finding out. Every minute in that gap is a table you are not turning, and every order that travels on paper or in somebody's memory is a chance to send the wrong dish to the wrong table.

QR ordering closes that gap by moving the order point to the guest. They do not wait for a server to be free, and the order does not wait for a server to walk it back.

No waiting to catch someone's eye, for the first order or the fourth
No wrong table, missed add-on or item nobody rang up
No reprinting a menu because one price changed
No reconstructing the bill from three slips at the counter

What your staff get out of it

The board is the point. Orders appear as they are sent, with a sound alert, and the table board beside it shows the room at a glance — which tables are seated, which have asked for the bill, which are free. Nothing needs refreshing and nobody has to shout across the pass to find out where an order got to.

A live order board with sound alerts, on any device you already own
A live table board: vacant, occupied, bill requested
Guests can call a server, or ask for water or cutlery, from the table
Staff can raise an order by hand for a guest who would rather not use a phone
Move a whole visit — orders and running bill — to a different table

Guests who will not use their phone

Some will not, and that is fine. Your staff can place the order for them from the same system: pick the table, build the order, send it to the kitchen. The bill and the reports do not care how the order arrived, so a table where one guest scans and another dictates still ends up as one clean record.

The same applies at the counter. A parcel or takeaway order is raised by staff in seconds, with a priced review screen before anything commits — same menu, same kitchen board, same reports as a scanned order.

Ordering only where you are actually sitting

A table code is a public thing. If you want, a branch can require the guest's phone to confirm it is at the venue before the menu opens, so a code photographed once cannot be used to order from the next street. It is optional, per branch, and off unless you switch it on.

Location confirmation depends on the guest allowing their browser to share it. It is a control for casual misuse, not a security boundary.

Where QR ordering does not help

It does not replace your staff, and a page that told you otherwise would be lying. Somebody still has to seat the party, carry the food, read the room and close the bill. What changes is that none of those people are also acting as a data-entry step between the guest and the kitchen.

It also needs a connection. There is no offline mode, by design: the guest's phone, the kitchen board and the counter have to be looking at the same floor at the same moment, and that cannot be true of a device that is working from a local copy.

The same visit, from both sides of the pass

01

The guest scans

The table code opens your menu in the browser on their phone — photos, sizes, add-ons and what is actually available right now. Nothing to download and nothing to sign into.

02

They order when they are ready

They build the cart at their own pace, apply an offer if one fits, and send it. The kitchen board picks it up immediately with a sound alert, and the guest can watch it move.

03

Your staff work the floor, not the notepad

Orders arrive priced by your own menu, against the right table. Nobody re-keys anything, and nobody carries an order in their head from the far corner back to the pass.

04

One bill closes the visit

The bill assembles itself as the visit happens. Ask for it from the phone, settle at the table or the counter, print a thermal receipt, and the table is released for the next party.

Questions about this

More general questions — price, commission, data, multiple outlets — are answered here.

How does the QR code know which table it is?

Each table gets its own code, printed once. The code identifies that table, so when a guest orders, the kitchen board shows the order against the right table without anybody typing a number. Branches keep their own tables and their own codes, and a seating area — rooftop, garden, AC hall — numbers its tables within itself, so two areas can both have a Table 5.

Can a guest order more than once during a meal?

Yes, and that is the point of it. Starters now, mains when they are ready, a dessert an hour later — every round attaches to the same table visit. The kitchen sees each round as it is sent, and the guest still gets one bill at the end rather than three.

What if two people at the same table both scan the code?

They both join the same visit. Whoever scans the table is attached to the session already open on it, so two phones ordering at one table produce one order list and one bill rather than two separate tabs to reconcile at the counter.

Does the guest have to make an account or give a phone number?

No. Dine-in QR ordering is anonymous: scanning the table is the whole of the sign-in. There is nothing to install, no password and no verification step between the guest and the menu — which is exactly why they use it instead of waving at somebody.

Can guests order the same thing again without hunting for it?

Yes. A guest can send a past order straight back into the cart, which is what most regulars actually want to do — and it takes the ordering interaction down to two taps.

What happens when the internet goes down?

Ordering pauses until it is back. Everything runs on the server so that the guest's phone, the kitchen board and the counter are always looking at the same floor, and that design has no offline mode. A phone hotspot is normally enough to keep the counter moving. We would rather you read that here than find it out on a busy Saturday.