Shipment tracking is one of the most important features in modern logistics. Customers expect real-time visibility into their deliveries, and companies rely on status updates to manage operations efficiently.

But behind a simple tracking page lies a surprisingly complex technical infrastructure.

Integrating shipment tracking data from multiple carriers is often far more difficult than companies expect.

In this article, we explain how shipment tracking works, why integrations are challenging, and how companies can build reliable tracking systems.

What Is Shipment Tracking?

Shipment tracking allows companies and customers to follow the progress of a shipment from pickup to final delivery.

Tracking systems typically provide:

• shipment status
• event timestamps
• location updates
• delivery confirmation

Example tracking timeline:

EventDescriptionShipment createdLabel generatedPicked upCarrier collected parcelIn transitMoving through logistics networkOut for deliveryDriver delivering parcelDeliveredShipment delivered

Each event is generated by the carrier’s internal logistics systems.

How Tracking Data Is Generated

Tracking events originate in various systems inside a carrier's infrastructure.

Examples include:

• sorting centers
• scanning stations
• delivery vehicles
• warehouse systems

Each scan generates an event that is stored in the carrier's system.

Example event:

{
  "trackingNumber": "00340434161094000000",
  "event": "ARRIVED_AT_SORT_CENTER",
  "timestamp": "2026-03-12T08:42:00Z",
  "location": "Hamburg"
}

These events are then made available through:

• carrier APIs
• EDI messages
• webhook notifications

Why Tracking Integrations Are Difficult

Tracking sounds simple — but integrating it across carriers is surprisingly complex.

There are several reasons for this.

Problem 1: Different Event Terminology

Each carrier uses its own terminology for tracking events.

Example:

CarrierEventDHLShipment processed in facilityUPSDeparted from facilityDPDParcel sortedHermesPaket im Logistikzentrum

Although these events mean roughly the same thing, the wording differs significantly.

This makes it difficult for systems to interpret tracking data automatically.

Problem 2: Different Data Formats

Tracking information may be delivered in several formats.

Examples:

CarrierFormatDHLREST APIUPSREST APIDPDSOAP APIFreight forwardersEDIFACT IFTSTALegacy systemsCSV

Integration teams must therefore maintain multiple adapters.

Problem 3: Missing or Delayed Events

Tracking data is not always complete.

Events may be:

• delayed
• missing
• duplicated
• delivered out of order

For example, a shipment may jump directly from:

IN_TRANSIT → DELIVERED

without intermediate events.

Tracking systems must therefore handle incomplete data gracefully.

Problem 4: Polling vs Webhooks

Some carriers provide tracking data via API polling.

Example:

GET /tracking/{trackingNumber}

Others send push notifications via webhooks.

Example:

POST /webhook/tracking-event

Supporting both approaches adds additional complexity to integration systems.

Normalizing Tracking Data

To solve these issues, companies often introduce a tracking normalization layer.

Architecture example:

Carrier APIs / EDI
        ↓
Tracking Integration Layer
        ↓
Event Normalization
        ↓
Internal Tracking API
        ↓
Customer Portal / ERP

This system converts carrier-specific events into standardized tracking statuses.

Example normalized events:

Normalized StatusCREATEDPICKED_UPIN_TRANSITOUT_FOR_DELIVERYDELIVERED

This allows internal systems to process tracking data consistently.

Real-Time Tracking with Event Streams

Modern logistics systems increasingly rely on event-driven tracking architectures.

Instead of polling carrier APIs repeatedly, events are streamed into a central platform.

Example architecture:

Carrier Webhooks
       ↓
Event Queue
       ↓
Tracking Processor
       ↓
Tracking API

Benefits include:

• real-time updates
• reduced API calls
• better scalability

The Future of Shipment Visibility

Tracking systems are evolving rapidly as supply chains become more digital.

Future tracking platforms will combine:

• carrier APIs
• EDI transport messages
• IoT tracking devices
• event-driven data streams

Companies that invest in modern integration architectures will gain significantly better supply chain visibility.

Conclusion

Shipment tracking may appear simple from the outside, but integrating tracking data across multiple carriers requires sophisticated infrastructure.

Key challenges include:

• different event terminology
• inconsistent data formats
• missing or delayed events
• mixed communication methods

By introducing a tracking normalization layer, companies can create reliable shipment visibility across all logistics partners.

About Hemutis

Hemutis helps logistics companies integrate carrier systems, normalize tracking data, and build scalable digital infrastructure for modern supply chains.