Read the event before the headline
FedEx distinguishes a created label, a parcel moving through its network and an out-for-delivery scan. It describes an exception as a delay caused by circumstances such as weather or customs. Those definitions help illustrate the difference between electronic information and physical handling. Other services can use different labels. Source: FedEx tracking guide.
| What you can see | What it supports | What to ask next |
|---|---|---|
| Label or shipment data created | A shipping record exists | Is there an acceptance scan or confirmed handover? |
| Dated carrier facility or movement event | A handling event was recorded | Which carrier and next stage does the selected line use? |
| Exception or action requested | Something requires review | What information or action is needed, and by whom? |
| Out for delivery or delivered | A last-mile event was recorded | Is there a delivery attempt, proof of delivery or address issue? |
An empty local record may be only one part of the journey
If a service uses more than one carrier, ask which number covers the current stage and which belongs to final delivery. A local label may exist before that carrier receives the parcel. Do not infer that the parcel is lost solely from that record, or assume it is already in your country.
Save the complete event sequence with dates, time zones and the source where you read it. A summary such as “in transit for a week” loses the distinction between no new scans and several recorded movements. If two tracking pages differ, compare timestamps and carrier names before deciding that one must be wrong.
Send one evidence bundle
A support request is more useful when it includes the parcel reference, selected line, destination country, dispatch date and tracking number. Add the last event verbatim as a short quotation or screenshot, with its timestamp. Remove unrelated personal information before sharing a public screenshot.
Ask three precise questions: has the parcel been accepted by the next carrier, what is the next expected event, and is action required from the recipient? If the carrier asks for documents, verify that the request is associated with your real shipment through the carrier's known channel. Do not post account passwords or full payment details in a forum.
Know when a trace is the right question
Compare the present record with the service's stated estimate and enquiry procedure. Ask the sender or contracted provider when a formal trace is appropriate and who must open it. Do not use an arbitrary universal rule such as “no scan for three days means lost.”
Keep each case reference and reply in one place. If the status says delivered but the parcel is absent, record the delivery evidence and any safe-place or reception details, then report the mismatch promptly through the relevant service. A general complaint post does not replace that case record.
For planning a future purchase, use the stage-by-stage time guide. For an existing Pikobuy order, the platform account and the named carrier remain the sources of shipment-specific information.
Sources & scope
- FedEx tracking status guide ↗FedEx event definitions used as examples; not universal terminology or tracking evidence for a particular Pikobuy parcel. · Checked 2026-10-25T16:04:30Z