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.
- Food Truck POS & Route Planner
- Features
- Preparation and service
Preparation and service
Record preparation time, served portions and fulfillment events.
OverviewServed Stop Order Lines×
Food Truck POS & Route Planner · Preparation and service
New
Served Stop Order Lines
Stop order lines
| Line number | Menu item | Portions | Served portions | Prepared at | Parent | |
|---|---|---|---|---|---|---|
| 70 | MI-330 | 170 | 810 | 03 Oct | SO-43418 | |
| 190 | MI-500 | 200 | 660 | 04 Oct | SO-13696 | |
| 180 | MI-691 | 340 | 630 | 19 Oct | SO-35538 | |
| 400 | MI-990 | 200 | 860 | 27 Oct | SO-91450 | |
| 900 | MI-334 | 250 | 600 | 20 Oct | SO-77858 |
6 of 6 records
MI-330Stop order lines · SOL-43032
Line number70
Portions170
Served portions810
Prepared at03 Oct
ParentSO-43418
What you can do
Separate the work at each handoff
An accepted order gives the kitchen a priced and dated meal scope. Kitchen Lead checks the approved recipe revision for the released lines and records the actual preparation time. Ingredient movements capture consumption and waste with signed quantities. The prepared scope is then checked before the order is marked ready. Service Lead records served portions and the actual serving time; preparation alone never establishes that the customer was served.
The line keeps requested portions and served portions separately. That distinction matters when part of an order is served and the remaining scope is cancelled or corrected. The order status and serving time help the shift team see what still needs attention. A serving record should match the actual portion handoff, while any unserved amount remains clear for the supervisor’s review.
How the work is organized
- Kitchen preparation. Work from the reviewed ticket and record actual line preparation.
- Service handoff. Confirm which portions were served and when the order reached served status.
- Fulfillment trail. Record allocation, picking, shipping, delivery or return events as their own facts.
What to agree during setup
Agree who records prepared time, who confirms served portions and what evidence the team needs for a discrepancy. The kitchen and service leads should use the same order and line identity. Define how waste is measured, including the unit and ingredient. If a venue receives packaged goods, decide how external fulfillment event IDs are obtained and checked against the order before the event is treated as delivered.
Take a stop order for a lunch service. The kitchen prepares the approved recipe quantities and records consumption. Service Lead serves fewer portions than originally requested. The order line now shows both the original portions and what reached the guests. Shift Supervisor can review the remaining scope and any waste without erasing the preparation time or served portions. A delivery event, if one exists, stays in the fulfillment trail rather than replacing the service record.
Check the handoff on an actual case
Prepare an accepted order using the approved recipe revision and check that the ingredient movements name the right ingredients and units. Record a partial service and verify the line retains both quantities. Rehearse a return event and confirm its external ID and quantity remain linked to the parent order. Try to complete an order when the recorded served scope disagrees with the actual handoff, then review the discrepancy before closing the shift.
What your team sees
- Served Stop Order Lines — Compare requested portions with what was actually served.
- Completed Stop Fulfillment Events — Review delivered and returned quantities by order.
- Open Stop Orders — Find accepted or ready work that still needs a service decision.
Follow the work through
What it keeps track of
Data model- Stop orders
- Customer orders accepted and fulfilled by the kitchen and service team.
- Stop order lines
- Individual menu item lines within a meal order.
- Menu recipes
- Versioned recipe headers for products, with yield and approval state.
- Recipe ingredients
- Ingredient quantities required per recipe yield.
- Ingredient movements
- Signed inventory movements for ingredient consumption and waste.
- Stop fulfillment events
- Allocation, picking, shipping, delivery and return events.
Who uses it
Permissions- Kitchen Lead
- , Service Lead, Inventory Manager and Shift Supervisor.
Set up Food Truck POS & Route Planner your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.