1ST Tracking

What 1ST is — and how to avoid the wrong “1st”

The safest public owner for this page is the 1ST / 一代国际 group-level logistics identity at 1st56.com. First-party English pages also use renderings around 1st International Group. The English wording is not perfectly consistent across the site, so this page does not convert every translated company phrase into a legal-name claim.

Inside that group, the current operating layer most relevant to ordinary 1ST tracking is 一代国际 / 深圳市一代国际货运代理有限公司, whose current site is 1st168.com. That operating site is not an unrelated carrier simply because the wider group site uses a different domain.

This page is therefore for tracking intent that can be tied to the 1ST logistics identity. Use logistics/entity context such as 1st56.com, 一代国际, or a shipment-specific 1ST label before assuming this page is the correct owner.

If the only thing you have is an unfamiliar identifier and you are not sure which carrier it belongs to, use the tracking-number verification guide before treating a recognized format as proof of shipment or possession.

Use the native 1st168 tracking surface first

For a shipment identified as 1ST / 一代国际, open the current native 1st168 tracking site.

The visible first-party function is labeled:

• 运单追踪 — waybill/shipment tracking
• 快件查询 — express/shipment query

The wider 1ST group FAQ also says that a user can query shipment trajectory by entering a 单号 — a shipment/tracking number in that context — on the company's cargo-tracking website.

The visible first-party surface confirms the native tracking route, but the reviewed public evidence does not establish a complete native input/result contract. Treat undocumented input syntax, result fields, status vocabulary, and later-leg behavior as unconfirmed rather than filling them from third-party trackers.

Why 17TRACK may also recognize a 1ST shipment

In July 2023, 1ST published a first-party announcement stating that the group had completed integration with 17TRACK and that users of 1ST-number channels could use 17TRACK to query parcels. Current 1ST group surfaces also continue to expose 17TRACK as an external/friendly link.

That supports a simple route model:

1. Native first-party route: use 1st168.com first for a shipment tied to 一代国际.
2. Additional documented route: use 17TRACK when a 1ST number is recognized there.
3. Downstream-carrier route: if the shipment evidence identifies a separate physical carrier and that carrier has accepted the parcel into its own system, use that carrier's official record for carrier-specific delivery actions.

Do not reverse the authority model. A field shown by 17TRACK is not automatically a field defined by 1ST. Do not treat third-party identifier labels as documented native 1ST tracker inputs unless first-party evidence says so.

Likewise, a third-party tracking API is not an official 1ST API merely because it can retrieve a 1ST shipment.

1ST is not FIRST LINE

The wider group presents 一代国际 / 1ST and 壹号专线 / FIRST LINE separately. The wider group presents FIRST LINE as a separate company/brand. Treat it as a separate tracking owner rather than importing FIRST LINE behavior into 1ST.

That means:

If your shipment is explicitly identified as FIRST LINE, do not import its identifiers or tracking behavior into the 1ST model.

Which 1ST number should you use?

The safest first-party term is 单号: the shipment/tracking number used to query trajectory in the current 1ST FAQ context.

Start with the number that the merchant, shipper, shipping label, or 1ST shipment record explicitly associates with 1ST / 一代国际. Then test that identifier on the native 1st168 surface.

If 17TRACK recognizes the same 1ST identifier, that can be useful corroborating tracking visibility because 1ST itself documented the integration. It still does not tell you that every other identifier visible in a third-party result is a valid native 1ST input.

If the shipment later exposes a different carrier's tracking number, preserve both numbers. The 1ST number can remain useful for the cross-border history while the downstream number may become more useful for local delivery.

If you cannot tell whether the number is a tracking number, merchant order number, replacement number, or downstream number, see How to Find and Verify a Tracking Number.

Why there is no safe universal 1ST tracking-number format

The current first-party sources reviewed for this page do not publish one exhaustive rule for:

• a universal 1ST prefix;
• fixed character length;
• fixed suffix;
• checksum;
• one regular expression that covers all 1ST services.

That absence matters because 1ST's service model is broad. It includes express-agency relationships, special-line products, postal-packet services and other cross-border logistics flows. A format seen in one route or one external tracker should not be promoted into a universal detector.

So a number that “looks like” a community example is not enough to prove that it belongs to 1ST. Conversely, a number that does not resemble a familiar example is not enough to exclude 1ST.

Does a 1ST record mean 1ST physically has the parcel?

Not necessarily.

A 1ST shipment/reference can exist while the shipment is moving through different operational actors. First-party service material names UPS, FedEx and DHL within the group's international-express agency model and also describes postal-packet and customs-logistics services.

The safe evidence question is not simply “Does 1ST know about this shipment?” It is:

Which actor has the strongest item-level evidence for the physical leg happening now?

A data or shipment record can establish that a logistics object exists. Stronger possession evidence can come from a warehouse receipt, item-level acceptance, movement scan, downstream-carrier receipt, or another actor-specific physical event.

This prevents two opposite errors:

• assuming 1ST physically possesses the parcel merely because a 1ST record exists; and
• assuming 1ST has no role merely because another carrier later appears.

When UPS, FedEx, DHL, postal, or another carrier may own the next leg

1ST's current service portfolio explicitly names UPS, FedEx and DHL in an agency model and also includes postal-packet services. That supports a multi-actor architecture, not a universal partner list.

Do not infer that:

• every 1ST shipment uses UPS, FedEx or DHL;
• one final-mile carrier is used everywhere;
• a second tracking number must always be created;
• 1ST never physically handles freight itself.

Instead, wait for shipment-specific evidence.

When an external carrier is explicitly identified, compare the records:

• Assignment/reference only: another carrier may have been selected without item-level physical acceptance yet.
• Downstream carrier records receipt or handling: that carrier's own system becomes stronger evidence for that leg.
• Local delivery event appears in the downstream system: use that carrier for address, hold, redelivery, pickup or POD questions that it actually controls.

If the handoff is visible but the local carrier is unclear, use How to Find the Last-Mile Carrier and Local Tracking Number. If a downstream carrier is named but its own record stays silent, use Why Is the Local Carrier Not Updating After Handoff?.

What handoff evidence proves — and does not prove

A handoff-related record should be read as a transition claim, not as an automatic conclusion that every later step has happened.

First-party historical FBA documentation separated arrival at the final-mile carrier from later delivery milestones. That material is not used here as a current consumer status glossary; it supports only the narrower evidence lesson that final-mile arrival and delivery are different states.

For the general meaning of a local-carrier transition, see Handed to Local Carrier.

What a no-result does — and does not prove

If the native 1st168 query or another tracking system does not return a result, the absence of a visible record in that system does not by itself prove:

• fake tracking;
• loss;
• cancellation;
• that the merchant never shipped;
• that the number belongs to another carrier.

Use a bounded check instead:

1. Confirm the entity. Is this shipment actually tied to 1ST / 一代国际, rather than FIRST LINE or an unrelated “1st” company?
2. Recheck the number. Compare it with the merchant or shipping record rather than relying on a retyped copy.
3. Try the native route. Use 1st168.com.
4. Try the documented additional route where appropriate. 17TRACK may recognize 1ST-number channels.
5. Look for a downstream carrier. A later carrier number may become the better lookup key.
6. Return to the merchant or shipper when the commercial record cannot be connected to a transport record.

There is no first-party basis here for inventing a universal “wait X hours before 1ST activates the number” rule.

If the problem remains a lookup failure, use Why Is My Tracking Number Not Found or Not Working?. If a previously active record simply stopped receiving new events, use Why Has My Package Tracking Not Updated?.

Who should act now?

Use the actor that controls the next transition, not necessarily the brand most visible at the top of the tracking history.

For a general actor-selection problem, use Who Should I Contact About a Package? or the Official Carrier Support Directory.

Next decisive evidence

When two systems disagree, do not decide from brand familiarity alone. Identify the next record that would materially change the conclusion.

1. Native 1ST result vs no result

A valid native 1ST result strengthens attribution to the 1ST logistics record. A no-result only tells you that the queried system did not return a usable record under the conditions you used.

2. 1ST record vs physical possession

Look for item-level warehouse receipt, acceptance, movement or carrier-handling evidence before making a physical-custody claim.

3. Handoff assignment vs downstream acceptance

A named local carrier or new number is useful. The downstream carrier's own acceptance/handling record is stronger evidence that the handoff has actually entered that carrier's operational network.

4. Customs becomes the controlling issue

If a customs request, hold, document requirement, or payment/action request becomes the main problem, follow the named official customs/broker/shipper process instead of inferring a transport outcome from the carrier label alone. Start with What Does Customs Processing Mean? and move to Package Stuck in Customs when an unresolved customs action is the dominant problem.

5. Final-mile event vs delivery evidence

A final-mile arrival or assignment is not delivery. If the final carrier records Delivered but you do not have the parcel, use Package Says Delivered but I Did Not Receive It. If you need the carrier's photo, signer or other delivery record and it exists for that service, use How to Get Proof of Delivery.

1ST FAQ

Is 1ST the same carrier as FIRST LINE?

No. Current first-party group material presents them as separate companies/brands, so FIRST LINE is not a 1ST tracking alias.

What is the official 1ST tracking site?

For the operating 一代国际 layer, the current first-party site at 1st168.com exposes the native 运单追踪 / 快件查询 function. The wider group site at 1st56.com provides the group identity and tracking/support context.

Can I track a 1ST shipment on 17TRACK?

1ST published a first-party announcement documenting integration with 17TRACK for users of 1ST-number channels. Use 17TRACK as an additional lookup route, not as the source of native 1ST policy or undocumented tracker fields.

What does a 1ST tracking number look like?

The reviewed first-party sources do not establish one universal prefix, suffix, fixed length, checksum or regex. Use the shipment number that the merchant, shipper or 1ST record actually associates with the shipment rather than relying on a pattern found on an aggregator or forum.

Does a 1ST tracking result prove that 1ST has my parcel?

Not by itself. 1ST's logistics model can involve warehouses, express carriers, postal channels, customs stages and downstream carriers. Look for actor-specific physical acceptance or movement evidence.

Why does another carrier appear after 1ST?

That can be consistent with 1ST's multi-actor logistics model. When a downstream carrier is explicitly identified and records the current physical leg, its own tracking system can become the stronger source for local delivery actions.

Does a no-result mean my 1ST number is fake?

No. A no-result in one queried system does not by itself prove fraud, cancellation, loss or non-shipment. Verify the entity, the number, the native route, the documented 17TRACK route where appropriate, and any downstream-carrier evidence.

What 11Tracking can and cannot do

11Tracking can help you compare tracking evidence, identify which carrier or system is currently stronger, and route you to official tracking or help pages.

11Tracking cannot create or backfill 1ST scans, access private 1ST or ERP accounts, contact 1ST or 17TRACK for you, change an address, reroute or redeliver a parcel, clear customs, retrieve private proof of delivery, file or approve a claim, force a merchant refund, or guarantee a tracking update or delivery outcome.