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 Safety & HACCP
- Features
- Ingredient and Fulfillment Movements
Ingredient and Fulfillment Movements
Record ingredient consumption, waste and service events without losing the original batch scope.
OverviewDelivered Fulfillment Events×
Food Safety & HACCP · Ingredient and Fulfillment Movements
New
Delivered Fulfillment Events
Fulfillment events
| Parent | Product | Quantity | Event type | Occurred at | External event ID | |
|---|---|---|---|---|---|---|
| PB-64287 | MI-7682 | 500 | Delivered | 06 Oct | EEI-753 | |
| PB-49568 | MI-3105 | 60 | Delivered | 08 Oct | EEI-234 | |
| PB-20041 | MI-8422 | 80 | Delivered | 25 Oct | EEI-294 | |
| PB-31909 | MI-7543 | 860 | Delivered | 27 Oct | EEI-902 | |
| PB-53699 | MI-6512 | 660 | Delivered | 22 Oct | EEI-287 |
6 of 6 records
EEI-753Fulfillment events · FE-38328
DeliveredParentPB-64287
ProductMI-7682
Quantity500
Occurred at06 Oct
What you can do
Follow the operating record
Ingredient movements use signed quantities, units, occurrence times and operation keys. Kitchen Lead records consumption and waste separately so a reversed or cancelled line does not erase what was actually used. The source meal line identifies the operational reason for each movement. A correction is another traceable movement, not an edit that removes the earlier entry.
Fulfillment events distinguish allocation, picking, shipping, delivery and return. Each event links to the parent batch and product and carries a quantity, time and external event identity. Operations Lead can review a delivered event alongside served portions on the batch lines. They should agree on the scope that was actually fulfilled, especially when a batch is partly served.
Payment evidence stores provider event identity, receipt type, amount, provider reference and verification state. Reconciliation Analyst checks a capture or refund against the batch and any compensating action before marking the evidence verified. If a partially served batch is cancelled, the team retains the served history, accounts for waste and verifies the provider evidence for the remaining scope. The original order and effects remain readable.
How the work is organized
- Record physical use. Kitchen Lead enters signed ingredient movements with unit, time, source line and operation key.
- Follow delivery. Operations Lead compares each fulfillment event with the parent batch and menu product.
- Verify provider evidence. Reconciliation Analyst checks payment identity, amount and type before using a receipt in a correction.
What to agree during setup
Agree which team records consumption and waste and how a source meal line is identified. Identify the fulfillment and payment systems that issue external events. Decide who verifies their identities and who investigates a mismatch. Keep the served line quantities visible when reviewing a delivery or partial cancellation.
Check the handoff on an actual case
Choose a batch with a delivered fulfillment event and a partly served line. Kitchen Lead enters consumption and any waste as separate signed movements. Operations Lead compares the delivered event quantity with served portions and checks the external event identity. If the order is cancelled after partial service, preserve the served line and movement history. Reconciliation Analyst checks a provider refund or void receipt against that parent batch before treating it as compensation.
What your team sees
- Delivered Fulfillment Events — Inspect delivered quantity, product and external event identity.
- Completed Batch Lines — Compare served portions with the original line scope.
Follow the work through
See the related process and the data model before rehearsing the handoff. The implementation plan sets the order for loading people, products and live batches.
What it keeps track of
Data model- Lot and expiry movements
- Signed inventory movements for ingredient consumption and waste.
- Fulfillment events
- Allocation, picking, shipping, delivery and return events.
- Batch lines
- Individual menu item lines within a meal order.
- Payment evidence
- Provider-issued authorization, capture, refund and void receipts.
Who uses it
Permissions- Kitchen Lead
- Records ingredient use and waste.
- Operations Lead
- Follows fulfillment and served quantities.
- Reconciliation Analyst
- Verifies payment evidence for changed or cancelled scope.
Set up Food Safety & HACCP your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.