Prepare and serve at a stop

Trace approved kitchen scope through preparation, serving and fulfillment events.

Step by step

Read released scope Kitchen Lead

Kitchen Lead checks the accepted order, approved ticket and current lines before starting preparation.
- Current approved scope checked
- Updates Stop orders, Line tickets, Stop order lines
Prepare portions Kitchen Lead

Kitchen Lead uses the approved recipe revision, records actual preparation time and captures ingredient consumption or waste as signed movements.
- Actual preparation and movements retained
- Updates Menu recipes, Recipe ingredients, Ingredient movements, Stop order lines
Check readiness Kitchen Lead

Kitchen Lead compares the prepared scope with the requested lines before the order becomes ready for service.
- Ready status follows prepared scope
- Updates Stop orders, Stop order lines
Serve portions Service Lead

Service Lead records the actual portions handed to guests and serving time. A partly served order keeps its remaining scope visible.
- Served quantity and time recorded
- Updates Stop orders, Stop order lines
Record fulfillment Service Lead

Service Lead records allocation, picking, shipping, delivery or return events when those events occur, using the external event ID for the source event.
- Event trail linked to the order
- Updates Stop fulfillment events, Products

And how to keep it from happening.

A new recipe revision replaces the one used for an already released order.
Prepared food is mistaken for food actually served.
Waste is added to served quantity rather than recorded as an ingredient movement.
A delivery event is entered twice under different local records.

Start free, then use Proto to change fields, steps and approvals before your team goes live.