Skip to content
Back to blog tecnologia

Kitchen Display Systems (KDS): When a Restaurant Should Drop the Paper Ticket

By Pablo Bouzon · 1 September 2026 ·5 min read
Kitchen Display Systems (KDS): When a Restaurant Should Drop the Paper Ticket

Paper tickets don’t fail because they tear. They fail because they can’t tell you how long table 7 has been waiting, and because once one slips behind the grill it stops existing for everybody. A kitchen display system — a KDS — solves exactly that, and not much more than what you’re about to be sold.

This article is about when a kitchen display is worth it in a restaurant, and what to demand from one. I’m writing it from the uncomfortable side: we built ours, then measured what it got wrong.

The one thing paper can’t do: keep track of time

A printed ticket is a still photo. The moment it leaves the printer it knows nothing: not how long it’s been hanging, not whether table 7 came in before table 4, not whether it has two dishes left or none. All of that lives in the section chef’s head, and it’s lost entirely at shift change or in a rush.

A screen holds three things paper can’t:

  • The age of every ticket, live. Ours warns at 10 minutes and flags a delay at 15; the card changes colour on its own.
  • First-in-first-out order that nobody has to defend. Paper gets reshuffled by hand; a screen doesn’t.
  • One explicit exception to FIFO: “rush”. It’s the only one the industry recognises, and it should be a timestamp rather than a switch — between two rushed tickets, arrival order takes over again.

KDS vendors quote ticket-time improvements of around 20% when kitchens move from paper to screen. Treat that for what it is — a claim from an interested party — but the mechanism behind it is real: what gets measured gets sequenced.

The flaw almost no KDS demo shows you: the ticket born off-screen

When we reviewed ours with actual cooks, the problem wasn’t the one we expected. On a landscape tablet they could see two and a half tickets and had no idea about the ones arriving below. Measured with 7 tickets and 50 lines on a real tenant, the result was fairly humbling:

  • The navigation sidebar ate 196px — 19% of the width on a screen that never navigates anywhere. It cost a whole column. Today /cocina runs in kiosk mode: no sidebar, no surplus headers.
  • The ✓ Done button sat on a row of its own: 42 of every line’s 71px were that button. With 70 lines on the board, that’s half a screen of buttons.
  • The grid stretched every row to the tallest ticket: a 3-line ticket rendered at 1,306px with 630px of blank card. In newspaper-style columns, that same ticket takes 338px.
  • And the real one: a new ticket is always born at the bottom (oldest-first ordering), which means off-screen — and it carried no marker at all. It just played a chime.

From 1,306px down to 737px on an 11-line ticket, and from 2 columns to 3 at 1024×768. None of that is a feature you’ll find in a comparison table, and it’s what decides whether a cook trusts the screen or asks for the paper back.

What to demand from a KDS because of this: a “new” badge that doesn’t expire on its own (it clears when someone touches the card — that touch is the acknowledgement), a pinned “N more tickets below ↓” bar that jumps to the first one out of view, and an audible reminder that repeats while anything is still unacknowledged and goes quiet by itself when nothing is.

Half the value is in the routing, not the screen

A kitchen with a grill, a cold section and desserts doesn’t want a screen: it wants each line to appear where it belongs. That’s routing by category, and it’s where the expensive mistake hides — if the screen and the printer each decide where a dish goes, the same dish ends up printing at the bar and showing in the kitchen.

Concrete question for whoever is selling it to you: does printer routing and screen routing come out of the same configuration? In ours, each station can output to screen, printer, or both — which enables what almost everyone needs in month one: bar on paper, kitchen on screen, side by side, without reconfiguring anything.

Add the aggregated item summary to your list (Toast calls it All Day): “12 pork fillets, 7 potato salads”, so you can cook in batches. It complements the board; it never replaces it.

How to know whether your kitchen needs one

Not everyone does. A 20-cover bar with one griddle and one waiter gains nothing: a ticket on a clip is faster than looking up. It pays off when at least two of these are true:

  • You run two or more sections working at different speeds.
  • At peak there are more than 4–5 live tickets and somebody has to decide the order.
  • You mix channels: dining room + online orders + table QR arriving through different doors.
  • You’ve already lost tickets — dropped, misfiled, or fired twice.
  • Your kitchen printer gives you trouble (paper, heat, cabling) more than once a month.

If none of those apply, save the hardware. If three do, the screen pays for itself in tickets that don’t get lost.

Our Cloud POS (from €29.99/month) includes the kitchen display: it opens on any tablet or computer with a browser, with no extra per-screen licence. If you’d like to see it running with your own menu, tell us about your kitchen →