Shipment tracking is the process of recording and reporting the location and status of a parcel from the moment a shipping label is created until the package is delivered or returned. In orders and fulfillment within e-commerce, it connects the warehouse, the carrier and the customer through a shared reference, the tracking number, and a sequence of scan events that describe each step of the journey.
For the merchant, tracking is both an operational control and a customer service tool. It reveals delays and lost parcels early, and it answers the most common post-purchase question, where is my order, before the customer has to ask.
How shipment tracking works
Tracking starts when the merchant or warehouse creates a shipping label through a carrier system. The carrier assigns a unique tracking number, encoded in a barcode on the label, and links it to the shipment data: sender, recipient, weight, service level and promised delivery window.
Every time the parcel passes a checkpoint, a handheld scanner or sorting machine records a scan event with a timestamp, location and status code. These events travel to the carrier’s tracking system, from which they reach the merchant through carrier APIs, webhooks, EDI messages or tracking aggregators that normalize many carriers into one format.
| Status | What it means | Common pitfall |
|---|---|---|
| Label created | Shipment data exists, parcel not yet scanned | Customers read it as already shipped |
| Picked up or accepted | Carrier has physically received the parcel | First scan may happen hours later at the depot |
| In transit | Parcel moves between hubs and sorting centers | Long gaps between scans look like a loss |
| Out for delivery | Parcel is on the final delivery vehicle | Delivery may still slip to the next day |
| Delivered | Carrier recorded handover or drop-off | Package left at a door may still go missing |
| Exception | Delay, damage, wrong address or customs hold | Needs action, not just a notification |
Carriers use their own status vocabularies, and the same word can mean different things across companies. A tracking platform therefore maps carrier codes to a small, consistent set of statuses before showing them to customers or triggering automated messages.
Data sources and update methods
The way tracking data reaches the store determines how fresh and reliable the status is. Large merchants usually combine several methods, using push notifications where available and polling as a fallback.
| Method | How it works | Freshness | Main limitation |
|---|---|---|---|
| Carrier API polling | Store queries status for each tracking number | Depends on polling interval | Rate limits with many parcels |
| Webhooks | Carrier pushes events when they occur | Near real time | Not offered by every carrier |
| EDI messages | Batch status files between business systems | Minutes to hours | Complex setup, mainly for freight and large shippers |
| Tracking aggregator | One service collects data from many carriers | Near real time to hourly | Additional cost and dependency |
| Carrier website link | Customer checks the carrier page directly | Real time on the carrier side | No data or branding for the merchant |
Shipment tracking compared with related fulfillment concepts
Tracking is one layer of a broader post-purchase process. Order status and shipment status are not the same thing: one order can split into several parcels, and each parcel has its own tracking number and history.
| Concept | Scope | Relationship to tracking |
|---|---|---|
| Order management | Whole order from payment to completion | Consumes tracking events to update order status |
| Fulfillment | Picking, packing and handing over to the carrier | Ends where carrier tracking begins |
| Returns | Parcel traveling back from customer to merchant | Uses its own return tracking number |
| Proof of delivery | Evidence of handover such as signature or photo | Final, legally relevant tracking record |
| Fleet telematics | Live GPS position of delivery vehicles | Powers precise delivery time windows |
Designing a good tracking experience
A strong tracking experience reduces support contacts and builds trust. Customer service teams commonly report that delivery status questions form a large share of all post-purchase inquiries, so even modest improvements free considerable capacity.
- Send proactive notifications at key moments: shipped, out for delivery, delivered and any exception.
- Host a branded tracking page on the store domain, with order details and related help content.
- Show an estimated delivery date and update it when the carrier reports delays.
- Explain the label created status clearly so customers do not assume the parcel is moving.
- Handle multi-parcel orders by showing every package and its status on one page.
Notifications should be specific and actionable. A message that a parcel is held at customs, followed by what the customer must do, prevents frustration far better than a generic delay warning.
Common problems and how to handle them
Most tracking problems arise from gaps between physical events and recorded events. The table below lists typical symptoms with their causes and practical responses.
| Symptom | Likely cause | Recommended response |
|---|---|---|
| No scans for several days after label creation | Parcel not handed over or first scan missed | Check the warehouse handover manifest |
| Delivered status but customer has nothing | Wrong address, neighbor delivery or theft | Request proof of delivery and open a carrier claim |
| Status stuck in transit | Missed hub scans or misrouted parcel | Open a trace request after the carrier threshold |
| Wrong event times | Time zones not converted | Store events in UTC and display local time |
| Notifications sent twice | Duplicate webhook deliveries | Deduplicate events by ID and timestamp |
Put simply
Shipment tracking works like a trail of footprints for a parcel. Every time the package is scanned at a depot, on a truck or at the door, a new footprint appears in the record.
The tracking number is the key to that record. With it, the shop and the customer can see where the parcel was last seen. Good tracking turns waiting into knowing, which is why customers value it so much.
In practice
A mid-sized online cosmetics store ships about 1,200 parcels a day with three carriers. Its support team was receiving many emails asking where orders were, and agents copied tracking numbers into carrier websites by hand.
The store connected all three carriers to one tracking service that normalizes statuses and receives webhook events. It added a branded tracking page and automated emails for shipped, out for delivery and exception events. Parcels without a scan for 48 hours after label creation now create an internal alert for the warehouse.
Within two months, delivery status emails fell substantially, and the warehouse found that one evening pickup was regularly missed by a carrier. Fixing that handover shortened average delivery time by about a day for affected orders.