A tracking number is not trustworthy merely because the supplier API returned a non-empty string. It can be malformed, assigned to the wrong carrier, copied from another order, recycled, created but never used, or linked to a shipment whose destination clearly does not match the customer’s order. If your store forwards that number automatically, the customer becomes the first person to discover the data problem.
A better fulfillment system validates tracking at several levels before treating it as evidence that an order shipped.
Six common forms of bad tracking data
- Placeholder: values such as “TBD,” “000000” or a supplier order number copied into the tracking field.
- Wrong carrier: the number is valid, but your store sends customers to the wrong carrier website.
- Label only: a real number exists, yet the carrier never receives the parcel.
- Wrong order: a valid tracking number belongs to a different customer shipment.
- Recycled number: the carrier reuses an old identifier and a lookup initially shows historical scans.
- Unsupported last-mile handoff: the original number stops working when a local carrier takes over and the mapping is missing.
The first two can often be caught instantly. The others require time-based validation.
Validate tracking in layers
Layer 1: syntax
Reject empty values, placeholders, obvious supplier order IDs and characters that cannot belong to the expected carrier format. Syntax validation should be conservative: carriers have many services and formats, so a hard-coded regex can also reject legitimate shipments if it is too narrow.
Layer 2: carrier identification
If the supplier provides a carrier code, map it to your internal carrier list. If the code says “USPS” but the number format and tracking endpoint resolve to another carrier, send the order to review instead of guessing.
Layer 3: first carrier response
Query the carrier or a trusted tracking aggregator. Distinguish:
- not found;
- label created / pre-shipment;
- accepted by carrier;
- in transit;
- exception;
- delivered.
“Not found” for a few hours can be normal. “Not found” several days after the supplier claims dispatch is an incident.
Layer 4: consistency
Where the carrier exposes non-sensitive destination hints such as country, region or postal-code fragment, compare them with the order. Do not scrape or expose personal data unnecessarily, but use available signals to catch a tracking number moving to the wrong country or state.
Layer 5: movement over time
A tracking number that remains in pre-shipment indefinitely should not satisfy your “shipped” service-level metric. Track both label_created_at and first_scan_at.
Why recycled tracking numbers are confusing
Some carrier identifier formats can eventually be reused. A fresh lookup may then display old events until the carrier’s current shipment record fully propagates, or a third-party tracking cache may hold stale history.
Signs that you may be looking at stale or recycled history include:
- delivery scans dated months before the order existed;
- a destination inconsistent with the new shipment;
- events that end long before the supplier created the label;
- the same number appearing in your historical database for an unrelated order.
Keep a tracking-number history table. If a supplier sends a number your store has already used, trigger review. Do not automatically accuse the supplier of fraud; identifier reuse and data-entry mistakes are both possible. The important point is that the update is unsafe to publish until verified.
The dangerous case: valid tracking attached to the wrong customer
This can happen through spreadsheet row shifts, supplier-side copy/paste, race conditions, webhook mapping bugs or a fulfillment integration that updates the parent order instead of the intended line item.
Detection rules can include:
- one tracking number attached to two currently active orders;
- destination country mismatch;
- ship date before the customer order date;
- carrier service impossible for the selected route;
- a tracking update mapped to a SKU that the supplier never accepted.
Webhook duplication can cause related fulfillment errors. If your integration sends or receives the same event more than once, review the guide to idempotency and duplicate supplier orders after webhook retries.
Build an exception queue instead of emailing every anomaly
| Condition | Suggested operational state |
|---|---|
| Placeholder / malformed | Reject update immediately |
| Not found < grace period | Wait and recheck |
| Not found > SLA | Supplier investigation |
| Label created, no scan > threshold | Dispatch exception |
| Destination mismatch | High-priority manual review |
| Duplicate active tracking | High-priority manual review |
| Historical scans before order date | Possible stale/recycled data |
The thresholds should reflect carrier behavior. A domestic next-day parcel and an economy cross-border line should not share the same grace period.
What if a bad number already reached the customer?
Correct the information quickly. Tell the customer that the tracking reference was incorrect or has not validated, that you are verifying the shipment and when you will provide the next update. Do not fabricate a new status to make the problem look smaller.
If a package is later shown as delivered but the customer says it is missing, that is a different workflow. Use the delivered-but-not-received claim process rather than treating it as a bad-tracking case.
Supplier scorecard: include tracking quality
Measure how often each vendor provides:
- a valid number;
- the correct carrier;
- first scan within the promised dispatch window;
- correct order mapping;
- successful last-mile handoff;
- updates without manual support intervention.
Tracking data is part of fulfillment quality. A supplier that ships physically on time but sends unreliable numbers still creates avoidable support cost and customer anxiety.
FAQ
Is “label created” enough to mark an order shipped?
It proves that a shipping record may have been created, not necessarily that the carrier has the parcel. For operational metrics, track first carrier acceptance separately.
How long should I wait for a tracking number to become active?
There is no universal interval. Use carrier- and shipping-method-specific thresholds based on normal pickup and scan behavior.
Can a tracking number be reused?
Some identifier systems can eventually recycle numbers. That is why date consistency and your own tracking history are valuable validation signals.
admin
Author of practical guides to dropshipping, ecommerce, automation, and growing an online business.