How freight tracking and visibility works for forwarders

Start with the difference between two things that share a word.

Consumer parcel tracking answers one question for one person. You type a number, you read a status, you close the tab. It is a lookup. The person asking is the person waiting for the goods, and one screen finishes the job.

Forwarder visibility is an operation. You are holding shipments for many customers, on many carriers, in several modes, at the same time. Nobody types a number. Status arrives from a dozen directions, in a dozen shapes, at times you do not control. Your team has to turn all of it into three things. An answer when a customer asks. A warning when something has gone wrong. A message that goes out before the customer notices.

That is why “container tracking software” means something different to a forwarder than to an importer. The importer wants one container found. You want every container watched, and you want to know which one needs a person today.

From more places than any one screen shows.

Ocean, air and road each publish status differently, and the parties publishing it do not work for you.

• The Digital Container Shipping Association, a non-profit supported by the ten largest global carriers, puts it bluntly. The ways container data is exchanged today are “antiquated, manual, unaligned and unpredictable”, and “data is often exchanged inconsistently, with delays or not at all”.
• DCSA’s Track and Trace standard gives the industry one vocabulary for the events along a container journey: load and discharge, gate in and gate out, transhipment, pick up and drop off.
• The ONE Record community’s good practice for shipment tracking opens on “the myriad of non-standardized tracking systems, each requiring unique integration and understanding”, which “not only complicates operations but also escalates costs and reduces efficiency”. It maps around thirty standard milestones, from booked through departed and arrived to delivered, published usually by the operating carrier.
• Cargo iQ, an IATA interest group, describes its members as jointly mapping the air freight process in a Master Operating Plan, and generating and sharing one route map containing process indicators and KPIs.

The pairing a forwarder cares about is already in the ONE Record milestones above. Every event carries a code, a time, a place and a flag saying whether that time is actual or planned, and the gap between the two is what is worth watching.

Two things follow. No single feed is complete, so a product that reads only carrier APIs still leaves your team opening portals and emailing agents. And the most valuable status on a bad day came from a person, which no standard covers.

Three jobs. They are different jobs, and most teams only staff the first one.

1. Answer “where is my cargo?”

The customer asks on a thread they already have open, often with no booking number and a subject line from three weeks ago. Somebody has to work out which shipment they mean, find the current status, decide what is safe to say, and write it in a sentence the customer can use. A small task, done many times a day. It is also the one that pulls a coordinator out of everything else.

2. Spot the exception

Most shipments need no attention at all. A few need it today. The skill is separating them. The box that did not load. The flight that went without the cargo. The container held at a terminal for a missing document. The truck that has not moved since yesterday. Each one is visible in the status if somebody looks. Nobody has time to look at all of them.

3. Tell the customer before they ask

This is the job that pays. A delay you announce is a service. A delay the customer discovers is a complaint. The difference is not whether the cargo was late. It is whether your message arrived first.

Notice what the three jobs have in common. None of them is “look at a map”. They are all writing: an answer, a warning, an update. Which is why a dashboard so often changes nothing. It shows your team where the cargo is. They mostly knew. What they did not have was the twenty minutes to tell everybody.

Because the plan behind it moves.

Sea-Intelligence, which publishes the Global Liner Performance report, put global container schedule reliability at 56.4% in July 2026. That was the lowest level of the year, down 6.1 percentage points on June and 8.8 points on July 2025. For the vessels that did arrive late, the average delay was 6.06 days.

Read those two numbers together. Close to half of container sailings did not arrive when scheduled, and the ones that missed missed by most of a week. That is an ocean measure and does not transfer to air or road, but the shape is familiar in every mode. An arrival date is a forecast, and forecasts move.

So an arrival date is not a fact you publish once. It changes several times per shipment, and every change is a message somebody owes a customer. If your process only sends an update at booking and at delivery, each change in between becomes a phone call you take instead of a message you sent.

It also means the honest answer is often “here is what the carrier is showing today, and here is when I will check again”. Customers accept that. What they do not accept is silence followed by a surprise.

Be precise about this boundary. It is where budgets are wasted.

What a visibility product genuinely changes:

• it collects status from several carriers into one place, so nobody opens six portals;
• it turns different vocabularies into one set of milestones you can compare;
• it keeps a history, so you can see when a status changed and what it changed from;
• it raises an alert when a milestone is late or has not arrived at all; and
• it gives pricing, operations and accounts the same view of the same shipment.

What it does not change on its own:

• it does not know which of your customers cares about which shipment;
• it does not write the reply, so the answer still costs a person their attention;
• it does not chase the agent whose email is the only source of a status;
• it does not decide what is safe to promise a customer who is already unhappy; and
• it does not make the cargo move.

That second list is why so many forwarders buy visibility and still have a coordinator answering the same question all afternoon. The status arrived. The work after it did not.

So the useful question is not “how many carriers do you read”. It is “what happens in the ten minutes after the status changes”. Ask a supplier to walk through that on a shipment that went wrong.

Ask every supplier the same questions. Score the answers on evidence, not on the demonstration.

Two rows there are worth more than the rest. “Does your team still have to open the mailbox?” and “What runs by itself?” separate a screen from an operation. A product can pass every coverage question and still hand your team the same afternoon.

One example, so the two questions are not abstract. FreighAI answers them like this. Answers “where is my cargo?” on the customer’s own thread, from carrier status, for approval. Chasing, tracking checks, quote expiry and follow-ups run on their own. Nobody has to remember. Whether that shape suits your operation is your decision. Both questions have a concrete answer, and a supplier who cannot give one is selling a screen.

Bring the week you actually had, not the one you would like to show.

• your last fifty shipments, with the carriers and modes as they were;
• one tracking thread where the customer had to ask three times;
• one shipment that went wrong, with the emails around it;
• one shipment whose only status all week came from an agent;
• the customers who expect an update without asking;
• the reference your job carries and the one the carrier carries, side by side; and
• the hours a week your team spends answering “where is my cargo?”.

The last item is the one most forwarders have never measured. Count it for one week before any demonstration. Without it you cannot tell whether anything improved, and every supplier sounds convincing.