4PX Tracking

4PX tracking at a glance

• Enter: One supported 4PX tracking number.
• A recognised number confirms: A public shipment record may be available.
• It does not confirm: Physical pickup, current location, customs release, local-carrier possession, or delivery.
• Keep: The original 4PX number and any verified replacement or destination local number.
• Read: The exact event, timestamp, location, and publishing operator—not only a shortened parent status.
• First contact before possession: Usually the merchant or shipper.
• First contact after a local handoff: Usually the destination carrier for local delivery events, while the merchant remains responsible for the purchase remedy.
• No universal rule: 4PX does not publish one tracking-number format, delivery time, attempt count, holding period, last-mile carrier, claim deadline, or compensation table for every product and country.

Track one supported 4PX number

Use the tracking form with the identifier supplied as the carrier tracking number. Do not enter several numbers in one submission, even though an official legacy 4PX interface has supported multiple-number queries.

The one-number limit keeps the public result easier to interpret and reduces privacy, validation, rate-limit, and provider-routing risks.

Before submitting, check that you are not entering:

• a store order number;
• an AliExpress or marketplace order number;
• a payment reference;
• a 4PX warehouse account number;
• a phone number;
• a customs declaration reference;
• a claim case;
• a locker or pickup code;
• a number issued only for an inbound parcel sent to a consolidation warehouse.

A merchant or marketplace may show several references on the same order. The correct carrier number is the one linked to the logistics record, not necessarily the most prominent order identifier.

What a result can show

Depending on the product and data available, the public result can contain events for:

• electronic order creation;
• seller handoff or pickup;
• origin processing;
• warehouse receipt or intake;
• consolidation;
• outbound dispatch;
• export preparation;
• line-haul transport;
• destination arrival;
• customs;
• destination-carrier assignment;
• local-carrier acceptance;
• delivery route;
• pickup point or locker;
• Delivered;
• exception;
• return.

A route can be sparse. Absence of one expected event does not establish that the physical stage did or did not occur.

What the form cannot determine

The tracking form cannot independently establish:

• the contents or condition of the package;
• whether the declared value is accurate;
• whether a seller completed the handoff when no possession event appears;
• which exact 4PX product applies from an unsupported number pattern;
• whether a partner has physically accepted the package when only an assignment appears;
• the legal customs decision before an explicit release event;
• the named person who received a package;
• claim eligibility, liability, compensation, refund, or buyer-protection rights.

What is 4PX?

4PX, also written as 4PX Express and associated with the Chinese name 递四方, is a cross-border logistics brand. Its current official service architecture includes:

• Global Direct Shipping;
• Global Fulfillment;
• Global Reverse Logistics;
• B2B logistics services;
• warehouse and forwarding workflows;
• postal and commercial partner delivery.

Those services do not all use the same route, identifier, customs process, proof, delivery standard, or claim terms.

4PX and Cainiao are related but not the same tracker

Current corporate reporting identifies 4PX as majority-owned by Cainiao. That ownership relationship does not make the brands or tracking systems interchangeable.

Cainiao majority ownership
≠ 4PX and Cainiao are the same public carrier
≠ every Cainiao shipment uses 4PX
≠ one provider code
≠ one universal tracking number

Use a Cainiao tracking page or marketplace record when Cainiao is the actual logistics identity. Use the 4PX page when the shipment record is assigned to 4PX.

Historical SingPost investment is not current 4PX ownership

Older third-party descriptions often say that 4PX is owned or backed by Singapore Post. SingPost announced the unwind of its indirect minority position, and its later reporting described the investment as reduced to nil.

SingPost can still appear as a postal or logistics partner on a particular route. A partnership does not mean SingPost currently owns 4PX, and it does not prove that SingPost handles the shipment you are tracking.

4PX is not the marketplace or merchant

A merchant or marketplace can:

• create the purchase order;
• select a 4PX product;
• submit shipment data;
• display “shipped” in its own system;
• provide the first tracking number;
• control refund, replacement, and purchase disputes.

Those commercial events are not the same as physical 4PX possession. When tracking shows only electronic data and no origin acceptance event, the merchant or shipper is normally the party best placed to confirm whether the package was handed over.

4PX is not automatically the destination carrier

4PX can coordinate an international route without performing every physical mile. A postal operator or commercial carrier may control:

• local tracking;
• local acceptance;
• delivery attempts;
• pickup or locker service;
• final proof;
• final delivery;
• local investigation.

Do not infer the destination carrier from the country alone.

Which number should you enter?

The safest public rule is:

Enter the identifier explicitly supplied as the 4PX tracking number.

No current official public source reviewed for this page establishes one universal 4PX:

• prefix;
• length;
• suffix;
• domestic format;
• international format;
• regular expression;
• product-code pattern.

A number beginning with 4PX can appear in legitimate logistics contexts, but that observation does not prove that every valid number has that prefix or that every string beginning with it is a valid public tracking number.

Identifier types that must remain separate

A no-result response has more than one possible cause

“No result,” “not found,” or an unrecognised identifier can mean:

• the number was copied incorrectly;
• a merchant order was entered instead of a tracking number;
• shipment data exists but has not activated in public tracking;
• the wrong regional or product tracker was used;
• the route received a replacement number;
• the destination number is not active yet;
• data is account-only or outside retention;
• the product is unsupported by the current provider;
• the number is invalid.

A no-result response alone does not prove fraud. Recheck the exact characters, compare the number with the merchant’s shipping details, and ask the merchant which carrier record the identifier is intended to open.

From merchant order to delivery: the evidence ladder

A 4PX route can cross several systems. The following ladder shows what each stage can establish.

What evidence changes the conclusion?

The next visible evidence matters more than a guessed waiting period.

• Electronic order data becomes stronger possession evidence after a pickup, drop-off, warehouse intake, or origin-processing event.
• Warehouse receipt becomes stronger workflow evidence after intake, consolidation, or outbound dispatch.
• A replacement number becomes useful after the original and new identifiers are explicitly linked.
• A named partner becomes stronger handoff evidence after that partner records physical acceptance.
• Destination arrival becomes legal clearance only after a customs release event.
• Customs release becomes local possession only after the destination carrier records receipt or processing.
• Out for delivery becomes completion only after a Delivered, pickup, or other final outcome.
• A return becomes a merchant remedy only after receipt, inspection, and the merchant’s separate refund or replacement decision.
• A claim becomes compensation only after liability and settlement are accepted.

Electronic order data, pickup, and physical possession

Shipping order or label created

4PX merchant systems can create a shipping order before the physical package enters the network.

Use this interpretation:

shipping order or label created
→ logistics data exists
≠ package handed to 4PX

The merchant may still be packing the item, waiting for a pickup, transferring it to an origin partner, or preparing a bulk handoff.

Pickup requested

A pickup request confirms that collection was arranged or requested. It does not prove:

• the courier arrived;
• the sender presented the package;
• the item passed acceptance checks;
• the package entered a 4PX facility;
• the first public scan was recorded.

Which event is stronger possession evidence?

Look for wording that records one of the following:

• picked up;
• accepted;
• received by 4PX;
• received at an origin facility;
• warehouse intake;
• processed at an origin facility;
• a comparable event explicitly tied to the physical item.

The exact wording and operator matter. A status from an origin partner can establish possession by that partner without proving that the parcel has reached a 4PX-owned facility.

Can the first scan be delayed?

Yes, a visible scan can be delayed or omitted. That possibility does not allow the page to assume that an unscanned package is moving.

When only pre-advice or label data appears, the public evidence remains incomplete:

no possession event visible
≠ physical handoff definitely did not happen
≠ physical handoff definitely did happen

Contact the merchant or shipper when their stated dispatch window has passed and the record still contains only electronic data.

Warehouse, forwarding, and fulfillment tracking

4PX is not only a direct parcel carrier. It also operates warehouse, fulfillment, forwarding, and consolidation workflows. These can produce tracking stages that look like delivery but refer only to a warehouse leg.

Warehouse receipt is not always completed intake

A parcel can be delivered to a warehouse receiving point before it is:

• matched to the customer account;
• checked against a pre-declaration;
• measured or weighed;
• photographed;
• accepted for storage;
• cleared from an exception;
• made available for consolidation;
• dispatched outbound.

A regional 4PX forwarding workflow shows why these stages must remain distinct.

warehouse signed or received
→ a receiving event may exist
≠ intake completed in every workflow

If an inbound merchant carrier says delivered but the 4PX warehouse account does not show intake, preserve both records and contact the forwarding or warehouse support channel. The issue may involve matching, missing pre-declaration, incorrect account data, damaged labelling, delayed intake, or another warehouse exception.

Pre-declaration

In forwarding workflows, the customer can be required to declare an inbound parcel before or around warehouse arrival.

Pre-declaration can help the warehouse match:

• merchant carrier number;
• expected contents;
• customer or member account;
• package count.

A declaration does not prove the warehouse physically received the parcel.

Consolidation can create a new outbound number

Several merchant parcels can be combined into one outbound shipment.

inbound package A
+ inbound package B
+ inbound package C
→ consolidation
→ new outbound shipment

The outbound 4PX number can differ from every merchant carrier number. This does not make the earlier numbers false; they describe different legs.

The reverse can also happen: one order may be split into several pieces or outbound shipments.

Warehouse dispatch is a new evidence stage

Warehouse dispatch confirms that a warehouse or fulfillment process released the shipment into an outbound route. It does not, by itself, confirm:

• export departure;
• customs release;
• destination arrival;
• local-carrier acceptance;
• final delivery.

Warehouse delivery is not customer delivery

A merchant carrier may mark an inbound parcel Delivered when it reaches a 4PX warehouse.

That event can be fully correct for the inbound leg while the final recipient is still waiting for:

• intake;
• consolidation;
• outbound dispatch;
• a new tracking number;
• international transport;
• destination delivery.

Always identify the destination of the event: merchant-to-warehouse, warehouse-to-recipient, or return-to-warehouse.

Direct shipping and product distinctions

Global Direct Shipping

4PX describes Global Direct Shipping as a network that integrates postal and express resources. That structure explains why one public route can include several operators and why the final carrier can differ by:

• product;
• origin;
• destination;
• postcode;
• customs route;
• merchant contract;
• service availability.

4PX does not necessarily perform every delivery stage itself.

International special lines

A special-line product can combine:

• origin collection or warehouse handling;
• export processing;
• line-haul transport;
• destination customs;
• postal or commercial last mile.

Do not treat “special line” as one universal carrier, delivery time, customs process, or proof standard.

PostLink

4PX’s direct-shipping architecture includes PostLink, with registered and unregistered small-packet contexts.

Registered and unregistered products can differ in:

• event depth;
• destination visibility;
• proof;
• local-number availability;
• inquiry options.

Sparse tracking can be a product characteristic, but sparse tracking does not rule out delay, misrouting, or loss.

Product codes are not public carrier identities

4PX technical systems use product and service codes. Those codes can change and are not a safe public substitute for the carrier identity.

Do not infer from one code that:

• every route uses the same partner;
• the exact delivery standard is guaranteed;
• a fixed claim rule applies;
• a user can enter the code as a tracking number.

How to read 4PX route events

Public tracking is a sequence of recorded events, not a live map.

A route event may record:

• an electronic order;
• physical receipt;
• warehouse processing;
• departure preparation;
• line-haul movement;
• destination arrival;
• customs;
• partner assignment;
• local acceptance;
• delivery route;
• completion;
• return.

Read the exact event, not only “In Transit”

A normalized parent status can hide the operational distinction between:

• waiting for pickup;
• warehouse processing;
• export dispatch;
• airline or line-haul stage;
• destination customs;
• transfer to a local carrier;
• local delivery.

Preserve the raw event text and the operator that published it.

Events can be delayed, duplicated, or out of order

Possible reasons include:

• batch uploads;
• time-zone conversion;
• partner data exchange;
• late origin messages;
• duplicate system events;
• corrections;
• provider normalization;
• destination-carrier events arriving after 4PX events.

A later display time does not always equal a later physical event time.

Airport and line-haul events are not flight tracking

An airport, flight, departure, or line-haul event can confirm that an international transport stage was recorded.

It does not identify:

• the exact aircraft carrying the package;
• live aircraft location;
• continuous package location;
• completion of destination customs;
• a guaranteed arrival date.

Exception does not automatically mean loss

An exception can concern:

• data;
• address;
• export;
• customs;
• capacity;
• security;
• partner transfer;
• delivery access;
• damage;
• return.

Read the exact reason. A generic exception status is not a confirmed loss determination.

Number replacement and several tracking numbers

Some 4PX product and warehouse workflows can replace or supplement a tracking number.

Why can a number change?

Possible operational reasons include:

• warehouse consolidation;
• product conversion;
• outbound relabelling;
• postal injection;
• commercial-carrier assignment;
• reverse logistics;
• multi-piece handling;
• destination-number creation.

The public evidence supports the possibility of legitimate replacement in scoped workflows, not a promise that every shipment receives one.

What a replacement number proves

replacement number explicitly mapped
→ a new route identifier exists
≠ original number was fake
≠ the package changed ownership
≠ final carrier physically accepted it

What to preserve

Keep:

• merchant order;
• original carrier number;
• original 4PX number;
• replacement number;
• destination local number;
• date and event where the mapping appeared;
• partner name;
• screenshots or records needed privately for a dispute.

Do not publish those numbers publicly.

Which number should be used next?

• Use the original 4PX number to preserve the complete origin route where it remains active.
• Use the replacement number when the official or verified provider record links it to the shipment.
• Use the destination local number for local acceptance, delivery attempts, pickup, and proof after the partner takes over.
• Keep all mapped identifiers for a claim or merchant dispute.

Partner handoff and local tracking numbers

No universal last-mile carrier

4PX works with multiple postal and express partners. An official partner list demonstrates possible relationships; it does not identify the carrier for a specific parcel.

Do not assume:

• USPS always delivers 4PX shipments in the United States;
• Royal Mail always delivers in the United Kingdom;
• Australia Post always delivers in Australia;
• Singapore Post, China Post, Hongkong Post, DHL, FedEx, or another listed operator handles every route.

The route, service, postcode, customs entry, and merchant contract control.

Partner assignment is not physical acceptance

A data record can assign a destination carrier or create a local number before the physical package reaches that carrier.

partner assigned
→ destination carrier mapped
≠ partner physically received the package

Stronger evidence includes:

• accepted by destination carrier;
• received at a local facility;
• processed by the destination carrier;
• a local facility scan;
• a local delivery event.

“Handed to local carrier” is not delivery

The wording can refer to:

• data transfer;
• transfer to an intermediary;
• physical transfer to the final carrier;
• a broad normalized milestone.

It does not, without more detail, prove:

• the partner accepted the physical package;
• the package is out for delivery;
• the recipient received it;
• claim responsibility moved completely.

Local-number state model

4PX origin number
→ partner assignment
→ local number appears
→ partner receives electronic data
→ partner physically accepts package
→ local processing
→ delivery route
→ delivery outcome

Preserve both numbers

A local number does not invalidate the original 4PX number. The two records may contain different evidence:

• 4PX can show origin, export, and partner assignment;
• the destination carrier can show local acceptance, attempt, safe-place, pickup, signature, photo, or return.

How to identify the last-mile carrier

Use the strongest available mapping:

1. a partner name in the 4PX record;
2. a local number explicitly linked to the shipment;
3. the destination carrier accepting that local number;
4. a local event tied to that operator.

A familiar number format or country-based guess is weaker than an explicit mapping.

Use Find the Last-Mile Carrier when the partner is unclear.

Why 4PX tracking may not update

A tracking gap does not have one cause.

Common branches

• the merchant created data but did not complete handoff;
• a pickup or first scan was delayed;
• the package is waiting for warehouse intake;
• consolidation has not produced the outbound shipment;
• a replacement number exists but is not shown in the current view;
• export or line-haul events are sparse;
• customs is waiting for data, assessment, inspection, or payment;
• a destination partner is assigned but has not accepted the package;
• the local number is not active;
• partner data has not synchronised;
• the product exposes limited public events;
• the number is unsupported, incorrect, or outside retention.

What to check

1. Confirm that the identifier is a carrier tracking number rather than an order number.
2. Read the last exact event and operator.
3. Identify whether the package has a physical possession event.
4. Look for a replacement or local number.
5. Check the destination carrier when a verified handoff exists.
6. Check for a customs, address, pickup, or payment dependency.
7. Preserve any marketplace or payment-protection deadline.
8. Contact the actor that controls the current stage.

Who to contact

• Before a possession event: merchant or shipper.
• During 4PX origin or warehouse processing: shipper/account holder and the relevant 4PX support environment.
• During destination customs: the responsible customs authority, broker, 4PX, partner, or merchant, depending on the request.
• After local-carrier acceptance: destination carrier for local events.
• For refund or replacement: merchant or marketplace.

Use Tracking Not Updating for the broader escalation model.

Customs and 4PX tracking

4PX can transmit data, coordinate transport, use a broker or partner, and display customs-related events. It is not the government authority that makes the legal import decision.

Customs actor model

Customs events describe different stages

A customs-related event can mean:

• data submitted;
• package presented;
• documentation requested;
• assessment;
• inspection;
• payment requested;
• payment accepted;
• release;
• rejection;
• return.

Do not treat every customs event as a delay or every payment request as release.

Payment is not customs release

charge calculated
→ payment request
→ payer verifies the official route
→ payment submitted
→ payment accepted
→ customs decision
→ release
→ carrier processing resumes

Possible charges can include customs duty, VAT or sales tax, brokerage, disbursement, carrier handling, storage, remote-area fees, delivery charges, or merchant charges. The exact label matters.

What to do when customs needs action

1. Verify the request through an independently opened official 4PX, destination-carrier, broker, merchant, or customs page.
2. Identify whether the request concerns documentation, identity, classification, value, tax, duty, handling, or delivery.
3. Do not send identity documents or payment information through an unverified message.
4. Keep proof of submission and payment.
5. Wait for an explicit customs or carrier event showing what changed.
6. Preserve marketplace or payment-protection deadlines.

Use Package Stuck in Customs for the full problem workflow.

United States low-value imports: July 2026 context

The United States rules for low-value imports changed materially before this page was reviewed.

Duty-free de minimis is not a safe default

Current U.S. official material states that duty-free de minimis treatment remains suspended for covered low-value shipments, subject to the stated legal exceptions.

Do not assume that a 4PX package is duty-free because:

• it is below a former threshold;
• it is an ecommerce order;
• it came through a postal partner;
• the merchant charged tax at checkout;
• an earlier package was not assessed.

Postal and non-postal routes can differ

4PX can use postal, commercial, or mixed routes. Those routes can follow different entry processes.

The label “4PX” alone does not identify the U.S. import procedure.

Mail informal-entry process

U.S. Customs and Border Protection states that a new mail informal-entry process took effect on July 24, 2026.

This is a high-volatility operational rule. Verify the current CBP guidance when a shipment or payment decision depends on it.

No universal U.S. charge

Duty or fees can depend on:

• classification;
• origin;
• value;
• entry method;
• current trade measures;
• restrictions;
• broker or carrier handling;
• exemptions.

11Tracking cannot calculate, collect, dispute, or pay the amount.

European Union low-value imports: July 2026 context

Temporary €3 customs duty

European Union guidance reviewed for this page states that a temporary €3 customs duty applies from July 1, 2026 in the scoped low-value ecommerce flow for consignments up to €150. The current temporary measure is scheduled until July 1, 2028.

The €3 duty is not simply once per parcel

The European Commission describes calculation by qualifying item or tariff classification under the declaration, not simply once for the physical parcel.

Several items in different tariff classifications can therefore produce more than one €3 amount.

VAT, IOSS, customs duty, and handling are separate

• IOSS addresses VAT collection in its scope.
• It does not automatically remove the temporary customs duty.
• A carrier, postal operator, or broker handling fee is separate.
• A proposed Union handling fee discussed in the reviewed guidance was not the same as the €3 duty and was not presented there as a final universal amount.

Product identifiers

European Commission guidance states that product identifiers can be provided voluntarily from July 1, 2026 and become mandatory in the scoped system from November 1, 2026.

That is a customs-data requirement, not evidence that a package moved or was released.

Because these rules are highly volatile, use current European Commission and destination-customs guidance for shipment-specific action.

Delivery route, attempts, pickup points, and Delivered

Out for delivery

An out-for-delivery or local-route event means that a delivery attempt is planned or active.

It does not guarantee:

• delivery that day;
• a fixed appointment;
• successful access;
• recipient availability;
• signature completion;
• final proof.

The next event can be Delivered, attempted, delayed, redirected to pickup, returned to a facility, or another exception.

No universal attempt count

The reviewed official evidence does not establish one 4PX-wide global delivery-attempt rule. The destination partner commonly controls the local process.

No universal holding period

Pickup and locker holding periods depend on the destination carrier, location, product, notice, and local rules.

Do not apply one period from a postal operator, forwarding service, or country to all 4PX routes.

Pickup point or locker

A route to a pickup point or locker normally has several stages:

point assigned
→ partner receives the package
→ ready-for-pickup event
→ identity, code, or payment requirement
→ collection

Point assignment is not readiness. Ready for pickup is not collection.

Never enter a pickup or locker code into a public tracking form.

What Delivered confirms

Delivered
→ the publishing operator records completion
≠ named addressee personally received it in every route
≠ contents or condition proved

Possible delivery contexts include a household member, reception, mailroom, authorised agent, safe place, pickup point, locker, or another location allowed by the destination carrier and service.

Read the destination carrier’s proof when available.

4PX says Delivered, but the package is missing

1. Preserve the exact event, time, location, and operator.
2. Identify the destination carrier and local number.
3. Check the local carrier’s tracking record.
4. Check household members, reception, mailroom, building staff, safe place, pickup point, and locker.
5. Look for an official delivery photo, signature, pickup record, or driver note if the service provides it.
6. Contact the destination carrier through its official route.
7. Contact the merchant or shipper and preserve the purchase-protection deadline.
8. Ask the contract holder to open the appropriate carrier inquiry.
9. Keep carrier compensation separate from merchant refund or replacement.

A 4PX-origin completion label can be a normalized partner event. It does not by itself prove theft, fraud, named-recipient receipt, or correct contents.

Use Delivered but Not Received for the complete recovery sequence.

Interception, cancellation, address correction, and route changes

4PX’s authenticated open platform includes interception-related operations for eligible merchant workflows. This does not create a public recipient right to stop or redirect any 4PX package.

Interception is a multi-stage process

request submitted
→ eligibility checked
→ request accepted or rejected
→ package physically intercepted
→ new instruction
→ return, hold, correction, or release

Keep these boundaries:

request submitted
≠ accepted

accepted
≠ physically stopped

intercepted
≠ new route completed

Who can request a change?

Authority can belong to the merchant, shipper, account holder, payer, or platform. The recipient may not hold the 4PX contract.

Address correction can also depend on:

• product;
• route stage;
• customs data;
• destination carrier;
• account permissions;
• fees;
• local law.

An address exception does not automatically prove that the recipient supplied incorrect information.

11Tracking cannot change the route

11Tracking and USTracking cannot:

• cancel the merchant order;
• submit an interception;
• correct the address;
• hold the package;
• reroute it;
• confirm that a request was accepted;
• contact the carrier or partner on the user’s behalf.

Use Change, Reroute, or Hold a Package for the broader decision model.

Returns and reverse logistics

4PX provides Global Reverse Logistics, but the existence of a return service does not create one universal consumer return policy.

Return state model

return requested
→ merchant authorisation
→ return label or instruction
→ carrier acceptance
→ reverse transport
→ warehouse or merchant receipt
→ inspection
→ refund or replacement decision
→ payment

Return tracking does not prove a refund

return initiated
≠ carrier accepted

carrier accepted
≠ merchant received

merchant received
≠ refund approved

refund approved
≠ refund paid

A reverse route or warehouse process can create a new number. Preserve its mapping to the original purchase and outbound shipment.

The merchant or marketplace controls:

• whether the item is eligible for return;
• refund;
• replacement;
• inspection;
• buyer-protection dispute.

4PX controls the contracted logistics stage.

Claims, loss, damage, and compensation

No current official evidence reviewed for this page supports one universal 4PX claim deadline, claimant rule, insurance promise, compensation table, or payout amount for every product and country.

Why old compensation tables are unsafe

4PX has published product-specific and regional insurance or compensation material. Some sources are historical, warehouse-specific, B2B-specific, or limited to a regional forwarding service.

Those documents establish variation. They do not support a current global promise.

Do not rely on an old online table unless the current contract, product, territory, and date match the shipment.

Who usually controls a formal claim?

The merchant, shipper, marketplace, or account holder commonly has the logistics contract and may need to submit the formal claim.

The recipient can:

• preserve evidence;
• report non-delivery;
• report damage or missing contents;
• contact the destination carrier;
• contact the merchant;
• use marketplace or payment protection.

Recipient eligibility to file directly must be verified from current route-specific terms.

Claim state model

problem reported
→ correct claimant identified
→ claim submitted
→ evidence accepted
→ investigation
→ liability decision
→ compensation calculation
→ settlement

claim opened
≠ carrier fault
≠ compensation approved
≠ merchant refund

Evidence to preserve

Keep privately:

• merchant order details;
• original 4PX number;
• replacement number;
• destination local number;
• complete tracking history;
• exact timestamps and operator names;
• packaging and labels;
• photographs of damage;
• missing-content list;
• invoice or value evidence;
• customs communication;
• delivery proof;
• correspondence;
• relevant deadlines.

Do not post those records publicly.

Use Package Claim Guide and Package Damaged or Contents Missing for the broader evidence and action models.

Who should you contact?

Privacy and scam safety

Treat tracking numbers as shipment data

A tracking number can expose route, location, timing, destination area, delivery outcome, or partner information. Keep it private.

Do not place a real tracking number in:

• a public post;
• a review;
• a support screenshot;
• a page URL;
• metadata;
• an AI prompt that does not need it;
• a shared document accessible to strangers.

Never submit these to a public tracker

• phone number;
• home address;
• passport or national ID;
• invoice;
• tax number;
• customs document;
• payment card;
• warehouse login;
• merchant account credentials;
• claim case;
• signature;
• delivery photo;
• pickup or locker code.

Real tracking data does not authenticate a message

A fraudulent message can contain:

• a real 4PX number;
• a current route event;
• a destination city;
• a local number;
• a customs narrative;
• a redelivery narrative;
• 4PX or partner branding.

real number
≠ authentic message

correct event
≠ official payment link

carrier logo
≠ carrier-controlled website

Common suspicious narratives

• customs fee due immediately;
• address correction required;
• redelivery payment;
• storage fee;
• incomplete postcode;
• release payment;
• insurance payment;
• a request for a locker code;
• a request for identity documents.

Safe verification sequence

1. Do not use the link in the message.
2. Open the official 4PX, destination carrier, customs, broker, or merchant site independently.
3. Enter the tracking number only in the official or trusted tracker.
4. Identify the current operator.
5. Verify the exact charge or information request.
6. Do not send a password, payment card, identity document, or pickup code through an unverified page.
7. Preserve the suspicious message privately.
8. Use Fake Delivery Message for the complete verification process.

Frequently asked questions

How do I track a 4PX package?

Enter one supported 4PX tracking number in the tracking form. Use the carrier number, not the merchant order, payment reference, warehouse account, customs reference, or locker code.

Is 4PX the same as 4PX Express?

4PX Express is a legitimate public name variant associated with the 4PX tracking environment. It should not be treated as a separate carrier page unless the current runtime provider proves a separate entity.

Is 4PX the same as Cainiao?

No. 4PX is majority-owned by Cainiao, but it retains a separate brand, official tracker, service architecture, and provider identity. Not every Cainiao shipment uses 4PX.

Does Singapore Post own 4PX?

Current evidence does not support that statement. SingPost unwound its indirect minority position. It may still appear as a route partner, but partnership is not ownership.

Does a recognised 4PX number mean 4PX has the package?

No. Recognition can begin with electronic shipment data. Look for pickup, acceptance, warehouse intake, origin processing, or another physical-item event.

What does “shipping information received” mean?

It usually means logistics data exists. It does not, by itself, confirm that the merchant handed the package to 4PX.

Does every 4PX tracking number have the same format?

No universal public format was confirmed. Do not rely on one prefix, length, suffix, or regular expression for every product.

Why does my 4PX tracking number not work?

Possible causes include a transcription error, merchant order entered instead of a carrier number, inactive pre-advice, wrong tracker, unsupported product, replacement number, local number not active, old data, or an invalid number.

Why did my tracking number change?

Some warehouse, consolidation, product-conversion, postal-injection, destination-partner, or return workflows can create a replacement or local number. A verified replacement does not make the original number fake.

Should I keep the old number?

Yes. Keep the original 4PX number, replacement number, and destination local number. They may show different route stages and can be needed for an inquiry or dispute.

What does a 4PX warehouse event mean?

It can mean the parcel reached a warehouse receiving process. It does not always mean that account intake, consolidation, or outbound dispatch is complete.

Can several packages become one 4PX shipment?

Yes, in a consolidation workflow several inbound packages can be grouped into one outbound shipment. The outbound number can differ from the merchant carrier numbers.

Does 4PX deliver the final mile?

Sometimes 4PX or an affiliated operational route may control more of the delivery, but many shipments use postal or commercial destination partners. The actual carrier must be identified from the shipment record.

Who delivers 4PX in the United States?

There is no confirmed universal carrier. USPS, a commercial carrier, or another partner can appear depending on the product and route. Use a verified local number and partner acceptance event.

Who delivers 4PX in the United Kingdom?

There is no confirmed universal carrier. Royal Mail or another partner may appear on some routes, but country alone does not identify the carrier.

What does “handed to local carrier” mean?

It can mean the destination operator was assigned, data was transferred, or physical handoff occurred. Look for the partner’s own acceptance or facility event before concluding that it has the package.

Why is the local carrier number not active?

The number can be created before the local carrier receives the physical package. Partner data may also take time to activate or synchronise.

Is 4PX tracking live GPS?

No. Public tracking is a sequence of recorded events. Airport and line-haul events do not reveal live aircraft or package location.

Why is 4PX tracking not updating?

The route may be waiting for handoff, warehouse intake, consolidation, export, customs, partner acceptance, or data synchronisation. The exact event and current operator determine the safest action.

Does destination-country arrival mean customs cleared?

No. Arrival, customs presentation, assessment, payment, release, and local-carrier possession are separate stages.

Does paying customs mean the package was released?

No. Payment is one dependency. Wait for an explicit release or later carrier-processing event.

Does 4PX make delivery attempts?

The destination carrier usually controls local attempts. No universal 4PX-wide attempt count was confirmed.

How long will a pickup point hold a 4PX package?

There is no universal 4PX holding period. Use the destination carrier’s official notice and pickup rules.

Does Delivered prove I personally received the package?

No. It confirms that the publishing operator recorded completion. The service may allow delivery to another person, reception, mailroom, safe place, pickup point, locker, or another authorised location.

Can 4PX stop or redirect my package?

4PX has account-side interception capabilities for some merchant workflows, but that does not mean every recipient can request a change. The merchant, shipper, account holder, route stage, and destination partner control eligibility.

Does return tracking mean my refund is approved?

No. Return transport, merchant receipt, inspection, refund approval, and payment are separate events.

Who can file a 4PX claim?

The merchant, shipper, marketplace, or account holder commonly controls the carrier contract. Direct recipient eligibility depends on current route-specific terms.

Is there one 4PX claim deadline?

No current universal deadline was confirmed. Product, contract, origin, destination, problem type, and claimant can change the rule.

Can 11Tracking contact 4PX or the local carrier?

No. 11Tracking can display supported public tracking data and guidance. It cannot contact carriers, merchants, brokers, or customs authorities.

Can 11Tracking pay customs or file a claim?

No. It cannot calculate or pay customs, submit documents, file claims, recover a package, obtain a refund, or guarantee compensation.

Use USTracking as a tracking companion

After identifying the correct number and current operator, USTracking may help you:

• save a supported 4PX tracking number;
• organise public route events;
• preserve original, replacement, and verified local numbers;
• monitor later public updates;
• compare public 4PX and destination-carrier events;
• receive notifications.

USTracking cannot access protected warehouse or merchant accounts, identify a product from an unsupported number pattern, choose a universal last-mile carrier, locate an aircraft or vehicle, contact an operator, change the route, pay customs, retrieve protected proof, file a claim, recover the package, guarantee delivery, or guarantee a refund.

Related guides

• Package Tracking Help Center
• How Package Tracking Works
• Label Created
• Carrier Received Package
• In Transit
• Handed to a Local Carrier
• Customs Processing
• Customs Cleared
• Tracking Not Updating
• Tracking Number Not Found
• Out for Delivery
• Out for Delivery but Not Delivered
• Delivered
• Delivered but Not Received
• Package Stuck in Customs
• Find the Last-Mile Carrier
• Change, Reroute, or Hold a Package
• Proof of Delivery, Photo, and Signature
• Package Claim Guide
• Who to Contact About a Package
• Fake Delivery Message
• How International Package Tracking Works

Scope, evidence, and limitations

This page is an English-language guide to public 4PX tracking evidence, identifier relationships, warehouse and direct-shipping stages, partner handoffs, customs, destination delivery, returns, and responsible-party routing.

It is based primarily on official 4PX public pages, 4PX Open Platform documentation, official 4PX regional forwarding material, current corporate ownership reporting from SingPost, and current U.S. and European Union customs sources reviewed on July 25, 2026.

Important limitations:

• The current runtime provider and accepted identifier families must be verified during implementation.
• No universal 4PX number format was confirmed.
• No universal destination carrier was confirmed.
• No universal delivery time, attempt count, holding period, claim deadline, compensation table, insurance promise, or customs charge was confirmed.
• 4PX technical APIs describe authenticated merchant capabilities and must not be treated as universal public rights.
• Regional forwarding examples do not automatically apply to every 4PX product.
• U.S. and EU customs rules are highly volatile and can change before the next scheduled review.
• Public tracking can be delayed, incomplete, normalized, translated, corrected, or out of order.
• 11Tracking does not diagnose a specific live shipment and cannot act on the package.

Last reviewed: July 25, 2026 Review due: October 23, 2026 Research decision: Ready to draft with explicit limitations and runtime verification