Stock requests

An Inventory Coordinator raises a request for a specific item, location, quantity and required date. The request owner can identify the intended counterparty location and keep the store proposal linked to the same parent. A request starts in Draft. Review, Approved, Executed, Rejected and Cancelled distinguish work awaiting a decision from work with a recorded outcome.

Each request has its own owner and revision. The coordinator checks the item and destination before asking for review, and keeps the source location in the counterparty field. The reviewer reads the same revision that the coordinator submitted. A reservation or proposal linked later does not replace the request as the case record.

• Prepare the request. Inventory Coordinator records the organization, owner, item, destination location, counterparty, units and required date.
• Present the current revision. Attach the store explanation and check that the reviewer sees the latest request details.
• Record the decision. Inventory Reviewer records Approve, Reject or Return with a reason against that revision; the request status shows the resulting handoff.

Agree how a store identifies the source and destination locations, how the required date is set, and who owns each request. Keep the item base unit consistent with the requested units. For example, when a store needs another case of a lot-tracked item before Friday, the coordinator records the item and destination, then attaches any supporting explanation to the request.

Inventory Coordinator owns request preparation. Inventory Reviewer decides on the current revision. App Administrator maintains the item and locations used by both people. Auditor follows the linked decision and stock evidence.

The reviewer reads the current revision and the linked proposal before deciding. A returned or rejected decision should carry a reason. After approval, the coordinator can trace reservations and posted movements back to the request; the receipt shows whether the guarded action completed or needs attention.

For the store that needs a case of a lot-tracked item before Friday, compare the requested units with the item base unit and the destination location. If the reviewer returns the case, keep the reason and revise the request before another review. After approval, compare the reservation with the posted movement; only the posted movement establishes a stock effect.

• Requests awaiting review — Requests in Review with owner, item, location, required date and revision for the reviewer.
• Open stock requests — Draft, Review and Approved work for the coordinator to follow.
• Requests due — Requests at or past their required date for a timing check.

See request review for the decision path and stock execution for the resulting stock effect. The data model shows the record links behind the screens.