SDK Tracking
Please enter the SDK tracking number to check the latest shipping status.
About SDK
SDK is the public-facing brand used by 斯德克（深圳）国际物流有限公司, a China–Russia international logistics and overseas-warehouse provider. Its documented role covers collection in China, first-mile transport, customs-related logistics services, warehousing in Russia and last-mile delivery through local partners and marketplace channels.
| Fact | Confirmed information |
|---|---|
| Official name | 斯德克（深圳）国际物流有限公司 |
| Official website | https://www.sdk-express.cn/ |
| Carrier type | International logistics provider, overseas-warehouse operator and logistics coordinator. |
| Primary region | China–Russia trade and logistics; documented services also mention Belarus, Kazakhstan and a United States warehouse project. |
| Operating history stated by SDK | The About page describes a focus on Russia international logistics for 10 years and identifies 2018 registration of SDK（深圳）国际物流. |
| Headquarters | Longhua District, Shenzhen, Guangdong, China, at the address published on the official website. |
Carrier Entity Relationships
| Entity | Relationship to SDK |
|---|---|
| SDK | SDK coordinates China collection, China–Russia transport, Russian warehousing and downstream delivery services. |
| Russia overseas warehouse | The warehouse is an SDK-operated storage and fulfillment project; warehouse inventory and outbound actions are handled through its WMS environment. |
| CDEK | CDEK is identified on SDK pages as a last-mile delivery partner for all-region delivery in Russia, Belarus and Kazakhstan; a CDEK scan does not by itself prove that CDEK issued the original number. |
| OZ, WB and YD | SDK states that it connects warehouse dispatch with these Russian marketplace channels for FBO and FBS delivery. |
| 17TRACK | 17TRACK is an independent tracking platform that may aggregate available events; it does not operate SDK transport or decide claims. |
Quick Answer
Enter the shipment identifier supplied by the seller or SDK on the official SDK website or in the 17TRACK tracking tool. Start with the number rather than the marketplace order number. If no result appears, check spaces, copied characters, label activation and whether the shipment is still waiting for a physical handoff.
How to Track SDK Packages
The practical route is to obtain the shipment or warehouse dispatch identifier from the seller, then test it through the official SDK website or 17TRACK. SDK’s public pages describe logistics and warehouse systems, while the available tracking experience can depend on the service and partner handling the parcel.
| Step | Action |
|---|---|
| 1. Find the identifier | Check the dispatch notice, seller message, warehouse record or shipping label. An order number is not automatically a tracking number. |
| 2. Try official SDK channels | Use the tracking or logistics entry supplied by SDK on SDK’s official website, when the relevant service provides one. |
| 3. Try 17TRACK | Open 17TRACK, enter the identifier and allow carrier recognition to identify available SDK or downstream events. |
| 4. Resolve no result | Remove spaces only when the tracking interface requires it, compare every character, wait for label activation, and ask the shipper whether a partner-issued number or replacement last-mile number exists. |
Tracking Number Formats and Examples
SDK’s supplied public pages do not publish a complete universal tracking-number specification or official sample number. Do not infer a service solely from a prefix. A seller may provide an SDK shipment reference, a line-haul partner number, a warehouse order identifier or a last-mile number.
Tracking Number Format
| Identifier family | Normalized pattern or example |
|---|---|
| SDK shipment reference | Format not publicly specified; use the exact identifier supplied by the shipper. |
| Partner or last-mile identifier | Format depends on the partner, including CDEK or a marketplace delivery channel. A partner number may appear after handoff. |
| Warehouse or WMS reference | A warehouse, inventory or outbound reference may identify an operation without being a public parcel number. |
| International postal identifier | Use the actual postal or partner format if supplied; no S10 relationship is established by the supplied SDK pages. |
Tracking Statuses and Meanings
Tracking events describe the latest reported logistics action, not necessarily the physical location at every moment. Responsibility can move from SDK to a transport or last-mile partner.
Status Quick Lookup
| Status | What it means |
|---|---|
| Label created / awaiting item | Shipment data exists, but physical acceptance may not have occurred. Ask the shipper to confirm handoff. |
| Collected or accepted | A collection or receiving scan has been reported. SDK or its origin facility normally processes the next movement. |
| In transit | The shipment is moving through collection, sorting, line-haul or destination processing. |
| Customs or handoff | The parcel may be undergoing export/import processing or transfer to a partner; arrival at customs is not proof of release. |
| Out for delivery / delivered | A downstream delivery operator reports final delivery activity or a delivery scan. Check the delivery location and proof before disputing it. |
| Exception / returned | An address, customs, transport or delivery problem requires shipper or recipient action; the parcel may be redirected or returned. |
Services and Delivery Times
SDK’s official pages describe China–Russia road and rail logistics, a Russia warehouse, Russian last-mile delivery and a United States warehouse project. Published transit figures are route estimates, not universal guarantees.
Service Comparison
| Service | Best documented use |
|---|---|
| China–Russia road logistics | China collection, road line-haul, customs-related service and Russian fulfillment. |
| China–Russia rail logistics | Rail line-haul through western or eastern corridors to Russia. |
| Russia overseas warehouse | Storage, WMS inventory operations, labeling and outbound delivery. |
| Russia last mile | Delivery to pickup points, users or marketplace stations through stated local channels. |
| United States warehouse project | Warehouse fulfillment and selected Temu and TikTok logistics services. |
Delivery Time
| Route or service | Published estimate |
|---|---|
| China–Russia road transport | 25–30 days according to the official homepage; this is an estimate and can change with customs, route and handoff conditions. |
| China–Russia rail transport | 40–45 days according to the official homepage; no money-back guarantee is stated in the supplied material. |
| Special line referenced by SDK | The homepage describes a fastest time of 18 days for the China–Russia international logistics offering; the applicable service and start point should be confirmed with SDK. |
| United States TikTok line | 8–10 business days is stated for the described US TikTok line; the published figure is route-specific. |
Destination Country Delivery Times
| Destination country or region | Documented service and timing |
|---|---|
| Russia | Road: 25–30 days; rail: 40–45 days. Last-mile channels include CDEK, Russian pickup points and marketplace stations. |
| Belarus | CDEK delivery is described as covering Belarus; a country-specific transit average is not published in the supplied official material. |
| Kazakhstan | CDEK delivery is described as covering Kazakhstan; a country-specific transit average is not published in the supplied official material. |
| United States | The US warehouse project states 8–10 business days for its described TikTok line and 3–5 days to the warehouse for the TemuY2 model. |
The official material does not provide verified averages for a wider country list. Actual timing depends on collection cut-off, customs, route capacity, holidays, address quality, warehouse processing and partner scans.
Common Tracking Problems and Solutions
Most tracking issues are resolved fastest by the shipper, because the shipper can confirm the booking, physical handoff, declared address and service. Recipients should preserve delivery evidence and contact the seller when a parcel is missing.
Problem & Solution
| Problem or status | Check first and immediate action |
|---|---|
| Invalid number | Compare every character, remove accidental punctuation and ask the seller whether the identifier is an order reference or partner number. |
| No tracking events | The label may be created before physical acceptance. Ask the shipper to confirm collection and activation. |
| Long gap in transit | International line-haul, customs and partner handoff can create scan gaps. Ask the shipper to open an inquiry if the service terms permit it. |
| Customs hold | Check importer information, documents and taxes with the shipper or destination authority; arrival at customs is not release. |
| Delivered but not received | Check the door, pickup point, building desk, household members and neighbors; request proof of delivery and contact the local delivery partner and seller. |
| Returned to sender | Ask the shipper for the return reason, verify address or customs information and confirm whether reshipment is possible. |
| Damage or loss | Photograph packaging and contents, preserve the parcel and ask the shipper to start the applicable carrier investigation or claim. |
International Shipping, Customs and Carrier Handoffs
A typical SDK China–Russia shipment can move from Chinese collection to road or rail line-haul, customs-related processing, Russian warehouse or destination handling, and local delivery. A downstream CDEK or marketplace scan indicates a reported partner event, not necessarily an SDK-issued number.
| Stage | What customers should understand |
|---|---|
| China collection | SDK or an origin collection point receives shipment information and cargo; label creation alone is not physical acceptance. |
| Road or rail line-haul | The shipment moves through the selected China–Russia corridor. Scan frequency may be lower during line-haul. |
| Export and import processing | Declarations, documents, duties and tax treatment depend on the shipment and jurisdiction; customs arrival is not customs release. |
| Partner handoff | SDK pages identify CDEK, pickup-point channels and marketplace stations for downstream delivery. The first partner acceptance scan is stronger evidence of physical handoff than an electronic pre-alert. |
| Russian last mile | CDEK, a pickup point or an OZ, WB or YD marketplace channel may perform the final delivery or collection step. |
Delivery Management and Post-shipment Options
SDK’s public pages describe delivery to users, pickup points and marketplace stations, but they do not publish a general public policy for interception, address change, guaranteed redelivery or delivery holds. Contact the shipper or the identified last-mile partner before the parcel reaches final delivery.
Lost, Damaged, Claims, Insurance and Refunds
A tracking inquiry, carrier investigation, insurance claim, postage refund and marketplace refund are separate processes. The shipper should preserve the label, invoice, declared value, packaging, photographs and tracking history, then ask SDK or the contracting seller which claim route applies.
Shipping Restrictions and Special Handling
SDK’s public pages distinguish customs and route models, including low-declaration tax-inclusive routes and normal-declaration routes requiring complete product documentation and applicable duties and VAT. Senders must obtain the current route-specific rules before tendering goods.
| Category | Practical requirement |
|---|---|
| Normal-declaration route | SDK states that product documentation, purchase invoices, legal EAC where applicable and normal customs duties and VAT may be required. |
| Low-declaration or tax-inclusive route | The official service page describes a route with low declaration and customs-related service; eligibility and permitted products must be confirmed before booking. |
| Special-line goods | SDK references a China–Belarus special line for certain tools and adult products; product acceptance, documents and customs conditions require direct confirmation. |
Customer Service
Use the shipper or SDK for booking, route, customs, warehouse and claim questions. For final-mile questions, also use the partner named in the latest event, such as CDEK or the relevant marketplace channel.
Customer Service
| Channel | Verified contact or use |
|---|---|
| Official website | SDK official website; use the published contact and service navigation. |
| Phone consultation | 188-5025-3991 is published for urgent consultation and business discussion. |
| yanglijuan@SDK-express.net is published on the official homepage and About page. | |
| Headquarters | Longhua District, Shenzhen, Guangdong, China, at the address published by SDK. |
| Prepare before contact | Provide the tracking or shipment reference, ship date, origin and destination, service, latest event, declared contents, value evidence and photographs where relevant. |
Ecommerce and Business Tracking
Businesses should distinguish SDK’s warehouse and logistics systems from a public carrier API. SDK’s site references logistics, warehouse, cloud-warehouse, supply-chain and POD systems, but the supplied public material does not establish a current public API endpoint, authentication method or webhook specification.
Developer/API Comparison
| Option | Provider | ||||||
|---|---|---|---|---|---|---|---|
| SDK logistics or WMS systems | SDK | ||||||
View all details for SDK logistics systems
| |||||||
| Multi-carrier tracking API | 17TRACK | ||||||
View all details for 17TRACK API
| |||||||
FAQ
Basic FAQs
Enter the shipment identifier on the official SDK website or 17TRACK, then compare the latest event with the seller’s dispatch information.
Look in the seller’s shipping notice, warehouse record, dispatch message or label; an order number may not be the parcel identifier.
SDK’s supplied public pages do not publish one universal pattern, so use the exact number provided and let the official tool or 17TRACK identify it.
The first event normally appears after shipment data is activated and a collection or partner scan is reported; label creation alone does not prove acceptance.
Line-haul, customs and partner handoff can create visibility gaps; ask the seller to verify physical handoff and open an inquiry where the service permits.
SDK publishes 25–30 days for China–Russia road transport and 40–45 days for rail transport; these are route estimates rather than universal guarantees.
Check the address and delivery notice, then contact the shipper and the named last-mile partner to determine redelivery, pickup or return handling.
Check the delivery location, household members, neighbors, building desk and pickup point, then request proof of delivery and contact the seller.
Preserve the packaging and evidence and ask the shipper to start the applicable investigation or claim with SDK or the contracted delivery operator.
The official website publishes 188-5025-3991 and yanglijuan@SDK-express.net for consultation; include the shipment number and latest scan.
Expert FAQs
SDK describes downstream delivery through CDEK, pickup-point channels and OZ, WB and YD marketplace stations, so the final physical carrier can be a partner.
A warehouse scan records receiving, storage or outbound processing, while a delivery scan is a downstream partner report about final delivery or collection.
No; customs arrival only indicates presentation or processing, and release depends on documents, declarations, duties and the competent customs authority.
SDK describes road corridors through Xinjiang or Manzhouli and rail corridors through Alashankou or Manzhouli; the booked route determines the applicable sequence.
The supplied public pages mention logistics, WMS and POD systems but do not establish a current public SDK tracking API specification; businesses should request integration details directly.
Tracking API
The official SDK website evidence does not establish a current public official tracking API endpoint. The following is a 17TRACK API registration example; replace the carrier placeholder only after confirming the current 17TRACK carrier code in your account or documentation.
// 1. SDK official tracking API
// Current public official tracking API not confirmed.
// 2. 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"
}
]
Sources & References
- SDK official website — China–Russia logistics, warehouse and contact information. 斯德克（深圳）国际物流有限公司
- About SDK — company history, business positioning and warehouse information. 斯德克（深圳）国际物流有限公司
- Russia overseas warehouse — first-mile, storage, WMS and last-mile services. 斯德克（深圳）国际物流有限公司
- China–Russia international logistics — collection, transport and CDEK delivery. 斯德克（深圳）国际物流有限公司
- United States warehouse project — warehouse fulfillment and described route estimates. 斯德克（深圳）国际物流有限公司
- 17TRACK API documentation. 17TRACK
17TRACK is an independent tracking platform and is not affiliated with SDK.
Track your package
Global express parcel tracking service
