Allocation and fulfillment

The Fulfillment Coordinator starts from an order and its product lines. Allocation records an Allocated fulfillment event for each eligible Draft or Open line, then marks that line Allocated. The workflow also sets the parent order to Approved and checks for an existing allocation event before creating another one. This matters when someone repeats a manual action after an uncertain response: the same line should not gain a second allocation simply because the request was retried.

The release workflow begins with an Approved order. It records a Shipped event per line, marks each line Fulfilled, advances the order revision, moves the order to Executed and records a processing receipt for the run. Fulfillment events can also describe picking, packing, delivery and returns. Their event type, quantity, date and status let a team distinguish what was planned, recorded or confirmed.

• Allocate. Work from the order lines and record allocated quantities as fulfillment events.
• Release. Use the approved order and its lines to record shipped quantities and the release receipt.
• Follow up. Compare later delivered or returned events with what was shipped for the same order.

Decide which Fulfillment Coordinator owns each location and how an order moves between physical teams. Set a rule for recording event quantities and dates so a shipment can be reconciled to its lines. The product catalog carries the unit of measure; make sure that unit is understood at the pick and ship points.

Agree how to use the event status. Planned and Recorded are different from Confirmed, and Failed needs an owner. Release moves the order to Executed when it records shipment. Operations should use reconciliation to compare that result with the payment and fulfillment evidence; a later discrepancy leaves a failed receipt and an exception to investigate.

Take an Approved order with two lines. Run allocation and inspect each line for an Allocated event, its quantity and location. Repeat the allocation action and check for duplicates. Then release the order and compare the Shipped event for each line to the order quantity. The processing receipt should identify the release run, and the order should be Executed with its next revision.

Now record delivery for one line and a return for the other. Fulfillment Coordinator and Order Operations Manager should be able to follow both event histories from the original order. If the quantities disagree with the lines, assign an exception with an owner and detail. Do not erase the earlier shipment to make the current view look balanced.

• Orders Open for Fulfillment — Approved orders ready for the coordinator’s next action.
• Shipped And Delivered Events — Shipment and delivery evidence by order and date.
• Open Order Exceptions — Quantity or shipping issues requiring a named owner.

Follow review to allocation and release to completion.