The Kitchen Display That Runs the Line

Most kitchen display systems are just a screen. They take a printed ticket, drop it in a box on a monitor, and call that digital transformation.

The order still routes on habit. The fryer still runs on a lookup table from the menu. And the first anyone hears about a bottleneck is a customer complaint. The screen changed; the kitchen didn't.

Zentallio's KDS starts from a different premise: every ticket, every scan, every station's pace is signal — and a kitchen that reads its own signal can run itself better while the shift is still happening. Iris does the reading. The board is just where that intelligence surfaces, in time to act on it.

One board, every channel

The Expo board is the first thing a shift lead sees, and it's deliberately unified. Every ticket carries its full context — allergy flags, modifiers, rider ETA — so a decision that used to mean walking to three screens now takes one glance.

Four streams in

Marketplace Dine-in Drive-thru Scheduled pickup

↓

One Expo board, one prioritised line.

↓

Routed to the stations that own the work

Grill Fry Cold Pass Drive-thru

Each station sees only what's relevant to it, with its own equipment status beside the queue. A grill cook doesn't need the drive-thru's bay wait. A fry cook does need the oil temperature and which basket is next — so that's what's on the screen.

Where the intelligence actually lives

Underneath the screens, three layers do the work — deterministic where it must be, predictive where it pays, and conversational where a human needs an answer, not a dashboard.

Layer 1 · deterministic

Zen Rules

The things that should never require a judgment call — cold-chain compliance, delivery radius, allergy blocking. They just hold, every ticket, every time.

Layer 2 · predictive

Zen Models

Forecast and learn: prep time per item and station (the number your kitchen actually produces, not the menu's guess), demand against the day's real signals, and rolling bottleneck detection that catches drift before a customer feels it.

Layer 3 · conversational

Ask Iris

Puts all of it into plain language. "What's slowing us down tonight?" gets an answer — the station, the item, the fix — instead of a chart to interpret at the pass.

The menu says loaded fries take four and a half minutes. Your fryers, your crew, and tonight's ticket mix make them in seven. Every ready-time on every ticket should say seven — not the number on a laminated card. That middle layer is what changes how a kitchen runs day to day

When one station starts trending slower than its own baseline, the system says so before it becomes a missed promise time — not in the report the morning after.

Built to keep running

Offline-ready

A kitchen doesn't get to pause because the internet did. When the cloud connection drops, the KDS keeps taking orders from the POS and floor tablets over the local network, keeps every station in sync, and arms printers as an automatic fallback — nothing waits on a screen that isn't there. Everything queues locally and reconciles the moment the connection returns. A small line on a spec sheet; a very large deal at 7 p.m. on a Friday.

Built for the kitchen it's actually in

None of this replaces judgment — a shift lead can always override a routed ticket, adjust a threshold, or decide Iris should speak up more or less. What it removes is the guesswork: the manual tally at close, the fryer nobody was watching, the ticket that quietly aged past its promise time while everyone was heads-down on the one in front of them.

The kitchen already knows how it's doing. Zentallio's KDS just makes sure someone's listening.

The kitchen display that runs the line — not just reflects it.

One board, every channel

Where the intelligence actually lives

Built to keep running

Built for the kitchen it's actually in