Kitchen flow
Route before the queue. Then let preparation move visibly.
Kitchen should only receive work that actually requires preparation. Everything else takes the shorter route.
Follow the routeKITCHEN · TABLE 05Preparation queue
Veg Momo × 2Sent to kitchenPrepare
Paneer Tikka × 1PreparingReady
Fried Rice × 1Ready
Before the queue
Not every accepted item belongs in the kitchen.
Dwaar uses the item’s preparation mode as the routing truth. That keeps bottled drinks and other ready items from pretending to be kitchen work.
Mineral Water × 1READY
Veg Momo × 2SENT TO KITCHEN
Preparation runway
Sent → Preparing → Ready. Three states, three different responsibilities.
01Sent to kitchen
Accepted prep work is waiting for kitchen attention.
02Preparing
Someone has actually started the item.
03Ready
Preparation is finished. Kitchen responsibility stops.
KITCHEN · TABLE 05Preparation queue
Veg Momo × 2Sent to kitchenPrepare
Paneer Tikka × 1PreparingReady
Fried Rice × 1Ready
Exceptions stay visible
Sold out is not a silent disappearance.
Unavailable or cancelled items remain explicit so staff and customers are not left reconciling different versions of the order.
Cold Coffee is unavailableSold out · customer notified
The boundary
Ready is not Serve.
Kitchen finishes preparation. The floor owns the next handoff. That separation is small in the UI and enormous during a rush.
Kitchen never serves Floor receives Ready Item status stays canonical
See who owns what next READY FOR THE FLOORVeg Momo × 2Table 05 · Kitchen is done here