Stock requests

Inventory Coordinator prepares a stock request for an organization, item and location. The request identifies an owner, required date, requested quantity and revision. It can also name a counterparty location. Those facts give Inventory Reviewer a concrete scope to decide: which stock, where, for how much and by when.

A request starts as Draft and can move into Review. A reviewer decision belongs to a source revision, so a later edit is not silently covered by an earlier decision. Approved, Executed, Rejected and Cancelled are distinct outcomes. Inventory Coordinator can use the status to locate work, while the decision record gives the reviewer and reason behind a decision.

• Prepare. Inventory Coordinator identifies the item, locations, owner, quantity and required date.
• Review. Inventory Reviewer examines the request revision and the related evidence before making a decision.
• Outcome. The request status gives the operating team a shared place to find approved, executed or closed work.

Agree when a coordinator may submit a draft and which changes require another review. Set the required date in the organization’s time zone and decide how the team will handle requests due soon. Define how the owner is assigned and who covers that owner when unavailable. Decide what supporting attachment is expected for a request involving a hold or exception.

The request records support both a source location and a counterparty location. Confirm what each means for your operation before importing open work. If a request can change after review, make its revision and any fresh reviewer decision part of the handoff.

Inventory Coordinator prepares a request for a refrigerated item at an active location and checks a candidate lot that is released. The coordinator records the quantity, owner and required date, then checks the candidate lot expiry and any linked reservation for that stock context. Inventory Reviewer reads that scope and records a decision with a reason against the current revision.

Now change the requested quantity. The earlier decision still describes the earlier revision. The team should examine the new scope and record its decision rather than treating the old approval as transferable. If work is rejected, retain the reason and related evidence. If approved work later executes, the movement and operation receipt should still lead back to the request.

• My stock requests — Assigned work with status and due date in one list.
• Requests under review — Current review work with revision and stock context.
• Request status board — Requests grouped by their recorded stage.

Use request review for the decision handoff and stock outcome for the resulting record trail.