FourKites

FourKites is the enterprise supply chain visibility platform, with a REST API for live load tracking, ETA and delivery events. With Cargofy connected, tracking starts when a load is covered, predicted delays reach the dispatcher as exceptions, and facility and yard data match what is on the road. The transportation manager usually switches it on; IT owns the credentials and the location mapping.

What teams use it for

Start tracking when the carrier is assigned

Without the connection, someone enters the truck, driver and phone into FourKites after the load is covered, sometimes hours later. With it, Cargofy sends the tracking information assignment to FourKites when the load gets a carrier in Load Hub. FourKites begins tracking, and the first position appears in Tracking before the truck reaches the shipper.

See the delay the night before

The evening before delivery, a truck is still hours out from its morning appointment. FourKites predicts the delay from the truck's position and the appointment and sends the delay event by webhook. The digital worker opens an exception on the shipment in Tracking and assigns it to the dispatcher. With the predicted arrival next to the appointment, the dispatcher rebooks the dock slot and tells the receiver before the shift starts. Arrival and delivery events from FourKites close the timeline once the truck is unloaded.

One lifecycle for every carrier

A customer calls asking where their load is, and the customer service rep opens it in Tracking. FourKites returns each carrier's status events along the shipment lifecycle, and the digital worker normalizes them into one set of milestones: pickup, in transit, arrival, delivery. Every carrier reads the same way, so the rep answers on the call without decoding carrier status codes.

Keep pickup and delivery locations in step

Facilities change: a new DC opens, a customer moves receiving to another gate. When the location lists in FourKites and the TMS drift apart, geofences fire at the wrong address. Cargofy creates and maps pickup, delivery and facility locations through the TMS Locations API, so FourKites tracks against the location on the load. The IT admin sets the mapping once, and the digital worker keeps it applied.

Run the yard from the same timeline

A delay exception opens in Tracking on an inbound load. In Facilities, where Cargofy reads appointments, trailer moves and dock assignments from Dynamic Yard, the yard coordinator sees the truck's new ETA beside its assigned dock. The coordinator moves the appointment in Dynamic Yard, and Cargofy updates the load's record in Facilities with the new slot. Yard position and road position sit on one record. This requires a FourKites Dynamic Yard subscription.

How it fits your stack

Your TMS stays the system of record for loads; FourKites stays the record for carrier connectivity. Cargofy reads positions, ETA, predicted delays, milestone and status events and yard appointments, and writes tracking assignments, shipment and load records and locations. Setup is per installation: your FourKites admin issues API credentials and Bill-to IDs, and Cargofy maps your load identifiers, locations and carrier data. Cargofy does not enroll carriers in the FourKites network; that stays on the FourKites side.

Who it is for

Shippers with a FourKites subscription and carriers enrolled in the network. Dispatchers act on delay exceptions, customer service watches Tracking, yard coordinators use Facilities where Dynamic Yard is on, and the IT admin owns the credentials and the location mapping.