Kitchen Display System (KDS) Explained: Sending Orders to the Kitchen Without Paper

KOT vs KDS: what each one actually is

People use the two terms as if they mean the same thing, so it helps to separate them. A KOT is the document: the table, the course, the items, and the changes the guest asked for. A KDS is one way of delivering that document: a screen in the kitchen that shows live tickets and lets the cook mark them as prepared. You can send a KOT to a printer, to a screen, or to both. Most kitchens that move to a screen keep the printer as a backup for a station or for the pass. The table below shows where the two approaches differ in daily use.

Why paper slips fail when the kitchen gets busy

A paper ticket works until the room fills up. At the lunch rush in a busy GCC restaurant, a single kitchen printer is spitting out slips for dine-in, takeaway and delivery at the same time. The paper curls, the thermal print fades, a slip falls off the rail, and the cook reads the wrong line because three tickets look alike. Handwritten tickets, still common in smaller restaurants and some cafés in Iraq, add a second problem: the server writes in a hurry, in two scripts, and the kitchen has to decode it. The mistakes cluster around the same places every time. Modifiers get missed (no onions, extra sauce, large size). Course timing is lost, so the starter and the main arrive together. And an item added at the table after the first slip is printed is easy to overlook. Each of these ends the same way: a dish is thrown away and made again, the table waits longer, and the guest remembers the wait more than the food. A KDS does not make cooks faster by itself. What it does is remove the paper-handling step where these errors enter, and put the right items in front of the right station.

Step 1: Create kitchen stations so every item goes to the right cook

A kitchen display is only as good as its routing. If every ticket goes to one screen, the cook at the grill has to read past the drinks, the salads and the desserts to find their own lines. In Culina you create Culina Kitchen Station records, for example Grill, Barista and Bar. Each station routes items in one of two ways: by item group, so the Barista station receives your Hot Drinks and Cold Drinks, or with All items, which suits a small kitchen with one pass. Each station can also have an optional printer, which prints a paper KOT in addition to the screen. Start with the real layout of your kitchen: one station per place where someone actually stands and cooks. If you are unsure, begin with two or three stations and split further when a station is clearly overloaded. Every station name also has an Arabic field, so the Arabic-speaking cook sees the station tab in Arabic.

Step 2: Send to kitchen, and let only new items through

When the order is ready, the server uses Send to kitchen. Culina creates one kitchen ticket per station. Each ticket carries the items, their modifiers, the course and the table. The detail that matters in practice is that only new items since the last send are fired, so a server who adds a drink or a dessert to an open table does not reprint the whole order, and the kitchen does not cook anything twice. Guest orders placed from the table's QR menu reach the floor plan as new orders and follow the same route to the kitchen when the order is sent. Because the modifiers are priced and named once in the menu, what the guest chose, what the kitchen sees and what is charged on the receipt are the same thing, in the same language.

Step 3: Work the Kitchen screen and bump as you cook

The Kitchen screen shows live tickets grouped by station. Each cook opens their own station tab, cooks from the top of the list, and bumps an item, or a whole ticket, as it is prepared. Item names, modifiers and station tabs all follow the active language, and Arabic is supported, so a cook who reads Arabic best can work in Arabic while the front of house works in English. Two habits make the difference. First, one person owns the pass and does not let a table's plates leave until every station's items for that table are marked done. Second, keep a printer on any station where a screen is hard to see, such as a hot grill, so a ticket still reaches the cook if a screen is out of sight.

Worked example: a Doha grill restaurant

Take a 60-seat grill restaurant in Doha, call it Mashawi Al-Dafna. It sends about 300 kitchen tickets a day across dine-in, takeaway and delivery. These figures are illustrative assumptions, not benchmarks, so replace them with your own. Before the change, paper slips and handwritten additions cause 3% of tickets to be remade, which is 9 tickets a day. After moving to stations and a Kitchen screen with new-items-only sending, remakes fall to 1%, which is 3 tickets a day. The average ingredient cost of a remade dish is QAR 14.000. Qatar had not yet implemented VAT as of April 2026 (a rollout is expected but no date is confirmed), so the figures carry no tax effect; confirm the current position before you plan. Here is one day:

That is 180 fewer remade dishes a month and QAR 2,520 saved in ingredient cost, about USD 692 at the fixed rate of QAR 3.64 per dollar. The figure is conservative on purpose: it counts only the ingredients thrown away, and leaves out the cook's time, the guest's longer wait and any dish given away to apologise. It also does not rely on the 20–30% ticket-time claim, which is a vendor figure. If your own remake rate is already low, the saving will be smaller, and if you run delivery with several aggregator channels it is often larger. The point of the example is that the case rests on one number you can measure yourself: how many dishes were cooked twice last month.

What to measure after you switch

Do not judge a KDS by how it looks. Pick three numbers and write them down for two weeks before going live and two weeks after. The first is the remake count, from your waste or void log. The second is the average time from Send to kitchen to the last item bumped, which you can read from your ticket records. The third is how many tickets each station handles at the busiest hour, which tells you whether a station is overloaded and should be split. If remakes do not fall, the cause is usually routing (items going to the wrong station) or a screen in the wrong place, not the idea of a kitchen display itself.

The bottom line

A kitchen display system earns its place by removing the paper step where orders get lost, not by looking modern. Route items to stations, send only what is new, bump as you cook, and keep a printer where a screen cannot be seen. Culina, a restaurant management system built on ERPNext and used across the GCC and Iraq, provides this in one system: kitchen stations that route by item group or All items, a kitchen ticket per station carrying modifiers, course and table, a Kitchen screen with live tickets you can bump, optional printers per station, and Arabic and English throughout. The same orders feed recipe costing and the Menu Engineering report, so the kitchen's data also tells you which dishes to keep. Payment still settles at the till on your local rails, whether that is KNET, BENEFIT, NAPS / Himyan, OmanNet, mada, or cash, Qi Card and Zain Cash in Iraq.