T-120m
- 2×Burratano balsamic
- 1×Sourdough
What it does
Take the order at the table, the counter or the kerb, and get it to the kitchen.
- Grouped the way the kitchen works
- Tickets are broken out by menu category so the section that cooks it sees it, instead of every ticket landing whole on every screen.
- You can see what is late
- Each ticket carries its own age and warms as it goes. A board with an ember ticket on it is telling you something a printer never could.
- Modifiers and notes attached
- Whatever the guest chose travels with the item — no allergy note lost between a table and a docket spike.
- Clears to the floor
- Marking an item ready updates the guest’s own screen and the floor view at the same moment, so nobody has to ask.
See it
Example data
Service running19:42
- Just in
- 1
- On the pass
- 2
- Ready
- 1
On the boardExample service
T-046m
- 1×Sea bassno fennel — allergy
- 2×Truffle fries
T-0914m
- 3×Wagyu burger2 medium, 1 well
- 1×Halloumi skewer
Pickup2m
- 2×Sunday roast
Where it sits
One system, five pillars
Kitchen display is part of ordering.
Take the order at the table, the counter or the kerb, and get it to the kitchen. It runs on the same menu, the same tables and the same bill as everything else here — nothing to integrate, nothing to reconcile.
Revenue & insights
Know what sold, what almost sold, and what caused the difference.
Dish reviews · Revenue & attribution · Analytics · AI insights · Guest intelligence · Automated messaging · Experiments · Discounts & promotions · Campaigns
Bookings
Fill the diary — and give a forgotten table a chance to be sold again.
Bookings & events
Food cost & stock
Cost the menu on what you are actually paying for the food.
Stock & purchase orders
Suppliers
Compare what you ordered, what arrived, and what you were billed for.
Supplier control
Team & shifts
Build the rota, publish it once, and know who did what on the floor.
Team & shifts