Shippeo

Shippeo is a European transportation visibility platform that pulls tracking data from more than 1,100 TMS, telematics, ELD, AIS and parcel sources across road, ocean, rail and air. Connected to Cargofy, every shipment in Tracking carries its milestones and a predictive ETA, and the team stops chasing carriers for status. A logistics manager who runs Shippeo and wants its exceptions worked usually switches it on.

What teams use it for

Send a booking to Shippeo when it is confirmed

When a planner confirms a carrier, Cargofy writes the shipment to Shippeo as a transport order, with the carrier, lane and dates taken from the load. The planner no longer keys the order into Shippeo by hand to start tracking. The shipment appears in Tracking with a Shippeo status on it.

Follow a container from vessel to truck

A container bound for a plant near Lyon sails from Rotterdam to Marseille, with a road leg to follow. Shippeo reads AIS milestones while the box is at sea. After the road carrier picks it up in Marseille, the carrier's telematics feed the same shipment. Every milestone lands on one shipment in Cargofy. Customer service opens it in Tracking and reads one timeline from departure to arrival, without a carrier portal for the ocean leg or a phone call for the road leg.

Flag a late ETA before the receiving site does

On delivery morning the predictive ETA slips past the plant's receiving window. A digital worker compares the ETA with the promised slot, opens an exception on the shipment in Tracking and drafts an update to the receiving site. The transport planner works from the exception and decides whether to rebook the dock or hold the truck. The plant hears about the delay before the truck is due.

Close the shipment on the POD milestone

When the carrier confirms delivery, Shippeo sends the POD milestone to Cargofy over webhook. Cargofy matches the event to the shipment and sets it to delivered, with the delivery timestamp on the record. Customer service sees the shipment closed in Tracking. Billing waits for the same status: the shipment is ready to invoice, and the delivery time is on it for the invoice check.

Test the mapping in the sandbox before go-live

The Shippeo account team issues credentials for Cargofy under your contract. Your IT admin enters them in Cargofy settings and confirms which carrier connectors are in scope. Cargofy maps your transport orders and milestone events to its shipment model against the Shippeo sandbox and runs a test shipment. The IT admin and the logistics manager check its milestones and ETA in Tracking before Cargofy switches to production.

How it fits your stack

Your TMS or ERP stays the system of record for orders. Cargofy writes transport orders and shipments to Shippeo for tracking. It reads milestone events, predictive ETAs, delivery statuses and carrier positions back over webhook, with no polling. Setup is per installation: the Shippeo account team provisions OAuth credentials (there are no self-serve tokens), and order and event mapping is agreed at scoping. Carriers outside Shippeo's network are not covered. Tender, rate and booking data are out of scope.

Who it is for

European shippers with multimodal freight and a Shippeo contract. Logistics managers own the rollout, customer service and transport planners work in Tracking daily, and the IT admin holds the credentials. Shippers without Shippeo need the contract first.