Fulfillment events

A fulfillment event records its order, product, quantity, event type, occurrence date and external event ID. Allocation, picking, shipment, delivery and return are distinct events. They form a history that can explain a line’s quantities and the order’s status. The event ID is especially important when a warehouse or carrier message arrives again after a timeout.

• Record the event type. An Allocated event describes a reservation; Picked and Shipped record different physical steps.
• Tie quantity to product. Keep the product and order references with every quantity so partial work can be reconciled.
• Preserve external identity. The external event ID helps recognize a replay rather than posting the same effect twice.

The order is the anchor for the event history. A shipped order may still receive a later Delivered or Returned event. These event types do not have matching order status values, so the event history remains the place to understand what happened after shipment. Staff reviewing a return also need the original shipped quantity and any provider refund evidence.

Decide which system supplies each physical event and the point at which its external ID is assigned. Define the meaning of the occurrence date across time zones and delayed messages. Agree who resolves events that arrive out of sequence and who checks an event with a product or order reference that cannot be matched. The warehouse or carrier connection must be tested with repeated, delayed and corrected messages before staff rely on the event history.

Choose a split shipment in the pilot. Ask the operator to show the ordered, allocated and shipped quantities beside the event history. A missing Picked event should be investigated before treating a Shipped event as proof of the whole pick path. The operating team should agree which correction they would make and how it is attributed.

A confirmed order is allocated for a product after available stock is checked in the connected warehouse source. The operator records the allocated quantity and its external event ID after the order revision moves. A picking event records the units found. The first parcel includes only some units; the Shipped event records those units and the order is marked part shipped. A second parcel completes the remaining units. A later Delivered event records the delivery observation.

Suppose the warehouse sends the first shipping message twice. The team checks the external event ID and the operation receipt before changing a line again. If the effect is uncertain, the reviewer uses the receipt queue to reconcile what happened. The staff should be able to show the same order history without an extra shipped quantity or duplicate event.

• Fulfillment event history — Physical events with product, quantity and external identity.
• Active order queue — Orders still being allocated or shipped.
• Receipts needing attention — Failed or uncertain execution to inspect before replay.

Allocation to delivery follows the normal path. Return and reconciliation covers later exceptions. Read the implementation plan before connecting event sources.