Delivery order intake & client onboarding
Stage 2 · Dispatch & Drayage Operations
P1Core Operations
Four-Lane View
Software Function
- ›DO ingestion from FF/NVOCC/importer via EDI 204/990, API, and AI email/PDF parsing Auto-create the shipment record: container #, SSL, vessel/ETA, commodity, delivery window Client rules engine: accessorial rates, free-time terms, notification preferences Credit check + published rate agreement at client onboarding
Service Provider / Admin
- ›Client ops reviews AI-parsed DOs only on low confidence Owns rate agreements and free-time terms per client Monitors intake SLA: DO → dispatchable in minutes, not hours
User — Driver / IOO
- ›Clean, complete work orders — pickup #, terminal, chassis plan, delivery window — no calling dispatch for basics
Customer — Client / FF / NVOCC
- ›Email a DO like they do today, or connect API/EDI — zero forced workflow change on day one Instant confirmation with the FreightShift shipment record link
Software Function
- ›DO ingestion from FF/NVOCC/importer via EDI 204/990, API, and AI email/PDF parsing Auto-create the shipment record: container #, SSL, vessel/ETA, commodity, delivery window Client rules engine: accessorial rates, free-time terms, notification preferences Credit check + published rate agreement at client onboarding
Competitors
PortPro (DO management core), Trinium (EDI depth), McLeod RespondAI (email-to-order), Uber Freight AI agents
Differentiation
Incumbents force clients onto portals or choke on email. We meet FFs/NVOCCs where they are — parse anything, confirm instantly, and upgrade them to API later.
Make It Better
A forwarder can tender a container by forwarding an email and get a tracked, dispatched, visible shipment back in under 10 minutes.