About WST
WST(WanShunTong Logistics or 万顺通) is the carrier name supplied for this tracking page. Shipment-specific responsibility, service type, origin, destination and delivery partner should be determined from the tracking record and the seller’s shipping information rather than inferred from the brand name alone.
| Field | Verified information |
| Displayed carrier name | WST |
| Official website | https://www.wst.group/ |
| Tracking responsibility | The current holder of the parcel should be identified from the latest physical acceptance, handoff or delivery scan. |
Pro Tip: A carrier label, merchant reference and destination-country delivery number can be different identifiers for the same order. Compare the latest event, location and date before deciding which company currently has the parcel.
Carrier Entity Relationships
| Entity | Relationship |
| WST | WST is the carrier label selected for this page; the shipment record determines the operational service and current custodian. |
| Merchant or marketplace | The merchant supplies the order and may provide a reference number that is not a carrier tracking number. |
| 17TRACK | 17TRACK aggregates available tracking events and does not transport parcels or decide delivery outcomes. |
| Destination delivery partner | A destination partner may perform the final delivery when a shipment record shows a handoff or a new local identifier. |
Quick Answer
Enter the shipment tracking number supplied by the seller or shown on the shipping receipt into the official WST website or 17TRACK. If no result appears, first remove spaces and punctuation, check every character, confirm that you are not using an order number, and ask the seller whether the parcel has been physically handed to the carrier.
17TRACK is an independent tracking platform. It does not transport parcels, change addresses, approve refunds, open carrier investigations or decide claims.
How to Track WST Packages
Use the official website when you need carrier-specific instructions, and use 17TRACK when you want available events from multiple logistics parties in one view.
Tracking Number Format
| Identifier family | Normalized pattern |
| Carrier tracking number | Use the exact identifier shown by the seller or receipt; a redacted example is TRACK########. |
View all details for WST carrier tracking numbers
| Issued by | The issuing logistics party is identified by the label, receipt or electronic shipping record. |
| Where users see it | Common locations include a seller dispatch email, marketplace shipment page, carrier receipt or parcel label. |
| Tracking scope | Visibility begins when the identifier is registered or scanned and can change when another delivery party receives the parcel. |
| Caveat | A merchant order number, reference number, customs number or local delivery identifier may not be accepted as the primary tracking number. |
|
| International or handoff identifier | Use the destination or origin identifier supplied in the shipment record; do not infer ownership from a prefix alone. |
View all details for WST international identifiers
| Possible relationship | One order can have an origin number, a carrier number and a last-mile number linked in the logistics record. |
| Customer action | Try each shipment identifier supplied by the seller and compare the latest event location before contacting a delivery party. |
| Recognition limit | Format alone cannot establish service, ownership, delivery speed or current physical custody. |
|
Service Comparison
| Shipment type | Best tracking approach |
| Domestic parcel | Check the carrier identifier on the receipt or seller notification. |
| Cross-border parcel | Check both the original shipment number and any destination-country number provided after handoff. |
| Merchant shipment | Use the shipment tracking number rather than the marketplace order number. |
Delivery Time
| Timing question | How to interpret it |
| Estimated delivery date | An estimate can move when acceptance, customs, handoff or delivery scans are delayed. |
| Service standard | A published standard applies only to the relevant service, origin, destination and operating conditions. |
| Actual arrival | The delivery scan is stronger evidence of completion than an estimated date. |
Destination Country Delivery Times
| Destination group | Planning guidance |
| Domestic destination | Use the shipment-specific estimate and latest scan; route-level timing depends on origin, service and address. |
| International destination | Allow additional time for export processing, line-haul, import clearance, taxes, handoff and local delivery. |
| Remote or rural destination | Final-mile frequency and local operating conditions can extend the delivery window. |
Do not treat an estimated delivery date as a money-back guarantee. Customs, weekends, holidays, weather, address quality, peak volume and missing scans can change the delivery path.
Common Tracking Problems and Solutions
The latest event usually indicates which party should act. A label-created event does not by itself prove physical acceptance, and a partner event does not by itself prove that WST has received the parcel.
Status Quick Lookup
| Status stage | Immediate interpretation |
| Pre-shipment | Electronic shipment data exists, but a physical acceptance scan may not yet exist. |
View all details for WST pre-shipment status
| Current responsible party | Usually the sender, merchant or origin logistics party until physical handoff is recorded. |
| What happens next | The parcel should receive an acceptance, pickup or first movement scan. |
| Customer action | Ask the seller when the parcel was handed over and verify the identifier character by character. |
|
| In transit | The shipment has a movement event; tracking may remain quiet between facilities or transport legs. |
View all details for WST in-transit status
| Current responsible party | The party associated with the latest physical scan is the best operational contact. |
| What happens next | Another facility, customs point or delivery partner should generate the next visible event. |
| Customer action | Compare the event date with the seller’s promised window and avoid opening duplicate cases with multiple parties. |
|
| Customs or handoff | The parcel is being processed, transferred or presented for import or export procedures. |
View all details for WST customs or handoff status
| Important distinction | Arrival at an exchange or customs facility does not equal customs release. |
| What happens next | Authorities or the destination delivery party may request documents, payment or address information. |
| Customer action | Check official notices and contact the seller or named destination party using the shipment identifier. |
|
| Out for delivery or delivered | The parcel is assigned to final delivery or has a recorded delivery scan. |
View all details for WST delivery status
| If delivery failed | Check the event for a new attempt, pickup location, address issue or return instruction. |
| If marked delivered | Check the entrance, mailbox, reception desk, household members and nearby safe locations before escalating. |
| Next contact | The seller can often request assistance or replacement when the delivery party cannot resolve the case. |
|
Problem & Solution
| Problem or status | First action |
| Invalid number | Check for an order number, missing character, extra punctuation or an identifier belonging to another parcel. |
| No update or label created | Ask the seller whether the parcel was physically handed over; electronic pre-advice is not acceptance. |
| Customs delay | Review official customs or delivery notices and prepare invoice, identity, address or tax information if requested. |
| Delivered but missing | Check all delivery locations, household members, reception staff and neighbors, then ask the seller to investigate. |
| Damaged or lost | Photograph the parcel, retain packaging and contact the seller or eligible claimant using the shipment evidence. |
View all details for WST tracking problems
| When to escalate | Escalate when the promised delivery window has passed, the event indicates an exception, or the seller cannot explain the latest scan. |
| Who should contact the carrier | The sender or merchant may have stronger investigation and claim rights; recipients should follow the delivery party’s local process where offered. |
| Evidence to prepare | Tracking number, order reference, dispatch date, delivery address, latest event, invoice, contents description and photographs. |
|
International Flow
| Stage | What customers should understand |
| Origin preparation | The seller prepares the label and export information before physical acceptance is recorded. |
| Export and line-haul | The shipment moves through origin processing, security or export customs and international transport. |
| Destination processing | Import customs and the destination delivery party may process the parcel before final delivery. |
View all details for WST international handoffs
| Physical custodian | The latest physical scan provides the strongest indication of which party currently holds the parcel. |
| Can the number change? | A destination or last-mile identifier may appear after handoff, while the original number can remain linked to the shipment. |
| Visibility gap | Longer gaps can occur during international transport, customs processing and transfer between systems. |
| Customer action | Use the destination identifier if supplied, check import notices and ask the seller to coordinate an investigation. |
|
Customer Service
| Channel | Use it for |
| Official WST website | Website access and any contact or shipment instructions published there. |
| Seller or marketplace | Order changes, replacement, refund coordination and cases where the sender must initiate a carrier inquiry. |
| Destination delivery party | Local delivery attempts, customs notices, pickup instructions and delivery-location questions when a handoff is shown. |
Tracking API
// WST carrier-specific public API endpoint and authentication
// were not established from the available evidence.
// Use the current WST developer documentation before implementation.
// 17TRACK API
POST https://api.17track.net/track/v2.4/register
Headers:
17token: YourKey
Content-Type: application/json
Body:
[
{
"number": "TRACKING_NUMBER",
"carrier": "CARRIER_CODE"
}
]
// Confirm the current 17TRACK carrier code from the official
// carrier directory or API documentation before sending production requests.
Sources & References
17TRACK is an independent tracking platform and is not affiliated with WST.