These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Online Food Ordering Platform
- Features
- Kitchen Fulfillment
Kitchen Fulfillment
Record preparation and actual service as different events.
OverviewFulfilled Order Lines×
Online Food Ordering Platform · Kitchen Fulfillment
New
Fulfilled Order Lines
Order lines
| Parent | Line number | Menu item | Portions | Prepared at | Served portions | |
|---|---|---|---|---|---|---|
| OO-49603 | 570 | MI-444 | 670 | 20 Oct | 390 | |
| OO-83568 | 710 | MI-240 | 930 | 10 Oct | 410 | |
| OO-92902 | 460 | MI-638 | 430 | 20 Oct | 490 | |
| OO-40368 | 240 | MI-624 | 480 | 06 Oct | 100 | |
| OO-35085 | 430 | MI-540 | 90 | 07 Oct | 790 |
6 of 6 records
MI-444Order lines · OL-94497
ParentOO-49603
Line number570
Portions670
Prepared at20 Oct
Served portions390
What you can do
Kitchen Fulfillment in daily work
Kitchen Lead releases accepted meal lines to preparation and uses the approved recipe revision tied to that work. Order lines records the menu item, requested portions, preparation time and served portions. Ingredient movements records signed consumption or waste against a source meal line. Those records allow a partly served order to retain its real history.
How the work is organized
- Start with accepted lines. Kitchen Lead reads requested portions and the approved recipe effective for that meal.
- Record preparation. Preparation time and signed ingredient movements show when work began and what stock was used.
- Record service separately. Service Coordinator enters actual served portions and checks any delivery event against the same order.
What to agree during setup
Agree when the kitchen starts preparation, who enters the actual preparation time, and how a partial service is reported. Use the same local order and line identities from acceptance through service. Do not treat a prepared line as delivered; the service coordinator records the actual served quantity and any delivery event separately.
Kitchen Lead and Service Coordinator should agree who enters preparation time, ingredient movements and actual served quantity. When only part of the requested meal reaches the guest, both people need the same order line and a clear record of the remaining scope.
Check the handoff on an actual case
Take an accepted order for four portions. Record when preparation happened, then serve two. The line shows four requested and two served, while ingredient movements account for consumption and waste against the source meal line. A delivery event, if present, should name the affected order and product with its own time and quantity. The remaining scope still requires an explicit decision rather than an invented full completion.
Compare the line’s requested and served portions after the coordinator records service. A preparation timestamp alone must not advance the meal to served. Check the movement source and operation key before correcting waste; a repeated movement should not silently count the same consumption twice.
What your team sees
- Order Status Board — Orders grouped by their current state, so the kitchen can select accepted work.
- Fulfilled Order Lines — The team compares requested portions with what reached service.
- Open Online Orders — The coordinator checks the next order due for service.
Kitchen Lead sees accepted work ready for preparation. Service Coordinator sees the preparation time and what has actually been served. Order Owner can follow an order as it moves through preparing and ready to served, using the line details to explain any difference between requested and served portions.
Follow the work through
Follow order acceptance, kitchen preparation, ticket release and reconciliation to rehearse the handoffs around this module.
What it keeps track of
Data model- Online orders
- Customer orders accepted and fulfilled by the kitchen and service team.
- Order lines
- Individual menu item lines within a meal order.
- Menu recipes
- Versioned recipe headers for products, with yield and approval state.
- Ingredient movements
- Signed inventory movements for ingredient consumption and waste.
- Delivery events
- Allocation, picking, shipping, delivery and return events.
Who uses it
Permissions- Kitchen Lead
- , Service Coordinator, Order Owner.
- Kitchen Lead
- Records preparation; Service Coordinator records service; Order Owner follows the unresolved remainder.
Set up Online Food Ordering Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.