QR orders
The table orders. The floor still runs the room.
A guest scans the table QR, builds a ticket on their phone, and the floor approves it. Kitchen gets a real ticket, not a WhatsApp screenshot. You keep the pace.
Included in · Main & Chef’s Table
See the kits
Table T7 · order from your phone
Floor is reviewing it
On a busy night
How Waiter actually uses it.
01
They scan the table
Not a generic PDF. The carta of this venue, this service, this table.
02
The floor reviews
A chime. The waiter opens the pending ticket, checks the table, sends it or sends it back.
03
The pass treats it as a ticket
Timer, coursing, allergy banner. Payment still closes on the POS, with the guest card attached.
01
Order from the chair
Each table has its own QR. The guest sees the live carta: available dishes, allergens, prices. They send. The floor decides when it is real.
02
Approval, not chaos
A pending ticket waits for the waiter. Reject with a reason, or send it to the pass. Nobody fires a second steak because a child mashed a button.
03
One ticket, one kitchen
Approved QR orders land on the same KDS as waiter tickets. Coursing, allergies, VIP: same language. The pass does not run two systems.
What's inside
Everything you get with QR orders.
- Unique QR per table, tied to the floor plan
- Live menu: 86s and allergens included
- Floor approval before the kitchen sees it
- Reject with a reason the guest can read
- Sound and counter for pending tickets
- Same ticket the POS and KDS already know
“We put QR on the terrace so two waiters could hold forty covers. The kitchen never knew which tickets came from a phone.”
Same role, next screen