DFD — Parcel Sortation Hub
Inbound trailer to outbound van at a parcel hub, proving that the scan, route and customs stores are each both written and read, and flagging the 7 flows that reach the partner network.
Make it your own.
title "Parcel hub — inbound trailer to outbound van"
level 1
entity "Retail shipper API"
entity "Line-haul driver"
entity "Delivery courier"
entity "Customs (CDS)"
process 1 "Pre-advise consignment"
process 2 "Unload and scan inbound"
process 3 "Sort to outbound lane"
process 4 "Clear cross-border parcels"
process 5 "Load van and manifest"
process 6 "Publish tracking event"
store D1 "Consignment master"
store D2 "Scan events"
store D3 "Route plan"
store D4 "Customs declarations"
boundary "Partner network" { "Retail shipper API", "Customs (CDS)" }
boundary "Hub operations" { 2, 3, 5, D2, D3, "Line-haul driver", "Delivery courier" }
boundary "Core platform" { 1, 4, 6, D1, D4 }
"Retail shipper API" -> 1 : "EDI 214 pre-advice"
1 -> D1 : "consignment header"
"Line-haul driver" -> 2 : "trailer seal + barcode"
D1 -> 2 : "expected parcels"
2 -> D2 : "inbound scan"
D2 -> 3 : "parcels on belt"
D3 -> 3 : "lane assignment"
3 -> D2 : "sort scan"
3 -> 5 : "sorted totes"
D1 -> 4 : "declared value + HS code"
4 -> "Customs (CDS)" : "H1 declaration"
"Customs (CDS)" -> 4 : "clearance or hold"
4 -> D4 : "clearance status"
D4 -> 5 : "released parcels"
5 -> D3 : "planned route"
5 -> "Delivery courier" : "manifest (142 stops)"
D2 -> 6 : "scan stream"
6 -> "Retail shipper API" : "tracking webhook"