Every channel on the same board
Dine-in, takeaway and delivery orders live in one live view for the branch, each tagged with the channel it arrived on, so nobody reconciles three screens during a rush.
Restaurant order management
Every channel, one board, one truth.
Dine-in, takeaway and delivery arrive on the same live orders board. Each order carries the channel it came from, the status it is in, and a record of every change made to it.
- All channels on one board
- Status owned, not guessed
- Voids on the record
- Scheduled orders fire on time
What the orders board is
One queue, whatever door the order came through.
In Plato an order is created, fired to the kitchen, served and closed — and it carries its channel with it the whole way. Dine-in, takeaway and delivery differ in how they arrive and how they leave, not in how they are tracked, so the floor reads one board instead of three screens.
From intake to close
Nothing sits in someone's head.
Orders go wrong in the handovers — the till to the kitchen, the kitchen to the floor, the floor to the driver. Each handover is a status somebody has to own.
Status is a step, not an opinion
Created, fired, served, cancelled. Each transition is an explicit action against the order rather than a note someone shouts across the pass.
Changes leave a trail
Order events are recorded, and voids carry a reason. When a cheque is disputed at the end of the night, the history answers instead of the loudest person.
Scheduled orders fire themselves
An order placed for later is held and fired at the right time by a scheduled job, so a pre-order for 8pm does not depend on someone remembering at 7:45.
Order #1042FiredSample order
- Channel
- Delivery
- Created
- 19:04
- Fired to kitchen
- 19:05
- Served
- 19:23
Each step is stamped and attributed, so a disputed order has an answer.
The order's own history
Every order can account for itself.
An order records when it was created, when it was fired to the kitchen and when it was served, alongside the channel it came from and the events that changed it. That history is what makes a disputed order answerable.
- Channel carried on the order itself
- Created, fired and served each stamped
- Order events kept as an audit trail
- Voids recorded with a reason
Against a screen per channel
More than three tablets on the counter.
Most restaurants add a channel by adding a device. It works until two of them disagree about the same order.
| Capability | A device per channel | Plato |
|---|---|---|
| Intake | One screen per channel | One board, channel tagged per order |
| Status | Different words on each device | The same four steps everywhere |
| Kitchen | Re-keyed by hand | Fired straight from the order |
| Disputes | Whoever remembers loudest | Order events and void reasons |
| Pre-orders | A note and a hope | Held and fired on schedule |
| Reporting | Combined afterwards | One set of orders to read |
Fitted to how orders arrive
Three intakes, one queue.
Dine-in floors
Orders open against a table and move through the same statuses as everything else, so the floor and the kitchen read one queue.
Takeaway counters
Fast intake, a visible queue, and a clean close — without a separate system for walk-ups.
Delivery operations
Delivery orders carry their channel to dispatch, so the trip is attached to the order rather than tracked on paper.
Getting on one board
Four steps to a single queue.
The board is fed by the till you already use. Most of the setup is deciding what a channel means for your branch.
- 1
Define your channels
Set up the channels the branch actually sells through, with their own pricing and charge policy if they differ.
- 2
Take orders into them
Orders created at the till carry their channel from the first tap.
- 3
Fire and serve
Move orders through fired and served so the kitchen and the floor share one status.
- 4
Read the trail
Use order events and void reasons when a night needs explaining.
Order management questions
What managers ask about the board.
Do delivery and dine-in orders live in the same place?
Yes. Orders for the branch appear on one live board regardless of channel, and each order carries the channel it arrived on so you can still read them apart.
What statuses does an order move through?
An order is created, fired to the kitchen, then served, and it can be cancelled. Each transition is an explicit action rather than an assumption.
Can I see who changed an order?
Order events are recorded as the order moves, so changes have a trail. Voids carry a reason, which is what makes end-of-night disputes resolvable.
Can guests order ahead for a later time?
Yes. A scheduled order is held and fired at the right moment by a background job, rather than relying on someone watching the clock.
Can channels have different prices?
Yes. Pricing and charge policy can be set per channel, so a delivery price can differ from the dine-in price without a second menu.
Does a branch have to run every channel?
No. A channel can be paused for one branch and resumed later, so a location can stop delivery for the night without affecting the rest of the group.
See it on your own service
Put every channel on one board.
Book a walkthrough with your channels, your busiest hour and the handover that currently goes wrong.
30-minute walkthrough
See Plato on your menu.
Send us a few details. We'll set up a live walkthrough on your real menu, in your language, within one business day.
- We respond within one business day.
- The walkthrough runs on your menu, in your language.