Kitchen Display System for Restaurants
Orders reach the right station the moment they're placed. And when the food is actually ready, the system already knows which waiter to tell.
Why it matters
Most kitchen display systems solve the first half of the problem: getting the order onto a screen instead of a printer. The half that costs you money is what happens after the food is plated — it sits under the pass while someone shouts, or waits for a waiter to walk past and notice. That gap has never been measurable, because "the kitchen was slow" and "nobody collected it for four minutes" look identical on a receipt.
Gueridon closes the loop. A station marks its part done, and once every station owing something on that order has reported, the order flips to Ready and the waiter responsible for that table gets told — on screen and audibly, without anyone shouting.
How an order moves through the kitchen
The order routes itself
Each menu item carries a station, either set on the item or inherited from its category. Anything without one goes to the kitchen. A single order can therefore split across the grill, the bar, and the pass without anyone sorting it by hand.
Each screen shows only its own work
A display is pinned to the stations it serves, so the bar sees drinks and the grill sees grill. Pin nothing and the screen becomes the pass — it sees every ticket in the venue. Pinning is per screen, so several tablets in one kitchen each show something different.
Stations report, the order decides
A station presses Mark ready for its part. The order only becomes Ready when every station that owes something has reported — until then the ticket shows exactly who it's still waiting on, by name.
The right waiter gets told
Ready triggers a notification to whoever claimed that table. If nobody claimed it, everyone on shift assigned to that section is alerted; if that's empty too, it goes to the whole floor and is labelled as such, so nobody assumes someone else has it.
It keeps asking until collected
The alert is a banner that stays put, not a toast that fades while the kitchen is busy, and it comes with an audible chime. If the order is still sitting there after five minutes it chimes again, and again at ten.
Every close has an undo
Marking a ticket ready or served clears it from the board immediately but holds the change for thirty seconds. A misfire is one tap to take back, and nothing has been written yet — so no stock is deducted and no waiter is alerted in error.
Kitchen timing you can actually act on
Because each station stamps its own start and finish, and the order stamps when it became ready and when it was handed over, the reporting can separate three things that used to be one number: how long the cooking took, how long the food waited under the pass, and which station the rest of the kitchen was waiting on.
Kitchen timing reports median and 90th-percentile prep time per station, how often each station was the last to report, and how many minutes that cost. Prep times are also bucketed in five-minute bands, because a median hides the tail — and the tail is what guests remember. Orders closed without any station reporting are counted and shown separately rather than folded in, so you can see what fraction of service the numbers actually describe.
Common questions
Do we have to set up stations to use it?
No. Without stations the board still works as a single queue and orders move from preparing straight to served, exactly as before. Stations, and the Ready step that comes with them, only switch on once you define them.
How does it know which waiter to notify?
Staff claim their own tables from the staff portal for the duration of a shift — it isn't assigned from the back office. That claim is what the alert follows. Where there's no claim, it falls back to whoever is rostered to the section, then to the whole floor.
What about counter and kiosk orders with no waiter?
Those deliberately notify nobody. A kiosk order has no table to deliver to, so the guest watches the pickup board instead of a member of staff being pulled away.
Can a station take a ticket back after marking it ready?
Within the thirty-second undo window, yes. After that the timestamp stands — the stamps are written once, so a ticket reopened later can't quietly rewrite how long the first attempt took.
What happens if a station runs out of something mid-service?
A manager can pause a station from the display, and new items stop routing to it until it's resumed. Staff tablets don't show the control.
Does it replace our ticket printer?
It's built to. The display is the queue — there's no print step in the flow — though a printed backup can run alongside it during rollout.
What happens if the internet drops?
The board updates over a live connection and reconnects on its own, refetching everything it missed rather than resuming half-informed. While it's disconnected it says so, instead of showing a stale queue that looks current.