--- title: "Kitchen Display System (KDS) Explained: Stations & Timers | GoSufra" description: "What a KDS actually replaces, how tickets reach the right station, what Rush and VIP lanes are for, and why prep timers change kitchen behaviour more than any rule posted on a wall." url: "https://gosufra.com/en/blog/kitchen-display-system-explained/" language: "en" source: "https://gosufra.com" --- # The kitchen display system, explained: stations, priority lanes and prep timers What a KDS actually replaces, how tickets reach the right station, what Rush and VIP lanes are for, and why prep timers change kitchen behaviour more than any rule posted on a wall. 2026-08-29 · 7 min read ![Illustration of live kitchen tickets with a done tick and a prep timer](https://gosufra.com/blog/kitchen-display-system-explained.svg) ## Key points - A KDS is not a screen that prints less paper. It is a queue with a status per item. - Stations let each section see only its own work, which is what removes the shouting. - Rush and VIP lanes are for exceptions — used on every ticket, they mean nothing. - Prep timers turn late tickets from an argument into a number you can act on. Paper tickets fail quietly. One curls off the rail, one is written in handwriting only the day shift can read, and one is simply never picked up. Nobody notices until a guest asks where their food is. A kitchen display system replaces the paper — but calling it a screen instead of a printer misses what it is actually for. ## A KDS is a queue with a status Every ticket on the screen has a state, and so does every item on it: | Ticket state | Meaning | | --- | --- | | Queued | Received, nobody has started | | In progress | Someone has started cooking | | Ready | Waiting to be run to the table or bagged | | Served | Handed over — off the active board | Because each item carries its own state too, a four-item ticket can have two items ready and two still cooking, and the pass sees exactly that without asking anyone. ## Stations are the point The biggest change is not the screen — it is that the grill sees grill items, the salad line sees salad items, and neither has to read past the other’s work. A ticket is split by station on arrival. Each station shows its own queue in the order it should be worked; the pass sees the whole ticket assembled. That is what removes most of the shouting from a kitchen: nobody is reading someone else’s job off a shared rail. ## Priority lanes, used sparingly Tickets can carry a priority: **Normal**, **Rush** or **VIP**. A rush ticket sorts to the top of its station’s queue; a VIP ticket is flagged visually as well. The discipline matters more than the feature. If a manager marks every third ticket as Rush, the lane becomes decorative and the kitchen learns to ignore it. Priority should mean a real exception — a re-fire, a table that has already waited, a guest the owner asked you to look after. ## Prep timers change behaviour Each ticket carries an estimated prep time and a running clock from the moment work started. That one number does three things no wall poster ever did: 1. It replaces “that order took ages” with “that order took 19 minutes.” 2. It shows *where* the time went — eleven minutes queued before anyone started is a staffing problem, not a cooking problem. 3. It gives the floor an honest answer for the guest. Over a week, the completed-ticket history becomes a picture of your kitchen’s real capacity by hour — the input you need before you argue about the roster. ## Chef assignment and accountability A ticket can be assigned to a specific chef. This is not surveillance; it is how a busy kitchen avoids two people starting the same dish while nobody starts the other one. It also lets the history answer a question that is otherwise pure opinion: which section slows down first when the room fills. ## What it looks like on the floor The kitchen display runs on any screen you already have — a cheap Android tablet on a stand, a TV with a small box behind it, or a laptop. Tickets arrive in the same second the order is taken, because the POS, the waiter app and the kitchen display are one system rather than three products passing messages. And when the internet drops, the till keeps taking orders. Tickets created offline arrive as soon as the link returns, in the order they were really placed. ## The rule that makes it work Turn the kitchen printer off once the screens are trusted. Running both is the common mistake: staff learn that neither is authoritative, and you get the failure modes of paper *and* the cost of screens. Pick one source of truth. Then let the timers tell you what is actually slow. - kitchen display system - KDS - restaurant kitchen software - prep time ## In the product ### [Kitchen Display System](https://gosufra.com/en/features/kitchen-display-system/) Explore ## Run all of this from one system POS, kitchen, inventory, recipe costing, staff and accounting — connected, and free to start. [Create your free account](https://app.gosufra.com/register?lang=en) ## Related articles ![Illustration of six tiles wired back to one hub](https://gosufra.com/blog/six-connected-apps.svg) How it works 2026-08-31 · 7 min read ### [The six apps, explained: who gets which screen and why](https://gosufra.com/en/blog/six-connected-apps/) Manager dashboard, POS, kitchen display, waiter, driver and customer app — what each one is for, who logs into it, and how one order moves through all six. Read article ![Illustration of a floor plan with one table flagged](https://gosufra.com/blog/table-management-and-waiter-app.svg) Operations 2026-08-22 · 7 min read ### [The floor plan, the waiter app and the four states a table can be in](https://gosufra.com/en/blog/table-management-and-waiter-app/) How table status, waiter assignment, merges and split bills work together, why 'waiting for bill' deserves its own state, and what reservations should do about no-shows. Read article [← All articles](https://gosufra.com/en/blog/) [Contact us](https://t.me/GoSufraSupport)