Logistics agent delivery, by the numbers
04
- week delivery cycles
- 10-14
A tracking dashboard shows you what happened. An AI agent decides what to do about it. When a shipment misses a checkpoint, an agent can classify the exception, check carrier ETAs, draft the customer update, and route the case to a dispatcher only when the situation falls outside its resolution logic.
We build logistics AI agents with defined scope, explicit escalation rules, and integration into the carrier APIs, TMS platforms, and customs systems your operations already depend on. Integration is scoped during discovery because that's where most logistics projects carry the most hidden complexity.
Capabilities
What we build
01Carrier selection and booking agent
Queries connected carrier APIs and rate engines using shipment parameters, applies your routing guide logic, and submits bookings via carrier API or EDI when a carrier meets all criteria. Confirmations write back to the TMS with PRO number and pickup window. Lane exceptions, spot-market decisions, and new carrier relationships route to your team; the audit trail captures every rate query and booking so lane performance accumulates automatically.
- Built with
- LangGraph · EDI 204
02Customs document automation agent
Generates commercial invoices, packing lists, and certificates of origin from structured shipment data. HS code classification uses a trained model plus knowledge base; low-confidence classifications route to a trade compliance reviewer with the rationale attached. New trade lanes require human review before submission; established lanes with validated templates can move to exception-only review.
- Built with
- ACE filing · SAD
03Delivery exception handling agent
Classifies exception events, weather delay, address correction, damage, customs hold, against a defined taxonomy and applies resolution logic automatically for classes with playbooks. A weather delay with a strong carrier recovery rate triggers a customer notification with no dispatcher action; a damage report triggers a claim workflow with the case pre-documented. Escalation happens when the exception falls outside the taxonomy or involves a flagged SLA.
- Built with
- project44 · Fourkites
04Shipment status update agent
Pulls tracking data from carrier APIs and aggregators, normalises it to a unified status taxonomy, and pushes structured updates to customer portals, ERP records, and internal channels. A status cache answers "where is order 98765?" in seconds without a live carrier API call. High-priority shipments get more frequent polling and immediate push notifications on any change.
05Invoice reconciliation agent
Matches carrier invoices against rate confirmations, BOLs, and TMS records to catch billing discrepancies before payment, weight disputes, accessorial disputes, rate disputes, duplicate invoices. Discrepancies below a threshold generate a dispute notice automatically; above it, they escalate to a freight auditor with the matched record for review. Monthly reports show total billed, disputed, and recovered by carrier.
- Built with
- EDI 210
06Demand forecasting agent
Analyses historical volume, seasonal patterns, and confirmed order history to generate lane-level and carrier-capacity forecasts. Capacity risk signals flag lanes where forecast volume exceeds contracted capacity or carrier performance has degraded, each with supporting data attached. Commercial decisions, requesting spot capacity, adjusting contracted volumes, stay with your carrier relations team.
- Built with
- SARIMA · Prophet
How we work
From scope to live agent
- Week 1
01Workflow and TMS scoping
We map the target workflow, your TMS and carrier API coverage, and escalation logic. You leave week 1 with a written scope document and a fixed-price quote.
- Weeks 2-3
02Routing and playbook design
Routing guide rules, exception taxonomy, and human-in-the-loop checkpoints defined and confirmed with your operations team.
- Weeks 4-10
03Build and integrate
Agent workflow built against LangGraph, tested against real TMS and carrier sandbox data every sprint.
- Final 2 weeks
04Launch and monitoring
Production deployment with audit logging and escalation queues staffed from day one.
Why us
Why logistics operators choose RaftLabs
01Senior engineers build what they scope
The engineers who assess your carrier network also build the solution. No bait-and-switch, no offshore handoff after the contract is signed.
02Fixed price before development starts
We scope the work, calculate the cost, and lock it in writing before any development starts.
039 years and 100+ products shipped
Clients include Vodafone, T-Mobile, Aldi, Nike, Cisco, and Lockheed Martin. Track record building logistics and carrier-integration platforms.
04Normalisation handles your full carrier mix
REST JSON, EDI, and PDF invoices all translate into one schema before the agent reasons over them, so the agent applies the same logic regardless of how a carrier delivers data.
05Customs stays human-reviewed on new lanes
The agent doesn't submit to customs authorities without a review step for new trade lanes. Established lanes can move to exception-only once templates are validated.
Have a logistics AI agent project?
Tell us the workflow you want to automate, your TMS platform, and your carrier mix. We'll scope what an agent can handle and give you a fixed cost.