Skip to content
Tracking Intelligence

Every carrier speaks its own language. Your team should only have to learn one.

Delivered normalizes tracking across parcel, LTL and truckload onto one shared set of states, then tells you the when and why a shipment is in the current status.

Tens of millions
Tracking events processed
across parcel, LTL and truckload
1,000,000+
Shipments monitored
and every scan behind them
One
Event model
every carrier, every mode
The problem

Your customer finds out before you do. And the person who has to answer them is looking at the same carrier portal as everyone else.

Most teams are in one of two places. Either nobody has tooling at all, and customer service keeps four or five carrier portals open in browser tabs, or there is a visibility vendor in place that forwards the carrier's own status text without changing it.

Both fail the same way. The status arrives in whatever words the carrier chose, so nothing downstream can reliably key off it. And it arrives after the fact: somebody runs a report, notices a shipment missed a day, and starts making calls. By then the consignee has already called you.

The gap is not data. It is that raw carrier text cannot be compared, cannot be triggered on, and says nothing about whether a shipment is on pace.

Normalization

Five carriers, five sentences, one state.

Each carrier writes its own status text. Most visibility tools give you that text without a change. We map each carrier onto one shared set of states. Therefore, a rule that you write one time is correct for every carrier.

  • FedEx On FedEx vehicle for delivery
  • UPS Out For Delivery Today
  • USPS Out for Delivery, Expected by 8:00pm
  • DHL With delivery courier
  • Amazon Package out for delivery (SD-071)
Normalized state Out for delivery

Every carrier on the shipment gives the same state, in the same shape.

  • On scheduleyes
  • Dwell since last scan4h 12m
  • Against cohorton pace

The state is the same for every carrier. A trigger that you write one time stays correct when you add a new carrier.

Detection

Three things a carrier feed will never tell you.

A carrier reports the event. We also know the plan for that shipment. And we know the progress of the other shipments that left at the same time.

  • Dwell time

    A shipment that does not move is the first sign of a problem. No carrier publishes this measurement. We compare the time since the last scan with the normal time for that facility on that lane.

    What firesA shipment stays at a facility longer than its normal time.

  • Off schedule

    Linehaul operates to a timetable. A truck leaves at 22:00 and arrives at 06:00. If the scan for that leg does not occur, we identify the miss. We compare each leg with the plan, not with the promised date.

    What firesA leg takes longer than the plan, or an expected scan does not occur.

  • Wrong facility

    A scan at the wrong facility adds days to the route. On a carrier feed, it looks like normal progress. We compare the actual route with the planned route.

    What firesA scan occurs at a facility that the route plan does not include.

Worked example

The same shipment, against the plan it was supposed to run.

Each leg has a planned duration, because linehaul operates to a timetable. We compare the actual duration with the plan. A large list of scans becomes a short list of exceptions.

Actual
14h 45m 26h 45m 9h 26h
Planned
11h 48m 21h 24m 13h 12m 12h 48m
  1. 1 Origin hub Newark, NJ dwell 14h 45m Held long
  2. 2 National sort Atlanta, GA dwell 26h 45m Held long
  3. 3 Regional hub Chicago, IL dwell 6h
  4. 4 Regional hub Phoenix, AZ dwell 10h Not on plan
  5. 5 Destination Los Angeles, CA
Actual path Planned path
Cohort

On pace is a comparison, not a guess. A shipment nobody else can see is hard to judge. One moving alongside thousands of others is not.

A shipper watching their own freight has nothing to compare it against. We are watching the shipments that left the same origin, the same day, on the same service, so we can see yours falling behind while it is still moving.

That is the difference between a delay you learn about on Thursday and a delay you can act on Tuesday.

Your brand, not the carrier's

Make tracking part of your brand. Your logo, your colors, your URL, and the numbers your business runs on.

Track by your number order, PO, or a Delivered number, not just the carrier's

Your customer types the number they already have. They never need to know which carrier moved it, and you are not sending them to fedex.com to find out.

Public or private open by link, or behind an email and zip code

Tracking anyone can view or behind a gated login. Sign in and the tracking page shows the information you want them to see, and notifications the customer can subscribe to themselves.

Bring ninety days of history.

We run your last quarter through Tracking Intelligence and show you what you would have caught, and when you would have caught it.

Talk to us See the platform

No integration required to run the analysis. The findings are yours either way.