Freight Tracking Software: 5 Checks Before Launch

Freight Tracking Software: What Forwarders Need Before Offering Customer Self-Service Updates

Picture this: Maya, a forwarder, has just poured her first coffee when a customer calls. “Your portal says our cargo arrives Thursday. Can I book the warehouse crew for Friday?”

Maya checks the shipment. Thursday is when the ship is expected at port. Nobody has confirmed when the container can be collected, let alone when the truck will reach the warehouse. There goes the coffee.

That’s a made-up story, but it’s a useful test. Before you launch freight tracking software for customers, check that every status says what happened, what’s still an estimate, and who can help when the answer is unclear.

That last part often depends on people at the other end of the shipment. One Globe Alliance helps independent forwarders find and communicate with overseas partners. Agree with those partners on who confirms pickup, customs release, and delivery, and you’ll know who to call when the portal can’t answer the next question.

What is freight tracking software?

Freight tracking software brings shipment updates from carriers, agents, and your own systems into one place. A customer portal or tracking link lets shippers check those updates themselves. A useful first version shows the shipment reference, last confirmed milestone, next expected milestone, and a way to contact the team.

Before your customers log in, run these five checks.

1. Decide what counts as a confirmed milestone

Start with the statuses that customers act on. For each one, pick the source your team trusts and decide exactly what triggers it.

Customer sees What backs it up
Vessel arrival estimated The latest carrier schedule for the named port
Container unloaded A discharge event from the carrier or terminal
Container available for pickup A terminal or destination agent confirmation that pickup can proceed
Delivered Confirmation from the delivery partner, such as proof of delivery

The Digital Container Shipping Association’s Track & Trace standard separates transport events from events involving the container. For air freight, IATA’s Cargo iQ is a starting point for common milestones. Use those distinctions underneath the portal, then write the labels in words your customer would use.

Try a split shipment in the demo. If one of two containers is unloaded, the portal should say “1 of 2 containers unloaded.” Otherwise, a customer might send a truck for both.

2. Show customers when an estimate was last checked

Give the event time and the last verified update separate labels. A carrier can send you a Tuesday departure event on Wednesday. Both dates matter, and neither tells you when delivery will happen.

There’s a reason to be careful with estimated arrival times. Sea-Intelligence’s Global Liner Performance report found that late vessel arrivals averaged 6.65 days behind schedule in September 2026. That’s a snapshot of vessel performance. Your customer still needs a separate answer about their warehouse delivery.

Set a point at which your team checks a missing milestone. A few quiet days at sea may be normal; a missed pickup confirmation might need attention the same afternoon. If an update is overdue, keep the last confirmed event visible and explain what you’re checking. For Maya’s shipment, that could read:

Last confirmed: Vessel departed Singapore on Tuesday at 18:00 SGT.
Port arrival estimate: Thursday. Last carrier update: Wednesday at 14:20 SGT. A fresh estimate is overdue.
Warehouse delivery: Not yet confirmed. Our destination agent is checking pickup availability. We’ll update you by Thursday at noon, destination time.

That tells the customer to hold off on booking the crew.

3. Give exceptions an owner before you turn on alerts

Decide who investigates an overdue milestone, who covers after hours, and who tells the customer what happens next. Give the tracking page a contact button that includes the shipment reference so the customer doesn’t have to start from scratch.

Then test the messy stuff: a duplicate event should send one alert, an older update shouldn’t move a shipment backward, and a legitimate correction should be logged and shown clearly. If a carrier and terminal disagree, send the conflict to the person who can verify it. Three texts about the same container? That’s a shipping notification with an echo.

4. Test permissions from a customer account

Log in as Customer A and try opening a shipment or proof of delivery from Customer B using a direct link. Repeat with the permissions you give to different branches. Keep buy rates and internal notes out of the customer view.

OWASP explains this access risk: the system needs to check whether the user can access each specific record. Hiding it from the dashboard is only a display choice.

5. Pilot one lane before you roll out everywhere

Choose a familiar lane and a few customers who will give you honest feedback. Run the portal alongside your usual updates and check three things:

  • Milestone coverage: How often do expected milestones show up with a reliable source?
  • Status requests: Do routine calls and emails per shipment go down?
  • Exception response: How long does it take to send a useful update when a milestone is missed?

If you’re shopping for freight tracking software, ask the vendor to run a recent, anonymized shipment from that lane through the demo. Pick one with a split delivery or a missed connection. A clean demo tells you how the portal looks. A messy shipment tells you whether your team can use it.

Go live on the pilot lane when customers can tell an estimate from a confirmation, every overdue update has an owner, and the access tests pass. Add more lanes as you confirm their coverage. If your gaps are in overseas handoffs, explore One Globe Alliance membership to connect with partners and agree on who sends each update.

Table of Contents