GTD Tracking

Please enter the GTD tracking number to check the latest shipping status.

TRACK

About GTD

GTD is the carrier name supplied for this tracking guide. Shipment-specific service coverage, tracking identifiers, delivery standards, handoff partners and support channels should be checked against the current information published on the official GTD website.

Verified item	Official reference
Official website	GTD official website
Tracking source	Use the tracking or shipment-support entry published on the official GTD website and follow the instructions for the relevant shipment.

Pro Tip: A marketplace order number is not necessarily a carrier tracking number. Use the identifier shown in the dispatch notice, shipping label, receipt or carrier tracking result.

Quick Answer

To check a GTD shipment, enter the tracking identifier supplied by the sender into the official GTD tracking entry or into 17TRACK. If no result appears, first check the characters, remove accidental spaces or punctuation, confirm that the seller has handed over the parcel, and ask the sender whether the number is an order reference rather than a tracking number.

17TRACK is an independent tracking platform. It displays available carrier events but does not transport parcels, change delivery addresses, approve refunds, open carrier investigations or decide claims.

How to Track GTD Packages

The most reliable workflow is to start with the identifier provided by the sender and compare the result from the official GTD source with the available 17TRACK events.

Tracking route	Recommended action
Official GTD route	Open the official GTD website, locate its tracking or shipment-support entry, enter the identifier exactly as supplied, and save the displayed event history.
17TRACK route	Open 17TRACK, enter the identifier, allow carrier detection where available, and compare the latest event with the official source.
Seller or marketplace route	Open the dispatch notification and confirm the tracking identifier, origin, destination and any stated handoff carrier before contacting support.

A label may be prepared before a parcel receives its first physical acceptance scan. An empty result can therefore mean that the identifier is new, mistyped, assigned to another carrier, or still waiting for the first event. The sender is usually best placed to correct an incorrect number or request an investigation.

Tracking Number Formats and Examples

A carrier-specific public format cannot be inferred safely from the brand name alone. Do not treat an order number, invoice number, customer reference or dispatch notice number as a GTD tracking number unless the sender or tracking result identifies it as such.

Tracking Number Format

Identifier family

Safe interpretation

Carrier tracking identifier

Use the exact identifier supplied in the shipping confirmation or shown on the shipping label; a masked example such as TRACK-#### is illustrative only.

View all details for carrier tracking identifiers

Issued by	The issuing party depends on the shipment arrangement and may be the named carrier, an origin logistics provider or a postal operator.
Where it appears	Common locations include a dispatch email, merchant order page, shipping label, receipt or carrier notification.
Tracking scope	One identifier can cover only one transportation stage, or it can remain associated with a shipment after a partner handoff.
Caveat	A prefix or length alone does not establish the service, issuing carrier or current physical custodian.

Merchant order or reference number

Use it to locate the purchase with the seller. It may not return carrier events in an external tracking tool.

View all details for merchant references

Issued by	The seller, marketplace or warehouse system.
Where it appears	Order confirmation, invoice, account page or customer-service correspondence.
Next step	Ask the seller to provide the shipment tracking identifier if the dispatch message does not include one.

Tracking Statuses and Meanings

Status wording varies by carrier system. The practical meaning depends on whether the event is a data-preparation event, a physical scan, a customs event, a delivery attempt or a final delivery event.

Status Quick Lookup

Status stage

Immediate interpretation

Pre-shipment or label created

Shipment data may exist, but the physical parcel may not yet have received an acceptance scan. Ask the sender to confirm handover.

View all details for pre-shipment status

Responsible party	The sender or shipping platform generally controls the next action until physical acceptance is recorded.
What happens next	An acceptance, pickup or processing event may appear after handover.
Customer action	Verify the identifier and contact the sender if the parcel was described as dispatched but no physical event appears.

In transit

The shipment has a movement or processing event. Scans may be intermittent between facilities or during partner handoff.

Customs or handoff

The shipment may be undergoing border processing or moving between transportation systems; arrival at a gateway is not the same as customs release.

Out for delivery or delivery attempt

A local delivery step is in progress or was attempted. Check the event instructions and delivery location.

Delivered

A delivery event was recorded. If the parcel is missing, check the delivery location, household, reception desk, neighbours and any proof-of-delivery information before escalating.

Exception or return

An obstacle may require action, or the shipment may be moving back to the sender. The sender should review the carrier instructions and contact route.

Common Tracking Problems and Solutions

Start with the event text and the party that controls the next step. A tracking platform can display an event, while the sender, carrier, customs authority or destination delivery operator may control the remedy.

Problem & Solution

Problem or status	First action
Invalid number	Re-enter the identifier exactly, check confusing characters and ask the sender whether it is an order reference.
No events	Allow for the first scan after handover, then ask the sender to verify dispatch and carrier assignment.
No update during transit	Compare the latest event with the expected route, allow for processing or handoff gaps, and escalate through the sender when the shipment is materially overdue.
Delivery exception or failed attempt	Read the event instructions, check the address and delivery access, and follow the carrier or local delivery operator's next-step process.
Delivered but missing	Check the porch, mailbox, reception desk, household members and neighbours; review proof of delivery; then contact the sender promptly.
Customs hold	Check whether the destination authority or delivery operator requests documents, duties or recipient information. Do not treat an arrival scan as a release scan.
Lost or damaged parcel	Preserve packaging and evidence, notify the sender, and use the applicable carrier inquiry or claim route. 17TRACK cannot approve a claim or refund.
Returned to sender	Ask the sender why the return was initiated and whether a corrected address, re-shipment or refund process is available.

Customer Service

Use the official GTD website for the current support route. Before contacting support, prepare the tracking identifier, sender and recipient details, shipment date, latest event, service description, delivery address and any photographs or value documents relevant to the issue.

Customer Service

Channel	Best use
Official GTD website	Open the official website and use the current tracking, contact or support route shown there.
Sender or marketplace	Use this route for an incorrect tracking number, seller refund, replacement, shipping-label correction or carrier inquiry initiated by the shipper.
17TRACK	Use 17TRACK to compare available events across supported carriers; it cannot alter delivery instructions or process a claim.

Tracking API

API

// Carrier-specific official API:
// Current public official tracking API documentation is not included here.

// 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"
  }
]

// Replace TRACKING_NUMBER with the shipment identifier.
// Use the current 17TRACK documentation to confirm the carrier code
// and account requirements before sending production requests.