WANB Express Tracking

Where should I track a WANB Express parcel?

Use the WANB Express Track & Trace Platform first. Its public interface includes fields for:

A named destination carrier is useful routing evidence. The stronger handoff signal is item-level evidence from that carrier — for example, its own acceptance or movement event for the parcel.

If you are unsure whether you copied the shipment number correctly, use the tracking-number verification guide before assuming the parcel is missing.

Why can WANB and another carrier both appear?

WANB's own tracking-support material says WanB acts as a forwarder and integrates multiple companies to deliver a parcel. WANB also says it cannot fully manage tracking information from every partner.

That creates an important distinction:

WANB tracking identity is not the same thing as continuous WANB physical custody from origin to doorstep.

A parcel can move through WANB-related processing, linehaul agents, customs, and a downstream delivery company. Partner names shown in WANB or service materials describe possible network relationships; they are not enough to assign a specific parcel to that carrier.

For a particular shipment, prefer this evidence order:

1. a carrier is merely named or assigned;
2. a local/final number exists;
3. that carrier recognizes the number;
4. that carrier records item-level acceptance;
5. that carrier records movement in its own network.

The farther down that sequence you get, the stronger the evidence that the downstream carrier owns the next delivery step.

Data received is not the same as physical receipt

WANB's documented tracking model distinguishes electronic shipment information from later physical-receipt events.

For example, WANB documents a DataReceived event separately from OriginalWarehouseReceive. Its parcel model also distinguishes Confirmed or pre-advice from Arrived / received and InStock / received-and-verified states.

The practical rule is:

A shipment record, confirmation, or electronic-data event can exist before the parcel is physically received into that process.

So if the newest evidence is only data creation, confirmation, or pre-advice, do not describe the parcel as physically handed over yet. A warehouse-receipt or item-level carrier-acceptance event is stronger custody evidence.

These are examples from WANB's documented system semantics; the public consumer tracker does not have to display every technical label exactly as the API documentation does.

Which tracking number should I use?

Use the WANB/shipment tracking number explicitly associated with your parcel first.

WANB's documentation shows that additional identifiers can exist in some workflows, including virtual numbers and later final/last-mile numbers. It also documents a workflow where a last-mile tracking number and label can exist before the goods are handed to the last-mile delivery warehouse.

Two consequences follow:

• a second or local number is not guaranteed for every WANB parcel;
• the existence of a local/final number is not proof of downstream-carrier acceptance.

If a local number appears, test it in the named carrier's own tracking system. If that carrier has no item-level record yet, keep WANB as the primary evidence source until stronger handoff evidence appears.

The reviewed first-party evidence does not establish one universal WANB prefix, fixed length, suffix, checksum, or route-independent tracking-number pattern. Do not reject a number simply because it fails an unofficial WANB format rule.

For more detail on changing identifiers after a cross-border handoff, see how to find the last-mile carrier and local tracking number.

WANB tracking is not updating

A stale WANB record does not have one universal explanation. WANB itself says it cannot fully manage tracking information from all partner companies, so a missing WANB update can be a visibility or synchronization gap.

That is only a possibility. It is not proof that the parcel is still moving, and it is not proof that the parcel is lost.

Use this sequence:

1. Check the latest WANB event and whether it confirms physical receipt or only electronic data.
2. Look for a destination-carrier name.
3. Look for a local, final, or secondary tracking number.
4. If a downstream carrier is named, test the shipment-specific number in that carrier's own tracker.
5. If that carrier shows acceptance or movement, use its record for the leg it controls.
6. If WANB cannot track the parcel and no stronger downstream record exists, use WANB's tracking-support form. The form asks for your name, email, tracking number, and message, and WANB says customer service may contact partner companies when its site cannot track the parcel.

For general diagnosis when an active record stops changing, see why package tracking may not be updating.

What does a customs event prove?

A customs event tells you something about the customs stage. It does not automatically prove the parcel has been accepted by the destination carrier.

In particular:

customs cleared ≠ local-carrier acceptance ≠ out for delivery

After customs clearance, look for the next shipment-specific evidence: a downstream-carrier acceptance scan, movement in that carrier's own system, or another event showing the parcel entered the next delivery process.

Customs requirements, payments, holds, and release rules vary by jurisdiction. If an authority, broker, or carrier asks for documents or payment, follow the request from the party actually controlling that customs action rather than treating a generic tracking label as legal advice.

What does Delivered prove?

WANB's tracking model includes Delivered as a completion status, but its technical model exposes PODReady and DeliveryPhotoReady separately.

That means a Delivered event should be read as:

the tracking system recorded a completion event

It should not automatically be read as universal proof of:

• possession by the named recipient;
• a signature;
• a delivery photo;
• GPS evidence;
• entitlement to a refund or claim payment.

If the parcel says Delivered but you do not have it, identify the carrier that controlled the final leg and use any stronger delivery evidence that carrier provides. Then follow the delivered-but-not-received guide rather than assuming the status alone resolves what happened.

Who should I contact next?

Use the actor that controls the next useful action.

WANB's tracking-support page says its customer service may contact partnered companies when the parcel cannot be tracked on WANB's site. That does not mean WANB can force a partner to create scans, guarantee a response time, or control every downstream delivery action.

What 11Tracking can and cannot do

11Tracking can help you organize tracking evidence and identify the carrier or actor that appears to own the next step.

It cannot create or backfill WANB scans, make WANB recognize a number, access private WANB merchant or API systems, contact WANB or another carrier for you, reroute or release a parcel, clear customs, obtain private proof of delivery, decide a claim, issue a refund, or guarantee an update or delivery.

Use the tracker evidence to identify the responsible system, then take the action with the party that actually controls that stage.