- 1Ribeye
- med rare
- no butter
- 1Burger
- add egg
- Home
- Kitchen Display System
Kitchen Display System
The Clover kitchen display system that runs on the screens you already own.
LiveOrder is a full KDS for Clover POS: real-time tickets, station routing, one-tap bumping, recall, prep timers and alert thresholds — delivered to any browser, on any tablet or TV, with nothing to install on your Clover devices.
01/The board
Tickets arrive already sorted into the work.
The moment an order is fired on a Clover Station, Flex, Mini, Duo, kiosk or online channel, it lands on the board. Items split to the station that cooks them, so the grill screen shows grill work and nothing else.
Each ticket carries its number, channel, table or guest name, elapsed time and every modifier exactly as the guest asked for it. Nothing is abbreviated into a code that only the owner understands.
Design the ticket layout02/Capabilities
What a KDS has to get right
Station rules
Map Clover categories, labels or individual items to stations. A ticket with wings and a salad appears on fry and on cold — each showing only its own lines — and expo sees the whole thing.
Item and ticket bump
Tap a line to mark it made, tap the header to clear the ticket. Touch, mouse, keyboard or a USB bump bar all work, because the board is just a web page.
Undo, logged
Pull back recent bumps in order when a guest changes their mind or a cook is too quick. Every recall records who did it and when.
Age and thresholds
Every ticket counts up from the moment it fired. Set a warn minute and a late minute per station; the ticket changes color and rises to the top on its own.
Hold and fire
Hold long-cook items and release them so everything plates together. Table-service kitchens can fire courses when expo calls for them instead of all at once.
The all-day view
An expo profile shows every open ticket with per-station completion, plus an all-day count of each item still owed, so the pass knows what is actually left.
03/Hardware
You do not need a kitchen display to run a kitchen display.
The usual objection to a KDS is the capital cost: purpose-built screens, mounts, a controller box and a per-device software fee, multiplied by every station you want covered. That math is why a lot of Clover kitchens are still running on a thermal printer and a rail of curling paper.
LiveOrder is a web application. If a device has a modern browser and a network connection, it can be a kitchen display:
- An Android tablet or Amazon Fire tablet on a $20 mount
- An iPad, including older ones that are no longer app-store current
- Any TV with a Chromecast, Fire Stick, or a cheap mini-PC behind it
- A laptop or all-in-one already sitting in the office
- Clover KDS hardware, if you have it
Because the price is per location rather than per device, adding a screen is a hardware decision only. Most kitchens end up running more displays than they originally planned, which is the point — a fry cook staring at a shared screen across the line is the reason things get missed.
Practical notes on screens
Mount at eye level and keep it out of the direct steam path. Wipe-down matters more than resolution: a 10" tablet in a silicone case survives a kitchen far better than a bare 24" panel. For a TV, 1080p is plenty — the ticket designer scales type up to whatever the sightline needs, so pixel count is rarely the constraint.
When the network drops
Kitchens lose Wi-Fi. When that happens, the board keeps every ticket already on it and stays fully usable — cooks bump as normal. Bumps and timings queue locally and sync the moment the connection returns, so your timing data stays intact rather than showing a hole in the shift.
04/Compared to
Kitchen printer, stock KDS, or LiveOrder
| Ticket printer | Stock KDS | LiveOrder | |
|---|---|---|---|
| Cost to add a station | New printer + paper | Per-screen hardware and software fee | The screen only — software included |
| Ticket layout | Fixed 80mm receipt | One or two presets | Per-station layouts you design |
| Prep timing | None | Basic average | Per ticket, item, station, hour, daypart |
| Drive-thru timing | None | Usually separate hardware | Built in, no sensors |
| Mistake tracking | Paper and memory | Rare | Two-tap logging with reason codes |
| Customer-facing display | No | Extra product | Included on every plan |
| Runs on | Its own hardware | Its own hardware | Any browser |
05/Questions