Inbound receipt & staging — one record from the dray
Stage 5 · Warehouse & Transload
P1Expansion
Four-Lane View
Software Function
- ›Dray leg (Stage 2) auto-becomes the ASN: container arrives already expected, contents pre-loaded Receipt at dock: scan, count, condition photos — variance vs expected flagged live Staging inventory state: received-not-putaway visible to client instantly Warehouse receipt ISSUED into the same document chain as the eBOL
Service Provider / Admin
- ›Receiving supervisor works exceptions (variances, damage) not data entry Inbound labor scheduled from the container pipeline — no surprise trucks
User — Driver / IOO
- ›Dray driver’s handoff is one scan — no waiting for a clerk to find the paperwork
Customer — Client / FF / NVOCC
- ›Sees "container discharged → gated out → received: 1,847 units, 3 damaged (photos)" as one CLIENT/FF/NVOCC thread — the PO-to-shelf record no one else can render
Software Function
- ›Dray leg (Stage 2) auto-becomes the ASN: container arrives already expected, contents pre-loaded Receipt at dock: scan, count, condition photos — variance vs expected flagged live Staging inventory state: received-not-putaway visible to client instantly Warehouse receipt ISSUED into the same document chain as the eBOL
Competitors
Extensiv/Camelot (ASN modules fed by EDI from strangers), Manhattan (enterprise). All treat the truck as an external event.
Differentiation
Everyone else’s WMS learns about the container from an EDI message. Ours dispatched the truck — receipt is a state change, not an integration.
Make It Better
Container-to-visible-inventory in under 4 hours, photographed, reconciled against the PO — the "where is my freight" answer extended into the building.