2 × Risotto
Nuts
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 kitsT7
Salad× 2
OrderPending
Approve the request to send it to the kitchen.
Usage example · illustrative data
QR orders / 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.
Explore the connection: Digital menuGuests see the dish, availability and allergens on their phone.
Usage example · illustrative data
QR orders / 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.
T7
Salad× 2
OrderPending
Approve the request to send it to the kitchen.
Usage example · illustrative data
How it works during service
- 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.
QR orders / 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.
Explore the connection: Kitchen display1 × Fish
1 × Salad
—
T7 · Preparation
Mark T7 as ready and follow it into the next column.
Usage example · illustrative data
What you can manage
- 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