Kitchen Display System (KDS) for QR Menus

A kitchen display system, or KDS, is a screen in your kitchen that shows incoming orders in real time, replacing handwritten chits and printed tickets. Paired with a QR code menu, it means orders placed on guests' phones appear in front of your cooks within seconds, with no one retyping anything. This guide explains what a KDS does, how it works with QR ordering, what you need to run one, and how to roll it out without disrupting service.

What a kitchen display system does

A KDS receives each order the moment it is placed and shows it as a ticket on screen. A typical ticket shows:

• the table number, or a name or token for takeaway
• each item with its modifiers ("no onions", "extra spicy", "large")
• notes from the guest or waiter
• how long the ticket has been open

Cooks move the ticket through simple stages — for example received → preparing → ready → done — and everyone looking at the screen sees the same state. It is mission control for the line.

How a KDS works with QR menu ordering

With table ordering, the flow is direct:

1. A guest scans the QR code menu at their table.
2. They add dishes and modifiers to a cart and submit.
3. The order appears on the kitchen screen seconds later, already tagged with the table number.
4. The kitchen marks it preparing, then ready, and front-of-house knows exactly when to run it.

There is no handwriting to decipher and no walking to a terminal to key in orders, so the kitchen starts cooking sooner and servers spend their time with guests instead of relaying orders. Orders taken by staff can go to the same screen, so the kitchen has one queue rather than two.

Benefits of a live KDS

Fewer mistakes. Orders arrive exactly as entered, including modifiers and notes, so "no onions" actually reaches the pan. Misread handwriting disappears.

Faster service. Orders reach the kitchen instantly, and timers make slow tickets visible before a guest has to complain.

Better coordination. Every station sees the same queue, and when a ticket changes state everyone sees it at once — no shouting across the pass.

Calmer front-of-house. Servers can see when food is ready instead of checking the kitchen repeatedly.

A complete record. Because every order is digital, you have a searchable order history showing what was ordered, from which table and when — useful for staffing, prep and resolving disputes.

KDS vs paper tickets

Paper still has a place. Many kitchens keep a receipt printer for customer bills or as a backup, and some print kitchen tickets for particular stations. The best setups use the screen as the single source of truth and print only where paper genuinely helps.

What you need to run a KDS

You do not need specialist hardware:

• A screen. A tablet on a wall mount, or any computer or TV with a browser. Put it at eye level near the pass, protected from heat and splashes.
• A reliable internet connection. Use your restaurant Wi-Fi, ideally with a mobile-data hotspot as a backup.
• Sound. An audible alert for new orders, loud enough to hear over the extraction fan.
• Optional: a receipt printer for bills or printed tickets.

Setting up a KDS in MenuBeacon

MenuBeacon's live kitchen dashboard is included in the Free plan, together with table ordering and cash or pay-at-counter orders. To set it up:

1. Build your menu and generate table QR codes.
2. Turn on ordering for your menu.
3. Open the kitchen view on the tablet or screen in your kitchen.
4. Place a test order from your phone and walk it through every stage.

Pro adds card, Apple Pay and Google Pay payments at the table, staff accounts with PINs, receipt printing and daily prep reports. See the pricing page and the full feature list for details.

Rolling it out without disrupting service

• Start on a quiet shift. Run the screen alongside your current process for a lunch service or two.
• Agree on the stages. Decide who moves a ticket to "preparing" and who marks it "ready", and stick to it.
• Name one owner per shift. Someone checks that the screen is on, logged in and loud enough before service.
• Keep a fallback. If the internet drops, staff should know how to take orders on paper until it is back.
• Review after a week. Look at which tickets ran long and ask cooks what slows them down.

Common mistakes

• Placing the screen where cooks cannot see it without leaving their station.
• Muting alerts during a rush and missing new orders.
• Leaving finished tickets on screen, so the queue becomes cluttered.
• Letting some orders bypass the screen, which creates two queues.

Getting started

If you already run a QR menu, adding a kitchen display is mostly a matter of switching on ordering and opening the kitchen view on a tablet. If you are still choosing how to host your ordering system, read our comparison of cloud vs self-hosted ordering systems, or see how MenuBeacon works from menu to kitchen.