“Label created” is not the same as “shipped.” It usually tells you that shipment information or a label exists; it does not by itself prove that a carrier has collected and scanned the parcel. In dropshipping, that distinction determines whether your delivery promise is still realistic, whether a supplier has missed its dispatch commitment and what you can responsibly tell the customer.
The right response is not to send another tracking email every morning. It is to identify the last confirmed physical event, establish ownership of the delay and set a deadline for a verifiable update.
What does “label created” actually establish?
A tracking number can be allocated before a parcel is picked, packed or handed to a carrier. The supplier’s order management system may display “fulfilled” as soon as it purchases a label, while the carrier has no possession scan. Some carriers also receive parcels in bulk and scan them later, so a missing first scan does not conclusively prove the package stayed at the warehouse.
| Status | What you know | What you still need to establish |
|---|---|---|
| Label created / pre-advice received | A shipment record exists | Whether the parcel was physically handed over |
| Carrier accepted / origin scan | The carrier recorded receipt or processing | Whether onward movement is proceeding |
| In transit | At least one movement event is visible | Expected arrival and exceptions |
| Delivery exception | A problem was flagged | Who can resolve the exception and by when |
Start with a timeline, not with the tracking page
- Record the customer’s order timestamp, payment confirmation and promised dispatch window.
- Record when the order was accepted by the supplier, not just when it entered your store.
- Record the label creation time and the shipping service selected.
- Check the carrier’s own tracking page as well as the supplier dashboard.
- Compare these events against the supplier’s processing cutoff, working days and holiday calendar.
- Open a supplier inquiry once the agreed handover period has passed, with the order ID, label number and exact unanswered question.
If your workflow already maintains a queue for overdue orders, add the shipment to that queue rather than treating it as a new exception system. The separate guide to fulfillment exception queues and aging orders explains how to set ownership and escalation thresholds.
Five questions a useful supplier reply must answer
- Has the exact parcel physically left your facility?
- On what date and local time was it handed to which carrier or collection driver?
- Can you provide a collection manifest, acceptance event or another carrier-verifiable reference?
- Was the label voided, replaced or assigned to a different package?
- If there is no evidence of handover, when will the order be dispatched or replaced?
A screenshot showing the tracking number is not an answer to these questions. The aim is a verifiable event, not a reassurance that the status will update “soon”. During seasonal closures, compare claims against the supplier holiday shutdown and restart schedule before escalating.
Do not create a second shipment too early
Resending too soon can produce two deliveries, two product charges and an avoidable return. The alternative is not endless waiting: establish a decision deadline based on the actual customer promise and the supplier’s agreement. If the supplier cannot confirm possession, decide whether cancellation, an alternative fulfillment location or a replacement is necessary.
Keep the original number on the order until you have evidence it was invalidated. If the supplier has issued a fresh carrier number, follow the separate process for a tracking number changed after dispatch. When a legitimate order contains several cartons, do not confuse a split shipment with duplicate labels; see the guide to orders with two tracking numbers.
How to communicate with the customer
Say what is confirmed, what remains unconfirmed and when you will update them. For example: “Your order has been prepared for shipment. We are checking the carrier handover because the first tracking event has not appeared. We will update you as soon as we have a verified dispatch status.” Do not claim “the parcel is on the way” without evidence. If the delivery promise can no longer be met, communicate the available remedies promptly in line with the rules of the customer’s market.
Useful operational metrics
Track label-to-first-scan time separately from order-to-label time. A supplier may generate labels quickly yet hand parcels to the carrier late. Compare medians and unusually long delays by supplier, warehouse, service and destination. You can also calculate the share of orders with no first scan after the agreed window:
No-first-scan exception rate = orders without a confirmed first scan after the cutoff ÷ orders eligible for a first scan × 100%.
Exclude orders that have not yet reached their contractual cutoff. This prevents false alarms on weekends or holidays.
Frequently asked questions
Does “label created” mean the supplier has shipped my order?
No. It confirms label or shipment data, not necessarily physical transfer. A carrier acceptance event or another reliable handover record is stronger evidence.
Can a carrier miss the first scan?
Yes. Bulk collection and scanning practices can produce a delay, which is why absence of a scan is a warning, not proof of wrongdoing.
Should I refund immediately?
Base that decision on the promised delivery date, confirmed facts, applicable customer rights and whether fulfillment is still feasible. Do not treat a tracking status as a substitute for those obligations.
What should I measure across suppliers?
Measure accepted-order-to-label, label-to-first-scan and first-scan-to-delivery separately. Combining them hides where delays actually arise.
Sources
admin
Author of practical guides to dropshipping, ecommerce, automation, and growing an online business.