Stock requests

A stock request starts with a record number, subject, needed date, requested units and a named owner. The item and location references tell the coordinator what stock is in scope. The organization reference keeps the request with the company or site responsible for it. A counterparty location can identify the other physical endpoint when a move is involved.

The coordinator uses the request as the parent for scans, movement records, attachments, review decisions and operation outcomes. Keeping those links together makes a later question answerable: which physical read supported this request, who reviewed its revision, and what stock effect was recorded? A status alone is a short summary; the linked evidence gives the reason behind it.

• Prepare demand. Inventory Coordinator enters the subject, requested units, due date, item, location and owner before asking for review.
• Route a revision. Inventory Reviewer compares the current request with its attachments and records an approval, rejection or return with a reason.
• Follow fulfillment. Inventory Coordinator checks the posted movements and reservations linked to the request before treating the work as executed.

A draft is work in preparation. Review tells the reviewer which request needs a decision. An approved request authorizes the next operating step; it does not by itself say that stock moved. Executed is the request outcome after the team checks the physical action and its recorded effect. Rejected and Cancelled keep their own meaning and history.

Agree on what a request number identifies across sites, who owns each location and how the team records a move between locations. Decide which attachments are needed for receiving, issue and correction cases. Define how the requested unit relates to the item’s base unit before comparing demand with stock. A request for cases and an item stored in pieces need an agreed conversion outside the request record.

The reviewer needs a clear rule for revision changes. If the coordinator changes the item, quantity or location after review, the team should submit the new revision for another decision. The decision record carries the source revision, reviewer, date and reason so people can distinguish a current approval from an older one.

Suppose a maintenance team needs replacement parts from a storage location by Friday. The coordinator enters the item, needed quantity, owner and date, then attaches the issue instruction. The reviewer reads the same request and decides whether the quantity and destination are justified. Once approved, the coordinator checks the lot and reservation before recording a scan or movement.

If the scanner reads a different tag, the coordinator keeps the request open for investigation. The team should not interpret an approved request as evidence that the parts left the location. The linked scan, movement and operation receipt carry those later facts.

• Requests awaiting review — Requests whose current status asks for a review decision.
• My stock requests — Assigned work organized by owner and needed date.
• Active request board — Draft, review and approved requests grouped by status.

Continue with request review and scan to movement. Use the data model when mapping existing item and location lists.