What does a restaurant kitchen display system (KDS) actually do?

A kitchen display system is easy to describe and easy to misunderstand. Described: a screen in the kitchen that shows orders. Misunderstood: a screen in the kitchen that shows orders. The difference is everything that happens around the screen—the order states, the data feeding it, and the habits of the people looking at it.

What a KDS does during a service

Take a Friday at 7:45pm. Orders are arriving from the till, a table QR code and the website within the same minute. A KDS does four things with them:

1. Receives each order as a ticket the moment it is confirmed, whatever channel it came from.
2. Shows context: items, quantities, modifiers ("no nuts", "extra hot"), fulfilment type (table 12, collection at 8:10, delivery zone A) and any allergen note.
3. Moves tickets through states—typically pending → preparing → ready—so everyone can see what is being worked on and what is waiting at the pass.
4. Tells the rest of the system when a ticket is ready, so a collection customer's tracking page updates and front of house knows to run the plate.

That last point is the one paper tickets can never do. A KDS is a two-way participant in the order, not a printout.

What it replaces

• Printed tickets that curl, fall off the rail and cannot be re-ordered when priorities change.
• Verbal relays between the till and the pass, which fail exactly when the room is loudest.
• Marketplace tablets read out by whoever is nearest—if marketplace orders flow into the same board.
• The "is table nine's food coming?" walk from front of house to the kitchen.

What it needs from the rest of your systems

A KDS is only as good as the order record behind it. Three requirements matter more than screen size:

One order record

If the till, the website and the marketplace each create their own version of an order, the KDS becomes a merge exercise. In TableSyncAI, POS, direct ordering and QR ordering create the same order object, so the kitchen board simply shows all of them—and marketplace orders are designed to join the same flow as each integration goes live.

Explicit, one-way states

Pending, preparing, ready. Tickets should move forward, not sideways. If a system lets a ticket bounce between states, the board stops being trustworthy and staff go back to shouting.

Modifier and allergen fidelity

A board that shows "Chicken tikka ×2" but not "no nuts" is a liability. The KDS must display the same modifier and allergen data the customer entered, unedited.

Is your kitchen ready for one?

A short, honest checklist:

• Do you take orders from more than one place (till, phone, web, QR, marketplaces)?
• Do tickets get lost, duplicated or re-shouted at least once per busy service?
• Does anyone currently walk to the kitchen to find out whether an order is ready?
• Would collection customers benefit from knowing their order is actually ready?

Two or more "yes" answers and a KDS will pay for itself in fewer remakes and calmer services. One or none, and a good printer may be fine for now.

Common mistakes

• Buying the screen before fixing the order flow. A KDS fed by three separate systems just displays the chaos in higher resolution.
• Too many states. Six statuses look thorough in a demo and are ignored in service.
• No "ready" hand-off. If marking a ticket ready changes nothing for anyone else, staff stop doing it.
• Ignoring the pass. The board must be readable from where food is plated, not from the office.

Frequently asked questions

Does a KDS replace the POS?

No. The POS takes orders and payments; the KDS displays and progresses them. They should share one order record.

Can marketplace orders appear on a KDS?

Only if the marketplace order enters the same order flow. That is one of the main reasons restaurants look at marketplace aggregation.

Do I need special hardware?

A robust tablet or touchscreen in a splash-safe mount is usually enough. Readability and placement matter more than specification.

Related reading: The complete guide to restaurant online ordering · POS on TableSyncAI · QR ordering.