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.
- Supply Chain Analytics
- Features
- Review Queue
Review Queue
Record an independent approver's decision on each submitted request and service snapshot.
OverviewReview Decisions Log×
Supply Chain Analytics · Review Queue
New
Review Decisions Log
Review decisions
| Parent | Source revision | Decision | Reason | Reviewer | Decided at | |
|---|---|---|---|---|---|---|
| PR-59577 | 370 | Approve | Approve rd-887 | 17 Oct | ||
| PR-55504 | 840 | Return | Reject rd-705 | 12 Oct | ||
| PR-34090 | 490 | Approve | Return rd-281 | 07 Oct | ||
| PR-51105 | 590 | Return | Approve rd-861 | 20 Oct | ||
| PR-82826 | 390 | Approve | Reject rd-404 | 09 Oct |
6 of 6 records
Approve rd-887Review decisions · RD-43090
ApproveParentPR-59577
Source revision370
Decided at17 Oct
What you can do
Approve the version that was submitted
A request becomes a supplier commitment only after someone other than the buyer approves it. A review decision records the decision (Approve, Reject or Return), the reason, the approver, the time and the version it applies to. A commitment can be issued only when an approval matches the request’s current version.
The same queue locks service snapshots. A snapshot is completed only after an independent approval of its submitted version, so reported fill rates cannot be changed quietly.
How the work is organized
- Approve. The request moves to Approved and can be issued; a snapshot is completed.
- Return. The work goes back with a reason for a revised version.
- Reject. The work stops, with the reason recorded.
What to agree during setup
Name approvers and their limits by budget code and amount. Agree what an approver checks on a request: supplier eligibility, quantities, price and budget. Agree what they check on a snapshot: scope, as-of date and the units behind it. Confirm buyers never approve their own requests.
Check the handoff on an actual case
A buyer submits a request for 500 pallets of corrugated boxes at a price 12 percent above the last order. The Procurement Approver returns it asking for the supplier’s quote. The buyer attaches the quote, which shows a resin surcharge, and resubmits.
The approver approves the new version with the reason “Surcharge confirmed for Q3.” When the buyer issues the commitment, the approval matches the current version, so the order reference is generated. The earlier return stays in the log.
During the pilot, have each approver return one request and approve its revised version, and reject one snapshot whose filled units exceed requested units. Check that a commitment cannot be issued from the earlier version and that every decision keeps its reason and approver.
What your team sees
- Requests Awaiting Approval — Submitted requests with supplier, amount, required-by date and version.
- Service Snapshots Awaiting Lock — Submitted snapshots with scope, as-of date and units.
- Review Decisions Log — Every decision with reason, approver and version.
Follow the work through
- Demand to receipt: Where approval sits.
- Fill rate snapshot lock: Locking a snapshot.
Rehearse access with a buyer account before go-live.
What it keeps track of
Data model- Review decisions
- Independent review decisions recorded against a source revision.
- Purchase requests
- Purchase demand records with lifecycle, owner, counterparty and approved commitment.
- Service snapshots
- Reconciled service snapshot records supporting the lock operation.
- Team members
- Named team members with organization membership and platform identity.
Who uses it
Permissions- Procurement Approver
- , Buyer, Supply Chain Analyst.
- The approver decides.
- Buyer
- S and analysts prepare and resubmit.
Set up Supply Chain Analytics your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.