Stock requests

Keep each proposed stock operation tied to a named owner, SKU, location and reviewable revision. Keep the related request, decision and stock evidence together as the case moves between people.

• Record the operating identity. Inventory Coordinator begins with the apparel SKU and the location that will be affected. The request records the organization, owner, counterparty, requested units and required date. A clear subject gives the reviewer enough context to find the operating reason without treating the subject as approval evidence.
• Keep the control visible. The request status distinguishes preparation, review, approval and execution. The revision matters because a decision must be tied to the version actually reviewed. When quantity or location changes, the coordinator should bring the new revision back through review instead of relying on an earlier decision.
• Make the decision traceable. The reviewer records a decision and reason against the source revision. A returned case needs a corrected request; a rejected case remains visible as a decision, not as an invisible deletion. The coordinator only proceeds from an approved version that still matches the intended stock effect.

Agree who can own a request for each organization and who independently reviews it. Decide how the team will name subjects, identify counterparties, and reconcile a request with its posted movement and operation receipt.

Use a real size-color SKU and storage location to rehearse the first case. App Administrator should confirm the entity and site codes; Inventory Coordinator and Inventory Reviewer should agree which revision is ready for a decision. Keep that convention available to Auditor when the movement is reconciled.

A coordinator requests a size-color SKU for a distribution location before a seasonal launch. The reviewer finds that the location is wrong, records Return with a reason, and asks for correction. The coordinator updates the request revision and resubmits it. Once the reviewer approves the new revision, the team checks the lot and records the eventual signed movement against that same request.

At the handoff, compare the current request revision with the reviewer decision and any related lot, claim, receipt or posted movement. If a reference differs, give the case back to Inventory Coordinator with the mismatch named. Keep the earlier decision and effect visible to Auditor.

• Requests in review — Requests awaiting an independent decision, with revision and due date visible.
• Request board — The coordinator’s owned work with current status and requested units.

Open the underlying record before making a decision that depends on revision, expiry, ownership or location. Inventory Reviewer should read the linked request and evidence before recording a reason; Auditor can follow the same references later.

See the operating handoff and the implementation sequence. Use the data model when mapping existing identifiers and references.