Label created or no movement
Check whether the parcel has been packed, handed to the carrier or received its first physical scan. These are different milestones.
Read the tracking-handoff guide →Start with the parcel's physical stage, the evidence available and the next carrier or supplier deadline. A tracking number, delivered scan or complaint is a starting point; the remedy depends on what can still be changed and what the evidence supports.
Check whether the parcel has been packed, handed to the carrier or received its first physical scan. These are different milestones.
Read the tracking-handoff guide →Send the corrected field and ask whether the order is still editable. After carrier acceptance, a change may fail, cost extra or require pickup.
Prevent address failures →What is still possible depends on where the parcel is, not on how the request is made. Ask for the cut-off hour and weekend rule in writing before you need them.
See what each stage allows →Record the pickup location or carrier contact route, the deadline, and any redelivery instruction. The first move is the recipient contacting the local carrier with the contact details we supply; a first-attempt failure often resolves within a day, so re-read the scan before escalating. Missing the deadline can lead to return or disposal.
What happens after a failed delivery →Confirm why the return started, where the parcel is going, whether another attempt is possible and which charges or evidence apply. A returned parcel goes to the carrier's overseas return hub, not to China; a resend needs a corrected full address plus a reachable phone number and carries a fee, and the hub holds the parcel only for a limited time before disposal.
Compare remedy paths →Check the address, household or reception, local carrier path, timestamp and any delivery certificate. A scan is evidence, not automatic proof of handover to the recipient.
Understand the investigation →Keep the packaging and send a focused photo or video pack that shows identity, condition, context and the requested outcome.
Build the evidence pack →| Stage | What we check | Possible next step |
|---|---|---|
| Before dispatch | Editable order, stock, address, product and packing status | Correct, hold, cancel, repack or release |
| In carrier network | Physical scans, route, address options and trace eligibility | Wait for next event, request trace, arrange pickup or attempt redelivery |
| Delivered or returned | Carrier evidence, local checks, return reason and deadlines | Carrier review, recovery, reship, refund or another evidence-based outcome |
| Product complaint | Approved version, parcel condition, evidence and repeat pattern | Troubleshoot, replace, refund, hold related stock or open supplier corrective action |
Carrier investigations, proof availability, reporting windows and after-sales terms vary by route. Confirm the terms for your order. We will state the current stage, owner, next update and closure evidence rather than treating an acknowledgement as a resolution.
Most change requests are refused for one reason: the parcel has already moved past the point where that change is possible. This is the window, stage by stage.
| Stage | Still changeable | No longer changeable |
|---|---|---|
| Received, not yet purchased | Product, variant, quantity, destination, packing, cancel at no cost | Nothing |
| Purchased, not yet received | Address, packing treatment; cancellation possible, sometimes with a supplier deduction | Product and variant, in practice |
| Received, not yet packed | Address, packing, inserts, consolidation; variant subject to stock | Nothing purchased-specific |
| Packed and labelled | Address, by unpacking and relabelling — the last inexpensive moment | Product, variant, consolidation |
| Handed to the carrier | Refusal, return, redelivery at a cost, after-sales remedy | Recall, address change, cancellation |
Ask for your account cut-off in writing — the processing day, the hour after which a batch stops being editable, and the weekend rule — so you can publish it in your own store policy instead of requesting an exception each time.