
JDE Tracking
Please enter the JDE tracking number to check the latest shipping status.
About JDE
JDE is the display name used for this 17TRACK carrier page. The supplied official website identifies the operating company as ЖелДорЭкспедиция, a Russian transport and freight-forwarding company founded in 1995. Its services include rail transport, road freight, air freight, consolidated cargo, express delivery, warehousing and courier delivery.
| Field | Verified information |
|---|---|
| Official website | https://www.jde.ru/ |
| Official operating name | ЖелДорЭкспедиция; the website also uses Ж.Д.Э. |
| Carrier type | Multimodal transport and freight-forwarding operator with terminal, warehouse, courier and business-logistics services. |
| Primary region | Russia, with stated delivery activity involving Kazakhstan, Belarus and shipments from China. |
| Tracking page | JDE cargo tracking |
| Founded | 1995. |
Carrier Entity Relationships
| Entity | Relationship and tracking significance |
|---|---|
| ЖелДорЭкспедиция | ЖелДорЭкспедиция is the operating logistics company represented by the JDE tracking identity. |
| Rail, road and air services | JDE organizes transport using rail, trucks, aircraft and consolidated-cargo networks, so the physical custodian can change during line-haul. |
| ER / shipment number | The official tracking page refers to an ER number and PIN code; these identify the shipment in the official tracking workflow. |
| Terminals and pickup points | JDE uses branches, terminals and pickup points for acceptance, transfer and collection; a terminal scan does not necessarily mean final delivery. |
| 17TRACK | 17TRACK aggregates available tracking events as an independent platform; it does not transport cargo or decide claims. |
Quick Answer
Use the ER number shown on the JDE receipt, shipping notification or merchant order record. Enter the number on the official JDE tracking page or in 17TRACK. If no result appears, check whether the number is an order number rather than an ER number, whether the shipment has been accepted, and whether the PIN is required by the official page.
How to Track JDE Packages
JDE tracking follows a cargo record rather than a universal postal S10 format. The official page describes an ER number and PIN-code workflow, while business integrations can use shipment and customer-reference fields.
| Path | Steps and limitations |
|---|---|
| Official JDE tracking | Open the official tracking page, enter the ER number and provide the PIN when requested. Use the official result for cargo status and estimated arrival information. |
| 17TRACK | Enter the shipment identifier in 17TRACK. Automatic recognition may depend on the identifier and the events supplied by JDE. |
| Where to find the number | Check the JDE receipt, waybill, merchant dispatch email, personal account or shipment documents. An order number or invoice number may not be trackable. |
| No result | Remove spaces and punctuation, confirm every character, ask the merchant whether the cargo was physically accepted, and request the ER number and PIN rather than only an order reference. |
Tracking Number Formats and Examples
JDE’s public tracking page identifies the ER number and PIN as the key tracking credentials. The supplied official material does not establish one universal public character-length rule, so a prefix alone should not be used to infer a service.
Tracking Number Format
| Identifier family | Normalized pattern and use |
|---|---|
| ER number | Use the shipment identifier printed on JDE documents. A safe redacted example is ER XXXXXXXX; the public material does not define a single fixed length. |
| PIN code | A separate PIN may be requested by the official tracking page to reveal full ER information. Do not publish a real customer PIN. |
| Customer order reference | A merchant reference can be passed in business workflows, but it is not automatically the JDE shipment identifier. |
| Partner or last-mile number | A marketplace or delivery partner may display another identifier. It may link to the JDE cargo record without being issued by JDE. |
Tracking Statuses and Meanings
JDE tracking events should be read as custody milestones. A created record is not the same as physical acceptance, and an arrival at a terminal is not the same as delivery to the consignee.
Status Quick Lookup
| Status stage | Meaning and next action |
|---|---|
| Pre-shipment | A record or request exists, but physical acceptance may not have occurred. The shipper should confirm handover. |
| Accepted | JDE or an authorized facility has recorded receipt. Wait for sorting or dispatch events. |
| In transit | The cargo is moving between facilities or transport modes. The current terminal or line-haul operation remains responsible for the next scan. |
| At destination terminal | The cargo has reached a destination facility and may await sorting, appointment, pickup or last-mile dispatch. |
| Out for delivery | The shipment has been assigned to a local delivery operation. Keep the address and recipient available. |
| Delivered or collected | JDE records completion, delivery or pickup. If the recipient cannot locate the cargo, request delivery evidence from JDE. |
| Exception or return | An address, payment, packaging, access, damage or acceptance issue requires intervention by the shipper, recipient or JDE branch. |
Services and Delivery Times
JDE publishes route-specific calculator results rather than one universal delivery promise. The official site shows examples such as Moscow to Saint Petersburg from one day, Moscow to Kazan from two days, Moscow to Novosibirsk from four days and Moscow to Vladivostok-related routes handled through the wider network. Actual timing depends on service, terminals, cargo characteristics and delivery method.
Service Comparison
| Service | Best use and main condition |
|---|---|
| Rail freight | Suitable for planned cargo movements and long-distance routes; rail loading, terminals and documentation affect timing. |
| Road freight | Covers freight from small consignments up to stated truckload handling; terminal or door delivery can be selected. |
| Air freight | A faster transport mode for suitable cargo, subject to route, acceptance and handling conditions. |
| Express delivery | For time-sensitive shipments where the selected route and quote support express handling. |
| Internet package and courier delivery | Ecommerce delivery to addresses or pickup points; courier delivery is offered in major cities. |
Delivery Time
| Route example | Published example and limitation |
|---|---|
| Moscow to Saint Petersburg | From 1 day on the official route example; this is a route estimate, not a universal guarantee. |
| Moscow to Kazan | From 2 days on the official route example; cutoff, cargo and delivery option can change the result. |
| Moscow to Novosibirsk | From 4 days on the official route example; long-distance terminal transfers may add time. |
| Other routes | Use the official calculator for origin, destination, weight, volume, delivery mode and extra services. |
Destination Country Delivery Times
| Destination | Service and timing guidance |
|---|---|
| Russia | Domestic road, rail, air and express services are supported. Use the route calculator; timing depends on terminals, distance and delivery type. |
| Kazakhstan | The official site states delivery activity involving Kazakhstan. Customs, documentation and cross-border handoff can affect the route estimate. |
| Belarus | The official site states delivery activity involving Belarus. Confirm the current route and documentation requirements before dispatch. |
| China origin | JDE states that it delivers shipments from China; origin export, border processing and Russian domestic acceptance can create visibility gaps. |
Common Tracking Problems and Solutions
| Problem or status | What to check and do next |
|---|---|
| Invalid number | Check that the identifier is an ER number, remove punctuation, and ask the shipper for the PIN if the official page requires it. |
| No tracking events | A label or order record may exist before physical acceptance. Ask the shipper to confirm handover to JDE. |
| No update during transit | Terminal and line-haul movements may have fewer scans. Compare the official result with the promised route and contact the shipper if the delivery estimate passes. |
| Delivery exception | Confirm address, recipient availability, access, payment and pickup instructions with the responsible JDE branch. |
| Delivered but not received | Check the delivery address, receiving desk, warehouse, family members and neighbors; then request delivery evidence and open an inquiry through the shipper or JDE. |
| Lost or damaged cargo | Keep packaging and contents, photograph the condition, preserve invoices and notify the contracting shipper promptly. A 17TRACK result cannot approve a claim. |
| Return or refused delivery | Ask the merchant or contracting party why the cargo was returned and confirm whether redelivery, pickup or a new shipment is possible. |
International Shipping, Customs and Carrier Handoffs
JDE’s official website describes activity involving Kazakhstan, Belarus and shipments from China. International visibility can therefore include an origin carrier, border or customs authorities, JDE facilities and a destination delivery provider. Arrival at a border or exchange facility does not by itself prove customs release.
International Flow
| Stage | Custody, event and customer action |
|---|---|
| Origin preparation | The shipper creates the cargo record and prepares documents. The number may exist before physical handover. |
| Export and line-haul | Origin facilities, transport operators or border authorities move the shipment. Scans may be intermittent. |
| Partner handoff | An electronic pre-advice, physical handover and first receiving scan are different events. Do not treat a partner pre-alert as acceptance by JDE. |
| Import and customs | Authorities review documents, value, contents and duties. The shipper or importer must provide information when requested. |
| Destination delivery | JDE or a destination delivery partner completes terminal, pickup or door delivery. Ask the contracting party which entity controls the next action. |
Delivery Management and Post-shipment Options
JDE’s ecommerce material describes delivery to an address or pickup point, courier delivery in major cities, selectable delivery timing and address changes within the current city. Eligibility depends on the shipment contract and processing stage.
| Option | Who should request it and limitation |
|---|---|
| Pickup point or terminal collection | The recipient or merchant can select the available collection method where the service supports it. Bring the required identification and shipment information. |
| Courier delivery | Available for stated major-city services. Confirm the address, contact number and delivery window with the merchant or JDE. |
| Address change within the city | JDE’s ecommerce page describes this capability for supported orders. Request it before final dispatch; success is not guaranteed after route assignment. |
| Return | The merchant can arrange a return when a buyer refuses or sends back an order; the transport record and commercial refund are separate processes. |
Lost, Damaged, Claims, Insurance and Refunds
A tracking inquiry, a transport investigation, an insurance claim and a merchant refund are different processes. The contracting shipper should normally preserve the waybill, invoice, cargo description, declared value, photographs and packaging and then contact JDE through the applicable service channel.
| Process | Use and evidence |
|---|---|
| Tracking inquiry | Use when an event is unclear or delayed. Provide the ER number, PIN if applicable, route and latest scan. |
| Damage investigation | Report visible or concealed damage promptly; retain packaging, contents, photographs and commercial documents. |
| Insurance or transport claim | The contracting party should follow the applicable JDE contract and insurance terms. Filing deadlines vary by service and agreement. |
| Merchant refund | The seller or marketplace decides the commercial refund. 17TRACK cannot issue it or change the transport record. |
Shipping Restrictions and Special Handling
JDE offers specialist handling for oversized, valuable, fragile, temperature-controlled, pharmaceutical, cosmetic and chemical-related cargo. Acceptance depends on packaging, documentation, route and the applicable transport rules.
| Category | Handling and tracking impact |
|---|---|
| Oversized or heavy cargo | May require special equipment, loading plans, securing, permits and a route-specific quotation; scans can follow multiple facilities. |
| Fragile or valuable cargo | Use approved packaging and request applicable protection or handling services before acceptance. |
| Temperature-controlled goods | Pharmaceutical and cosmetic shipments may require temperature conditions and specialist coordination. |
| Chemical, liquid or regulated goods | Provide accurate contents and safety documentation; acceptance, route and timing can be restricted. |
Customer Service
| Channel | Best use and information to prepare |
|---|---|
| Official tracking page | JDE tracking; prepare the ER number and PIN if requested. |
| Official website | JDE website; use the relevant service, calculator, branch or feedback path. |
| Specialist email | The official industrial-cargo page publishes ktk@JDE.ru for oversized-cargo requests, and the temperature-controlled service page publishes termo@JDE.ru for specialist enquiries. |
| Business API support | The developer portal lists its support email as itsupport@JDE.ru. This is intended for integration questions, not a substitute for a consumer delivery claim. |
For an escalation, prepare the ER number, PIN, ship date, origin, destination, service, latest event, recipient details, cargo description, value evidence and photographs. Start with the shipper or contracting party when the shipment was bought through an online store.
Ecommerce and Business Tracking
JDE’s ecommerce solution supports preliminary applications through Excel or API, shipment-status control, customer notifications, personal-account history, warehouse functions and delivery to addresses or pickup points. Businesses should distinguish the JDE integration from the independent 17TRACK multi-carrier API.
Developer/API Comparison
| Option | Provider |
|---|---|
| JDE developer API | ЖелДорЭкспедиция |
| 17TRACK API | 17TRACK |
The JDE developer portal documents methods for creating shipments, obtaining cargo status, calculating prices, searching terminals and retrieving documents. The 17TRACK API is designed for multi-carrier tracking and requires a 17TRACK token.
FAQ
Basic FAQs
Enter the ER number on the official JDE tracking page or use 17TRACK to view available shipment events.
Look on the JDE receipt, waybill, merchant dispatch notice, personal account or shipment documents.
JDE’s public tracking workflow refers to an ER number and may also require a PIN; the official material does not define one universal public length.
The shipment record may have been created before physical acceptance, or the cargo may be between terminals; ask the shipper to confirm handover.
Timing is route-specific; official examples show Moscow to Saint Petersburg from one day, Moscow to Kazan from two days and Moscow to Novosibirsk from four days.
Confirm the address, recipient availability, access and pickup instructions, then contact the merchant or responsible JDE branch.
Check the receiving desk, warehouse, family members and neighbors, then request delivery evidence through the shipper or JDE.
Preserve the packaging and contents, take photographs, gather value documents and ask the contracting shipper to start the applicable investigation or claim.
Yes, JDE’s ecommerce material describes delivery to pickup points as an available option for supported orders.
Start with the official website or tracking page and provide the ER number, PIN if applicable, route and latest event.
Expert FAQs
No. A merchant order reference can be different from the JDE ER number used by the official tracking service.
No. A created application or pre-advice can precede physical acceptance; look for an acceptance or facility event.
Terminal arrival means the cargo reached a facility; delivery requires a later courier, pickup or consignee-completion event.
JDE states that it handles activity involving Kazakhstan, Belarus and shipments from China, but cross-border events may be supplied by origin, border and destination partners.
Yes. JDE publishes a developer portal and describes API integration for order creation, status control, calculation and related logistics workflows.
No. 17TRACK only aggregates tracking information; address changes must be requested from the merchant or JDE where the shipment permits them.
Responsibility depends on the physical handover and receiving scan; an electronic pre-advice alone does not prove that JDE or a destination partner has accepted the cargo.
Tracking API
// JDE official developer API:
// Use the current documentation at https://api.jde.ru/dev/
// The public evidence describes JDE REST methods, including cargo status,
// order creation, calculators, geography and documents.
// 17TRACK API:
POST https://api.17track.net/track/v2.4/register
Header: 17token: YourKey
Header: Content-Type: application/json
Body:
[
{
"number": "TRACKING_NUMBER",
"carrier": "CARRIER_CODE"
}
]
// Replace TRACKING_NUMBER with the shipment identifier.
// Confirm the current JDE carrier code in 17TRACK documentation
// before production use; do not infer it from the brand display name.
Sources & References
- ЖелДорЭкспедиция — Official website. ЖелДорЭкспедиция
- Cargo location tracking. ЖелДорЭкспедиция
- Ecommerce delivery and logistics solutions. ЖелДорЭкспедиция
- Oversized and heavy cargo transportation. ЖелДорЭкспедиция
- Pharmaceutical and cosmetic cargo solutions. ЖелДорЭкспедиция
- Transport-company partnership and API integration. ЖелДорЭкспедиция
- JDE developer portal. ЖелДорЭкспедиция
- 17TRACK API documentation. 17TRACK
17TRACK is an independent tracking platform and is not affiliated with JDE.
Track your package
Global express parcel tracking service























