Empty-bin request

Step by step

1. Identify demand Order Coordinator

   Order Coordinator reads the customer order, promised date and line quantities before starting a pull request. The order gives the signal its commercial context.

   • Establish the parent demand and remaining units
   • Updates Customer orders, Order lines

2. Check customer eligibility Order Coordinator

   Order Coordinator checks the customer and organization associated with the order. A wrong customer or organization would send replenishment work into the wrong scope.

   • Confirm the intended account and organization
   • Updates Customers, Organizations

3. Prepare signal Order Coordinator

   Order Coordinator enters the bin code, requested units and parent order on a Draft signal. They check the current revision before submission.

   • Record the bin and requested units on the order
   • Updates Replenishment signals, Customer orders

4. Submit signal Order Coordinator

   Order Coordinator submits the draft. The signal moves from Draft to Submitted at the expected revision, and a completed operation receipt records the action under a stable key.

   • Record the submitted revision and operation result
   • Updates Replenishment signals, Operation receipts

5. Inspect receipt Order Coordinator

   Order Coordinator compares the completed receipt and stable operation key with the signal. Order Reviewer can inspect the same submitted scope.

   • Compare operation result with submitted revision
   • Updates Operation receipts, Replenishment signals

6. Trace outcome Order Coordinator

   Order Coordinator follows the submitted signal and its receipt. Fulfillment events and line quantities provide the later physical trail.

   • Compare later events with remaining demand
   • Updates Fulfillment events, Order lines

Order Coordinator

Prepares and submits; Order Reviewer inspects submitted scope; Auditor reads the trail; App Administrator maintains membership.