Quick answer:
A kitchen display system, shortened to KDS, is a screen that replaces printed order tickets with live digital cards. Orders arrive from the point of sale, appear on the right station’s display, and get cleared with a bump when the food goes out.
The benefit is not saved paper. A KDS shows exactly how long every order has been waiting and changes color when that time gets too long, turning a rail of identical slips into a queue with a visible priority.
A kitchen display is one of the few pieces of hardware that changes how your kitchen runs rather than just what it runs with. That is also why a bad installation disappoints.
A KDS enforces a workflow whether your team agrees with it or not, and a screen configured to mirror the old paper habits delivers almost nothing. Here is what the system does, how it routes orders, and what changes on a busy service.
What is a Kitchen Display System? The Basics
A KDS is a screen, a bracket, and software that receives orders from the till.
When an order is sent from the counter, a handheld, or an online channel, the KDS shows it as a card: the items, the modifiers, the table or collection reference, and a timer counting upward. The timer is the feature that matters most, because it is the measurement paper never provided.
Staff clear completed items using a bump bar, a row of physical buttons mounted below the screen, or by touching the screen directly. Bump bars survive a hot, wet kitchen better because they can be wiped down and pressed with a gloved hand.
The display is the visible part and the routing is the useful part. A KDS decides which station sees which item, so a burger and a milkshake on the same order appear on two different screens without anyone splitting the ticket by hand.
KDS vs a Kitchen Printer
The comparison is with an impact printer on the pass, which is what most kitchens replaced.
| Kitchen printer | Kitchen display system | |
|---|---|---|
| Order timing | Invisible, unless someone reads the print time | A live timer per order, color coded |
| Routing | One printer per station, tickets split by hardware | Software routing, changeable in settings |
| Changes to an order | A second ticket prints, the first stays on the rail | The card updates in place |
| Lost tickets | Common, and invisible until a customer asks | Not possible, the order stays until bumped |
| Reporting | None | Prep times per item and per station |
| Consumables | Paper and ribbons | None |
The third row is the one that causes real service failures. A modified order on paper produces two tickets that contradict each other, and the kitchen has no way to know which one is current.
The fourth row is the one owners notice. A ticket that slides off the rail becomes a table waiting forty minutes for food nobody is cooking. Kitchens that keep a printer usually keep it as a backup, and it should be an impact model rather than a thermal one, for the reasons set out under receipt printers.
How Orders Are Routed
Routing is the configuration that determines whether a KDS helps or simply moves paper onto glass.
- By station: grill items to the grill screen, cold items to the larder, drinks to the bar. The standard setup for anything above a single-section kitchen.
- By course: starters released immediately, mains held until the pass fires them. This is what stops a table getting everything at once.
- By channel: delivery orders separated from dine-in, so a courier waiting at the door is visible against a table that is not.
- By prep time: longer items released first so a plate finishes together, which is the hardest to configure and the most valuable when it works.
The expediter screen at the pass ties these together, showing the whole order across every station. Without a pass screen the kitchen has stations and no coordination, which is the most common way a KDS installation disappoints.
Routing depends on the till and the screen agreeing about the menu, which makes a KDS a practical example of a POS integration rather than a standalone purchase.
What a KDS Changes on a Service
Take a 60-cover restaurant doing 110 covers on a Friday night with a two-section kitchen.
On paper, the pass reads a rail of tickets and judges priority by position and memory. When a table complains, nobody can say how long the order actually waited, because the only timestamp is the moment the ticket printed.
On a KDS, each order carries a live timer, and the screen turns amber then red against thresholds you set. A ticket at 18 minutes is visibly different from one at 4 minutes, from across the room, without anyone reading it.
Afterward the system reports average prep time per item. If the burger averages 14 minutes against a target of 9, that is a menu problem or a station problem, and it is now measurable rather than argued about.
The takeaway is that a KDS converts opinions into numbers. The saving on paper is trivial. The value is knowing which item is slowing the pass, which is the same reason kitchens track par levels rather than guessing at prep quantities.
What to Check Before Buying a KDS
Four questions decide whether the screens earn their place.
Is it built into the POS or bolted on? A native KDS shares the menu automatically, and a third-party one needs the item list maintained in two places, which drifts within weeks.
How many screens does the license cover? Pricing is usually per screen, so a three-station kitchen plus a pass is four charges, not one.
What happens if the network drops? A screen that loses the connection mid-service is worse than paper, so check the behavior against POS offline mode before you commit.
Is the hardware rated for a kitchen? Consumer tablets fail quickly near heat and steam, and a screen that cannot be cleaned properly becomes a hygiene problem rather than a hardware one.
One further question is worth asking of the kitchen rather than the vendor. A KDS only works if staff bump orders honestly, and a screen that gets cleared early to keep the timers green produces reporting that looks excellent and describes nothing. The numbers are only as good as the bumping discipline, which makes the rollout a training exercise as much as an installation.
Systems Worth Comparing
Kitchen displays are sold as part of a restaurant platform rather than separately, so the KDS decision usually follows the till.
Toast builds its kitchen displays into the platform and targets full-service restaurants where routing and course firing matter.
Lightweight operations may not need a dedicated screen at all, and the comparison in Lavu versus SpotOn covers two systems aimed at different ends of that range.
For the wider shortlist, start with POS systems for restaurants, or pizza POS systems where prep-time routing carries most of the value. Budget context sits in restaurant POS system cost.
