Allocation and shipment

Step by step

1. Select order Fulfillment Operator

   Fulfillment Operator reads the customer order, promised date, product lines and related exceptions. An expired batch or stock shortage needs an owner before the team proceeds.

   • Confirm operating scope
   • Updates Customer orders, Order lines, Order exceptions

2. Allocate lines Fulfillment Operator

   Allocation examines Draft and Open lines, creates an allocated fulfillment event for each eligible line and changes its line status to Allocated. Existing allocated events prevent a repeated request from producing another event for the same line.

   • Draft or Open → Allocated; allocated event
   • Updates Order lines, Fulfillment events, Operation receipts

3. Check approval Fulfillment Operator

   Order Reviewer has recorded the independent decision. The operator also checks the order is in its Approved state before release.

   • Decision and Approved order state checked
   • Updates Review decisions, Customer orders
   ApprovalA person approves before the work moves on.

4. Release shipment Fulfillment Operator

   Fulfillment Operator starts release on the approved order. A shipped event is recorded for each line, and the lines become Fulfilled. The operator checks event quantity, facility and occurrence date against the work performed.

   • Shipped event; lines Fulfilled
   • Updates Customer orders, Order lines, Fulfillment events

5. Follow event history Support Specialist

   Support Specialist can find shipped, delivered, returned or failed event records when a customer asks what happened after release.

   • Event and issue follow-up
   • Updates Fulfillment events, Order exceptions

Fulfillment Operator

Allocates and releases.

Order Reviewer

Owns the approval decision.

Support Specialist

Follows exceptions and later events.