Read-only trace
Follow any pack from factory gate to school desk
Every event keeps date, time, location, status and user. Finalised invoices are never edited — changes appear as linked amendments.
B2S-20261022-0012
DiscrepancyBlock → SchoolBlock SadarSample Govt. School A · 09-0123
Batch SC-2511-CSheCare Ultra 8sExp. 02 Nov 2028UP00 CD 0000 · Driver B
Parent invoice D2B-20261020-0007
- Sent
- 800
- Received
- 790
- Damaged
- 0
- Missing
- 10
Shipment timeline
Created to closed — each step with user and time.
Created
22 Oct 2026, 09:48
Draft for Sample Govt. School A · 800 packs of SC-2511-C
By block.u2
Invoice generated
22 Oct 2026, 09:55
B2S-20261022-0012 issued · parent invoice D2B-20261020-0007
By block.u2
Dispatched
22 Oct 2026, 10:02
Block stock 3,000 → 2,200 · 800 packs now in transit
By block.u2
In transit
22 Oct 2026, 10:20
Vehicle UP00 CD 0000 left Block Sadar store
By Driver B
Received at school
23 Oct 2026, 11:05
Sample Receiver confirmed 790 accepted, 0 damaged
By school.u1
Discrepancy reported
23 Oct 2026, 11:06
DSC-20261023-0006 · 10 packs missing · photos attached
By school.u1
Resolution
Pending since 23 Oct
Waiting for block officer — re-supply, write-off or adjustment
By block.u2
Closed
Not yet closed
Closes when DSC is resolved and RCV-20261023-0045 is reconciled
No actor yet
Batch traceability chain
Parent–child links survive splits into many shipments.
Factory dispatch
F2D-20251110-0003
12,000 packs · Parent invoice
Depot receipt
12 Nov 2025
12,000 accepted · Child of invoice 1
Depot to block
D2B-20261020-0007
3,000 packs · Child of receipt
Block to school
B2S-20261022-0012
800 packs · Child of invoice 3
School receipt
RCV-20261023-0045
790 received · 10 missing · Closes the chain
Recall reach · SC-2511-C
Every depot, block and school this batch reached.
Audit log
Every sensitive action with user, time and document. Read-only for auditors.
Integrity controls enforced by the platform
These guarantees back every figure shown on this screen.
Invoices are immutable
Finalised invoices are never edited; changes use linked amendments.
Unique invoice numbers
Numbers come from concurrency-safe sequences and cannot be reused.
Idempotent receiving
The same receipt can never add stock to a location twice.
One transaction per movement
Stock and dispatch records change together in a single database transaction.
History is never erased
Cancellations and returns are linked records, not deletions.