The kitchen's own screen: what to cook, in what order, and how long it has been waiting — without a printer full of curling paper.
A check sent from the floor is on the kitchen screen immediately, with its table and its time.
Drag an item to change its status; every other screen — the waiter's included — updates at once.
A ticket can still print automatically on the station's own printer, for the sections that prefer paper.
Timers show how long each item has been open, so the oldest ticket is obvious rather than remembered.
The narrowest role in the system, deliberately. A cook's account reaches the kitchen and the menu it cooks from, and nothing about money or people at all.
Roles are yours to define: these are the defaults a new organization starts with, and every line above is a permission you can grant or revoke.
An order cannot fall behind a counter or print on a machine that ran out of paper. It stays on the screen until someone closes it.
A waiter can see that an item is ready without walking to the pass, which is the interruption that costs a kitchen most.
How long each item took is recorded, so the kitchen report shows where service slows down instead of who people think is slow.
The parts of the system this role spends its day in.
Only if you want one. Tickets can print automatically on the printer assigned to a station, and the screen works with no printer at all.
Yes — items are grouped so the grill and the bar see their own work rather than the whole order.
The board reconnects and reloads the current orders when it wakes, so nothing is missed while the screen was off.
Yes, recipes included, which is usually what a new cook needs. What that account cannot do is change anything in it.
The same system, seen from a different job.
Create an organization, invite the team and set what each of them reaches. No credit card required.
Start free →