1. SCM with Returns Management
  2. Features
  3. Stock requests
Feature · Stock requests

Stock requests

Give each returned item a responsible owner, quantity, location and review path.

OverviewMy return requests
SCM with Returns Management · Stock requests

My return requests

Stock requests

New
Record numberSubjectStatusItemLocationRequested units
SR-93774Draft sr-330DraftSI-8212SL-150620
SR-94027Review sr-922ReviewSI-3307SL-150580
SR-68702Approved sr-222ApprovedSI-7088SL-110860
SR-71615Executed sr-986ExecutedSI-5090SL-110660
SR-35059Rejected sr-413DraftSI-8287SL-110230
6 of 6 records
Draft sr-330Stock requests · SR-93774
Draft
ItemSI-8212
LocationSL-150
Requested units620
Required by19 Oct
Example screen with sample data

What you can do

Start with a traceable request

Inventory Coordinator prepares the stock request around one item and the location where work will occur. The subject tells the team what is being returned or moved. The requested units and required date make the expected work visible. The owner is a team member in the operating organization, and the counterparty is a storage location. This is the record everyone should open when they need to understand why quantity changed.

A return request should be specific enough for Inventory Reviewer to make a decision without reconstructing the case from messages. For example, a return dock can raise a request for a damaged batch, name the receiving location and identify the item. If the item uses lots, the team should inspect the lot evidence before reserving or posting quantity. The request revision matters: a decision on an earlier quantity should not be treated as approval for a changed one.

How the work is organized

  • Prepare. Set the item, owner, organization, location, counterparty, quantity and required date while the request is in Draft.
  • Review. Move the current revision into Review and attach the evidence the reviewer needs to make a reasoned decision.
  • Execute. Work from an Approved request, then reconcile the actual signed movement and the Executed date.

What to agree during setup

Decide how staff distinguish a return dock from a warehouse or quarantine area. Agree who can own a request, who may review it and how a revised quantity returns to the reviewer. Check the base unit on every active item before importing requests. Decide when staff should cancel a request instead of editing its purpose. An operations lead should also define which attachments are shared and which stay internal.

The organization and storage location must be correct before work starts. If a team operates across organizations, a local request must keep the organization, item and team member aligned. A location name alone is a poor substitute for its code and operating ownership. Keep the required date useful for prioritization, especially when return evidence arrives later than the goods.

Check the handoff on an actual case

Take a returned lot that has reached a receiving dock. Inventory Coordinator opens a Draft request for its item and expected units, assigns the owner and attaches a receiving file. Inventory Reviewer reads the current revision, records a decision and explains the reason. Once Approved, the coordinator checks eligible quantity and the actual destination before posting. The movement points back to the request, so Auditor can connect the physical change to the earlier decision.

Change the requested units during the rehearsal. Verify that the new revision gets a fresh review before the team treats it as approved. Repeat the case with a rejected request and confirm that no stock movement is presented as its completed effect. This makes the reviewer handoff concrete before live returns arrive.

What your team sees

  • My return requests — The coordinator’s assigned requests, with status, item, location and due date.
  • Requests in review — Current requests awaiting an independent decision.
  • Request workboard — Draft, Review, Approved and Rejected work grouped by status.

Follow the work through

What it keeps track of

Data model
Stock requests
Return and stock movement requests raised against a storage location counterparty
Stock items
Returnable and refurbishable items with base unit and lot tracking rules
Storage locations
Warehouses, return docks and quarantine areas receiving inspected stock
Organizations
Operating organizations that own return operations
Team members
Organization members who prepare, review and execute return operations

Who uses it

Permissions
Inventory Coordinator
Prepares and owns requests.
Inventory Reviewer
Decides the current revision.
App Administrator
Maintains operating scope; Auditor follows the completed record and its evidence.

Set up SCM with Returns Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started