Kitchen display screen or ticket printer: what does a small kitchen need?

A ticket printer suits a small kitchen with one or two stations, a POS that already prints, and cooks who like a ticket in their hand. A kitchen display screen suits a kitchen with several stations, dishes whose timing matters, and orders that arrive from more than one place, such as servers and guests’ phones. WaiterPilot gives you a kitchen screen on a phone or tablet you already have; it has no printer connection and doesn’t connect to your POS. This guide compares the two honestly, gives a decision guide, and shows three ways a kitchen can run with WaiterPilot.

What is a kitchen display system?

Short answer: a screen in the kitchen that shows each order as a ticket, how long it has waited, and what is done.

A kitchen display system (KDS) does what a ticket rail does, on a screen. Orders appear as tickets, usually routed by station (grill, fryer, cold), with a timer and a button to mark each one finished. Most POS companies sell one as an add-on. As published on 15 October 2026:

Prices are the vendors’ own, for the plans named, and don’t include the screen or printer itself.

KDS vs kitchen printer: which is better?

Short answer: neither wins everywhere. Count your stations, check what your POS already does, and ask your cooks.

The real question is less “paper or screen” than “where do orders come from, and who has to see them”. A kitchen that gets every order from servers, through one POS that already prints, has little reason to change. A kitchen that gets orders from servers, phones and a delivery tablet has three queues, and a screen can bring them into one view, if they all feed it.

Do I need a kitchen display system?

Short answer: answer these five questions in order. The first clear “yes” usually decides it.

1. Does your POS already print to the kitchen, and do tickets rarely go missing? Yes: keep the printer. Spend the money elsewhere.
2. Do you run three or more stations that each need their own view? Yes: a screen with station views is worth pricing.
3. Do tickets go missing or get cooked out of order at peak? Yes: a screen with ticket ages helps, provided someone watches it.
4. Do orders arrive from more than one place (servers, phones, delivery)? Yes: decide whether they can all reach one screen or one printer. Two places to look is the most common failure.
5. Is your kitchen too hot, wet or cramped for a screen? Yes: a printer, or a small tablet in a protected spot at the pass.

What does WaiterPilot give the kitchen?

Short answer: a kitchen screen on a phone or tablet you already have, with dishes, choices and notes and no prices. No printer.

What it does, from WaiterPilot’s published behaviour:

• A kitchen screen. Staff use screens on their own phones or tablets: a main board with every ticket, a kitchen screen with dishes, choices and notes but no prices, and a floor screen for waiter calls and check requests.
• Stations as tabs. The staff board shows stations as tabs the restaurant sets. At our demo restaurant they are All staff, Kitchen, Floor service, Charcoal and Valet.
• Ticket ages. Waiting orders and calls change colour at 1, 5 and 10 minutes, so an unconfirmed ticket doesn’t sit unnoticed.
• Complete tickets. Required choices, such as size or side, must be picked before a guest can confirm, so the kitchen doesn’t get “steak, no temperature”.
• Notes as taken. Special requests go on the ticket as a short note, as the request was taken. Notes are not translated for staff.
• A person checks first. The first order at each table waits for a staff member to confirm it. After that, new orders from that table go straight to the kitchen until staff close the table.
• No hardware to buy. It runs in the browser on phones or tablets you have. On iPhone, lock-screen alerts need the board added to the Home Screen.

What it doesn’t do: it has no printer connection and no POS connection. Phone orders don’t print, and they don’t appear in your POS until someone enters them. In our tests on 15 October 2026, confirmed orders reached the staff board within 3 seconds (4 test orders, 0.8 to 2.7 s, on our demo restaurant), but that board is WaiterPilot’s screen, not your printer.

How can a kitchen run with WaiterPilot? Three setups

Short answer: screen only, re-key into a printing POS, or run both with clear rules.

Setup B is the one most restaurants with a printing POS start with. Our cashier’s guide on reconciling QR orders with your till covers when to ring orders in and how to check each table’s bill against the till.

A worked example: Casa Olivo’s line

Casa Olivo is a fictional restaurant (an example, not a customer). The numbers are assumptions.

Casa Olivo has two stations: a grill and a cold station. Its POS prints one ticket per order at the pass, and the expediter calls each dish to its station. On a Friday it serves about 120 covers, and the owner wants guests to order from their phones.

The owner looks at three options:

1. Keep paper, re-key phone orders (setup B). The host enters each confirmed phone order in the POS at a quiet moment. The kitchen changes nothing. Cost: the re-keying time. Risk: a phone order waits until someone enters it.
2. Kitchen screen at the pass for phone orders (setup C). The expediter’s tablet shows WaiterPilot’s kitchen screen next to the printer. Cost: a tablet they already own. Risk: the expediter now reads two places.
3. Buy the POS’s own QR ordering and KDS. Orders from phones print or appear on the POS screen with no re-keying. On Square Plus in the US, that is the $49 plan per location plus $30 a month per KDS device, as published on 15 October 2026, before card fees.

The arithmetic for option 2, with the expediter’s eyes as the cost: if a third of Friday’s 120 covers order by phone, that is 40 covers on the screen and 80 on paper. One person can watch both if the tablet sits at eye level beside the printer, and if the rule is “call tickets in time order, whichever place they come from”. Casa Olivo trials option 2 for a month, and keeps option 1 as the fallback if the two queues cause mistakes.

When is a printer-based tool the better choice?

Short answer: when phone orders must print automatically and land in your POS.

If your kitchen runs on paper and nobody has time to re-key, choose a QR ordering tool that connects to your POS and its printers. Square’s self-serve orders go to the POS and kitchen printers, and Toast’s Mobile Order & Pay items follow your print routing, as both vendors publish. WaiterPilot is the better fit when the problem is the conversation at the table, such as guests who ask questions or read the menu in another language, and your kitchen can work from a screen. Our Square comparison sets out that trade-off in full.

What to do next

Count your stations, list every place an order comes from, and ask your cooks where they look first. If your printer works and your orders come from one place, keep it. If you are adding phone ordering, decide on setup A, B or C before the first shift. Our guide to the small-restaurant tech stack shows where a kitchen screen fits among your other tools, and how it works shows the board, kitchen and floor screens. To see a ticket arrive, try a sample order.