Case Study / 2026
National Freight & Consolidated Logistics E-Manifest System (v2)
Redesigning freight e-manifest architecture from rigid A-to-B shipments to consolidated multi-sender, multi-receiver cargo with sequential multi-stop routing and Level-H QR PDF verification.
3-Level
Cargo Hierarchy
Manifest -> Consignments -> Packing Lists
Binary(16)
Key Storage
Compact UUID indexing across tables
Level H
QR Resilience
30% error recovery with logo overlay
Multi-Stop
Route Model
Ordered pickups, drop-offs & weighbridges
problem
Why Single-Origin Manifests Broke Real Logistics
The legacy V1 schema coupled every manifest directly to one sender, one receiver, and one static origin-destination route. Real freight consolidation carries cargo from multiple shippers to multiple consignees with intermediate weighbridge checkpoints.
architecture
Decoupled Consignment & Route-Stop Topology
interactive diagram
Decoupled Consignment & Route-Stop Topology
V2 separates vehicle/transporter headers (manifest) from independent waybills (manifest_pengiriman), item-level dangerous goods packing lists (manifest_packing_list), and ordered route stops (manifest_rute_stop) linked optionally to consignments.
results
Operational Impact
Enabled consolidated cargo manifests, automated SMB-XXXX/S/[RomanMonth]/[Year] numbering, cumulative weight checks against vehicle JBI limits, and high-fault-tolerance QR PDFs scannable at field checkpoints.
Architecture Decisions
ADR 1 / accepted
Decouple Packing Lists and Route Stops from Manifest Root
Binding items directly to the manifest root prevented partial loading/unloading across stops.
Introduce manifest_pengiriman as the intermediate aggregate owning packing lists and referencing sender/receiver parties.
