Skip to main content
Contact

By Sakshi Shah · 9 November 2026 · 11 min read

Shipment Visibility: Bringing Carrier, Warehouse and Order Data Into One View

How to build shipment visibility across couriers, transporters, warehouses and your order system — and use it to catch late deliveries before customers do.

Photo by Timelab on Unsplash

Introduction

For many businesses that ship physical goods, the most common customer question is also the hardest to answer quickly: "Where is my order?" The order is in the ERP. The warehouse system knows when it was packed. The courier's portal knows it left the hub. A regional transporter knows where the truck is, but only if someone phones the driver. Proof of delivery is a photo in a WhatsApp group. Each piece of the answer exists somewhere; nobody has all of them in one place.

The cost shows up in three ways. Customer service teams spend hours chasing updates. Late deliveries are discovered when the customer complains, not when there was still time to do something. And without a reliable record of what actually happened, it is impossible to tell which carriers and routes perform well. Shipment visibility means bringing that scattered information into one timeline per order, so you can see where everything is, spot problems early, and tell customers before they have to ask.

This guide covers where shipment data lives, how to join it together reliably, how to collect updates from carriers large and small, how to turn the data into exception alerts rather than another dashboard, and how to start without trying to connect everything at once.

Where Shipment Data Actually Lives

The first step is mapping every place a piece of the delivery story is recorded, and how each one can be reached.

SourceWhat it knowsHow it can usually be reached
Order system or ERPWhat was ordered, by whom, and the promised delivery dateAPI, database or export
Warehouse systemPicked, packed, dispatched; which carrier and tracking numberAPI, database or export; sometimes only a spreadsheet
National couriersScan events from pickup to delivery, failed attempts, returnsTracking APIs or webhooks; sometimes only a web portal
Courier aggregatorsNormalised tracking across many couriersOne API covering several carriers
Regional transportersTruck departure, location, arrival — often informallyPhone, WhatsApp, a driver app or a GPS device
Shipping documentsConsignment numbers, vehicle details, delivery proofDocument uploads; in India, e-way bill records carry vehicle details

Most businesses find a mix: larger couriers with decent tracking APIs, a few regional transporters with no system at all, and a warehouse that may or may not record the tracking number reliably. That mix is normal, and it shapes the design.

Joining It Into One Timeline per Order

The core of shipment visibility is a single shipment record that links the order to everything that happens to it. Two problems have to be solved for that to work.

Matching identifiers. The order has an order number. The warehouse may split it into several packages. Each package gets a tracking number, air waybill or lorry receipt number from whichever carrier takes it. The visibility system has to hold those links — one order, several shipments, each with its own carrier reference — and they must be captured at dispatch, ideally automatically from the warehouse system or a label printing step. If tracking numbers are typed in by hand, a meaningful share of shipments will never be found again.

Translating carrier events. Every carrier describes progress in its own vocabulary, often with dozens of event codes. To compare carriers and set rules, those events need translating into a small set of standard milestones that mean the same thing everywhere.

raw carrier eventsCarrier A: "Manifested"Carrier B: "Picked up from shipper"Carrier A: "Bagged at hub"Carrier C: "Arrived at dest. facility"Carrier B: "With delivery agent"Carrier C: "Consignee not available"Carrier A: "Delivered — POD captured"standard milestonesBookedPicked upIn transitOut for deliveryExceptionDeliveredkeep the raw event for reference; base rules and reports on the standard milestone
Each carrier's own wording is translated into a handful of milestones that mean the same thing everywhere, so rules and reports work across every carrier.

Keep the original carrier event alongside the standard milestone. The standard milestone drives alerts and reports; the original is what a customer service agent needs when explaining exactly what happened.

Collecting Updates From Every Kind of Carrier

Carriers with APIs or webhooks. The best case: the carrier pushes events to you as they happen, or you query its tracking API on a schedule. Webhooks are faster and cheaper; scheduled checks are simpler where webhooks are not offered. Respect rate limits, and query less often for shipments that are not expected to move soon.

Courier aggregators. If you use many couriers, an aggregator that normalises their tracking into one API can save a great deal of integration work. The trade-off is another dependency and per-shipment cost.

Regional transporters with no system. These are often the least visible and the most important for business-to-business freight. Practical options include a very simple mobile page or app where the driver or transporter taps "departed", "arrived" and uploads a delivery photo; structured WhatsApp updates captured by an automated process; GPS trackers on vehicles; or, in India, vehicle details from e-way bill records. Even two or three updates per trip transform visibility compared with none.

Portals with no API. As a last resort, a carefully monitored automated process can read a carrier's web portal. It works, but breaks whenever the portal changes, so it is worth pushing the carrier for proper access in parallel.

Whichever route each carrier uses, the integration work follows the same principles as any other — retries, duplicate detection, logging and monitoring — described in API & Middleware Development: Connecting Systems That Don't Talk to Each Other.

Exceptions, Not Another Dashboard

A map full of moving dots is satisfying to look at and changes very little. The value of shipment visibility comes from noticing the few shipments that need attention, early enough to act, and sending them to the person who can do something.

Useful exception rules include:

  • At risk of missing the promised date — the shipment has not reached the expected milestone given the typical transit time for that carrier and route.
  • Stuck — no new event for longer than normal for that stage, such as a day in transit with no scan.
  • Not picked up — dispatched in the warehouse system but no carrier pickup event by the end of the day.
  • Failed delivery attempt — customer unavailable, address problem, or refused delivery, which may need a call before the carrier returns it.
  • Return to origin started — often the most expensive outcome, worth catching as soon as the carrier signals it.
  • Delivered without proof — marked delivered but no proof of delivery captured.

Tell the customer first. A short, honest message — "your delivery is running a day late; here is the new estimate" — sent before the customer notices builds far more trust than a perfect explanation after they complain.

Typical transit times should be learned from your own history per carrier and route, not taken from the carrier's brochure. With a few months of data, the system can judge "late" against what actually happens on that route rather than a single fixed rule — the same idea behind AI for Operational Anomaly Detection: Finding Problems Before They Cost Money.

Sharing Visibility With Customers

Once you have one reliable timeline per order, sharing it is straightforward and removes a large share of "where is my order?" contact. Options range from proactive email or WhatsApp notifications at key milestones, to a tracking page per order, to a full customer portal where business customers see all their open orders, delivery documents and invoices. The portal approach is covered in Customer Portal Development: What Businesses Should Automate First. Whatever you choose, show customers the standard milestones in plain language, with an honest estimated delivery date.

Measuring Carriers and Starting Small

A reliable delivery history gives you something most businesses negotiate without: evidence. On-time delivery by carrier and route, average and worst-case transit times, failed delivery rates and return rates turn carrier reviews from anecdote into data — and help decide which carrier to use for which customer or region.

1

Start with most of the volume

Pick the two or three carriers that handle most of your shipments, plus your order and warehouse systems.

2

Fix identifier capture

Make sure every shipment's carrier and tracking number is captured automatically at dispatch.

3

Map events and add rules

Translate carrier events into standard milestones, then switch on two or three exception rules.

4

Add carriers and customers

Bring in remaining carriers, including informal transporters, then turn on customer notifications.

Packaged visibility platforms are worth evaluating, especially if you mainly use large national couriers they already support. A custom approach makes more sense when much of your freight moves with regional transporters, when visibility has to sit inside your own ERP and customer portal, or when your exception rules are specific to how you sell — the general trade-off is covered in Build vs Buy: Should Your Business Develop Its Own AI Automation System?

Conclusion

Shipment visibility is less about maps and more about joining data that already exists. Map every source, from the order system to the informal transporter. Capture carrier references automatically at dispatch, link them to the order, and translate each carrier's events into a small set of standard milestones. Collect updates from every carrier in whatever way it can support. Then use the result for exception alerts that reach the right person early, proactive messages to customers, and honest data on carrier performance.

Finding out about late deliveries from your customers?

We will map where your order, warehouse and carrier data lives and design the first set of exception alerts that matter. See our Data Pipeline Engineering work or start the conversation.

Frequently Asked Questions

What if some of our transporters have no tracking system at all?

Use the simplest method they will actually use: a basic mobile page for departure and arrival updates with a delivery photo, structured WhatsApp updates captured automatically, or GPS trackers on vehicles. A few reliable updates per trip are far better than none.

Should we use a courier aggregator?

If you ship with many national couriers, an aggregator can save significant integration work by providing one normalised tracking API. It adds a per-shipment cost and another dependency, so compare that against integrating your main carriers directly.

How accurate can estimated delivery dates be?

Estimates based on your own history for each carrier and route are much more reliable than carrier brochure times. Accuracy improves as more delivery history accumulates.

Can shipment visibility work inside our existing ERP?

Yes. The shipment record and alerts can live in a separate service while statuses and dates are written back to the ERP, so staff see delivery progress where they already work.

What should we measure once visibility is in place?

On-time delivery by carrier and route, transit times, failed delivery and return rates, and how often customers contact you about order status. These give you evidence for carrier reviews and show whether proactive notifications are working.

Further Reading