These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- SCM with Cycle Counting
- Features
- Stock requests
Stock requests
Give each count or stock operation a defined item, location, owner and requested scope.
OverviewMy Stock Requests×
SCM with Cycle Counting · Stock requests
New
My Stock Requests
Stock requests
| Record number | Subject | Status | Required by | Requested units | Item | |
|---|---|---|---|---|---|---|
| SR-66730 | Draft sr-427 | Draft | 09 Oct | 50 | SI-5056 | |
| SR-66517 | Review sr-851 | Review | 27 Oct | 430 | SI-3748 | |
| SR-23551 | Approved sr-335 | Approved | 25 Oct | 380 | SI-6638 | |
| SR-83824 | Executed sr-890 | Executed | 26 Oct | 150 | SI-7390 | |
| SR-47368 | Rejected sr-511 | Draft | 08 Oct | 110 | SI-9507 |
6 of 6 records
Draft sr-427Stock requests · SR-66730
DraftRequired by09 Oct
Requested units50
ItemSI-5056
LocationSL-140
What you can do
Start with a bounded request
Inventory Coordinator opens a stock request for the item and storage location where work will occur. The request identifies its organization, owner, requested units and required date. Its record number gives the count session, evidence, decision and eventual movement a common reference. A team can distinguish a request still in Draft from one in Review or Approved without relying on a comment thread.
Consider an item counted in a named storage location. The coordinator records the quantity being requested and the due date, then checks that the item uses the expected base unit. If the item is lot tracked, the team also identifies the relevant lot and its release state before any stock effect. The request revision matters because a decision on an older revision should not silently authorize a changed quantity.
How the work is organized
- Request scope. Record the item, organization, location, owner, quantity and due date on the parent request.
- Review history. Keep decisions and attachments linked to that same request so a reviewer can inspect the current revision.
- Execution trail. Link movements, reservations and operation receipts to the request that authorized the work.
The owner can prepare a request and move it to Review. Inventory Reviewer makes the independent decision. Warehouse Operator handles physical movement only after the relevant scope has been authorized. Program Manager checks that execution and review remain tied to the same record number.
What to agree during setup
Decide how the team chooses a storage location and when it uses Counterparty for another location. Agree how requested units are entered in the item’s base unit, who owns requests that cross shifts, and when a due date makes work urgent. Set the rule for correcting a request after review begins. A new revision needs a new decision if the approved scope changes.
Define when a request moves to Cancelled and who releases a related active reservation. A request already Executed needs a traced compensating movement for any stock correction. Keep the original execution history available to the reviewer. Agree what source evidence staff will retain on the request.
Check the handoff on an actual case
Take a request for a lot-tracked item at a single location. Have Inventory Coordinator enter its requested units, owner and date. Open a count session under that request and attach the source evidence. Then ask Inventory Reviewer to inspect the revision and decision history before approval. Finally, check whether the posted movement and operation receipt point back to the same parent. A mismatch is a handoff issue to resolve before the count is closed.
What your team sees
- My Stock Requests — The owner’s requests with status, due date, item and location together.
- Requests in Review — Requests awaiting an independent decision on the current revision.
- Stock Request Board — Work grouped across draft, review, approval and execution states.
Follow the work through
See count and review and stock execution.
What it keeps track of
Data model- Stock requests
- Operational stock request that parents counts, movements and reviews.
- Stock items
- Stock keeping units with base unit and lot tracking policy.
- Storage locations
- Warehouses, zones and storage locations where stock is held.
- Count sessions
- Blind cycle count sessions for a stock request and zone.
- Review decisions
- Independent reviewer decisions on a source revision.
- Stock movements
- Posted signed stock movements; the only source of on-hand balances.
- Stock reservations
- Reservations that reduce available quantity without changing on hand.
- Operation receipts
- Idempotent execution receipts for each guarded operation.
Who uses it
Permissions- Inventory Coordinator
- Prepares and revises the request.
- Cycle Count Operations
- Records assigned count work.
- Inventory Reviewer
- Decides the review scope.
- Warehouse Operator
- Handles physical effects.
- Program Manager
- Checks completion.
Set up SCM with Cycle Counting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.