Kitchen display systems: when to stop printing tickets

Printed tickets work. They work until the kitchen has three stations, a delivery channel and a table that ordered starters twenty minutes before mains. Then they stop working, and the symptoms are always the same: food going out cold, courses landing together, and a chef shouting at a spike of paper.

What a KDS actually is

Not a screen showing the same ticket you used to print. Four things:

Station routing. Each item goes to the station that makes it. The grill sees grill items. The barista sees drinks. Nobody reads past items that are not theirs.

Course firing. Starters fire immediately; mains fire when the starters are bumped, or when the server fires them. This is the single biggest quality improvement a KDS brings to a table-service restaurant.

Timers. Every order shows how long it has been open. Colour changes as it ages. The expediter sees the whole board.

Bump and recall. An item is marked done and disappears; if it comes back, it can be recalled. No paper, no doubt about what has gone out.

When it pays off

One station, one cook, counter service: printed tickets or a shout is faster. A KDS is overhead.

Two or more stations: routing starts to matter. This is the threshold.

Table service with courses: course firing alone justifies it.

A delivery channel: orders arriving from Jahez, HungerStation, Keeta and the rest need to reach the kitchen without a person re-keying them. A KDS plusaggregator integration removes an entire job.

How to set it up so it works

Route by category, not by item. Maintaining a per-item routing table is a job nobody will do after month two. Get the categories right and routing maintains itself.

Put the expo screen where the expediter stands, not where there was a free socket.

Choose a bump method and enforce it. A bump bar, a touch screen, or a foot pedal. What fails is a screen that is too far away or that requires clean hands the kitchen does not have.

Screens need to survive a kitchen. Heat, steam and grease. A consumer tablet on a shelf above a fryer has a short life.

Wire them. Not wifi. This matters more in a kitchen than anywhere else in the building.

The outage question

A KDS depends on the network between the till and the screen. This is worth being clear about, including about our own product:Wameed's kitchen display needs the local server. Sales, ZATCA signing and printing continue for 24 hours offline; the KDS does not.

So your fallback is printed tickets, which means:

1. Keep a working kitchen printer even after you move to screens
2. Wire it, so that it depends on as little as possible
3. Rehearse the switch once, so that staff have done it before the night they need it

Of the systems we track, only NCR and Revel are marked as having offline kitchen display. If uninterrupted KDS is critical to you, that is a real differentiator and we would rather say so.

What to measure after you install it

• Ticket time by station. Which station is the bottleneck at peak?
• Course gap. Time between starters bumped and mains bumped.
• Recalls. A rising recall rate means the routing or the firing is wrong.
• Items bumped after the table left. The worst number, and the one that justifies the whole investment.

The mistake to avoid

Installing screens and keeping the old process. A KDS is a change in how the kitchen communicates, not a replacement for paper. If the expediter still shouts every order after the screen shows it, you have bought a screen and kept the problem.

Give it two weeks, measure the four numbers above, and adjust the routing before you decide whether it worked.

More on Wameed's kitchen features on thefeatures page.