Request review

Open Stock Requests puts requested quantity beside the item, locations and required date. Inventory Clerk prepares the request so Inventory Supervisor can decide what may proceed. A request can be Draft, Review, Approved, Executed, Rejected or Cancelled. A review decision separately records Approved, Rejected, Returned or Escalated. Keep request progress and the decision outcome clear so the clerk can identify the next permitted action.

Inventory Supervisor runs the review action for the current request. It records the decision against that request, increments the revision for an approved state and writes the matching operation receipt. The result is a traceable authorization for a particular request scope, with stale input refused before it can replace a later decision.

Start with a complete request and its supporting attachments. Inventory Clerk identifies item, location, counterparty location, organization and owner, then checks requested units and required date. Inventory Supervisor uses the current revision when deciding the request and records the rationale for the outcome. A second browser showing an earlier revision cannot authorize the newer request by accident.

• Preparation ownership. Link the request owner to the operating team member and confirm that person’s platform account during setup.
• Decision evidence. Each review decision retains source request, decision, rationale, revision and decision date so the next person can inspect the basis.
• Repeat handling. The stable operation key replays the original decision result; a retry is not permission to create another decision effect.

Agree what evidence makes a request ready for Review and how the clerk communicates the intended receive, move, reserve or issue action. Use a clear subject and supporting evidence so the supervisor can distinguish the operating cases. Rehearse the action input for each case before the team uses it during a live shift.

Inventory Supervisor decides the request. Auditor reads the queue and its supporting evidence. Agree who may run the review action and test that responsibility under each person’s account. Use Review Queue for decisions. During setup, filter Stock Requests Register to Draft requests owned by the signed-in clerk for preparation. Keep those handoffs clear when the request changes.

Inventory Clerk prepares a 45-unit request at revision 3. Inventory Supervisor approves it, advancing the revision. Another browser still shows revision 3. A separate decision attempt using that stale revision must be refused. The supervisor reloads the request before considering any further decision.

Repeat the accepted call with its original stable operation key. Inspect the review decision and Operation Receipts Register to confirm that the response refers to the earlier result. Then try to review an Executed request and a Cancelled request. Neither may be reopened by the decision workflow. If further operational work is required, establish the correction or reversal path rather than treating another approval label as a repair.

• Open Stock Requests — In-flight demand with quantity, required date, owner and revision together.
• Review Queue — Requests awaiting the supervisor’s decision on the current quantity and evidence.
• Stock Requests Register — The clerk’s draft requests with required date and preparation details together.

Follow request review into reservation. Use scope correction when an authorized quantity changes.