Kitchen Display
A prep queue that knows which table is waiting.
Tickets arrive at the right station, ordered by what needs to fire first. When a dish starts running late, the floor hears about it before the guest does.
Kitchen display - Tandoor + Curry
Fire now
Chicken 65
0:40
Masala Dosa x2
1:15
Cooking
Paneer Tikka x2
6:10
Dal Makhani
11:30
Running late
Ready
Veg Biryani
Plated
Station routing
Tandoor, curry, grill, bar, each gets its own items
Automatic sequencing
Wait time and dish effort decide the order
Delay flags
Late tickets turn ember and alert the floor
Bump to serve
One tap marks a dish ready for pickup
Prep prioritisation
The queue sorts itself, and shows its working.
Crustrol weighs how long each table has waited, how much effort each dish takes and what else is already plated for that table. The result is a queue your head chef can read at a glance and reorder by hand.
- Table-aware. Dishes for the same table are timed to finish together.
- Station-aware. A loaded tandoor does not hold up a free curry station.
- Always overridable. Drag a ticket up and the system learns nothing it should not. Your chef stays in charge.
Why this order, sample
Tandoor stationT7 has waited 26 minutes and its other dishes are already plated. Firing Dal Makhani now lets the whole table eat together.
Delay flagging
Catch the late ticket while there is still time to fix it.
Every dish carries an expected prep time based on your own kitchen's history. As a ticket nears that time it moves from green to amber, and past it to ember, with a message for the server.
- Expected times from your data. Estimates come from how long your kitchen actually takes, by dish and by hour.
- Floor alerts. Servers see which table, how late, and a suggested line for the guest.
- Service review. After close, see which dishes ran late most often and at which station.
T2 Veg Biryani
On time
Plated 1 min ahead of estimate
T4 Paneer Tikka
Watch
At 80% of expected prep time
T7 Dal Makhani
Late
4 min past estimate. Floor notified: tell guest 2 more minutes.
On the line
Designed for wet hands and a loud kitchen.
Multi-station routing
Split one order across stations automatically. Each sees only what it cooks.
Per-dish timers
Every item shows elapsed time against its expected prep time.
Server notifications
Ready and late alerts go to the floor, not just the pass screen.
All-day counts
See totals across open tickets: 14 naan, 6 tikka, 3 biryani.
Printer fallback
Keep a ticket printer as backup at any station that wants paper.
Prep time tuning
Adjust expected times per dish when a recipe or station changes.
Ticket time reports
Average and slowest ticket times by station, dish and shift.
Rush mode
Large tickets and party orders are flagged so the pass can plan ahead.
Questions
Asked at the pass.
What screens work as a kitchen display?
Any modern tablet or wall-mounted screen with a browser. Larger kitchens often use a 21 inch or bigger touch screen per station.
Can the chef override the order of tickets?
Yes. Tickets can be dragged, held or fired manually at any time. Suggestions never lock the queue.
How are expected prep times set at first?
You enter a starting estimate per dish during setup. After a few services Crustrol updates them from your kitchen's actual times.
The pass is open
Your restaurant is the next ticket on the rail.
Pick a ticket. We take it from there.
Ordered
Table 9 sends 4 dishes to the pass
This is a sample flow for illustration. Connect your restaurant for real, live order tracking.
Live walkthrough on your own menu
- 1 xYour menu loaded before the call
- 1 xFloor, kitchen stations and billing mapped
- 1 xGo-live plan for your next quiet day
Set it up yourself
- Create your account
- Add tables, stations and menu
- Open your first order