DHLink Tracking

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

https://www.dhlink.com

TRACK

About DHLink

DHLink is the logistics service platform associated with DHgate cross-border ecommerce. In tracking, DHLink normally acts as a logistics organizer or shipping-service platform that may combine seller pickup, warehouse processing, export transport, customs-related handoff, line-haul, and destination last-mile carriers rather than operating every physical delivery scan itself.

Core DHLink Profile

Field	Verified information
Official name	DHLink
Official website	https://www.dhlink.com
Carrier type	Cross-border logistics platform and shipping-service organizer for ecommerce shipments; physical scans may be performed by origin handlers, postal operators, express carriers, airlines, customs-related facilities, or destination last-mile partners.
Primary region	China-origin cross-border ecommerce shipments and international destination delivery lanes used by DHgate sellers and buyers.
Tracking page	DHLink official website; if the shipment is shown with a postal or last-mile number, also check the destination carrier after handoff.
Parent organization	Associated with DHgate logistics services; a separate current legal headquarters, founding date, and corporate registration details are not publicly confirmed on the landing information normally available to parcel recipients.
Founded and headquarters	Not publicly confirmed for recipient-facing tracking purposes; do not rely on third-party directory data for claims, address changes, or legal notices.

Carrier Entity Relationships

Entity

Relationship summary

DHLink

DHLink is the canonical logistics platform used for DHgate-related cross-border shipping services.

View all details for DHLink

Entity type	Canonical carrier or logistics-platform entity.
Why it matters to tracking	Users should search DHLink when the marketplace shipping method, seller label, or parcel notice identifies DHLink as the logistics channel.
Official evidence	The official website is published at https://www.dhlink.com.

DHgate

DHgate is the ecommerce marketplace relationship most recipients associate with DHLink shipments.

View all details for DHgate relationship

Entity type	Ecommerce marketplace context.
Why it matters to tracking	A buyer may see an order number inside DHgate and a separate DHLink or partner tracking number after the seller ships.
Official evidence	DHgate buyer and seller logistics workflows point users to platform-based shipment records and logistics support.

Operated shipping services

DHLink offers cross-border ecommerce shipping options, but service names, lane availability, and carrier partners can vary by seller account, origin, destination, and product category.

View all details for DHLink shipping services

Entity type	Service entities.
Why it matters to tracking	The service selected by the seller determines whether the first visible event is a warehouse scan, a postal acceptance scan, a line-haul milestone, or a destination-carrier event.
Official evidence	DHLink website and DHgate logistics workflow information.

Postal and last-mile partners

Destination postal operators and commercial last-mile carriers may perform delivery after DHLink or an upstream partner transfers the parcel.

View all details for partner handoff entities

Entity type	Network and delivery entities.
Why it matters to tracking	A destination-carrier scan means the partner physically handled the parcel; an electronic pre-advice event alone does not prove the parcel has arrived at that carrier.
Official evidence	International postal and commercial carrier tracking practices, plus carrier-specific tracking results when a partner number is issued.

17TRACK

17TRACK aggregates available tracking events for DHLink and possible downstream carriers when the tracking number or linked carrier route can be identified.

View all details for the 17TRACK relationship

Entity type	Independent multi-carrier tracking platform.
Why it matters to tracking	17TRACK can help compare DHLink events with destination-carrier events, but 17TRACK does not transport parcels, approve refunds, change addresses, or decide claims.
Official evidence	17TRACK tracking and API documentation.

Quick Answer

To track DHLink packages, enter the tracking number shown in your DHgate order, seller shipping notice, or parcel label on the official DHLink website or on 17TRACK. If no result appears, first check whether you entered a marketplace order number instead of a logistics tracking number, whether the seller has only created a label, and whether a downstream carrier number has been issued.

Pro Tip: 17TRACK is an independent tracking platform. 17TRACK can display available tracking events, but only the seller, DHLink support, or the physical delivery carrier can correct shipment data, update the address, investigate loss, or handle a refund.

How to Track DHLink Packages

Use both the official DHLink route and a multi-carrier route when a cross-border parcel passes from a DHLink logistics channel to a postal or commercial last-mile carrier.

Tracking path	What to do
Official DHLink tracking	Open https://www.dhlink.com, enter the logistics tracking number, and compare the latest event with your order shipment date.
17TRACK tracking	Enter the same number on 17TRACK to detect DHLink and possible partner carriers, especially after destination-country handoff.
Marketplace order record	Open the DHgate order detail page and check whether the seller has provided a tracking number, carrier name, and shipment date.
Destination-carrier tracking	If a USPS, Royal Mail, Canada Post, local postal, or commercial last-mile number appears, track that number with the destination carrier after the first partner acceptance scan.

Copy the logistics tracking number exactly as shown; remove spaces and punctuation unless the carrier page requires them.
Do not use a DHgate order number, payment transaction number, invoice number, or seller reference as a tracking number unless DHLink explicitly accepts it.
If tracking is empty, wait for the first physical acceptance or warehouse scan and ask the seller to confirm that the parcel has been handed to the logistics provider.
If the destination carrier shows more detail than DHLink, use that carrier for delivery appointment, pickup, proof of delivery, or local address questions.

Tracking Number Formats and Examples

DHLink shipments may use DHLink-issued logistics identifiers, seller-facing order references, postal S10 identifiers, or last-mile carrier numbers. A number being searchable in DHLink or 17TRACK does not always mean DHLink issued the number.

Tracking Number Format

Identifier family

Normalized pattern

DHLink logistics identifier

Alphanumeric or numeric platform identifier; exact public rule not fully published.

View all details for DHLink logistics identifiers

Length/structure	Varies by service lane and upstream partner. Remove spaces and hyphens before searching.
Issued by	DHLink or a DHLink-connected logistics system.
Typical service/use	Cross-border ecommerce shipping records visible to sellers and buyers.
Who sees it and where	Buyers usually see it in the DHgate order page or shipping email; sellers see it in shipping management records.
Tracking scope	May cover order handover, warehouse processing, export, line-haul, and partner handoff when events are transmitted.
Important caveat	Do not infer exact service or destination carrier from the prefix alone because DHLink route mapping can vary.

Postal S10 identifier

Two letters + nine digits + two-letter country code, for example LX#########CN or RR#########CN.

View all details for postal S10 identifiers

Length/structure	13 characters under the UPU S10 family; the final two letters normally identify the issuing postal operator's country.
Issued by	Usually an origin postal operator or postal logistics partner, not necessarily DHLink.
Typical service/use	Registered, tracked packet, ePacket-like, EMS-like, or postal parcel services depending on issuing operator and product.
Who sees it and where	Marketplace buyers may see it after the seller ships; destination postal operators may continue using the same number after import.
Tracking scope	Can show origin-post acceptance, export, destination exchange, customs-related events, and local delivery where data is exchanged.
Important caveat	An S10 number ending in CN is commonly issued in China-origin postal channels; DHLink or 17TRACK may display it without being the issuing postal operator.

Destination last-mile number

Carrier-specific number issued by the destination postal or commercial delivery company.

View all details for destination last-mile numbers

Length/structure	Depends on the last-mile carrier; it can be numeric or alphanumeric.
Issued by	Destination postal operator, courier, parcel network, pickup-point operator, or local delivery contractor.
Typical service/use	Local delivery, pickup, proof of delivery, failed-delivery notice, or return routing.
Who sees it and where	Recipients may see it in later tracking events, delivery notices, SMS or email notifications, or the local carrier website.
Tracking scope	Usually strongest after destination import handoff and first local acceptance scan.
Important caveat	A last-mile number may not show early export events; keep the original DHLink or postal number for seller disputes.

Marketplace order or reference number

Order ID or seller reference; not a parcel tracking number by default.

View all details for order and reference numbers

Length/structure	Platform-specific order number or merchant reference format.
Issued by	DHgate, seller system, payment platform, or merchant order management system.
Typical service/use	Order lookup, buyer protection, seller communication, invoice reconciliation.
Who sees it and where	Buyers see it in the order page and order confirmation; sellers see it in store management tools.
Tracking scope	Usually not trackable on carrier websites unless explicitly linked to a shipment identifier.
Important caveat	If only an order number is available, ask the seller for the logistics tracking number and carrier name.

Tracking Statuses and Meanings

DHLink tracking events should be read as a logistics lifecycle. The responsible party changes when a parcel moves from seller preparation to DHLink processing, export transport, customs-related processing, and last-mile delivery.

Status Quick Lookup

Status

What it means

Shipment information received

A shipping record or electronic pre-advice exists, but the parcel may not yet be physically accepted.

View all details for shipment information received

Lifecycle stage	Pre-shipment.
Current responsible party	Seller or warehouse preparing the parcel.
What happens next	Pickup, drop-off, or warehouse acceptance scan should follow.
What you should do	Check the seller shipment date; ask the seller if no physical event appears after the promised dispatch window.

Accepted or received by warehouse

The parcel has entered a logistics facility or partner handover point.

View all details for accepted or received by warehouse

Lifecycle stage	Accepted.
Current responsible party	DHLink-connected warehouse, origin handler, or first-mile carrier.
What happens next	Sorting, security screening, export consolidation, or assignment to line-haul.
What you should do	No action is usually needed unless the seller shipped the wrong item or address.

In transit or departed facility

The parcel is moving between facilities, export hubs, airports, or partner networks.

View all details for in transit

Lifecycle stage	In transit.
Current responsible party	Origin logistics partner, line-haul carrier, airline, or transit hub depending on the event.
What happens next	Arrival at export facility, destination country, or partner processing center.
What you should do	Monitor for the next scan; gaps can occur during line-haul and customs data exchange.

Customs clearance in progress

Shipment data or the physical parcel is being processed for export or import clearance.

View all details for customs clearance in progress

Lifecycle stage	Customs or handover.
Current responsible party	Customs authority, broker, postal exchange office, or carrier compliance process.
What happens next	Release, request for information, tax or duty assessment, inspection, or return if prohibited.
What you should do	Watch for messages from the carrier or marketplace; provide tax ID, invoice, or payment only through official channels.

Arrived at destination country

The parcel or shipment data has reached a destination-country entry point; it is not necessarily cleared or out for delivery.

View all details for destination arrival

Lifecycle stage	Customs or handover.
Current responsible party	Destination exchange office, customs process, or receiving carrier.
What happens next	Import clearance and first local-carrier scan.
What you should do	Begin checking the destination carrier if a local tracking number is shown.

Out for delivery

A local delivery route has the parcel and intends delivery according to that carrier's local operations.

View all details for out for delivery

Lifecycle stage	Out for delivery.
Current responsible party	Destination last-mile carrier.
What happens next	Delivery scan, failed attempt, pickup notice, or exception.
What you should do	Follow local carrier delivery instructions and check safe places or building reception.

Delivered

The last-mile carrier recorded delivery, pickup completion, locker delivery, front-desk handoff, or another final delivery event.

View all details for delivered

Lifecycle stage	Delivered.
Current responsible party	Destination carrier for delivery evidence; seller or marketplace for order-resolution questions.
What happens next	No more transport events are expected unless the scan is corrected or a return is created.
What you should do	Check mailbox, parcel locker, porch, reception, family members, and neighbors before opening a seller dispute or carrier inquiry.

Delivery exception or failed attempt

The local carrier could not complete delivery because of access, address, recipient availability, customs, payment, or operational issues.

View all details for delivery exceptions

Lifecycle stage	Exception.
Current responsible party	Usually the destination carrier, but customs or recipient action may be required.
What happens next	Redelivery, pickup, address verification, tax payment, return, or investigation.
What you should do	Contact the local carrier quickly with the tracking number and address details; also notify the seller if a return risk appears.

Returned to sender

The parcel is moving back because delivery, customs, address validation, pickup, or import compliance failed.

View all details for returned to sender

Lifecycle stage	Return.
Current responsible party	Destination carrier during return initiation, then return logistics partners and seller after receipt.
What happens next	Return transit and seller-side resolution.
What you should do	Save screenshots and contact the seller or marketplace buyer-protection channel before the dispute deadline.

Services and Delivery Times

DHLink service availability and delivery speed depend on the seller's selected lane, destination country, parcel attributes, customs, and last-mile carrier. A marketplace estimated delivery date is an estimate unless the seller or carrier explicitly states a guaranteed service.

Service Comparison

Service

Best for

Cross-border economy parcel

Lower-cost ecommerce shipments where transit visibility may improve after major hub or destination-carrier scans.

View all details for cross-border economy parcel

Service type	International economy parcel logistics.
Coverage	Varies by origin, destination, product category, and seller eligibility.
Tracking level	Milestone-based tracking; local visibility depends on partner data exchange.
Key size/weight condition	Not publicly confirmed as a universal rule; seller shipping tools determine eligibility.
Included protection/extra service	Marketplace or seller protection terms may apply; carrier insurance is not publicly confirmed for every lane.
Main limitation	Longer gaps can occur during consolidation, line-haul, and customs.

Cross-border standard parcel

Tracked ecommerce parcels needing more predictable partner handoff than the slowest economy options.

View all details for cross-border standard parcel

Service type	International standard parcel logistics.
Coverage	Lane-dependent and seller-account dependent.
Tracking level	Expected to include dispatch, export, destination arrival, and delivery where partner scans are shared.
Key size/weight condition	Determined by current DHLink shipping tool and partner carrier rules.
Included protection/extra service	Not publicly confirmed as a universal included insurance product.
Main limitation	Address quality, customs declarations, and destination carrier capacity affect delivery.

Postal or registered channel

Small cross-border parcels that use postal exchange and a postal S10 number.

View all details for postal or registered channel

Service type	Postal-tracked packet or parcel channel.
Coverage	Countries supported by the issuing postal operator and destination postal partner.
Tracking level	Postal milestone tracking; delivery confirmation varies by country and product.
Key size/weight condition	Postal product limits apply and may differ from DHLink platform eligibility.
Included protection/extra service	Registered or postal compensation terms depend on the issuing post and product.
Main limitation	Postal exchange and customs can create visibility gaps.

Commercial express or priority channel

Higher-value or time-sensitive seller shipments where a commercial carrier is selected.

View all details for commercial express or priority channel

Service type	International commercial courier or priority logistics channel.
Coverage	Available only where the seller, commodity, destination, and carrier account support the lane.
Tracking level	Typically more frequent carrier scans, subject to the selected partner carrier.
Key size/weight condition	Commercial carrier dimensional weight, declared value, commodity, and customs rules apply.
Included protection/extra service	Coverage and signature options depend on the carrier and shipper account.
Main limitation	Customs duties, remote-area service, and restricted commodities may add cost or delay.

Delivery Time

Service

Published delivery standard

Cross-border economy parcel

Varies by origin, destination, customs, consolidation, and service; no universal recipient-facing fixed standard is publicly confirmed.

View all delivery-time details for cross-border economy parcel

Business or calendar days	Not publicly confirmed as a universal rule.
Guarantee status	No universal money-back guarantee is publicly confirmed for all economy lanes.
Starts counting from	Normally from physical acceptance or warehouse processing, not from order placement or label creation.
Main delay factors	Seller dispatch delay, consolidation, airport capacity, customs, restricted items, destination remote areas, weather, and local carrier workload.
Official source date/validity	Use the current DHLink or DHgate order page estimate for the specific shipment.

Cross-border standard parcel

Varies by route and selected partner; the order page may show an estimated delivery window.

View all delivery-time details for cross-border standard parcel

Business or calendar days	Depends on route and marketplace presentation.
Guarantee status	Treat as an estimate unless a specific guaranteed service is stated.
Starts counting from	Physical handover to the logistics provider or first confirmed acceptance event.
Main delay factors	Customs clearance, incomplete phone or address, destination carrier handoff, and peak-season capacity.
Official source date/validity	Use current shipment-specific DHLink, DHgate, or partner-carrier estimate.

Postal or registered channel

Varies by postal operator, destination post, customs, and international exchange processing.

View all delivery-time details for postal or registered channel

Business or calendar days	Postal standards differ by operator and product.
Guarantee status	Registered or tracked postal services are usually not the same as express guaranteed services.
Starts counting from	Origin postal acceptance or export handover, depending on the displayed service.
Main delay factors	Postal exchange, customs inspection, destination post scanning practices, and local delivery attempts.
Official source date/validity	Check the issuing post and destination post for the current product standard.

Commercial express or priority channel

Varies by carrier product and route; commercial carriers may publish shipment-specific delivery estimates.

View all delivery-time details for commercial express or priority channel

Business or calendar days	Carrier-specific and lane-specific.
Guarantee status	Only guaranteed if the actual partner carrier and product state a guarantee for that shipment.
Starts counting from	Carrier pickup or acceptance scan under the express carrier's rules.
Main delay factors	Customs documentation, duty payment, remote delivery, flight capacity, and dangerous-goods restrictions.
Official source date/validity	Use the current partner-carrier tracking page for the specific shipment.

Common Tracking Problems and Solutions

Most DHLink tracking problems are caused by identifier mismatch, seller dispatch delay, partner handoff gaps, customs processing, address issues, or destination-carrier delivery exceptions.

Problem & Solution

Problem/status shown

Immediate action

Invalid tracking number

Remove spaces, check every character, and confirm that you are not entering the DHgate order ID.

View all solutions for invalid tracking number

Likely cause	Wrong identifier, typo, not yet uploaded, or carrier auto-detection mismatch.
Check first	Order page, seller message, shipping email, and any second tracking number.
When to escalate	Escalate to the seller if no valid logistics number is provided after the seller's stated dispatch period.
Who to contact	Seller or DHgate order support first; 17TRACK cannot create a tracking number.

No tracking updates after label creation

Ask whether the seller has physically handed the parcel to the logistics provider.

View all solutions for label-created delays

Likely cause	Electronic record exists before pickup or warehouse acceptance.
Check first	Seller dispatch promise and first physical scan.
When to escalate	Escalate if the promised dispatch window has passed and no acceptance scan appears.
Who to contact	Seller or marketplace order support.

Stuck in transit

Check whether the parcel is between export and import scans, then compare DHLink, 17TRACK, and the partner carrier.

View all solutions for stuck in transit

Likely cause	Line-haul, customs, missed scan, data exchange delay, or destination carrier not yet accepted.
Check first	Last physical location, last event type, and whether a destination number exists.
When to escalate	Use the marketplace dispute or inquiry window shown in your order; no universal DHLink waiting period is publicly confirmed.
Who to contact	Seller for shipment inquiry; destination carrier if it has accepted the parcel.

Shipping partner awaiting handoff

Treat it as pre-advice unless the destination carrier has a physical acceptance scan.

View all solutions for partner handoff messages

Likely cause	Shipment data was sent before the parcel arrived at the partner carrier.
Check first	Look for accepted, received, arrived at facility, or processed by carrier.
When to escalate	Escalate to seller if handoff remains unchanged beyond the order's estimated dispatch or delivery timeline.
Who to contact	Seller or DHLink route support before the partner physically accepts it.

Customs hold

Watch for official requests for duty payment, tax ID, invoice, or recipient information.

View all solutions for customs hold

Likely cause	Import review, missing declaration data, duty and tax assessment, restricted product, or inspection.
Check first	Destination carrier messages, customs notices, email, SMS, and marketplace notifications.
When to escalate	Escalate if the carrier or customs asks for information and no official channel is clear.
Who to contact	Destination carrier, customs broker where identified, seller for commercial invoice, or marketplace support.

Delivered but not received

Check delivery location, mailbox, reception, household members, neighbors, parcel locker, and proof of delivery before opening a claim.

View all solutions for delivered but not received

Likely cause	Safe-place delivery, building reception, wrong address, premature scan, neighbor delivery, locker pickup, or theft.
Check first	Full address, delivery photo or signature if available, local carrier proof of delivery, and building records.
When to escalate	Escalate promptly to the destination carrier and seller if the parcel cannot be located after local checks.
Who to contact	Destination carrier for delivery evidence; seller or marketplace for order resolution.

Returned to sender

Save the tracking history and contact the seller before the marketplace resolution deadline.

View all solutions for returned to sender

Likely cause	Incomplete address, failed pickup, unpaid duties, prohibited item, recipient unavailable, or local storage expired.
Check first	Reason code from the destination carrier and whether redelivery or pickup is still possible.
When to escalate	Escalate immediately if the parcel is still in the destination country and can be intercepted.
Who to contact	Destination carrier for local options; seller or marketplace for refund or reshipment.

Lost or damaged parcel

Document tracking, packaging, contents, value, and photos; ask the seller which claim route applies.

View all solutions for lost or damaged parcels

Likely cause	Network loss, theft, handling damage, customs inspection, leakage, or inadequate packaging.
Check first	Last scan, delivery proof, package condition, photos, invoice, and seller protection policy.
When to escalate	Follow the marketplace dispute period and partner-carrier claim deadline for the selected service.
Who to contact	Seller for marketplace refund; physical carrier for delivery investigation where allowed.

International Shipping, Customs and Carrier Handoffs

DHLink shipments are typically international ecommerce parcels, so tracking visibility depends on electronic data, physical handoff, export transport, customs, and destination carrier acceptance. Arrival in the destination country is not the same as customs release.

International Flow

Stage

What is happening

Seller dispatch and pre-advice

The seller creates shipment data and may transmit parcel information before physical handover.

View all details for seller dispatch and pre-advice

Physical custodian/responsible entity	Seller or seller warehouse.
Typical tracking event	Shipment information received or label created.
Can the tracking number change?	Yes, a partner or last-mile number may be added later.
Normal visibility gap	Until pickup or warehouse acceptance.
What the customer should do	Confirm the seller has shipped if no physical scan appears.

Origin warehouse or first-mile acceptance

A DHLink-connected facility or first-mile partner receives the parcel for sorting and route assignment.

View all details for origin acceptance

Physical custodian/responsible entity	Origin handler, warehouse, or domestic pickup carrier.
Typical tracking event	Accepted, received, processed, or departed facility.
Can the tracking number change?	Sometimes, if the parcel is consolidated or assigned to a postal channel.
Normal visibility gap	Between sorting and export dispatch.
What the customer should do	Monitor for export or airline handoff scans.

Export customs and security

Shipment data and parcels may be screened for export compliance, commodity restrictions, and transport safety.

View all details for export customs and security

Physical custodian/responsible entity	Export facility, security screeners, customs authority, or logistics broker.
Typical tracking event	Export clearance, customs processing, security check, or handed to airline.
Can the tracking number change?	Usually no, but a master-bag or line-haul reference may be used internally.
Normal visibility gap	During screening and dispatch scheduling.
What the customer should do	Provide product or invoice information only if the seller or official carrier requests it.

Line-haul transport

The parcel moves by air, truck, or multimodal transport between countries or regions.

View all details for line-haul transport

Physical custodian/responsible entity	Airline, line-haul contractor, freight consolidator, or postal dispatch network.
Typical tracking event	Departed export facility, in transit, airline departure, or no event until destination arrival.
Can the tracking number change?	The customer-facing number usually remains linked, but partner identifiers may appear later.
Normal visibility gap	Common during flight, transit, and data exchange.
What the customer should do	Avoid opening duplicate claims solely because no scan appears during line-haul.

Import customs and destination exchange

The shipment is processed for import, duty and tax assessment, inspection, or release to the delivery network.

View all details for import customs and destination exchange

Physical custodian/responsible entity	Destination customs, postal exchange office, broker, or receiving carrier.
Typical tracking event	Arrived in destination country, customs clearance, released from customs, or arrived at sorting center.
Can the tracking number change?	Yes, the destination carrier may assign or expose a local number.
Normal visibility gap	Can occur while customs and carrier systems exchange data.
What the customer should do	Pay duties only through official carrier or customs channels and keep payment proof.

Last-mile delivery or pickup

The destination carrier attempts delivery, redirects to pickup, records delivery, or starts a return.

View all details for last-mile delivery or pickup

Physical custodian/responsible entity	Destination postal operator, parcel carrier, courier, locker network, or pickup point.
Typical tracking event	Out for delivery, available for pickup, delivery attempted, delivered, or return to sender.
Can the tracking number change?	A local number may be the best identifier for redelivery or pickup.
Normal visibility gap	Usually shorter, but local scans depend on the carrier.
What the customer should do	Use the local carrier for delivery instructions and DHgate seller support for order issues.

Delivery Management and Post-shipment Options

For DHLink parcels, post-shipment control usually depends on who currently holds the parcel. Sellers can often request shipment corrections earlier in the chain; recipients usually manage delivery only after the destination carrier has accepted the parcel.

Delivery Management

Option

Who can request

Address correction before export

Seller or shipper through the marketplace or logistics order channel.

View all details for address correction before export

Eligibility	Only if the parcel has not passed the stage where labels, customs data, or partner handoff are locked.
Deadline/available stage	Before export handoff or partner acceptance where change is still operationally possible.
Fee	Not publicly confirmed as a universal DHLink fee.
Guaranteed?	No; changes depend on shipment stage and carrier rules.
Official action link	Use the DHgate order or seller support channel associated with the shipment.

Redelivery or pickup

Recipient through the destination carrier after failed delivery or pickup notice.

View all details for redelivery or pickup

Eligibility	Requires destination carrier acceptance and a local delivery or pickup event.
Deadline/available stage	During the local carrier's storage or redelivery period.
Fee	Depends on the destination carrier and service.
Guaranteed?	No; local carrier rules control delivery management.
Official action link	Use the destination carrier tracking page shown in the tracking events.

Proof of delivery request

Recipient, seller, or shipper depending on the destination carrier and service.

View all details for proof of delivery request

Eligibility	Only if the last-mile carrier captured delivery evidence such as signature, photo, location, or pickup confirmation.
Deadline/available stage	After a delivered scan.
Fee	Depends on the destination carrier.
Guaranteed?	Evidence availability depends on the service and carrier.
Official action link	Use the local carrier or seller support route.

Lost, Damaged, Claims, Insurance and Refunds

A DHLink tracking inquiry, a destination-carrier investigation, a carrier insurance claim, and a marketplace refund are different processes. Buyers should preserve evidence and follow the DHgate order-resolution timeline, while sellers should check the logistics contract and selected service terms.

Claims and Refunds

Process

Use when

Tracking inquiry

Use when tracking is stalled, contradictory, or missing a handoff event.

View all details for tracking inquiry

Who files	Seller or buyer, depending on the support channel.
Earliest/latest filing time	Use the marketplace or carrier-specific inquiry window; no universal DHLink deadline is publicly confirmed.
Required evidence	Tracking number, order ID, seller dispatch date, latest scan, full address, and screenshots.
Possible outcome	Updated scan, partner check, request to wait, return confirmation, or escalation to seller dispute.
Official link	Use the DHgate order support route and the relevant carrier tracking page.

Marketplace refund or reshipment request

Use when the item is not received, significantly delayed, returned, damaged, or materially different from the order.

View all details for marketplace refund or reshipment

Who files	Buyer through the order-resolution channel; seller responds with shipment evidence.
Earliest/latest filing time	Follow the current protection period shown in the order; do not rely on generic third-party deadlines.
Required evidence	Tracking history, photos of damage, product photos, invoice, communication with seller, and delivery proof if available.
Possible outcome	Refund, partial refund, reshipment, denial, or request for more evidence.
Official link	Use the DHgate order page and help center.

Carrier damage or loss claim

Use when the physical carrier's rules allow a shipper, recipient, or account holder to file for loss or damage.

View all details for carrier damage or loss claim

Who files	Usually the shipper or account holder; recipient eligibility depends on the destination carrier.
Earliest/latest filing time	Carrier-specific and service-specific; verify on the current carrier claim page.
Required evidence	Tracking number, value proof, invoice, photos, packaging, contents, repair estimate, and written carrier notice.
Possible outcome	Investigation, compensation, claim denial, or request for additional documents.
Official link	Use the partner carrier claim page or seller logistics support.

Shipping Restrictions and Special Handling

DHLink restrictions depend on export rules, airline safety rules, destination import law, marketplace product policy, and partner-carrier acceptance rules. The summary below is not a complete legal or shipping manual.

Shipping Restrictions

Customer Service

For DHLink shipments, the fastest support path is usually: check tracking, contact the seller through the order page, contact DHgate order support if the seller cannot resolve it, and contact the destination carrier only after it has physically accepted the parcel.

Customer Service

Channel

Verified contact/link

DHLink official website

https://www.dhlink.com

View all customer-service details for DHLink official website

Best for	Official DHLink entry, tracking lookup, and current platform information.
Region/language	Cross-border ecommerce users; available languages depend on the website interface.
Hours and time zone	Not publicly confirmed as a universal recipient-facing service hour.
Information to prepare	Tracking number, order number, seller name, destination country, latest scan, and screenshots.
Important limitation	The website may not replace marketplace order support or destination-carrier delivery support.

DHgate order support

https://www.dhgate.com

View all customer-service details for DHgate order support

Best for	Buyer protection, refund requests, seller communication, and order-level disputes.
Region/language	DHgate account users; language options depend on the marketplace interface.
Hours and time zone	Use current DHgate help-center information; no single phone-hour claim is made here.
Information to prepare	Order ID, tracking number, payment record, communication history, photos, and delivery issue details.
Important limitation	Marketplace support can handle order resolution but may need carrier evidence for delivery disputes.

Destination carrier

Use the official tracking page of the carrier named in the latest local-delivery event.

View all customer-service details for destination carrier

Best for	Redelivery, pickup, delivery proof, local address issue, duty payment, and delivered-not-received investigation.
Region/language	Destination country and local carrier language.
Hours and time zone	Carrier-specific; verify on the current official contact page.
Information to prepare	Local tracking number, full delivery address, recipient phone, delivery notice, ID, and latest scan.
Important limitation	The destination carrier usually cannot issue a marketplace refund or change seller shipment terms.

17TRACK

https://www.17track.net

View all customer-service details for 17TRACK

Best for	Multi-carrier tracking visibility, automatic carrier detection, and checking partner handoff events.
Region/language	Global tracking users.
Hours and time zone	Tracking platform availability varies; 17TRACK is not the physical carrier.
Information to prepare	Tracking number and any known carrier name.
Important limitation	17TRACK cannot transport, intercept, redeliver, refund, or approve claims for DHLink parcels.

Ecommerce and Business Tracking

Businesses should separate consumer tracking, DHLink shipment-management access, partner-carrier APIs, and 17TRACK multi-carrier API tracking. DHLink-specific API endpoint details are not publicly confirmed for general open developer use on the recipient-facing website.

Developer/API Comparison

Option

Provider

Consumer tracking page

DHLink

View API comparison details for consumer tracking page

Carrier coverage	DHLink shipments and route events available to the official system.
Primary use	Single-shipment lookup by buyer or seller.
Authentication	Public or account-based use depends on the website flow.
Tracking/batch/webhook capability	Public batch or webhook capability is not confirmed.
Current developer documentation	No current open public DHLink tracking API documentation is confirmed here.
Migration/deprecation note	Do not integrate against undocumented endpoints.

Seller shipment tools

DHgate or DHLink account tools

View API comparison details for seller shipment tools

Carrier coverage	Services and lanes enabled for the seller account.
Primary use	Shipment creation, logistics selection, labels, order fulfillment, and support.
Authentication	Seller account authentication.
Tracking/batch/webhook capability	Account tools may support bulk shipment management; public webhook documentation is not confirmed.
Current developer documentation	Use current merchant documentation available inside official seller systems.
Migration/deprecation note	Account-specific tools can change; verify inside the current seller center.

Partner-carrier APIs

Destination postal or commercial carriers

View API comparison details for partner-carrier APIs

Carrier coverage	Only the carrier's own network and services.
Primary use	Delivery proof, local scans, redelivery, claims, and operational tracking after handoff.
Authentication	Carrier developer account or business contract.
Tracking/batch/webhook capability	Carrier-specific and usually limited to shipments tendered to that carrier.
Current developer documentation	Use the current official carrier developer portal.
Migration/deprecation note	Carrier APIs often migrate; verify before production integration.

17TRACK Tracking API

17TRACK

View API comparison details for 17TRACK Tracking API

Carrier coverage	Multi-carrier tracking coverage including many postal, express, and logistics providers.
Primary use	Bulk tracking, carrier auto-detection, standardized tracking visibility, exception monitoring, and customer notifications.
Authentication	17token API key.
Tracking/batch/webhook capability	Register tracking numbers through the Tracking API; additional capabilities depend on the 17TRACK API plan and documentation.
Current developer documentation	https://api.17track.net/en/doc
Migration/deprecation note	Use the current v2.4 documentation for new integrations.

FAQ

1. How do I track my DHLink package?

Enter the tracking number on the official DHLink website or track it with 17TRACK to view available shipment events and possible partner-carrier handoffs.

2. Where can I find my DHLink tracking number?

Look in your DHgate order details, seller shipping message, dispatch email, or parcel label; do not confuse the order ID with the logistics tracking number.

3. What does a DHLink tracking number look like?

DHLink shipments may show a DHLink logistics identifier, a postal S10 number such as LX#########CN, or a destination-carrier number, so service cannot be identified from the prefix alone.

4. When will the first DHLink tracking update appear?

The first meaningful update usually appears after physical acceptance by a warehouse, first-mile carrier, or partner facility, not necessarily when the seller creates the label.

5. Why is my DHLink tracking not updating?

DHLink tracking may pause during seller handover, consolidation, export transport, customs, or partner data exchange; check whether a destination-carrier number has appeared.

6. How long does DHLink delivery take?

DHLink delivery time varies by route, service, customs, and last-mile carrier; use the shipment-specific estimate in the order page or partner-carrier tracking result.

7. What should I do after a DHLink delivery failed?

Use the destination carrier's notice or local tracking page for redelivery or pickup, and notify the seller if the tracking shows a return risk.

8. What if DHLink tracking says delivered but I did not receive the package?

Check mailbox, parcel locker, porch, reception, household members, neighbors, delivery photo, and the local carrier before opening a seller or marketplace dispute.

9. What should I do if a DHLink package is lost or damaged?

Save tracking screenshots, photos, packaging, value proof, and seller messages, then follow the DHgate order-resolution route and any applicable partner-carrier claim process.

10. How do I contact DHLink about tracking?

Start with the official DHLink website and the DHgate order page; contact the destination carrier only after its tracking shows physical acceptance or a local delivery event.

11. Does DHLink physically deliver every parcel?

No, DHLink can organize the logistics route while origin handlers, postal operators, airlines, customs-related facilities, and destination carriers perform many physical scans.

12. Why does my DHLink parcel show a postal number ending in CN?

A postal S10 number ending in CN is usually associated with a China-origin postal channel, and DHLink or 17TRACK may display it even when the postal operator issued the identifier.

13. Can the DHLink tracking number change after handoff?

Yes, a destination last-mile carrier may assign or reveal a local number after import, while the original DHLink or postal number may remain linked for order evidence.

14. What does customs clearance mean for DHLink shipments?

Customs clearance means export or import authorities, brokers, or carriers are reviewing shipment data or the parcel; destination arrival does not automatically mean customs release.

15. Who can change the address on a DHLink shipment?

Before export, the seller or shipper may have the best chance to request correction; after destination acceptance, the local carrier controls any redelivery or pickup options.

16. Can businesses track DHLink shipments through an API?

A current open public DHLink tracking API is not confirmed here; businesses can use seller tools where eligible or the 17TRACK Tracking API for multi-carrier tracking.

17. Can 17TRACK refund or intercept a DHLink package?

No, 17TRACK is an independent tracking platform and cannot refund, intercept, change delivery, or approve claims for DHLink shipments.

Tracking API

// 1. DHLink official tracking API
// Current public official DHLink tracking API not confirmed.
// Do not copy undocumented browser endpoints into production integrations.
// Use official DHLink or DHgate seller documentation if your merchant account provides API access.

// 2. 17TRACK Tracking API
// Documentation: https://api.17track.net/en/doc
// CARRIER_CODE for DHLink should be confirmed in your current 17TRACK carrier list.
// If you cannot confirm the current carrier code, keep CARRIER_CODE as a placeholder.

POST https://api.17track.net/track/v2.4/register
Headers:
  17token: YourKey
  Content-Type: application/json

Body:
[
  {
    "number": "TRACKING_NUMBER",
    "carrier": "CARRIER_CODE"
  }
]