The only screen the kitchen should have to read.
Live tickets as cards and nothing else, with a sequence a busy hand cannot break.
No skipping a step
Placed, accepted, cooking, ready, done. Nothing can be marked ready that nobody started.
A table’s orders stay together
Guests order in waves, and each wave stays grouped so a second round of drinks is not folded into somebody’s entrée.
Pre-orders wait their turn
An order for 7pm sits above the line and drops in when it is time to start it.
Only this location
Cooks see their own kitchen and nothing else. Usually the reason a brand new screen looks empty.
Notes where they are useful
Order notes and special requests both print on the card. If one dish keeps causing trouble, turn requests off on that dish.
What the kitchen sees
It arrives
The moment it is ready to cook, whichever channel it came from.
Somebody starts it
One tap, and the customer’s phone says so.
It gets called
Ready puts it on the pickup screen and the driver’s phone at the same second.
It clears
Done, counted, and out of the way.
One screen. One tap per step.
All of this works today. If something here does not match how you actually run, tell us before you buy rather than after.
- Steps
- Placed → accepted → cooking → ready → done
- Grouping
- By table, by round
- Pre-orders
- Held until it is time
- Hardware
- Any screen with a browser
Run your next service on one system.
Build the whole thing on Build & Test for two months at no cost, with every feature unlocked. Move to a paid plan when you are ready to take money.