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
- Review and evidence
Review and evidence
Keep count evidence, independent decisions and guarded operation outcomes together.
OverviewDecisions by Reviewer×
SCM with Cycle Counting · Review and evidence
New
Decisions by Reviewer
Review decisions
| Parent | Reviewer | Decision | Source revision | Decided at | Reason | |
|---|---|---|---|---|---|---|
| SR-21990 | Approve | 610 | 15 Oct | Approve rd-521 | ||
| SR-97813 | Return | 670 | 12 Oct | Reject rd-838 | ||
| SR-46817 | Approve | 670 | 05 Oct | Return rd-864 | ||
| SR-95079 | Return | 650 | 14 Oct | Approve rd-136 | ||
| SR-53910 | Approve | 110 | 17 Oct | Reject rd-964 |
6 of 6 records
Approve rd-521Review decisions · RD-32148
ApproveParentSR-21990
Source revision610
Decided at15 Oct
What you can do
Put the decision on the right revision
A review decision names the parent stock request, reviewer, source revision, decision, time and reason. This gives Inventory Reviewer a specific scope to approve, reject or return. The count session holds the physical and recount quantities; attachments hold supporting files. The reviewer can compare the submitted observation with the request and evidence before any adjustment is treated as authorized.
Suppose Inventory Coordinator submits a count and later changes the requested quantity on the parent request. A decision against the earlier revision should remain visible as history, but it should not quietly authorize the changed scope. The review handoff is to inspect the current revision and record a fresh reasoned decision when the source changes. That protects both the counter and the reviewer from ambiguous approval.
How the work is organized
- Source evidence. Link attachments to the stock request and record their type, uploader and visibility.
- Independent decision. Record the reviewer’s decision and reason for a named source revision.
- Execution outcome. Use operation receipts to compare a guarded action with its linked effects.
An operation receipt has an operation key, action, expected revision, result state and effect references. It can be Pending, Completed, Failed or needs review. This is the trace for repeated or uncertain operations. A receipt marked Completed should point to the expected effect; a failed receipt should expose its reason for follow-up.
What to agree during setup
Assign reviewers separately from count preparers. Define which attachments can be Shared and which stay Internal. Agree what evidence justifies an Approve, Reject or Return decision, and require a reason for each. Decide who examines failed receipts and how discrepancies are escalated. The team should distinguish a count approved by a person from an operation receipt completed after its effects were verified.
Set a stable operation key for each guarded action. A retry with the same key should be checked against prior effects before any new movement is appended. If a receipt’s expected revision differs from the current request, send it to review. Keep the reviewer name and decision time alongside the reason so the audit trail can be read without reconstructing a conversation.
Check the handoff on an actual case
Submit a count session for a request with an attachment. Ask Inventory Reviewer to check the physical quantity, recount, attachment and revision, then record Approve with a reason. Have Warehouse Operator record the approved effect. Compare the operation receipt’s key and effect references to the movement. Repeat the check with a missing effect reference: the receipt should stay in the review queue until someone resolves the discrepancy.
What your team sees
- Count Sessions Awaiting Review — Submitted counts that need an independent decision.
- Decisions by Reviewer — Revision-specific decisions with reason and time.
- Receipts Needing Review — Guarded actions whose effects require investigation.
Follow the work through
See count and review and reconciliation.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions on a source revision.
- Record attachments
- Uploaded evidence files linked to a stock request.
- Operation receipts
- Idempotent execution receipts for each guarded operation.
- Count sessions
- Blind cycle count sessions for a stock request and zone.
- Stock requests
- Operational stock request that parents counts, movements and reviews.
- Stock movements
- Posted signed stock movements; the only source of on-hand balances.
- Team members
- Named staff tied to a platform identity and organization.
Who uses it
Permissions- Inventory Reviewer
- Makes decisions and checks exceptions.
- Inventory Coordinator
- Supplies source evidence.
- Warehouse Operator
- Records the physical effect.
- Program Manager
- Monitors unresolved receipts.
Set up SCM with Cycle Counting your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.