Kitchen Display System Setup: A Practical Guide

A kitchen display system setup starts with your kitchen's handovers, not the screen on the wall. A KDS presents order information to preparation areas, but the team still needs a shared understanding of who owns each item and when an order is ready. The most useful configuration reflects how your kitchen actually works.

Walk one typical order from entry to collection. Include drinks, modifiers, different preparation stations, and the final check before food leaves the kitchen. Write down each handover. This gives you a routing plan and a useful set of test orders before you change the live service.

Map preparation stations and responsibilities

Decide which items should appear at the grill, cold station, drinks station, or other preparation areas. Then define whether a separate expediter view is needed to bring the order together. Avoid sending every item to every display just because the system permits it; excessive information makes ownership harder to see.

For example, a burger and a cold drink may need separate preparation views but a shared order reference at handover. Confirm how combo meals, add-ons, and changed items appear. A routing rule is only useful if a member of staff can explain why the ticket arrived at their station.

Make modifiers easy to recognise

Test long item names and realistic combinations of modifiers. Staff should be able to distinguish the original item, requested changes, notes, and order channel without opening several screens. Keep the wording consistent between the menu, order entry, and kitchen display.

Use the restaurant's established process for handling allergies and special requests; a display note is not a substitute for staff communication and approved procedures. Check what happens when a modifier is changed after the ticket has already reached the kitchen.

Agree on what each status means

Decide when an order moves from received to preparing, prepared, checked, and handed over. Different products offer different states, so map your workflow to the available controls rather than assuming a particular button exists. A completed station ticket may not mean the whole order is ready for collection.

• Name the person responsible for the final order check.
• Define how cancelled and changed items are communicated.
• Test whether a completed ticket can be recalled.
• Establish a fallback for a display or network interruption.

Keep a distinction between preparing food and handing it to a guest or driver. Marking an order collected too early can create confusion at the collection counter even when the kitchen has finished correctly.

Run realistic tests before a busy shift

Test a dine-in order, a takeaway order, a split-station order, a cancelled item, and an order with several modifiers. Include a duplicate submission and a reconnect scenario if your provider supports those tests. Ask both kitchen and floor staff to explain what they see.

Begin with a supervised service and keep your agreed fallback available. Record unclear tickets and routing mistakes, then change one rule at a time. Review the preparation and handover delays alongside staff observations; a timer alone cannot tell you whether a dish waited for another station or was prepared incorrectly.

What should you ask a KDS provider?

Ask for a demonstration using your own menu and exception scenarios. Confirm routing controls, available order states, supported hardware, failure behaviour, and reporting definitions. Compare those answers with the needs of your kitchen before committing to a configuration.