Dwaar
Preparing the Dwaar service flow.
Online orders

Outside orders should join the restaurant, not bypass it.

Delivery orders keep their own context, while preparation, status and handoff should still move through the same restaurant discipline your team already understands.

One online entry point Same kitchen language Clear customer handoff
Follow an online order
Online orders
Live intake
Pickup2 Delivery1
#782PickupPreparing
#783DeliveryReady
#784PickupConfirmed
ONLINE MENUORDERKITCHENHANDOFF
ORDER #782Pickup
Order confirmed6:24 PM
Preparing6:31 PM
Ready for pickup6:42 PM
Completed—
Customer status

Status should answer the question before the phone rings.

A customer should always know whether the order landed, whether the kitchen is working on it, and when the next handoff is ready.

Order confirmed

The customer knows the restaurant received the order.

Preparing

Kitchen progress stays visible without a phone call.

Ready for handoff

Every delivery order gets a clear next step.

Same kitchen, every order

Online delivery should use the same preparation language.

Accepted preparation work still moves through Sent to kitchen, Preparing and Ready. Outside orders do not need a second kitchen vocabulary or a parallel operating system.

Restaurant kitchen preparing orders
KITCHEN · TABLE 05Preparation queue
Veg Momo × 2Sent to kitchenPrepare
Paneer Tikka × 1PreparingReady
Fried Rice × 1Ready
What stays consistent

Online orders should feel different to the customer, not disconnected to the restaurant.

The customer enters from outside the restaurant, but preparation, status and handoff still stay connected to the same team workflow.