What a KDS is, and when it beats paper
A kitchen display system replaces printed dockets with screens showing live tickets, each item routed to the station that cooks it, with a timer running from when the order was placed. It is worth the change when you run more than one ordering channel, have more than one cooking station, or need to know how long things actually take.
Paper remains genuinely fine for a single-station kitchen with one order channel and short tickets. The case for a screen strengthens sharply with each channel and each station you add — a printed ticket cannot tell you it has been sitting for eleven minutes, cannot split across two stations, and cannot be un-printed when the guest cancels.
Planning station routing
This is the part that determines whether the rollout works, and it is done before any screen is mounted.
- Map your stations as they actually are. Not the org chart — the physical positions people stand in during service.
- Assign every menu item to a station. Tedious, unavoidable, and the source of most launch-week problems when skipped.
- Decide what the pass sees. Usually every station's items on one ticket, so somebody owns whether the whole order is ready.
- Handle multi-station items explicitly. A composite plate touching four stations needs a rule for when it counts as done.
- Decide the timing basis. Time since ordered, or time since the station started? They produce different behaviour under load, and cooks will notice.
What belongs on a ticket
- Legible from three feet. The single most common design failure is a screen that looks fine on a laptop and is unreadable across a hot line.
- Modifiers next to their item, visually distinct, never in a separate block.
- The channel — counter, kiosk, delivery — because it changes packing and timing.
- Elapsed time, prominent enough to be seen without looking for it.
- The language the station reads. In a multilingual kitchen this is a throughput feature, not a courtesy: reading a second language costs a beat per ticket, and the errors land on the plate.
Rolling it out
- Run paper and screens together for a week. Cheap insurance, and it surfaces routing mistakes without risking service.
- Start on your quietest shift. Never launch into a Friday.
- Let the line choose the bump method. A bump bar is faster than a touchscreen for anyone with wet or oily hands, and the crew will tell you which they want if asked.
- Expect week one to be slower. Muscle memory is real. Judge it in week three.
- Keep a printer. Even as a fallback, it removes the fear that makes crews resist the change.
Where ThaliPOS fits: station routing, elapsed-time cues, batch cooking, refire, bump bars, ESC/POS printers alongside the screens, and eight display languages set per station. The ThaliPOS KDS →