Home › Blog › Kitchen Display System (KDS) for Restaurants & Cafés: The Complete 2026 Guide

Kitchen Display System (KDS) for Restaurants & Cafés: The Complete 2026 Guide

7 Jul 2026 • 12 min read

A Kitchen Display System (KDS) is the screen that replaces the paper chit rail in a modern kitchen. Instead of a printer spitting dockets that curl, smudge and get lost, every order lands on a display the moment it is rung up — organised, timed, and impossible to misplace. For a busy café or restaurant, a good KDS is the difference between a calm pass and a chaotic one.

This guide explains what a KDS actually does, how it works end-to-end, where it beats (and occasionally loses to) a kitchen printer, and how to choose one that holds up when the internet drops mid-service. It is written for independent operators in Singapore, but the fundamentals apply to any kitchen.

What is a Kitchen Display System?

A KDS is software running on a screen in the kitchen or on the pass that receives orders directly from your POS and from any QR or online ordering channel. Each order becomes a "ticket" on the board. Cooks work the tickets, mark items done, and "bump" (clear) a ticket when it's ready. Nothing is printed unless you want it to be.

The core promise is simple: one source of truth for what the kitchen has to make, visible to everyone at once, updating in real time. No shouting order numbers across the line, no deciphering a printer that's running low on ink, no chit blowing off the rail.

How a KDS works, step by step

1. Order is taken. A cashier rings it on the iPad, or a guest orders from a table QR. The order is tagged with a table or an order number.
2. Order fires to the kitchen. The ticket appears on the KDS instantly, with items, modifiers (e.g. "oat milk", "no chilli"), quantities and a running timer.
3. Kitchen works the ticket. Cooks tap items done as they plate them. On a station-filtered board, each station only sees what it's responsible for.
4. Ticket is bumped. When everything is ready, the ticket is bumped off the board. A recall function brings back the last bumped ticket if someone clears it too early.
5. Order is served or collected. Front of house sees the status and closes the loop.

The whole cycle is seconds of interaction, but it removes an enormous amount of friction that paper introduces.

KDS vs paper chits vs kitchen printer

Most kitchens today run one of three ways. Here is how they compare on the things that actually cost you time and money.

The one column where paper and printers traditionally win is that last row — they keep working with no network. That is why offline support is the single most important thing to check in a KDS (more on that below). We cover the head-to-head in depth in Kitchen Display vs Kitchen Printer.

Order routing and stations

In anything bigger than a one-person kitchen, different items are made in different places: coffee at the bar, mains on the line, desserts at the cold station. A capable KDS lets you route by category to a station view, so the barista's screen shows only drinks and the line's screen shows only food. Each station finishes its own items independently, and the order only fully clears when every station is done. This stops one station's "bump" from wiping another station's outstanding items — a classic cause of missed dishes.

Timing, ageing and colour

Every ticket carries a timer from the moment it fires. Good boards escalate colour as a ticket ages — white, then amber, then red — so the pass can see at a glance which table has been waiting too long. This is how you protect your slowest ticket instead of only working the newest one, and it is something paper simply cannot do.

Bump, recall and "all-day" views

• Bump clears a finished ticket from the board.
• Recall brings back the last bumped ticket — essential when a runner clears something a beat too early, or a guest adds an item.
• All-day / "to-make" view totals every outstanding item across all tickets ("12 lattes, 6 big breakfasts") so a station can batch efficiently during a rush.

Why offline support is non-negotiable

Most cloud KDS products are web pages. The moment your café's Wi‑Fi hiccups — and in Singapore shophouses, it does — a web KDS goes blank and the kitchen is flying blind. That single weakness is why many operators keep a printer "just in case", which defeats the point.

A KDS built for real service caches the live board locally and queues actions (start, bump, item-done) on the device, replaying them when the connection returns. Shopways' native iPad KDS does exactly this, and falls back to a printed chit as a backup when configured. If you take one thing from this guide: ask any KDS vendor precisely what happens on their board when the internet drops for two minutes mid-rush. Read more in Why your iPad POS must work offline.

Native app vs browser KDS

A KDS delivered as a native iPad app stays responsive under load, keeps working offline, and survives a screen that's been on all day. A browser-tab KDS depends on the tab staying open, the connection staying up, and the device not sleeping. For a production kitchen, native wins on reliability every time. Shopways' KDS is a native iPad app for this reason.

What it costs — and what it saves

KDS pricing outside Singapore is often a per-screen monthly add-on on top of an already-pricey restaurant platform. That adds up fast for a small operator. The saving side is real, though: no paper or ribbons, fewer remakes from misread chits, faster ticket times, and cleaner data on how long food actually takes. A KDS that is included in a flat plan — rather than metered per screen — is far kinder to a small café's margin.

How Shopways does KDS

Shopways includes a native iPad Kitchen Display System in its one flat plan (no per-screen fees). Orders from the POS and from table QR ordering flow straight to the board; you can filter by station, see live timers, tap items done, bump and recall, and it keeps working offline with a printed-chit fallback. You can also run hybrid — a chit prints and the KDS shows the order — which is a comfortable way for a paper-based kitchen to transition.

How the big platforms compare

To put Shopways in context, here is the wider landscape ("what's outside"):

• Toast — a powerful US-built restaurant platform with a strong KDS, but it runs on Toast's own Android hardware, is priced for larger operations, and is US-payments-centric.
• Square for Restaurants — a solid KDS app that runs on iPad, well designed, but built around Square's payment processing (MDR on every card sale) and tuned for US workflows.
• Lightspeed Restaurant (K-Series) — feature-rich and robust, aimed at established and multi-site venues, with pricing and complexity to match.
• TouchBistro — an iPad-based restaurant POS with a KDS add-on; capable, but features are often licensed as separate modules.
• Qashier — a Singapore all-in-one terminal with a KDS option; convenient, but tied to Qashier's hardware and payment rails. See our Shopways vs Qashier comparison.

The pattern: the global platforms are excellent but heavy and priced for scale, and most meter the KDS per screen. Shopways aims at the independent Singapore café and restaurant that wants a native iPad KDS, dine-in and offline reliability in one flat plan, on hardware it already owns.

Frequently asked questions

Do I need to throw away my kitchen printer to use a KDS?

No. The most comfortable path is hybrid — run the KDS and keep a printer as a backup or for a station that prefers paper. Many kitchens phase paper out over a few weeks once they trust the screen.

What hardware does a KDS need?

Shopways' KDS runs on a standard iPad mounted where the kitchen can see it. No special kitchen computer required. Add a receipt printer only if you want the chit fallback or hybrid mode.

Will a KDS work if my internet goes down?

It should — but only if it is built for offline. Shopways caches the board and queues actions on the device, and can fall back to a printed chit. Always test this before you commit.

Can guests' QR orders show on the KDS?

Yes. Orders from table QR ordering appear on the same board as POS orders, tagged by table, so the kitchen has one unified queue.

← Back to all articles