Tracking Number and Tracking

The tracking number is the central identifier of every parcel shipment in e-commerce fulfillment. It connects the warehouse, carrier, shop system, and end customer in a seamless chain. Without a correctly generated, transmitted, and communicated tracking number, tracking remains blind – and with it the ability to meet delivery promises, reduce support workload, and ensure customer satisfaction.

In this glossary entry, you will learn how tracking numbers are created, which tracking events are relevant, how systems work together, and which errors occur most frequently in day-to-day operations.

What is a tracking number?

A tracking number – also called a tracking ID, parcel number, or waybill number – is a unique identifier assigned to a shipment by a carrier. It enables tracking of the parcel from handover at the warehouse to delivery to the recipient.

Typical characteristics:

Uniqueness: Each shipment receives exactly one number; duplicate assignments lead to confusion.
Carrier-specific format: DHL, DPD, GLS, and UPS use different lengths and character sets.
Machine readability: The number appears on the shipping label and is scanned via barcode.
Cross-system reference: WMS, ERP, shop, and carrier API all reference the same ID.

The tracking number must not be confused with the order number or SKU. The order number identifies the customer order in the shop; the tracking number identifies the physical parcel in transit.

Tracking: Shipment tracking in the fulfillment context

Tracking refers to the ongoing capture and communication of status changes for a shipment. Every scan or system entry at the carrier generates a tracking event – for example, "Accepted at parcel center", "Out for delivery", or "Delivered".

For online retailers, tracking reduces WISMO inquiries, supports claims handling, and provides KPIs such as delivery rate and transit time.

Process flow: From tracking number to customer tracking

1

Label creation in WMS

2

Carrier assigns tracking number

3

Parcel scan at handover

4

Events in carrier system

5

API sync to shop system

6

Customer sees status in account

Difference: Tracking number, tracking link, and tracking URL

Term

Meaning

Example

Tracking number

Alphanumeric ID of the shipment

00340434161012345678

Tracking link

Clickable URL to carrier portal

dhl.de parcel tracking

Tracking URL with parameter

Direct link with embedded number

Carrier URL + query parameter

Element

Responsible party

Timing

Visible to customer

Tracking number

Carrier / shipping software

At label creation

Yes, after shipment

First tracking event

Carrier (first scan)

After parcel handover

Often delayed

Shipping confirmation email

Shop / OMS

Immediately after label print

Yes

Proof of delivery

Carrier

After successful delivery

Partially

How is a tracking number created in the fulfillment process?

The tracking number is typically assigned automatically as soon as a shipping label is generated in the warehouse. The typical flow in the pick-pack-ship process looks like this:

Order release: The WMS receives a shipment-ready order from the shop or ERP.
Picking and packing: Items are picked, checked, and packed.
Label request: The shipping software sends shipment data (weight, dimensions, address, product) to the carrier API.
Number assignment: The carrier responds with tracking number, label PDF, and optional tracking URL.
Booking and handover: The parcel is marked as "shipped" in the system; the number flows back to the shop and customer communication.
First scan event: When the parcel enters the carrier network, the first visible tracking status appears.

Important: The tracking number must be stored in the WMS before the shipping confirmation is sent to the customer. Otherwise, the customer receives an email without tracking capability – one of the most common triggers for support tickets.

Important tracking events and their meaning

Carriers differ in the granularity of their status updates. Nevertheless, most events can be grouped into overarching categories:

Standard events in domestic shipping

Electronic shipment data transmitted: Label created, parcel not yet with carrier.
Acceptance / drop-off: Parcel in carrier network; tracking becomes visible to customers.
Sorting at hub: Transit between hub and delivery depot.
Out for delivery: Parcel on delivery vehicle en route.
Delivered: Successful handover to recipient or neighbor.
Delivery attempt failed: Recipient not available, pickup notice issued.
Return to sender: After multiple failed attempts or undeliverable address.

Typical domestic tracking flow

1

Label created

2

Accepted at hub

3

Transit

4

Arrival at delivery depot

5

Out for delivery

6

Delivered

The phase between label creation and the first scan is often confusing for customers – proactive communication pays off here.

International shipments

For cross-border shipping, events such as customs declaration and customs clearance are added. The tracking number may change or be supplemented by an international reference – a common stumbling block in customer communication.

Event category

Typical customer reaction

Recommended action

No scan after 24 h

Anxiety, support inquiry

Check cut-off times and handover process

Long transit phase

Patience, occasional complaint

Proactive email for express shipping

Delivery attempt failed

High urgency

Immediate notification with pickup option

Return shipment

Frustration, refund request

Trigger automated return processes

System integration: WMS, carrier API, and shop

A tracking number only delivers its full value through seamless system integration. Three layers must work in sync:

WMS and shipping software

The warehouse management system or dedicated shipping software (multi-carrier platform) communicates via API with DHL, DPD, GLS, and other providers. The returned tracking number is assigned to the order in the WMS and transmitted to the shop via webhook or batch export.

Shop and order management

In the shop system, the number appears in the customer account, in the shipping confirmation email, and optionally in order history. Modern shops support automatic status updates via carrier webhook – the customer sees "In transit" or "Delivered" without visiting the carrier website.

Tracking aggregators

With multi-carrier strategies, many retailers use tracking platforms that normalize events from different carriers. This unifies the display and enables centralized analytics.

Tracking number data flow

1

WMS

2

Carrier API

3

WMS (storage)

4

Shop / OMS

5

Customer

Return channel: Carrier events → tracking aggregator → shop notification

Best practices for tracking number and tracking

Professional tracking does not start with the customer, but in warehouse operations. The following principles have proven effective in practice:

Communication

Send shipping confirmation within minutes of label printing.
Include tracking number, carrier name, and direct tracking link.
Communicate realistic delivery windows – not just the optimistic carrier promise.
Proactively inform about delays before the customer asks.

This aligns with customer expectations for delivery times and transparency in modern e-commerce.

Technical reliability

Escalate API errors during label creation immediately; no "silent" failed attempts.
Validate tracking numbers before shipment (format, length, check digit).
Avoid duplicate label prints – they create two numbers for one parcel.
Regularly reconcile tracking events against internal shipment lists.

Last mile and delivery quality

The last mile is the phase with the most customer touchpoints. Tracking events in this phase – "Out for delivery", "Forwarded to parcel locker", "Delivered" – shape the customer experience more than any marketing message.

WISMO reduction: Shops with complete tracking integration record up to 40% fewer "Where is my parcel?" inquiries.

Common errors and how to avoid them

Even experienced fulfillment teams struggle with recurring problems around tracking numbers:

Shipping confirmation without number: Label API returns error, email is sent anyway.
Wrong number in shop: Copy-paste error or mix-up during batch upload.
Delayed first scan event: Parcel sits in warehouse, handover to carrier only happens the next day.
Multiple numbers per order: Partial shipment without clear assignment confuses customers.
Outdated tracking link: Carrier changes URL structure, deep links no longer work.

Warning: A tracking number alone does not prove delivery. For claims and evidence, you need the delivery status "Delivered" with timestamp – or separate proof of delivery.

Checklist: Setting up tracking number and tracking correctly

Shipping software connected via API to all carriers in use
Automatic tracking number transfer to WMS after label print
Return channel WMS → shop configured for shipping confirmation
Email template includes number, carrier, and tracking link
Customer account shows live status or link to carrier
Process for partial shipment: one separate number per parcel
Escalation rule defined for missing scan after 24 hours
Monthly reconciliation: shipped orders vs. tracking events
Packing team training: no shipment without successful label print
Data privacy: tracking number only to authorized recipients

Tip: Use the full carrier name in the shipping confirmation ("Your parcel is shipped with DHL") – this increases trust and reduces clicks on phishing links.

Tracking number in the overall process: From order to delivery

The tracking number is the final digital stamp in the chain from order receipt to delivery. Only when picking, packing, and label creation run without errors can tracking fulfill its purpose.

For fulfillment service providers, correct number assignment is part of the contractual SLA. Missing or delayed tracking data can lead to marketplace penalties – especially on Amazon, eBay, and Otto, where proof of shipment and scan events are monitored.

Tracking maturity level comparison

Basic

Number only via email

Standard

Shop status + email

Premium

Proactive push, branded tracking page

Conclusion

The tracking number is far more than a string of characters on a label. It is the link between physical shipping and the digital customer experience. Those who reliably generate tracking numbers, distribute them across systems, and actively communicate tracking events reduce support costs, build trust, and meet the expectations of modern online buyers.

Investments in API integration and automated notifications pay off especially during periods of high order volume.

Frequently Asked Questions about Tracking Numbers and Shipment Tracking

Question

Answer

What is a tracking number and how does it differ from an order number or SKU?

A tracking number—also called a tracking ID, parcel number, or waybill number—is a unique identifier that a carrier assigns to a physical shipment. It enables tracking from warehouse handover through to delivery. The order number identifies the customer order in the shop, and the SKU identifies a product; neither replaces the tracking number. Typical traits include uniqueness per shipment, carrier-specific formats (for example DHL, DPD, GLS, or UPS), machine-readable barcodes on the label, and use as a shared reference across WMS, ERP, shop, and carrier API.

How is a tracking number created in the fulfillment pick-pack-ship process?

The number is usually assigned automatically when the shipping label is generated. After order release into the WMS, items are picked and packed; shipping software then sends weight, dimensions, address, and product data to the carrier API. The carrier returns the tracking number, label PDF, and often a tracking URL. The parcel is marked as shipped, the number flows back to shop and customer communication, and the first visible customer status appears when the parcel is scanned into the carrier network. The tracking number must be stored in the WMS before the shipping confirmation is sent—otherwise customers get an email without tracking capability.

What is the difference between a tracking number, a tracking link, and a tracking URL?

The tracking number is the alphanumeric ID of the shipment itself. A tracking link is a clickable URL that opens the carrier portal where status can be looked up. A tracking URL with parameters embeds the number in the carrier URL so the recipient lands directly on that shipment’s status. In practice, shipping confirmations should include the number, the carrier name, and a direct tracking link so customers can follow the parcel without copying the ID manually.

Which tracking events matter most in domestic shipping, and why can the first scan be delayed?

Common domestic events include electronic shipment data transmitted (label created, parcel not yet with the carrier), acceptance or drop-off into the network, sorting at the hub, out for delivery, delivered, failed delivery attempt with pickup notice, and return to sender after repeated failures or an undeliverable address. The phase between label creation and the first scan often confuses customers because the parcel may still sit in the warehouse until handover the next day. Proactive communication and checks of cut-off times and handover processes help when there is no scan after about 24 hours.

How do WMS, carrier API, and shop systems work together for tracking?

Value comes from seamless integration across three layers. Shipping software or a multi-carrier platform talks via API to carriers; the returned number is assigned to the order in the WMS and passed to the shop via webhook or batch export. In the shop or OMS, the number appears in the customer account, shipping confirmation email, and optionally order history; carrier webhooks can update status such as in transit or delivered without a visit to the carrier site. With multi-carrier setups, tracking aggregators normalize events, unify display, and support centralized analytics. The return channel runs from carrier events through an aggregator into shop notifications.

What common tracking-number errors cause support tickets, and how can teams avoid them?

Frequent issues include shipping confirmation without a number when the label API fails but the email is sent anyway, wrong numbers from copy-paste or batch-upload mix-ups, delayed first scans because parcels remain in the warehouse overnight, multiple numbers on one order from unclear partial shipments, and outdated deep links after carriers change URL structures. Prevention includes escalating label API errors immediately, validating format and check digits before shipment, avoiding duplicate label prints, assigning one number per parcel on partial shipments, and reconciling tracking events against internal shipment lists regularly.

Does a tracking number alone prove that a parcel was delivered?

No. A tracking number alone does not prove delivery. For claims and evidence you need the delivery status Delivered with a timestamp, or a separate proof of delivery from the carrier. Last-mile events such as out for delivery, forwarding to a parcel locker, and delivered shape the customer experience most strongly. Complete tracking integration also reduces WISMO inquiries—shops with full integration can see up to about 40 percent fewer where-is-my-parcel contacts—while missing or delayed tracking data can trigger marketplace penalties where proof of shipment and scan events are monitored.