Fulfillment

Fulfillment Coordinator records dated events against a customer order and product. Event types include Allocated, Picked, Shipped, Delivered and Returned. Each event carries a quantity and external event ID, which helps the team distinguish a new update from a replay. The customer order holds a separate lifecycle status and promised date.

• Record movement. Link each event to the relevant order and product.
• Compare quantities. Read shipped units against ordered and allocated units on the lines.
• Resolve exceptions. Inspect open orders by promised date and investigate missing shipment evidence.

The supplier route may be completed before the product ships. Its acknowledgement ID identifies supplier response; it is not a shipped or delivered event. For a partial shipment, the line quantities and order state should make the remaining obligation visible. A return event stays in history even if the team later changes its current order assessment.

When an event arrives, compare its product and quantity with the order line SKU and units. Keep the external event ID with the dated event, so a repeated update can be recognized without adding the quantity again.

Agree which external source sends fulfillment event IDs and the unit used for event quantities. Map that source’s product identity to the product SKU. Decide who updates order status after a partial shipment and how a return affects open work. Establish a routine for comparing the promised date with the latest recorded event, especially when a supplier acknowledgement exists but no shipment event follows.

Begin with an approved supplier route for an order containing two products. Record an allocation event for both, then a shipped event for one. Check the order line quantities and set the order’s current state accordingly. Record a delivered event only when a distinct delivery update arrives. The open order exception queue should still draw attention to the remaining units near the promised date.

Now receive the same external shipment event ID again. The team should identify the earlier event and avoid counting the quantity twice. Record a return as its own event, with date, product and quantity, so the reason for a later order correction remains traceable.

• Shipment events — Dated shipped, delivered and returned product events.
• Orders nearing promise — Orders whose promised date needs attention.
• Order line progress — Open units alongside allocated and shipped quantities.

Follow supplier response to fulfillment and review exception handling.