Shipment Status and Tracking Events DHL

The shipment status at DHL describes the current processing state of a parcel shipment – from electronic pre-announcement through to delivery or return. Tracking events are the individual, timestamped events that occur with every scan or system entry in the DHL network. For online retailers, fulfillment teams and customer service, both terms are central: they determine whether customers can track their delivery, whether WISMO inquiries ("Where Is My Order?") arise, and whether claims can be resolved with reliable data.

This glossary entry explains the most important DHL statuses and events, shows the typical lifecycle of a shipment, and provides concrete recommendations for system integration, customer communication and error handling in fulfillment.

What is a DHL shipment status?

A shipment status is the summarized snapshot of a shipment. It is derived from the most recent tracking event and displayed in the DHL portal, the DHL app or via the business customer API. End customers see simplified wording such as "Out for delivery" or "Delivered"; in the background, DHL works with more detailed event codes and internal status values.

Key characteristics in the fulfillment context:

• Near real-time: Status changes with every scan in the logistics network – not when the label is printed in the warehouse.
• Carrier authority: The authoritative status comes from the carrier, not from the shop system.
• Multiple display levels: Customer portal, API raw data and business customer portal can differ in granularity.
• Dependency on the tracking number: Without a valid tracking number and tracking, the status remains invisible.

What are DHL tracking events?

A tracking event is an individual, logged process in the shipment history. Each event typically contains:

• Timestamp (date and time)
• Location or facility (parcel center, delivery depot, Packstation)
• Event code or status designation
• Optional: additional information (e.g. "Recipient not met")

Events are created through barcode scans at sorting facilities, by the delivery driver, at Packstations or through automatic system entries (e.g. electronic shipment pre-announcement). For retailers with API integration, the raw events are the basis for automatic customer notifications, SLA monitoring and claim evidence.

Lifecycle of a DHL shipment

The most important DHL shipment statuses at a glance

The following table summarizes the most common statuses as seen by customers and retailers in parcel tracking. The exact wording may vary slightly depending on the product (parcel, small parcel, merchandise mail) and channel.

Typical DHL standard delivery

With Saturday delivery, weekend delays may occur.

Common tracking events and their meaning

In addition to the summarized statuses, the event history provides more granular information. For technical integration via shipping label and carrier API, these events are crucial.

Status vs. event: the difference

1. Shipment status = current overall state (one line in the tracking view).
2. Tracking event = individual entry in the chronology (complete history).
3. API mapping = shop system translates carrier events into own order statuses (e.g. "shipped", "in transit", "delivered").

For clean system architecture, it is recommended to store events as raw data and generate derived shop statuses from them – not the other way around.

Tracking in the fulfillment workflow

Integration of DHL tracking begins with label creation and ends with proof of delivery. A seamless process looks like this:

Manual vs. automatic status updates

Manual processes are suitable for very small shippers:

• Enter tracking number via copy-paste in shop backend
• Customer receives tracking link in shipping email
• Support checks DHL portal for inquiries

Automated processes are mandatory from medium volumes onward:

• Carrier API or aggregator (e.g. via shipping software) polls events
• Webhooks trigger customer emails for "Out for delivery" and "Delivered"
• Exception events (failed delivery attempt) create tickets in customer service

Details on general event logic can be found under Understanding tracking events.

Customer communication: which statuses to communicate?

Not every tracking event should reach the customer. Too many notifications are annoying; too few create WISMO inquiries. These triggers have proven effective:

Recommended customer notifications:

• Shipping confirmation with tracking number and tracking link (after label print)
• "Your parcel is on its way" (after first physical scan)
• "Out for delivery today" ("Out for delivery" event)
• "Ready for pickup at Packstation/branch" (with pickup deadline)
• "Delivered" (optional, often redundant with successful doorstep delivery)

Do not report every intermediate stop:

• Every parcel center in transit
• Internal sorting scans with no customer benefit
• Electronic pre-announcement before physical handover

Special cases and critical statuses

Some DHL statuses require active action in fulfillment or customer service:

Delivery not possible

Typical causes:

• Recipient not met
• Insufficient address data
• Access to delivery location not possible
• Parcel does not fit in Packstation locker

DHL typically leaves a notification card and plans another delivery attempt or deposit at a branch. Retailers should proactively inform the customer and refer to resolving delivery problems.

Delays and network disruptions

During high shipment volumes (peak season, Black Friday) or regional disruptions, transit events may be spaced further apart. A missing update for 24 hours is not automatically a loss – but after 48 hours without a new scan, support should initiate an inquiry with DHL.

Return to sender

If delivery ultimately fails, the shipment goes back to the sender. The "Return" status in tracking means: goods are coming back to the warehouse, the customer received nothing, refund or reshipment must be clarified.

Checklist: setting up DHL tracking in fulfillment

• Shipping software connected to DHL business customer API
• Tracking number is automatically written to OMS/WMS
• Shipping confirmation contains tracking link with tracking number
• Event polling or webhooks configured for status changes
• Shop status mapping defined (shipped → in transit → delivered)
• Triggers set up for "Out for delivery" and "Ready for pickup"
• Escalation rule documented for missing scan after 48 hours
• Customer service has access to complete event history

Deriving KPIs from DHL tracking events

Tracking data is more than a customer service tool – it provides measurable fulfillment metrics:

Common errors with DHL shipment status

API integration: using events technically

For business customers, DHL provides tracking data via interfaces (e.g. as part of the DHL parcel API or through shipping software providers). Typical data flow:

1. Push (webhook): DHL or middleware sends event on status change to your URL.
2. Pull (polling): Your system queries new events at fixed intervals.
3. Batch export: Daily CSV/XML export for reporting – less real-time, but sufficient for controlling.

During integration, you should maintain event codes in a mapping table and log unknown codes instead of ignoring them. DHL occasionally extends status designations; a robust integration tolerates new values without system errors.

Frequently asked questions about DHL shipment status

Why does tracking show "no information" although the label was printed?
The electronic pre-announcement is not yet a physical scan. Only after handover to DHL do events appear – often after a few hours.

How long until "Out for delivery" appears?
For standard shipping, typically on the delivery day in the morning when the driver takes over the route.

What does "The shipment has been electronically announced" mean?
The label was created and DHL was informed digitally. The parcel is not yet moving in the network.

Can I set the status manually in the shop?
Technically yes, but the carrier status is authoritative. Manual overrides lead to inconsistencies in claims.

When is a shipment officially delivered?
When DHL records the "Delivered" event with timestamp – including Packstation pickup by the recipient.

Conclusion

Shipment status and tracking events are the backbone of transparent delivery communication in DHL shipping. Those who know the most important statuses, integrate events cleanly into the shop system and inform customers only about relevant changes reduce support effort and increase trust. The technical basis lies in the correct tracking number, stable API integration and clear escalation rules for exception statuses.

Related topics

• Tracking number and tracking
• Shipping label and carrier API
• Packstation, parcel shop and branch
• Proof of delivery and POD
• Understanding tracking events

Last updated: July 6, 2026