Skip to content

See every load. Know when it really arrives.

Shipment Insight brings ELD, telematics, carrier APIs, EDI and the driver app into one live timeline per shipment, predicts the arrival and shows you what needs attention before your customer asks.

Montréal, QCToronto, ON
Simulated tripTrip time 9:33 AM
Montréal, QC to Toronto, ONOn the road
  1. Truck
Predicted arrival
2:22 PM
8 min early
Appointment 2:30 PM
Updated just now422 km to go90 km/h
A truck trailer on the highway at dusk

Every mile, as it happens

Positions, milestones and new arrival times stream in from every carrier. The moment something changes, you see it.

Live activitySimulated activity
  1. Departed pickup3s ago
    Newark, NJ → Boston, MAELD and telematics
  2. Arrival time updated9s ago
    Halifax, NS → Moncton, NBELD and telematics
  3. Departed pickup17s ago
    Laredo, TX → Monterrey, NLCarrier APIs
  4. Departed pickup26s ago
    Vancouver, BC → Calgary, ABELD and telematics
  5. Arrived at delivery41s ago
    Halifax, NS → Moncton, NBEDI 214

Every signal, one timeline

Carriers report in many ways. You get one answer. Each position and status is matched to the right load, checked against the plan and turned into milestones you can trust.

Where updates come from

  • ELD and telematics
  • Carrier APIs
  • EDI 214
  • Driver app
  • Push API for carriers

Milestones for one load

  1. 8:05 AMPicked upInferred from tracking: the truck left the pickup heading to the delivery
  2. 8:12 AMDeparted pickupELD
  3. 2:18 PMArrived at deliveryDriver app, inside the delivery geofence
  4. 3:02 PMDeliveredConfirmed when the truck left the delivery geofence

Run freight without guessing

  • Predicted arrival and risk

    An arrival time for every active shipment, with how confident it is and why it changed.

  • One inbox for problems

    Late, stopped, off route or silent: the shipments that need you come first, most severe on top.

  • Breadcrumbs that make sense

    Hours spent waiting at a dock collapse into one stop, so the trail shows the trip, not the noise.

  • Yard and dock

    Appointments, arrivals and wait times at your facilities, next to the shipments they belong to.

  • Your rules, per customer

    When a load counts as picked up or delivered is a setting, not a code change. Set it for a customer, a carrier or a single shipment.

  • Every mode on one load

    Truckload, LTL, parcel, ocean, air and rail, including loads that split up or come together along the way.

Any mode. One shipment.

Truckload, LTL, parcel, ocean, air, rail, intermodal, drayage and barge. A load that changes modes along the way stays one shipment, with one timeline.

A container ship leaving port, seen from above
Ocean
A cargo plane at the gate being loaded with freight containers
Air
A freight train under a stormy sky
Rail
A semi truck parked at dusk
Truckload and LTL
A container train passing through a city
Intermodal
A river barge passing under a bridge
Barge and inland water
A smiling courier beside a truck full of parcels
Parcel and last mile
A distribution center with trucks at the docks, seen from above
Yard and dock

Drayage, expedited and loads that split or merge between modes are tracked the same way.

One load, everyone on it

Shippers, brokers and carriers each see what they need, and nothing that belongs to someone else.

  • Shelves of boxes in a fulfillment warehouse

    Shippers

    Know when product will land, and tell your customers before they ask.

  • A distribution center with trucks at the docks, seen from above

    3PLs and brokers

    Run every carrier from one screen, with the rules each customer expects.

  • A driver with a phone mounted on the dashboard

    Carriers

    Connect your ELD once and stop answering check calls.

If two companies track the same truck, neither one ever learns about the other.

Plug in your systems

Carriers send positions and statuses from whatever system they have. Your systems get arrival updates pushed to them, signed and retried until they land.

  • Reference loads by your own numbers: load, PRO, BOL or container
  • Retry safely with idempotency keys, no duplicates
  • Every webhook signed with HMAC-SHA256
Send a position
curl "$SI_API_URL/v1/push/locations" \
  -H "Authorization: Bearer $SI_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"records":[{"ref":{"loadNumber":"LD-880142"},
       "time":"2026-11-07T14:02:11Z",
       "lat":45.5017,"lon":-73.5673,"speedKph":87}]}'
Get the new arrival time
POST /webhooks/shipmentinsight
SI-Signature: t=1762530130,v1=5257a869e7ec…

{
  "id": "evt_01HZX5B7K3",
  "type": "intelligence.eta.updated",
  "created_at": "2026-11-07T15:42:10Z",
  "data": {
    "shipment_id": "shp_0123456789",
    "stop_id": "stp_02",
    "eta": "2026-11-07T18:40:00Z",
    "previous_eta": "2026-11-07T18:05:00Z"
  }
}

The API is in preview. The full design is in the docs, so your team can plan the integration now.

Security from the first line of code

  • Passkeys and two‑step sign‑in
  • Each company's data kept apart in the database itself
  • Every sign-in and change recorded
  • Short sessions you can end from anywhere
A truck on a mountain road under a stormy sky

See your freight clearly.

Tell us about your freight and we'll get in touch to set up your workspace.

Already have an account? Sign in

Request early access

It takes less than a minute.

You are
Loads per month

We only use this to contact you about Shipment Insight.