eBOL, POD & document issuance
Stage 2 · Dispatch & Drayage Operations
P1Core Operations
Four-Lane View
Software Function
- ›We ISSUE the eBOL/POD/warehouse receipt — generated, e-signed, timestamped, GPS-anchored Document chain: DO → gate receipts → eBOL → POD → invoice, one thread per shipment Instant availability to client and (Stage 7) factoring engine — fraud-proof by construction
Service Provider / Admin
- ›Zero document chasing: billing starts the second POD signs Audit-grade document vault per client
User — Driver / IOO
- ›Sign and go — no paper, no photos of crumpled BOLs, no lost detention proof
Customer — Client / FF / NVOCC
- ›Every document on the shipment record in real time, issued by one party — not four emailed PDFs CLIENT/FF/NVOCC from strangers
Software Function
- ›We ISSUE the eBOL/POD/warehouse receipt — generated, e-signed, timestamped, GPS-anchored Document chain: DO → gate receipts → eBOL → POD → invoice, one thread per shipment Instant availability to client and (Stage 7) factoring engine — fraud-proof by construction
Competitors
Every TMS attaches documents; Uber/DAT collect them. Nobody ISSUES the full chain as the system of record.
Differentiation
The deck’s core claim operationalized: we didn’t receive these documents, we issued them. That’s why our visibility, billing, and factoring can’t be replicated by integrators.
Make It Better
Invoice latency collapses from days to minutes because the POD is born digital inside our chain — and it’s the anti-fraud backbone the factoring engine monetizes later.