Distribution events

Distribution events record each step against its parent order and product. The event type distinguishes allocation, picking, shipping, delivery and return. Quantity and occurrence time explain how much moved and when; the external event identity helps reconcile evidence received from another system. The record supports a trail for a delivered or returned product without collapsing the journey into one order status.

Delivery Operator works from the approved dispatch scope and records the actual events. The order may be ready before anything is shipped. A shipped event means the goods left the preparation stage; a delivered event says the destination received the recorded quantity. Served portions on order lines reflect service to guests and remain separate from a product’s distribution events.

• Order and product. Each event identifies the customer order and the product affected.
• Movement stage. The event type states whether the quantity was allocated, picked, shipped, delivered or returned.
• Evidence identity. Occurrence time and external event identity support later matching and exception review.

Agree which operator records each movement and where its external event identity comes from. Decide how the team handles partial delivery and returns, and what supporting attachment is needed when quantities differ. Keep product units consistent with the catalogue and with the event quantity. Confirm that staff distinguish kitchen preparation from movement through the delivery chain.

Suppose a venue order has several packaged products. The operator records a picked quantity and later a shipped quantity. If only part arrives, the delivered event shows that actual quantity. A return event records goods coming back; it does not erase the earlier shipped and delivered records. Exception Reviewer can then compare the event trail with the order’s remaining scope.

Take one order whose dispatch ticket is completed. Follow its distribution events by occurrence time and product. Compare the quantities at each stage and identify any return. Check the external event identities for duplicate reports from the source your team uses. The same externally reported event should be recognized during reconciliation rather than counted twice.

Then compare the order lines’ served portions. A delivered packaged product and a served meal portion answer different questions, so the service team records each in the appropriate place. If the distribution record is incomplete, use the operation receipt and attachment evidence to investigate before describing the order as finished.

• Completed Distribution Events — Delivered and returned quantities with their order and product.
• Open Distribution Orders — Orders still being prepared, dispatched or served.
• Operation Exceptions — Failed or uncertain operations needing comparison with actual events.

See delivery evidence for the event trail and corrections and reconciliation for an unresolved movement.