Replenishment signals

A replenishment signal records the bin, requested units, trigger date, order and organization for a pull request. The Order Coordinator prepares it while the signal is in Draft. Submission moves that request to Submitted at the expected revision. The operation records a receipt under a stable key so the team can inspect what happened when a submission is repeated or refused.

The saved Task Board by Status on replenishment signals is the shared screen for the signal lifecycle. It groups records by their status, from preparation through the current recorded state. This is where the coordinator and reviewer can see which requests need attention without treating a colored card as evidence of physical fulfillment.

• Demand context. Each signal points to a customer order and organization.
• Pull detail. The bin code and requested units say what the empty-bin request concerns.
• Revision control. Submission checks the current revision and records the operation result.

A signal’s identifier distinguishes one pull request from another. For a customer with recurring demand, ask the team to record the bin code consistently. That makes repeated signals easier to compare and avoids treating similar text as the same physical bin.

Decide what constitutes an empty bin and who may enter the requested quantity. Agree which order should receive a signal when multiple customer orders call for the same product. Use the customer and organization records to keep the request within its authorized scope. Train coordinators to inspect the current draft before submitting; a changed revision is a reason to review the card again.

Agree who can authorize a decision before treating a submitted card as approved work. Review Decisions holds a source revision, decision, reviewer, date and operation key when a decision is recorded. Read the board alongside any decision record; submitting the card alone gives no approval.

Prepare a pilot order with a known empty bin. Enter the signal, requested units and parent order. Have the coordinator submit the current draft. Verify the card appears under Submitted and that the operation receipt shows a completed result. Try to submit an older revision. The result should be a failed receipt, with the submitted signal unchanged.

Ask the reviewer to inspect the submitted scope and identify the order line that justifies the quantity. The coordinator can find the signal from the order and follow its submitted state on the board. An Auditor can reconstruct submission from the receipt, revision and occurrence date.

• Task Board by Status on replenishment signals — Pull cards arranged by their current state.
• Operations Overview — Pending reviews and failed operations in the authorized scope.

Follow an empty-bin request and review a signal.