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.
- Cold Chain SCM
- Features
- Evidence and reconciliation
Evidence and reconciliation
Trace attachments, operation results and exceptions to the request.
OverviewFailed operations×
Cold Chain SCM · Evidence and reconciliation
New
Failed operations
Operation receipts
| Parent | Operation key | Action | Expected revision | Result state | Occurred at | |
|---|---|---|---|---|---|---|
| SR-74155 | OK-304 | ACT-313 | 690 | Failed | 20 Oct | |
| SR-15086 | OK-182 | ACT-974 | 100 | Needs review | 25 Oct | |
| SR-12233 | OK-269 | ACT-603 | 510 | Failed | 25 Oct | |
| SR-36656 | OK-405 | ACT-454 | 340 | Needs review | 16 Oct | |
| SR-64132 | OK-941 | ACT-119 | 490 | Failed | 07 Oct |
6 of 6 records
OK-304Operation receipts · OR-13899
FailedParentSR-74155
ActionACT-313
Expected revision690
Occurred at20 Oct
Failure reasonCut to length
What you can do
Keep evidence attached to the action
Record attachments belong to a stock request and identify the uploader, type, title, upload time and visibility. Inventory Coordinator can supply supporting material for a reviewer. Shared visibility helps the authorized team read the same evidence; internal visibility keeps the scope explicit. The evidence stays connected to the request whose revision and decision are under discussion.
An operation receipt records a stable operation key, action, expected revision, result and time. It may carry an external reference, effect references or a failure reason. The result can be Pending, Completed, Failed or needs review. Inventory Reviewer can compare a receipt with its linked request and stock movements before concluding what happened.
How the work is organized
- Attach. Evidence is uploaded to the parent request with a type and visibility.
- Record. The operation receipt holds the action identity and persisted result.
- Reconcile. The reviewer compares the receipt with decisions and stock effects when the result is uncertain.
What to agree during setup
Agree on evidence types and the rule for internal versus shared visibility. Decide who verifies an upload and how long a supporting file remains accessible. Define the operation key format and which external systems supply a reference. If an action can be retried, require the same operation identity so the team can compare the new result with the persisted receipt.
Set a review routine for Failed and needs review results. The owner of that routine needs access to the request, decisions, receipt and related movements. Agree who closes the exception after the evidence has been checked and what note should explain the outcome.
Check the handoff on an actual case
An approved request appears with a receipt marked needs review. Inventory Reviewer opens the request, checks the expected revision and action key, then compares the effect references with posted movements. If a movement is present, the reviewer checks its quantity, lot and source effect key before deciding whether the action is complete. If no effect is present, the failure reason and supporting attachments guide the next investigation.
Repeat with a Failed result for a request whose review decision is older than its current revision. The team should see the mismatch and keep the earlier decision and receipt for audit. A later correction can add evidence without rewriting the original action history.
What your team sees
- Failed operations — Actions needing investigation with result and failure reason.
- Shared evidence — Request files available to authorized reviewers.
- Posted movements — Recorded stock effects to compare against an operation result.
Follow the work through
Follow evidence reconciliation and inspect stock outcome for the quantity trail.
What it keeps track of
Data model- Record attachments
- Uploaded evidence files linked to a stock request.
- Operation receipts
- Stable operation keys and persisted results for every guarded action.
- Review decisions
- Independent reviewer decisions recorded against a frozen request revision.
- Stock requests
- Operational stock requests that carry the lifecycle and revision for cold chain work.
- Stock movements
- Posted signed stock movements that establish on-hand quantity.
- Team members
- Authenticated platform identities with an operational role inside an organization.
Who uses it
Permissions- Inventory Coordinator
- Supplies request evidence.
- Inventory Reviewer
- Reconciles exceptions.
- Cold Chain Operations
- Follows operational results.
- Auditor
- Reads authorized evidence and reports.
Set up Cold Chain SCM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.