2xClassic burgerNo onionWell done
1xCaesar salad
2xFriesExtra salt
CloudyFy TVSolutions
Kitchen display system (KDS) software for order screens
CloudyFy TV puts live orders on your kitchen screens, routing them to the right station and branch so they can be bumped item by item as they are cooked. Orders arrive from your own system in CloudyFy TV's format or in yours, and every bump, void and recall is recorded.
1xVeggie burgerVegan bun
1xSweet potato fries
1xMargherita
1xChicken wrapGluten free
2xIced latteOat milk
2xClub sandwichNo mayo
1xLemonade
3xFish tacosSauce on side
1xGarden salad
2xPancakesSyrup on side
2xFlat white
1xClassic burger
1xFries
1xBrownieExtra cream
1xSteak fritesMedium rare
1xMushroom risotto
What is a kitchen display system?
A kitchen display system replaces printed dockets with a screen that shows open orders and lets the kitchen clear them as food goes out.
The screen is not just a viewer. It is the working surface: tickets appear when an order is placed, items are marked done as they are plated, and the whole ticket is bumped when it leaves the pass. Because the state lives on the server rather than on paper, the expo screen, the grill screen and the console in the office are all looking at the same orders.
In CloudyFy TV a kitchen ticket carries a channel (dine-in, takeaway or delivery), a branch, a station, its items, and a status: new, in progress, ready, completed or cancelled. Items themselves are pending, done or void. Everything that happens to a ticket is written as an event, so the history of an order is a list, not a memory.
How does a kitchen display work on CloudyFy TV?
Orders come in through one endpoint, appear on the screens that should see them, and are cleared with a bump.
Connect your order source
Create a kitchen connection and choose one of two formats. CloudyFy TV's own order format needs no mapping: point your sender at the endpoint with the key in the Authorization header, and it works as soon as you save. The custom format is for a system that sends its own JSON.Map a custom format once
Paste a real order payload from your system, map its fields to CloudyFy TV's format, check the ticket preview, and then save. The mapping is tested against your sample before it goes live, so the first real order is not the experiment.Set up stations and screens
Stations are routing buckets such as Grill, Cold and Pass. Bind a kitchen screen to a station, or leave it unbound to run as an expo screen that sees everything.Cook and bump
Mark items as done as they are plated. When the last item is done, the ticket moves to ready. Bump the order to complete it and clear it off the board.Fix mistakes
Undo a bump within 90 seconds. Recall a completed order for up to 30 minutes after it was closed. Both are ordinary actions, not support tickets.
What you can do with a CloudyFy TV kitchen display
Take orders from the system you already use
There are exactly two connection formats. CloudyFy TV's native format is for a POS or middleware that can be configured to send orders in that format and requires no field mapping. The custom format is for everything else: your system posts the JSON it already produces, and you map its fields onto ours once, against a real payload, with a preview of the resulting ticket before you commit. CloudyFy TV does not ship a named connector for any particular till, and we do not claim one.
Type an order in when you have to
A manual Add order drawer covers phone orders, staff meals and the till being down. The drawer asks which branch the order belongs to, so a hand-typed ticket reaches the same screens an ingested one would.
Route by station and by branch
A ticket reaches a screen based on two factors: the station the screen is bound to and the branch where the device is located. That is what lets one CloudyFy TV account run the grill screen in one restaurant and the cold section in another without either seeing the other's work.
Undo the bump
Everyone eventually bumps the wrong ticket. A bump can be undone for 90 seconds after it happened, and a completed order can be recalled for 30 minutes after it was closed, which covers the customer who comes back to the counter. The only status with no way out is cancelled.
Never look at a two-day-old ticket
Completed and cancelled orders drop out of the live feed after 12 hours. Separately, an order that is still open past your stale window, four hours by default and settable from 15 minutes to 7 days, is taken off the live grid and listed on its own, where a human completes or cancels it. Nothing is deleted, and changing the window re-sorts the boards immediately.
Bump items, void items, add a note
Items are marked done one at a time, so a partially plated ticket shows its actual progress rather than simply appearing as done or not done. Items can be voided, orders can be prioritised, and a note can be added to a ticket. Each of those is a recorded event with the actor that caused it.
Know when a screen is not really wired up
The kitchen screens list shows devices, not credentials. For each screen, it shows the device name and location, whether it has recently sent a heartbeat, which station it is bound to, which layout is governing it, and whether that layout actually contains the block assigned to the screen. A screen that looks connected but is showing the wrong layout is visible before service, not during it.
Run it on the screens you already own
Kitchen screens run the same players as the rest of CloudyFy TV: Android TV, Amazon Fire TV, Samsung Tizen 6.0 and later, LG webOS 6.0 and later, Android tablets, and Chromium browsers. Pair the device once with a code and manage it from the same fleet page as your menu boards.
Does a kitchen display screen speed up service?
There is no independent study we can point to that measured a kitchen display system specifically, so we will not claim a number for one.
The published research in this category measured customer-facing screens, menu boards and drive-thru displays, and it does not transfer to what happens behind the pass. Quoting it here would be borrowing credibility from an experiment that did not run in a kitchen.
- What CloudyFy TV can give you instead is your own measurement. Every ticket carries the time it was placed, and every bump, void, recall and cancellation is an event with a timestamp and an actor. Your ticket times are a real measure of your kitchen's performance, which is more useful than a vendor average based on someone else's operation.
2xClassic burgerNo onionWell done
1xCaesar salad
2xFriesExtra salt
1xVeggie burgerVegan bun
1xSweet potato fries
1xMargherita
1xChicken wrapGluten free
2xIced latteOat milk
2xClub sandwichNo mayo
1xLemonade
3xFish tacosSauce on side
1xGarden salad
2xPancakesSyrup on side
2xFlat white
1xClassic burger
1xFries
1xBrownieExtra cream
1xSteak fritesMedium rare
1xMushroom risotto
Which industries use kitchen display screens?
Any operation where orders are prepared to order and handed over rather than served according to a table plan.
In short
A CloudyFy TV kitchen display takes orders through one endpoint in either CloudyFy TV's format or your own mapped format, routes them by station and branch, and lets the kitchen bump them item by item. A bump is undoable for 90 seconds, a completed order is recallable for 30 minutes, finished tickets leave the feed after 12 hours, and anything left open past your stale window is set aside for a human. Kitchen Display is enabled per company, so ask us and we'll enable it for your workspace.
FAQs
CloudyFy TV ships two connection formats rather than a list of named connectors. The first is CloudyFy TV's own order format: your POS or middleware posts orders in our JSON to one endpoint with a key in the Authorization header, and there is nothing to map. The second is a custom connection: your system posts the JSON it already sends, and you map its fields onto ours once against a real sample, with a ticket preview, before it goes live.
Use the manual Add order drawer. It creates a ticket by hand with its branch, items and channel, and that ticket behaves exactly like an ingested one: it routes by station, it bumps, it can be recalled, and it appears in the event history. Kitchens use it for phone orders and for the day the till is being replaced, and small operations run on it permanently.
By station and by branch. A screen is bound to a station such as Grill, Cold or Pass, and it sits in a device that belongs to a branch. An order is shown on a screen when both facts line up, so the grill screen in one location never sees the cold section's work or another site's tickets. Leave a screen unbound from any station and it acts as an expo screen that sees everything for its branch.
Yes, for 90 seconds. Within that window an item bump or an order bump can be reversed and the ticket goes back to where it was. A completed order can also be recalled for 30 minutes after it was closed, which is the case where a customer comes back to the counter. Cancellation is the one action with no way back, so it asks before it commits.
Two rules. Completed and cancelled orders stop appearing in the live feed 12 hours after they close. An order that is still open past your stale window, four hours by default, is taken off the live grid and listed separately for someone to complete or cancel. Nothing is deleted by either rule, and the window is a per-company setting you can move between 15 minutes and 7 days.
Yes, once we switch it on for your company. Kitchen Display is behind a company feature flag that is off by default, because most CloudyFy TV customers are not food businesses, so ask us and it appears in your navigation alongside your other screens. The kitchen screen itself is an ordinary paired device: an Android tablet or a Chromium browser at the pass, paired once with a code, so it is managed from the same Devices list as the menu board out front. There is no separate KDS licence on top of your plan. See pricing for what a plan covers.
Get the kitchen off paper
Connect your order source in CloudyFy TV's format or map your own, route orders by station and branch, and bump with a 90-second safety net. Start a 7-day free trial of the plan you choose, Starter by default. No commitment, and ask us to enable Kitchen Display.