Shipment Twin

A live, AI-reasoned digital replica of every in-transit load across your global network.

Talk to an Outcome Advisor
Closed cardboard box with glowing blue grid pattern and flowing blue particles on black background.

See what your shipment will do next, not just where it is right now.

The Shipment Twin pulls data from your TMS, carriers, freight forwarders, and IoT sensors, then layers in weather, traffic, port congestion, and carrier history to build ETAs that get sharper the closer the shipment gets. What you end up with is the full picture: origin, destination, predicted arrival, exception status, carrier performance, all in one object that every other twin, agent, and system treats as the source of truth.

Supply Chain Objects Modeled

​

Load / Shipment

The primary object. A single freight movement with a carrier, origin, destination, and one or more stops. Attributes include mode (TL, LTL, Parcel, Ocean, Air, Rail, Intermodal, Drayage, Final Mile), carrier SCAC, PRO number, BOL, booking reference, and commodity details.
​

Stop

Each point in the shipment journey: pickup, intermediate stop, cross-dock, port of loading, transshipment, port of discharge, final delivery. Carries planned vs. actual timestamps, geofence events, dwell time, and appointment linkages.
​

Carrier / Equipment

The entity performing the movement. Linked to tracking method (ELD, API, mobile, EDI 214), equipment type (dry van, reefer, container, railcar, aircraft), and historical lane performance.
​

ETA / Prediction

A continuously refined arrival estimate for each stop. Incorporates live GPS, weather, traffic, port congestion, and the carrier's historical behavior on that lane (p50/p90/p99 transit distributions).
​

Exception

Any deviation from plan: late departure, missed pickup, temperature excursion, stopped movement, detention threshold breach. Classified by root cause (carrier, weather, shipper, facility) using network intelligence.

Execution Systems Ingested

TMS
Load tenders, planned shipments, carrier assignments, planned stops. SAP TM, Oracle OTM, Blue Yonder, MercuryGate, Manhattan, and custom platforms.
Carrier Systems
GPS/ELD location pings, EDI 214 status updates, carrier portal milestones, ocean carrier AIS vessel positions.
Freight Forwarders
Booking confirmations, multi-leg routing, container tracking, customs clearance milestones.
3PL / Broker Systems
Shipment creation via API or SFTP, milestone updates, proof of delivery documents.
IoT and Telematics
Temperature sensors, door open/close events, shock/tilt sensors for high-value or cold chain freight.

When you need this Twin

Your logistics team manually checks carrier portals and calls dispatchers for shipment updates, consuming hours of labor that should be spent on exception management and strategic decisions.

Late shipments are discovered reactively, after they have already impacted production schedules, appointment windows, or customer delivery commitments.

You operate across multiple carriers, modes, and geographies, but each mode has its own tracking silo. There is no unified view of all in-transit freight.

ETA accuracy is poor because existing systems rely on static transit times rather than live signals adjusted for weather, traffic, and actual carrier behavior.

Carrier performance conversations during RFPs are based on self-reported data rather than objective, lane-level reliability evidence.

Ocean shipments disappear into a black box after booking. No reliable container-level visibility between port of loading and port of discharge.

Core Capabilities

Capability
Description
Unified Multi-Modal Data Model
A single shipment object for all nine transportation modes. One API, one view, one set of events, regardless of mode.
ML-Powered Predictive ETAs
Arrival predictions trained on FourKites network data: lane-level distributions, carrier patterns, weather, traffic, port congestion. ETAs improve as the shipment moves.
Automated Exception Detection
Real-time identification and root-cause classification of late, at-risk, stopped, and temperature-deviated shipments.
Carrier Performance Intelligence
Objective reliability scoring by carrier, lane, mode, and season, built from actual outcomes across the FourKites network.
Agent-Ready Architecture
Tracy, Cassie, and Alan consume Shipment Twin data directly to trigger autonomous exception resolution, customer updates, and appointment adjustments.
Bidirectional System Sync
Status, ETAs, and exceptions flow back to your TMS, ERP, and WMS via REST API, webhooks, and EDI.

Frequently Asked Questions

Track-and-trace shows you where a truck is. The Shipment Twin models the entire shipment as a digital object: predicted arrival, downstream impact if late, carrier reliability on that lane, and which Digital Workers are already acting on exceptions. It is an AI-reasoned model, not a GPS dot on a map.

The Shipment Twin feeds all siblings. The Order Twin consumes shipment events to update PO fulfillment status. The Facility Twin consumes inbound ETAs for appointment scheduling. The Inventory Twin consumes in-transit positions for forward-looking projections. The Order Twin sends PO context back so exceptions can be prioritized by order value.

Multi-leg, multi-mode journeys are handled natively. An ocean container moving from origin port via vessel, through transshipment, to discharge via drayage, and final destination via truck is modeled as one shipment with mode-specific tracking at each leg.

One billion hours 
of operational work completed by AI agents over the next decade

Talk to an Outcome Advisor