Cainiao HK provides an account-gated order-status search portal. The supplied official tracking address redirects users to a unified sign-in page, so access to order-level information may require an authorized account. The public portal should be treated as a tracking interface rather than proof that Cainiao HK physically handled every transport stage shown in an order record.
Cainiao HK Overview
| Field | Verified information |
| Official name | Cainiao HK |
| Official website | https://pbc.cainiao.com/orderStatusSearch/ |
| Portal type | Authenticated order-status search |
| Tracking access | The official address can redirect to a unified account login before order information is displayed. |
| Independent tracking option | 17TRACK can aggregate available carrier events when a supported shipment identifier is entered. |
Carrier Entity Relationships
| Entity | Entity type |
| Cainiao HK | Canonical carrier page entity |
View all details for Cainiao HK
| Relationship to Cainiao HK | Cainiao HK is the fixed display name used for the tracking entity described on this page. |
| Why it matters to tracking | Users should match the shipment identifier and order record rather than infer physical custody from the display name alone. |
| Official evidence | The supplied official order-status address routes to an authenticated tracking workflow. |
|
| Official order-status portal | Tracking product |
View all details for the official order-status portal
| Relationship to Cainiao HK | The portal is the supplied official entry point for authenticated order-status searches. |
| Why it matters to tracking | Account access may be required before shipment records or internal references can be viewed. |
| Official evidence | The tracking URL redirects to a unified sign-in page. |
|
| Transport and last-mile operators | Physical-custody entities |
View all details for transport and last-mile operators
| Relationship to Cainiao HK | An order record can contain events generated during collection, line-haul, customs, handoff, or final delivery. |
| Why it matters to tracking | The entity named in the latest physical scan is usually more relevant to current custody than an earlier electronic-data event. |
| Official evidence | Use the event text and any carrier identifier displayed in the authenticated order record. |
|
| 17TRACK | Independent tracking platform |
View all details for 17TRACK
| Relationship to Cainiao HK | 17TRACK aggregates available shipment events and is independent from Cainiao HK. |
| Why it matters to tracking | It offers a second tracking path but cannot transport parcels, change addresses, release customs items, or approve claims. |
| Official evidence | 17TRACK documents its multi-carrier tracking API separately from the Cainiao HK portal. |
|
Quick Answer
To track a Cainiao HK shipment, enter the shipment tracking number in 17TRACK or open the official Cainiao HK order-status portal and sign in if requested. If no result appears, first remove spaces, verify every character, confirm that the value is a shipment number rather than an order number, and allow time for the first physical acceptance scan.
Pro Tip: 17TRACK is an independent tracking platform. It can display available tracking events, but it cannot change delivery instructions, correct an address, clear customs, issue a refund, or approve a loss claim.
How to Track Cainiao HK Packages
Use the official authenticated portal for order-linked records or 17TRACK for independent multi-carrier event aggregation.
- Copy the shipment tracking number from the dispatch email, order page, shipping label, receipt, or merchant message.
- For the official route, open the Cainiao HK order-status portal and complete the account sign-in process when prompted.
- For the 17TRACK route, paste the number into 17TRACK and use automatic carrier detection when available.
- Read the most recent physical scan, location, event time, and any handoff information before deciding who currently holds the parcel.
- If the result is empty, verify the identifier with the sender and retry after the shipment has been physically accepted.
Which Identifier Should You Use?
| Identifier | How to use it |
| Shipment tracking number | Use this first in Cainiao HK tracking or 17TRACK. It is normally attached to the shipment label or dispatch record. |
| Merchant order number | Use it inside the merchant account to locate the order; it may not work in a carrier tracking field. |
| Reference number | Use it only when the relevant portal explicitly supports reference searches. |
| Last-mile number | Use it after a handoff when the order record identifies a separate final-delivery number. |
| Delivery notice number | Use it with the delivery operator named on the notice for pickup or redelivery instructions. |
Tracking Statuses and Meanings
Read Cainiao HK events as a lifecycle. Electronic data creation is different from physical acceptance, arrival at a customs facility is different from customs release, and a delivery-partner notice is different from a confirmed handoff scan.
Status Quick Lookup
| Status | Lifecycle stage |
| Shipment information received | Pre-shipment |
View all details for shipment information received
| What it means | A label or electronic shipment record exists, but physical acceptance is not established by this event alone. |
| Current responsible party | The sender or collection party remains responsible until a physical receipt scan appears. |
| What happens next | Collection, drop-off, or an acceptance scan. |
| What you should do | Confirm dispatch with the sender if the status remains unchanged beyond the promised handling period. |
|
| Accepted or collected | Accepted |
View all details for accepted or collected
| What it means | A physical scan indicates that a transport participant received the shipment. |
| Current responsible party | The operator named in the acceptance event. |
| What happens next | Origin sorting and dispatch. |
| What you should do | Monitor the next processing scan; no action is usually needed. |
|
| Departed facility or in transit | In transit |
View all details for in transit
| What it means | The shipment is moving between processing points or awaiting the next scheduled scan. |
| Current responsible party | The transport operator identified in the latest physical event. |
| What happens next | Arrival, sorting, export processing, or a handoff event. |
| What you should do | Compare the last scan with the order-level delivery window before escalating. |
|
| Customs processing | Customs and handoff |
View all details for customs processing
| What it means | The shipment is undergoing import or export formalities; arrival does not mean release. |
| Current responsible party | The customs authority, declarant, broker, or facility operator controls the next action according to the event. |
| What happens next | Release, a request for information or payment, inspection, or return action. |
| What you should do | Respond only through the verified channel named in the order or customs notice. |
|
| Handover pending | Customs and handoff |
View all details for handover pending
| What it means | Electronic information may have been sent to the next operator, but the receiving operator may not have scanned the physical parcel. |
| Current responsible party | The dispatching party remains the clearest custody contact until the receiving scan appears. |
| What happens next | A physical receipt scan by the next operator. |
| What you should do | Check for a linked last-mile number and wait for the first destination scan. |
|
| Out for delivery | Out for delivery |
View all details for out for delivery
| What it means | The final-delivery operator has assigned the shipment to a delivery route. |
| Current responsible party | The operator named in the destination delivery event. |
| What happens next | Delivery, an attempted delivery, or transfer to a pickup point. |
| What you should do | Keep the delivery location accessible and follow only verified delivery instructions. |
|
| Delivered | Delivered |
View all details for delivered
| What it means | A delivery completion scan was recorded at the stated location or recipient point. |
| Current responsible party | The final-delivery operator holds delivery-scan details; the merchant handles purchase-resolution requests. |
| What happens next | No further movement is expected unless the scan is corrected or the parcel is returned. |
| What you should do | Check the delivery location, household, reception, secure areas, and any delivery evidence before reporting non-receipt. |
|
| Ready for pickup | Pickup |
View all details for ready for pickup
| What it means | The parcel is being held at the location identified in the delivery notice or tracking event. |
| Current responsible party | The named pickup-location operator. |
| What happens next | Collection after identity or notice checks, or return after the applicable holding period. |
| What you should do | Follow the notice and bring the requested identification or authorization. |
|
| Delivery exception | Exception |
View all details for delivery exception
| What it means | A delivery, routing, address, access, weather, or compliance issue prevented normal progress. |
| Current responsible party | The operator named in the exception event, unless recipient information is requested. |
| What happens next | Retry, correction, pickup, investigation, or return. |
| What you should do | Read the event details and contact the named operator or sender when action is requested. |
|
| Returning to sender | Return |
View all details for returning to sender
| What it means | The parcel has entered a reverse movement because delivery could not be completed or the shipment could not continue. |
| Current responsible party | The operator moving the return, while the sender controls replacement or refund decisions. |
| What happens next | Return transport and sender receipt. |
| What you should do | Contact the seller promptly; address changes may no longer be possible after return processing begins. |
|
Services and Delivery Times
Cainiao HK delivery expectations should be read from the booked order and its service promise. The order-status portal does not establish one universal delivery standard for every route, transport operator, customs process, or last-mile network.
Service Comparison
| Service | Service type |
| Order-linked shipment tracking | Authenticated tracking workflow |
View all details for order-linked shipment tracking
| Best for | Users with authorized access to the order record. |
| Coverage | Events linked to the shipment record and participating transport stages. |
| Tracking level | Depends on scans received from the entities handling the order. |
| Key size/weight condition | Use the conditions attached to the booked shipping product. |
| Included protection/extra service | Use the purchase, shipping, or insurance terms attached to the order. |
| Main limitation | Portal access may require sign-in, and tracking visibility does not prove one entity held the parcel throughout the journey. |
|
| Multi-stage cross-border shipment | Collection, line-haul, customs, handoff, and destination delivery |
View all details for multi-stage cross-border shipments
| Best for | International ecommerce orders where several parties can create tracking events. |
| Coverage | Route-specific origin and destination coverage. |
| Tracking level | Electronic and physical events may appear at different intervals. |
| Key size/weight condition | The booked product and destination rules govern eligibility. |
| Included protection/extra service | Determined by the shipping contract or purchase protection terms. |
| Main limitation | Customs and partner handoffs can create visibility gaps and separate tracking identifiers. |
|
Delivery Time
| Service | Published delivery standard |
| Order-linked shipment | Use the delivery promise or estimated window attached to the individual order. |
View all delivery-time details for order-linked shipments
| Business or calendar days | Follow the wording used in the order promise; do not convert between business and calendar days without supporting terms. |
| Guarantee status | An estimated date or window should not be treated as a delivery guarantee. |
| Starts counting from | Use the starting event specified by the booked product, which may differ from label creation. |
| Main delay factors | Sender handling, collection, missed scans, weekends, holidays, capacity, weather, address quality, customs, and partner handoff. |
| Official source date/validity | The current order record and applicable shipping terms control the shipment-specific estimate. |
|
Destination Country Delivery Times
| Destination Country / Region | Estimated Delivery Time Range |
| Destination shown in the booked order | Use the route-specific window displayed for the purchase rather than a universal country estimate. |
View all destination timing details
| Primary Service Type | The shipping product selected for the order. |
| Average Delivery Days | Assess progress against the order-level estimate and actual scans; a cross-route average is not a shipment commitment. |
| Last-Mile Partner / Handoff Carrier | Use the destination operator identified in the tracking record after physical handoff. |
| Customs & Clearance Tips | Ensure recipient contact details are accurate, watch for verified information or tax requests, and do not interpret arrival at an import facility as customs release. |
|
Delivery windows can move when the sender dispatches late, the parcel misses a scheduled connection, customs requests information, a handoff scan is delayed, or the destination address is incomplete. The latest estimated date is still an estimate unless the booked terms explicitly describe a guarantee.
Common Tracking Problems and Solutions
Start with the latest physical event, identify the party named in that event, and compare progress with the order promise. The sender is usually best placed to correct dispatch records or start a contractual investigation, while the destination operator handles active delivery and pickup events.
Problem & Solution
| Problem/status shown | Likely cause |
| Invalid number or no result | Typing error, order number entered instead of a shipment number, carrier mismatch, or data not yet activated. |
View actions for an invalid number or no result
| Check first | Compare every character with the dispatch record and remove accidental spaces. |
| Immediate action | Retry in the official portal and 17TRACK, then ask the sender to identify the shipment number. |
| When to escalate | Escalate when the sender's handling promise has passed without a valid shipment record. |
| Who to contact | The merchant or sender. |
|
| Shipment information received | Electronic data exists, but physical tender or acceptance has not been recorded. |
View actions for shipment information received
| Check first | The purchase handling time and dispatch confirmation. |
| Immediate action | Ask whether the parcel was physically collected or dropped off. |
| When to escalate | When the promised handling period expires without acceptance. |
| Who to contact | The sender or merchant. |
|
| Long period without an update | Movement between scan points, consolidation, missed scan, customs processing, or data-transfer delay. |
View actions for a long period without an update
| Check first | The last physical location, order delivery window, and any linked tracking number. |
| Immediate action | Track both the original and last-mile identifiers if both appear. |
| When to escalate | When the order window has passed or an event explicitly requests action. |
| Who to contact | The sender for an investigation; use the named destination operator for active local-delivery events. |
|
| Handoff pending | The receiving operator has electronic data but may not have the physical parcel. |
View actions for a pending handoff
| Check first | Whether a first receiving scan exists. |
| Immediate action | Monitor the dispatching identifier and any destination identifier. |
| When to escalate | When the expected delivery window passes without a receiving scan. |
| Who to contact | The sender or the party responsible before physical handoff. |
|
| Customs delay or hold | Inspection, declaration review, missing information, tax assessment, restricted goods, or processing backlog. |
View actions for a customs delay or hold
| Check first | The event text and any verified request for documents or payment. |
| Immediate action | Prepare the order invoice, product description, recipient details, and payment evidence if requested. |
| When to escalate | When an official request has a response deadline or the shipment exceeds the order window. |
| Who to contact | The declarant, broker, sender, or customs channel identified in the verified notice. |
|
| Delivery exception or address issue | Incomplete address, inaccessible location, route issue, recipient absence, or local operational disruption. |
View actions for a delivery exception or address issue
| Check first | The address on the order and the delivery notice. |
| Immediate action | Follow the destination operator's verified redelivery or pickup instructions. |
| When to escalate | Before the stated pickup or return deadline. |
| Who to contact | The destination delivery operator and the sender if the address itself is wrong. |
|
| Delivered but not received | Safe-place delivery, reception or household acceptance, neighbor delivery, premature scan, or incorrect delivery location. |
View actions for delivered but not received
| Check first | Door, mailbox, parcel area, reception, household members, neighbors, and any delivery evidence. |
| Immediate action | Ask the destination operator to check the delivery scan and location, then notify the merchant. |
| When to escalate | Promptly after location checks fail, following the purchase and delivery dispute terms. |
| Who to contact | The destination operator for scan evidence and the merchant for order resolution. |
|
| Lost or damaged | Unresolved movement interruption, damaged packaging, missing contents, or delivery failure. |
View actions for a lost or damaged shipment
| Check first | Purchase protection, shipping terms, latest event, parcel condition, and item count. |
| Immediate action | Keep the parcel, contents, label, and packaging; photograph all sides and the damage. |
| When to escalate | Within the applicable merchant, transport, insurance, or payment dispute window. |
| Who to contact | The merchant or contractual sender, who can identify the appropriate investigation or claim route. |
|
| Returning to sender | Failed delivery, unclaimed pickup, address problem, customs refusal, or shipping restriction. |
View actions for a return to sender
| Check first | The stated return reason and whether return movement has begun. |
| Immediate action | Contact the merchant about replacement, refund, or a corrected reshipment. |
| When to escalate | As soon as return processing appears, because destination changes may no longer be accepted. |
| Who to contact | The merchant or sender. |
|
International Shipping, Customs and Carrier Handoffs
A cross-border Cainiao HK order can involve separate collection, export, line-haul, import, and final-delivery entities. Electronic pre-advice, physical handoff, customs release, and final-mile acceptance are distinct events.
International Flow
| Stage | Physical custodian/responsible entity |
| Shipment data created | Sender or label-issuing system |
View details for shipment data creation
| Typical tracking event | Shipment information received. |
| What is happening | Electronic data exists before physical acceptance. |
| Can the tracking number change? | A later transport or delivery identifier may be linked. |
| Normal visibility gap | No physical events appear until collection or drop-off. |
| What the customer should do | Wait through the sender's stated handling period. |
|
| Origin acceptance and sorting | Origin collection or processing operator |
View details for origin acceptance and sorting
| Typical tracking event | Accepted, collected, or processed at origin facility. |
| What is happening | The shipment is physically received and prepared for dispatch. |
| Can the tracking number change? | The original identifier usually remains, but a consolidation reference may also appear. |
| Normal visibility gap | Time between origin processing scans. |
| What the customer should do | Monitor progress against the order window. |
|
| Export processing and security | Export facility, declarant, security authority, or customs authority |
View details for export processing
| Typical tracking event | Export clearance, departure preparation, or security processing. |
| What is happening | Documentation and transport eligibility are checked before international departure. |
| Can the tracking number change? | A line-haul or consolidated reference may supplement the shipment number. |
| Normal visibility gap | Processing and departure may not generate customer-facing scans at every step. |
| What the customer should do | Respond through verified channels if documentation is requested. |
|
| International line-haul | Contracted air, road, or other line-haul operator |
View details for international line-haul
| Typical tracking event | Departed origin, line-haul departure, or transport in progress. |
| What is happening | The shipment moves between origin and destination gateways. |
| Can the tracking number change? | The consumer identifier may remain while internal transport references change. |
| Normal visibility gap | No customer scan may appear between departure and destination processing. |
| What the customer should do | Wait for destination arrival unless the order window has passed. |
|
| Import arrival and customs | Destination facility, declarant, broker, or customs authority |
View details for import arrival and customs
| Typical tracking event | Arrived at destination facility, import processing, or customs review. |
| What is happening | The shipment is presented for destination processing; arrival is not proof of customs release. |
| Can the tracking number change? | A destination identifier may be assigned or linked. |
| Normal visibility gap | Inspection and data review can occur without intermediate public scans. |
| What the customer should do | Watch for verified information or payment requests and avoid unverified links. |
|
| Partner pre-advice | Dispatching party until physical receipt is scanned |
View details for partner pre-advice
| Typical tracking event | Information sent to delivery partner or handoff pending. |
| What is happening | The next operator has data but may not yet possess the physical shipment. |
| Can the tracking number change? | A last-mile number may appear before physical receipt. |
| Normal visibility gap | The gap lasts until the receiving operator performs its first physical scan. |
| What the customer should do | Track both identifiers and avoid treating pre-advice as completed handoff. |
|
| Destination handoff and last mile | Destination operator after its physical acceptance scan |
View details for destination handoff and last mile
| Typical tracking event | Received by destination operator, processed locally, or out for delivery. |
| What is happening | Local sorting and final delivery are underway. |
| Can the tracking number change? | The destination operator may use a linked local identifier. |
| Normal visibility gap | Data synchronization can make one tracking page update before another. |
| What the customer should do | Use the destination identifier for delivery attempts, pickup, and delivery evidence. |
|
Delivery Management and Post-shipment Options
Delivery-management options depend on the operator currently holding the shipment. Check the latest physical scan and use only the action channel identified in the order record or delivery notice.
Delivery Management
| Option | Who can request |
| Address correction | Usually the sender before dispatch; destination options depend on the current operator. |
View address-correction details
| Eligibility | Depends on shipment stage, security rules, and the booked product. |
| Deadline/available stage | Request correction as soon as the error is discovered and before delivery or return processing. |
| Fee | Any fee is determined by the applicable operator or merchant terms. |
| Guaranteed? | No; operational and security controls can prevent changes. |
| Official action link | Use the authenticated order record or the verified channel named in the latest event. |
|
| Redelivery or pickup | The recipient identified for the shipment, subject to destination-operator rules. |
View redelivery or pickup details
| Eligibility | A failed-delivery or ready-for-pickup event must offer the option. |
| Deadline/available stage | Follow the deadline in the delivery notice before return processing begins. |
| Fee | Use the destination operator's terms. |
| Guaranteed? | No; availability depends on the local delivery product and parcel status. |
| Official action link | Use the verified destination-operator link displayed in tracking or on the physical notice. |
|
| Proof of delivery inquiry | The sender or recipient according to the final-delivery operator's rules. |
View proof-of-delivery inquiry details
| Eligibility | A delivery completion scan exists. |
| Deadline/available stage | Request promptly when the parcel cannot be located. |
| Fee | Depends on the final-delivery product and operator policy. |
| Guaranteed? | Availability of signatures, images, or coordinates depends on the booked delivery service. |
| Official action link | Use the final-delivery operator identified by the delivery event. |
|
Lost, Damaged, Claims, Insurance and Refunds
A tracking inquiry, transport investigation, insurance claim, postage adjustment, and merchant refund are separate processes. The purchase contract and booked shipping terms determine who files and which evidence is required.
Claims and Refunds
| Process | Use when |
| Tracking inquiry | Events are unclear, delayed, or inconsistent. |
View tracking inquiry details
| Who files | The recipient can request clarification; the sender may have stronger contractual access to an investigation. |
| Earliest/latest filing time | Use the order window and applicable shipping terms. |
| Required evidence | Tracking number, order number, dispatch date, addresses, and latest event. |
| Possible outcome | Event clarification, trace initiation, or referral to the current operator. |
| Official link | Use the authenticated Cainiao HK order record. |
|
| Loss or damage claim | The shipment is declared lost, arrives damaged, or has missing contents. |
View loss or damage claim details
| Who files | The contractual sender, merchant, or insured party according to the booked terms. |
| Earliest/latest filing time | Follow the deadline in the purchase, shipping, or insurance terms. |
| Required evidence | Tracking record, value proof, item description, photos, label, packaging, and damage evidence. |
| Possible outcome | Investigation, evidence request, settlement under applicable cover, or denial. |
| Official link | Start with the merchant or sender responsible for the shipping contract. |
|
| Merchant refund or replacement | The purchased goods were not received, arrived damaged, or differ from the order. |
View merchant refund or replacement details
| Who files | The buyer submits the request through the purchase channel. |
| Earliest/latest filing time | Follow the order's buyer-protection or returns deadline. |
| Required evidence | Order record, tracking events, photos, delivery evidence, and communications. |
| Possible outcome | Refund, replacement, return instruction, further review, or denial under the purchase terms. |
| Official link | Use the merchant account or original purchase channel. |
|
17TRACK cannot approve a claim, issue a merchant refund, change an insurance decision, or alter the transport outcome.
Shipping Restrictions and Special Handling
Restrictions depend on the booked transport product, route, destination law, security screening, and customs requirements. The sender must verify eligibility before dispatch rather than relying on tracking acceptance as proof that an item is permitted.
Shipping Restrictions
| Category | Prohibited or restricted |
| Dangerous or hazardous goods | Restricted or prohibited according to the booked mode and route. |
View hazardous-goods details
| Typical examples | Flammable, explosive, corrosive, pressurized, toxic, or otherwise regulated materials. |
| Key condition/packaging | Classification, documentation, quantity limits, marks, and approved packaging may apply. |
| Transport limitation | Air, road, and destination restrictions can differ. |
| Possible tracking/delivery impact | Security hold, rejection, return, disposal, or regulatory referral. |
| Official rules | Use the terms for the exact booked shipping product and destination. |
|
| Batteries and powered devices | Restricted according to battery type, configuration, quantity, condition, and transport mode. |
View battery-shipment details
| Typical examples | Loose batteries, batteries packed with equipment, and battery-powered electronics. |
| Key condition/packaging | Terminal protection, damage prevention, approved packaging, and declarations may apply. |
| Transport limitation | Air transport commonly imposes additional controls. |
| Possible tracking/delivery impact | Screening delay, route change, rejection, or return. |
| Official rules | Verify the product-specific acceptance rules before shipment. |
|
| Liquids, perishables, and temperature-sensitive goods | Restricted according to leakage risk, shelf life, packaging, and destination controls. |
View liquid and perishable shipment details
| Typical examples | Cosmetics, food, biological material, and goods requiring controlled temperature. |
| Key condition/packaging | Leakproof containment, cushioning, labeling, and route-appropriate packaging may be required. |
| Transport limitation | Transit duration and customs inspection can make some products unsuitable. |
| Possible tracking/delivery impact | Inspection, leakage handling, spoilage, refusal, or return. |
| Official rules | Check the exact service, origin, and destination requirements. |
|
| Controlled, high-value, or legally regulated goods | Restricted or prohibited according to law, declaration rules, and service terms. |
View controlled-goods details
| Typical examples | Goods requiring permits, age controls, export authorization, or special valuation procedures. |
| Key condition/packaging | Accurate declaration, supporting documents, secure packaging, and permitted service selection. |
| Transport limitation | Origin, transit, and destination laws all apply. |
| Possible tracking/delivery impact | Document request, customs hold, seizure, refusal, or return. |
| Official rules | Obtain product-specific compliance guidance before booking. |
|
Customer Service
For efficient support, begin with the authenticated order record, then contact the merchant for order resolution or the operator named in the latest physical scan for an active delivery issue.
Customer Service
| Channel | Verified contact/link |
| Official order-status portal | Cainiao HK order-status search |
View official portal support details
| Best for | Viewing authorized order-status information and shipment references. |
| Region/language | Use the language and account options presented by the portal. |
| Hours and time zone | Web access is subject to account availability and portal operation. |
| Information to prepare | Account credentials, order reference, shipment number, dispatch date, addresses, and latest event. |
| Important limitation | The address can redirect to sign-in before order records are displayed. |
|
| Merchant or sender support | Use the support channel attached to the original purchase or shipping contract. |
View merchant or sender support details
| Best for | Invalid tracking, dispatch proof, refunds, replacements, address errors, and contractual investigations. |
| Region/language | Determined by the purchase channel. |
| Hours and time zone | Follow the merchant's stated support schedule. |
| Information to prepare | Order number, payment proof, item details, tracking number, and supporting photos. |
| Important limitation | The merchant may need to communicate with the contracted shipping party on the buyer's behalf. |
|
| Destination delivery support | Use the verified operator and contact path named in the latest local-delivery event. |
View destination delivery support details
| Best for | Delivery attempts, pickup, local address clarification, and delivery-scan questions. |
| Region/language | Determined by the destination operator. |
| Hours and time zone | Follow the destination operator's local schedule. |
| Information to prepare | Last-mile number, recipient name, address, notice details, and latest scan. |
| Important limitation | An operator that has only received electronic pre-advice may be unable to act before physical handoff. |
|
Prepare the tracking number, order reference, dispatch date, sender and recipient addresses, booked service, latest scan, item description, declared value, invoice, packaging photos, and damage photos before escalating.
Ecommerce and Business Tracking
Businesses should separate consumer order lookup, authenticated Cainiao HK order-status access, and multi-carrier API tracking. A normalized platform can consolidate events, but operational actions still belong to the merchant and the party physically handling the shipment.
Developer/API Comparison
| Option | Provider |
| Authenticated order-status portal | Cainiao HK |
View developer details for the Cainiao HK portal
| Carrier coverage | Order records available to the authorized account. |
| Primary use | Interactive order-status lookup. |
| Authentication | Unified account sign-in is presented before access to the supplied tracking destination. |
| Tracking/batch/webhook capability | Use only capabilities presented inside the authorized account workflow. |
| Current developer documentation | The supplied evidence supports an authenticated portal rather than a public integration endpoint. |
| Migration/deprecation note | Do not reuse undocumented endpoints extracted from the web interface. |
|
| Multi-carrier tracking API | 17TRACK |
View developer details for the 17TRACK API
| Carrier coverage | Multi-carrier tracking through supported carrier integrations. |
| Primary use | Registration and monitoring of shipment identifiers across carrier workflows. |
| Authentication | API requests use the 17token header according to the documentation. |
| Tracking/batch/webhook capability | Use the current 17TRACK documentation for registration, quota, tracking, and notification features. |
| Current developer documentation | 17TRACK API documentation |
| Migration/deprecation note | Pin integrations to the documented API version and review change notices before deployment. |
|
Cainiao HK FAQ
1. How do I track my Cainiao HK package?Enter the shipment tracking number in 17TRACK or open the official Cainiao HK order-status portal and sign in when prompted. Use the latest physical scan to identify the shipment's current stage.
2. Where can I find my Cainiao HK tracking number?Look in the dispatch email, order details, shipping label, receipt, or merchant message. If only an order number appears, ask the sender for the shipment tracking number.
3. What does a Cainiao HK tracking number look like?The structure depends on the label-issuing party and shipment route. Use the exact alphanumeric value in the dispatch record and do not identify a service from the prefix alone.
4. When will the first Cainiao HK tracking event appear?The first physical event normally appears after collection, drop-off, or facility acceptance. Electronic shipment information can appear earlier and does not by itself prove physical receipt.
5. Why is my Cainiao HK tracking not updating?The parcel may be moving between scan points, consolidated for transport, undergoing customs processing, or waiting for a partner receiving scan. Check for a linked last-mile number and compare progress with the order window.
6. How long does Cainiao HK delivery take?Use the delivery estimate attached to the individual order because timing depends on the booked product, route, customs, and destination delivery process. An estimated date is not automatically a guarantee.
7. What should I do after a failed Cainiao HK delivery attempt?Read the latest event or delivery notice and follow the verified redelivery or pickup instructions from the destination operator. Act before any stated holding or return deadline.
8. What should I do if Cainiao HK says delivered but I have no package?Check the mailbox, door, parcel area, reception, household members, neighbors, and any delivery evidence first. Then ask the destination operator to review the scan and notify the merchant promptly.
9. How do I report a lost or damaged Cainiao HK shipment?Contact the merchant or contractual sender and preserve the item, label, contents, and all packaging. Provide tracking records, value proof, and clear photographs within the applicable purchase or shipping deadline.
10. How do I contact Cainiao HK about tracking?Start with the official Cainiao HK order-status portal and the support path attached to the order. For active local delivery, use the verified destination operator named in the latest physical scan.
11. Why does Cainiao HK show shipment information before physical acceptance?Electronic label data can be transmitted before the parcel is collected or dropped off. Physical custody is better established by an acceptance or facility-receipt scan.
12. Can a Cainiao HK shipment receive a second tracking number?Yes, a partner or destination operator can assign a linked identifier for another transport stage. Track both values when the original record shows a separate last-mile number.
13. Does arrival at a destination facility mean Cainiao HK customs clearance is complete?No, destination arrival and customs release are separate events. Wait for a release, clearance-completed, or onward-processing event and respond to verified document or payment requests.
14. Who is responsible during a Cainiao HK partner handoff?The dispatching party remains the clearest custody contact until the receiving operator records physical acceptance. Electronic pre-advice alone does not prove that the next operator has the parcel.
15. Can businesses track Cainiao HK shipments through an API?Businesses can use the documented 17TRACK multi-carrier API for supported shipment identifiers. The supplied Cainiao HK evidence describes an authenticated order-status portal, so developers should not build against undocumented web endpoints.
16. Can the Cainiao HK tracking prefix identify the exact service?No, the prefix alone is not a reliable service determination because identifier families can be issued by different transport participants or reused across workflows. Validate the complete number through the official portal or carrier detection.
Tracking API
Use the authenticated Cainiao HK portal for authorized order lookup. For a documented multi-carrier integration, consult the 17TRACK API documentation. Keep the carrier value as a placeholder until the current carrier code is verified for the intended integration.
# 1. Cainiao HK official tracking
# Use the authenticated order-status portal.
# No public integration endpoint is documented in the supplied official materials.
# Do not automate undocumented web-interface endpoints.
# 2. 17TRACK API: register a tracking number
curl --request POST \
--url https://api.17track.net/track/v2.4/register \
--header '17token: YourKey' \
--header 'Content-Type: application/json' \
--data '[
{
"number": "TRACKING_NUMBER",
"carrier": "CARRIER_CODE"
}
]'
# Replace TRACKING_NUMBER with the shipment identifier.
# Replace CARRIER_CODE only after verifying the current code in 17TRACK documentation.
Sources & References
17TRACK is an independent tracking platform and is not affiliated with Cainiao HK.