Tracking
You shouldn't have to watch every load to stay ahead of every load.
Chain automates track and trace from pickup through delivery, following up with carriers, keeping statuses current, and surfacing the exceptions that need attention.
What changes
Track and trace that does more than track.
Knowing where the load is is only part of the job. Chain handles the rest.
Know what's happening
Track shipments across ELD, the driver app, geofences and tracking links, whatever the carrier already runs.
Automate what happens next
Follow up with carriers, capture arrivals and departures, keep the TMS updated, and handle the documents.
Focus people on the exceptions
Chain watches every load so your team can spend its attention on the few that actually need it.
Tracking sources
Whatever tracking the carrier already has.
The fight over which app a carrier should download is one you don't need to win.
- The Chain driver app. A phone number and three permission prompts.
- No app at all. Autopilot works the load over text and email either way.
- ELD and telematics. Samsara, Motive, Geotab, Verizon Connect, and the owner-operator ELDs that show up on one truck in your network.
- A link in the chat. The driver pastes a share link and Autopilot attaches it to the load.
- EDI 214, SFTP or a carrier API for carriers with a preference.
- Upstream to your shippers through project44 and FourKites.
TMS write-back
Times that write themselves into your TMS.
Geofences fire on arrival and departure. Draw them as a radius or a polygon over just the dock, and exclude the layover lot next door so nothing fires on a truck that's only sleeping there.
- Arrival and departure at every stop
- Check-in and check-out times, from the geofence or the conversation
- Stop ETAs, refreshed as they change
- Load status as it progresses
- Call-ins in your format, including X6 codes
- Truck, trailer and seal numbers, and reefer temps
- POD, BOL and lumper receipts, filed to the right slot
One more rule that saves a lot of cleanup: Chain won't let a driver mark himself arrived from outside the geofence.
Documents
Reads the paperwork, not just receives it.
The POD gets requested the moment the truck is unloading, read, classified and filed to your TMS, so loads reach ready-to-bill without anyone downloading anything.
- Wrong paperwork, caught. A POD from another load gets sent back with a request for the right one.
- Counts that don't match. When the pallets on the paperwork don't match the rate con, the rep gets it with the BOL attached, before it's a claim.
- Photos it actually reads. Seal numbers, reefer gauges, pallet counts, the MC on the door, and a flatbed that was strapped but never tarped.
One honest limit: it can't tell a pickup signature from a delivery signature unless the form labels them. We'll show you that on the demo too.
Fraud signals
Catches what a dot on a map can't.
Because tracking runs through Chain's own app, it sees the device, not just the pings. When a carrier trips a fraud signal on one load, every active load with that carrier gets flagged too.
- Impossible movement between pings
- An emulator running in the background
- A rooted phone or a VPN on the tracking device
- A battery pinned at 100% with no charger, which is what a desktop pretending to be a phone looks like
- Tracking sources that disagree: app, ELD and TMS telling different stories
Proof
Every shipment tracked. Nobody chasing it.
"With other providers we were limited to how many shipments we could track. Now every shipment is being tracked."
Gerald MorsovilloBusiness Analytics Manager, ILG Logistics
"We didn't know how inefficient our previous tracking provider was until we started using Chain."
David AbellCEO, AM Transport Services