About JND
JND is the carrier identity associated with the supplied official website below. Use the name JND exactly as displayed when selecting a carrier or asking a seller to investigate a shipment. A tracking result identifies electronic shipment events; it does not by itself prove which company physically holds the parcel unless an acceptance or handoff scan says so.
JND Overview
Carrier Entity Relationships
| Entity | Entity type |
| JND | Canonical carrier identity |
View all details for JND
| Relationship to JND | JND is the carrier name used throughout this guide and linked to the supplied official website. |
| Why it matters to tracking | Selecting the correct carrier prevents a similarly named organization from being assigned to the number. |
| Official evidence | JND official website |
|
| 17TRACK | Independent multi-carrier tracking platform |
View all details for 17TRACK
| Relationship to JND | 17TRACK displays available tracking events supplied through carrier and logistics data connections; 17TRACK does not transport JND shipments. |
| Why it matters to tracking | Users can monitor a shipment in a multi-carrier interface, including events exposed after a partner handoff. |
| Official evidence | 17TRACK API documentation |
|
| Seller or shipping platform | Shipment-data source and commercial counterparty |
View all details for seller or shipping platform
| Relationship to JND | The seller may purchase transport, create a label, and provide the tracking number to the buyer. |
| Why it matters to tracking | The seller can distinguish an order number from a carrier number and normally controls refunds or replacements. |
| Official evidence | The order confirmation, dispatch notice, invoice, or shipping label is the shipment-specific evidence. |
|
Quick Answer
Copy the carrier tracking number from the seller’s dispatch notice or shipping label and enter it on 17TRACK. If no result appears, remove spaces, verify that the value is a tracking number rather than an order ID, confirm that JND is the selected carrier, and allow time for the first physical acceptance scan.
Pro Tip: 17TRACK is an independent tracking platform. 17TRACK cannot transport a parcel, correct an address, authorize delivery changes, release customs shipments, approve claims, or issue a seller refund.
How to Track JND Packages
Track JND with the carrier identifier shown in the dispatch record. The most useful result is the latest event that identifies a location, lifecycle stage, and responsible carrier or partner.
- Open the seller’s shipping email, marketplace order page, receipt, or parcel label.
- Copy the carrier tracking number. Do not substitute the checkout order number unless the seller explicitly identifies it as the carrier number.
- Open 17TRACK, paste the number, and select JND if automatic carrier detection is inconclusive.
- Read the event timestamp, location, status, and carrier name together. A label-created event is electronic data, while an accepted event indicates a physical scan.
- If the result remains empty, ask the sender to verify the exact carrier number and whether the parcel has physically entered the logistics network.
Where to Find the Correct Identifier
| Identifier | How to use it |
| Carrier tracking number | Use this for JND or 17TRACK tracking. It usually appears beside “tracking,” “shipment,” or “waybill.” |
| Order number | Use it with the seller or marketplace. It may identify the purchase but may not query carrier events. |
| Merchant reference | Use it when contacting the sender. Ask the sender to map it to the carrier tracking number. |
| Partner or last-mile number | Use it after a handoff when the destination carrier displays a separate local identifier. |
Tracking Statuses and Meanings
The following normalized lifecycle meanings help interpret JND tracking. Read the original event text and carrier name because the responsible party can change during a partner handoff.
Status Quick Lookup
| Status | What it means |
| Shipment information received | Electronic shipment data exists, but a physical acceptance scan may not yet exist. |
View all details for shipment information received| Lifecycle stage | Pre-shipment |
|---|
| Current responsible party | The sender or booking party remains responsible until physical transfer is recorded. |
|---|
| What happens next | Collection, drop-off, consolidation, and an acceptance or processing scan. |
|---|
| What you should do | Ask the sender whether the parcel has physically departed if the status persists beyond the promised dispatch date. |
|---|
|
| Accepted or received | A carrier or logistics facility has recorded physical receipt. |
View all details for accepted or received| Lifecycle stage | Accepted |
|---|
| Current responsible party | The carrier or named facility shown in the event. |
|---|
| What happens next | Sorting, consolidation, security processing, or dispatch. |
|---|
| What you should do | Monitor the next processing scan; no action is normally required. |
|---|
|
| In transit or departed facility | The parcel is moving between processing points or waiting for the next transport connection. |
View all details for in transit| Lifecycle stage | In transit |
|---|
| Current responsible party | The named carrier, consolidator, line-haul operator, or processing facility. |
|---|
| What happens next | Arrival, sorting, export, import, or partner handoff. |
|---|
| What you should do | Compare elapsed time with the seller’s delivery window and check for a later partner event. |
|---|
|
| Customs processing | The shipment is undergoing or awaiting import or export formalities; arrival is not the same as release. |
View all details for customs processing| Lifecycle stage | Customs or regulatory processing |
|---|
| Current responsible party | Customs or another border authority controls release; the broker, importer, or carrier may need to supply data. |
|---|
| What happens next | Release, tax or document request, inspection, return, or seizure under applicable law. |
|---|
| What you should do | Respond only through verified carrier, broker, marketplace, or government channels. |
|---|
|
| Handed to delivery partner | A partner relationship is indicated, but responsibility transfers physically only when the receiving party accepts the parcel. |
View all details for partner handoff| Lifecycle stage | Handover |
|---|
| Current responsible party | The last party with a physical scan remains responsible until the receiving partner records acceptance. |
|---|
| What happens next | The receiving carrier creates an arrival or acceptance scan and may assign a local number. |
|---|
| What you should do | Track both identifiers if a partner number appears. |
|---|
|
| Out for delivery | The destination delivery unit has assigned the parcel to a delivery route. |
View all details for out for delivery| Lifecycle stage | Final-mile delivery |
|---|
| Current responsible party | The named destination or last-mile carrier. |
|---|
| What happens next | Delivery, attempted delivery, pickup routing, or an exception. |
|---|
| What you should do | Keep the delivery location accessible and follow only verified delivery instructions. |
|---|
|
| Delivered | A delivery scan was recorded at the stated time and location or delivery type. |
View all details for delivered| Lifecycle stage | Delivered |
|---|
| Current responsible party | The last-mile carrier recorded the delivery event; the seller remains the commercial contact for an unresolved order. |
|---|
| What happens next | The shipment closes unless a delivery inquiry is opened. |
|---|
| What you should do | Check the delivery location, household, reception, parcel locker, neighbors where appropriate, and proof of delivery before escalating. |
|---|
|
| Delivery exception or attempted delivery | Delivery could not be completed because of access, address, recipient, operational, or regulatory conditions. |
View all details for a delivery exception| Lifecycle stage | Exception |
|---|
| Current responsible party | The last-mile carrier manages the operational exception; sender authorization may be required for address changes. |
|---|
| What happens next | Reattempt, pickup, correction, investigation, or return. |
|---|
| What you should do | Follow the event instructions and contact the named delivery carrier or sender promptly. |
|---|
|
| Return to sender | The parcel is moving back because delivery, customs clearance, or acceptance could not be completed. |
View all details for return to sender| Lifecycle stage | Return |
|---|
| Current responsible party | The carrier or partner handling the return movement. |
|---|
| What happens next | Return transport, sender receipt, and commercial resolution. |
|---|
| What you should do | Contact the seller about reshipment or refund; interception may no longer be possible. |
|---|
|
Services and Delivery Times
Use the exact service and delivery window stated in the JND booking or seller confirmation. Tracking events can show progress, but they do not convert a merchant estimate into a carrier guarantee.
Service Comparison
| Service | Best for |
| Merchant-booked JND shipment | Orders whose dispatch record identifies JND as the carrier. |
View all details for merchant-booked JND shipments
| Service type | Use the service description printed on the label, booking, invoice, or seller confirmation. |
| Coverage | The shipment-specific booking defines origin, destination, and handoff scope. |
| Tracking level | Available scans may include booking, acceptance, processing, transport, handoff, customs, and delivery events. |
| Key size/weight condition | The booking party must apply the limits accepted for the purchased product. |
| Included protection/extra service | Check the shipment contract or seller confirmation for declared value, insurance, signature, or other protection. |
| Main limitation | Service names, limits, guarantees, and claims rights should not be inferred from tracking status alone. |
|
Delivery Time
| Service | Published delivery standard |
| Booked JND service | Use the shipment-specific delivery window communicated by the sender or booking record. |
View all delivery-time details for a JND shipment
| Business or calendar days | Apply the day-count definition printed in the applicable booking terms. |
| Guarantee status | Treat the date as an estimate unless the purchased service terms expressly state a guarantee and its remedy. |
| Starts counting from | Use the contractual starting event, which may differ from label creation or order placement. |
| Main delay factors | Physical acceptance, consolidation, transport capacity, weekends, holidays, weather, address quality, customs, restricted goods, partner handoff, and missed scans. |
| Official source date/validity | Confirm against the current shipment booking and applicable JND terms before relying on a deadline. |
|
Destination Country Delivery Times
| Destination Country / Region | Estimated Delivery Time Range |
| Destination stated in the JND shipment booking | Use the route-specific window supplied by the sender or booking record; do not substitute an unrelated carrier average. |
View all destination-time details for a JND shipment
| Primary Service Type | The purchased service shown on the label, invoice, booking, or dispatch notice. |
| Average Delivery Days | Calculate from comparable JND shipments using the same origin, destination, service, and acceptance period rather than mixing dissimilar lanes. |
| Last-Mile Partner / Handoff Carrier | Use the carrier identified by the first destination acceptance or final-mile event. |
| Customs & Clearance Tips | Ensure the declared contents, value, recipient details, tax information, and requested permits match destination requirements. Customs arrival does not mean customs release. |
|
Route estimates should be based on comparable shipment evidence. Unverified country averages can mislead users because the origin, service level, customs treatment, and destination partner may differ.
Common Tracking Problems and Solutions
Start with the latest physical scan, not only the headline status. The sender controls shipment data and commercial remedies, while the carrier or named partner controls transport operations.
Problem & Solution
| Problem/status shown | Check first |
| Invalid number or no result | Compare every character with the dispatch notice and distinguish the carrier number from the order ID. |
View solutions for an invalid JND number| Likely cause | Typing error, wrong identifier, wrong carrier selection, or shipment data awaiting activation. |
|---|
| Immediate action | Paste the number without surrounding spaces and ask the sender to confirm the carrier. |
|---|
| When to escalate | Escalate when the seller’s dispatch deadline or promised tracking-activation window has passed. |
|---|
| Who to contact | Seller or shipping platform first. |
|---|
|
| Label created with no acceptance | Check whether the sender states that the parcel was physically collected or dropped off. |
View solutions for label created| Likely cause | Electronic pre-advice was created before physical transfer or before the first scan. |
|---|
| Immediate action | Ask the sender for the physical handover date and collection evidence. |
|---|
| When to escalate | Escalate after the seller’s stated dispatch or activation window. |
|---|
| Who to contact | Sender or merchant. |
|---|
|
| Long gap or stuck in transit | Identify the last physical event, location, responsible party, and whether customs or a handoff follows. |
View solutions for a long tracking gap| Likely cause | Consolidation, line-haul movement, missed scan, customs processing, backlog, or partner transfer. |
|---|
| Immediate action | Check for a partner number and compare elapsed time with the shipment-specific delivery window. |
|---|
| When to escalate | Escalate when the delivery window passes or the sender’s applicable inquiry conditions are met. |
|---|
| Who to contact | Seller for investigation; named last-mile carrier when it has accepted the parcel. |
|---|
|
| Shipping partner awaiting handoff | Check which party recorded the last physical scan and whether the receiving partner has an acceptance event. |
View solutions for a partner handoff delay| Likely cause | The partner received electronic data but may not yet have the parcel. |
|---|
| Immediate action | Track the origin and partner identifiers and wait for receiving-carrier acceptance. |
|---|
| When to escalate | Escalate after the booked handoff or delivery window is exceeded. |
|---|
| Who to contact | The sender or party that booked transport. |
|---|
|
| Address issue or failed delivery | Read the event instructions and verify the address originally supplied to the seller. |
View solutions for an address or delivery issue| Likely cause | Incomplete address, access problem, recipient absence, or local delivery restriction. |
|---|
| Immediate action | Contact the named last-mile carrier and seller; do not rely on unverified redelivery messages. |
|---|
| When to escalate | Act before the parcel enters return processing. |
|---|
| Who to contact | Last-mile carrier for delivery instructions and sender for authorization or correction. |
|---|
|
| Held for pickup | Check the named location, identification requirements, and collection instructions in the event notice. |
View solutions for pickup| Likely cause | Pickup was selected, delivery was attempted, or local procedure requires collection. |
|---|
| Immediate action | Follow the named carrier’s pickup notice and bring required identification. |
|---|
| When to escalate | Contact the carrier before the stated collection deadline. |
|---|
| Who to contact | The pickup facility or destination carrier shown in tracking. |
|---|
|
| Customs hold | Check for a verified request for tax, invoice, product description, identity, or import authorization. |
View solutions for a customs hold| Likely cause | Assessment, inspection, missing data, restricted goods, or unpaid import charges. |
|---|
| Immediate action | Provide accurate documents through a verified broker, carrier, marketplace, or customs channel. |
|---|
| When to escalate | Escalate immediately when a formal deadline or document request is stated. |
|---|
| Who to contact | Named broker or destination carrier and the sender. |
|---|
|
| Delivered but not received | Check the delivery location, household members, reception, locker, safe place, neighbors where appropriate, and proof of delivery. |
View solutions for delivered but not received| Likely cause | Alternate placement, household receipt, location mismatch, premature scan, or misdelivery. |
|---|
| Immediate action | Record the event, request delivery evidence from the last-mile carrier, and notify the seller. |
|---|
| When to escalate | Escalate promptly under the seller’s buyer-protection and carrier inquiry rules. |
|---|
| Who to contact | Last-mile carrier for delivery evidence and seller for order resolution. |
|---|
|
| Lost or damaged parcel | Preserve the parcel, contents, label, packaging, photos, invoice, and tracking history. |
View solutions for loss or damage| Likely cause | Transport loss, contents loss, impact, crushing, moisture, tampering, or packaging failure. |
|---|
| Immediate action | Photograph all sides before disposal and ask the sender to open the applicable investigation or claim. |
|---|
| When to escalate | Use the shipment contract’s filing window; do not wait until evidence or buyer protection expires. |
|---|
| Who to contact | Seller or contracting shipper and the carrier identified in the shipment contract. |
|---|
|
International Shipping, Customs and Carrier Handoffs
For a cross-border JND shipment, tracking may combine events from the booking party, origin facility, line-haul operator, customs process, and destination carrier. Electronic pre-advice, physical custody, and legal customs control are separate concepts.
International Flow
| Stage | Typical tracking event |
| Shipment creation | Information received or label created |
View all details for shipment creation| Physical custodian/responsible entity | Sender or booking party until physical collection. |
|---|
| What is happening | Shipment and customs data are being prepared. |
|---|
| Can the tracking number change? | A partner identifier may be added later. |
|---|
| Normal visibility gap | No physical event may appear before collection or facility induction. |
|---|
| What the customer should do | Confirm physical dispatch with the sender if activation is delayed. |
|---|
|
| Origin acceptance and export processing | Accepted, processed, or departed origin facility |
View all details for origin processing| Physical custodian/responsible entity | The carrier, warehouse, or consolidator named by the event. |
|---|
| What is happening | Sorting, consolidation, security checks, and export preparation. |
|---|
| Can the tracking number change? | The original identifier may be retained or cross-referenced to a transport identifier. |
|---|
| Normal visibility gap | Scanning may pause while consolidated freight awaits departure. |
|---|
| What the customer should do | Monitor the shipment-specific delivery window. |
|---|
|
| International line-haul | Departed origin, in transit, or arrived destination gateway |
View all details for international line-haul| Physical custodian/responsible entity | The named line-haul operator or contracted logistics chain. |
|---|
| What is happening | The shipment is moving between countries or gateways. |
|---|
| Can the tracking number change? | A transport or destination reference may be linked to the original number. |
|---|
| Normal visibility gap | Events may pause between departure and gateway receipt. |
|---|
| What the customer should do | Do not interpret a scan gap alone as loss. |
|---|
|
| Import customs | Presented to customs, customs processing, or released |
View all details for import customs| Physical custodian/responsible entity | A bonded facility may hold the parcel while customs or another authority controls release. |
|---|
| What is happening | Declaration assessment, inspection, tax processing, or document review. |
|---|
| Can the tracking number change? | The customs or broker reference may differ from the carrier number. |
|---|
| Normal visibility gap | Tracking may remain unchanged until a decision or release event. |
|---|
| What the customer should do | Respond to verified requests and keep invoice and product information ready. |
|---|
|
| Destination partner handoff | Pre-advice sent, tendered to partner, or partner accepted |
View all details for destination handoff| Physical custodian/responsible entity | The last party with a physical scan remains custodian until the partner records receipt. |
|---|
| What is happening | Electronic data and the physical parcel are transferred through separate steps. |
|---|
| Can the tracking number change? | The destination carrier may add a local tracking number. |
|---|
| Normal visibility gap | A gap may occur between pre-advice, tender, unloading, and acceptance. |
|---|
| What the customer should do | Track both numbers and wait for the first destination-carrier acceptance event. |
|---|
|
| Final-mile delivery | At delivery facility, out for delivery, attempted, delivered, or pickup |
View all details for final-mile delivery| Physical custodian/responsible entity | The destination carrier shown in the latest physical event. |
|---|
| What is happening | Local sorting, route assignment, delivery, pickup, or exception handling. |
|---|
| Can the tracking number change? | The local number may become the most detailed source. |
|---|
| Normal visibility gap | Updates depend on local scanning and data exchange. |
|---|
| What the customer should do | Use the destination carrier for local delivery questions and the seller for purchase remedies. |
|---|
|
Delivery Management and Post-shipment Options
A delivery change depends on the purchased service, current custody, sender authorization, destination carrier, and shipment stage. Tracking platforms cannot change the address or stop a parcel.
Delivery Management
| Option | Who can request |
| Address correction or rerouting inquiry | The contracting sender should initiate the request; recipient options depend on the destination carrier. |
View address-correction details| Eligibility | Depends on service, identity checks, customs status, local rules, and whether delivery processing has begun. |
|---|
| Deadline/available stage | Request before final delivery or return processing; earlier requests have more operational scope. |
|---|
| Fee | Use the quote or terms given by the contracting carrier or seller. |
|---|
| Guaranteed? | No operational change should be assumed until the responsible carrier confirms it. |
|---|
| Official action link | JND official website |
|---|
|
| Redelivery or pickup inquiry | The recipient may follow instructions issued by the named destination carrier. |
View redelivery or pickup details| Eligibility | Requires an attempted-delivery, pickup, or delivery-management event from the last-mile carrier. |
|---|
| Deadline/available stage | Follow the deadline in the verified notice before return processing begins. |
|---|
| Fee | Apply the destination carrier’s current conditions. |
|---|
| Guaranteed? | A request is not a guarantee of successful redelivery. |
|---|
| Official action link | Use the verified destination-carrier link shown in the tracking event or delivery notice. |
|---|
|
Lost, Damaged, Claims, Insurance and Refunds
A tracking inquiry, carrier investigation, insurance claim, transport refund, and seller refund are separate processes. The contracting shipper usually has the transport contract, while the buyer normally seeks an order remedy from the seller.
Claims and Refunds
| Process | Use when |
| Tracking inquiry or transport investigation | Use when scans stop, custody is unclear, delivery is disputed, or the route exceeds the applicable delivery window. |
View investigation details| Who files | The sender or party that purchased transport is normally best placed to file; the recipient can provide evidence. |
|---|
| Earliest/latest filing time | Use the current service contract and seller protection deadline. |
|---|
| Required evidence | Tracking number, booking date, addresses, service, contents description, value, last event, and correspondence. |
|---|
| Possible outcome | Location update, delivery evidence, continued search, loss finding, return confirmation, or request for more information. |
|---|
| Official link | JND official website |
|---|
|
| Loss, damage, or missing-contents claim | Use when transport loss or physical damage is supported by shipment and value evidence. |
View claim details| Who files | The insured or contracting party specified by the shipment terms. |
|---|
| Earliest/latest filing time | Follow the purchased service and insurance terms without waiting for marketplace protection to expire. |
|---|
| Required evidence | Label, invoice, value proof, photos, packaging, contents, damage report, tracking history, and requested declarations. |
|---|
| Possible outcome | Investigation, settlement within applicable liability, denial, or request for further evidence. |
|---|
| Official link | JND official website |
|---|
|
| Seller refund or replacement | Use when the purchased order was not received, arrived damaged, or materially differs from the sales agreement. |
View seller-remedy details| Who files | The buyer files with the seller or marketplace under the purchase and buyer-protection terms. |
|---|
| Earliest/latest filing time | Use the order platform’s current dispute window. |
|---|
| Required evidence | Order number, payment record, tracking, photos, delivery dispute evidence, and seller correspondence. |
|---|
| Possible outcome | Replacement, refund, partial refund, return instruction, or denial under the sales terms. |
|---|
| Official link | Use the seller or marketplace order-resolution page. |
|---|
|
17TRACK cannot approve an investigation, claim, insurance payment, postage refund, seller refund, or replacement.
Shipping Restrictions and Special Handling
The sender must check the purchased service, origin, transit, airline or surface-transport rules, and destination law before tender. A carrier acceptance scan does not make prohibited contents lawful.
Shipping Restrictions
| Category | Prohibited or restricted |
| Dangerous goods | Treat explosives, flammables, compressed gases, corrosives, toxic substances, and other regulated hazards as restricted unless expressly accepted under applicable rules. |
View dangerous-goods details| Typical examples | Aerosols, fuel, fireworks, solvents, certain chemicals, and pressurized containers. |
|---|
| Key condition/packaging | Classification, documentation, labels, quantity limits, and approved packaging may be required. |
|---|
| Transport limitation | Air, road, sea, postal, and national restrictions can differ. |
|---|
| Possible tracking/delivery impact | Security hold, inspection, refusal, return, disposal, or enforcement action. |
|---|
| Official rules | Check the current JND service terms and every applicable transport authority. |
|---|
|
| Batteries, liquids, and magnetized items | Service acceptance depends on chemistry, installation, watt-hour rating, quantity, leakage risk, and transport mode. |
View battery and liquid details| Typical examples | Lithium cells, power banks, electronic devices, cosmetics, oils, and magnetic assemblies. |
|---|
| Key condition/packaging | Prevent activation, short circuit, movement, leakage, and damage; apply required declarations and labels. |
|---|
| Transport limitation | Standalone batteries and liquids may face stricter air-transport limits. |
|---|
| Possible tracking/delivery impact | Screening delay, route change, refusal, or return. |
|---|
| Official rules | Obtain written acceptance for the exact item and service before shipping. |
|---|
|
| Perishable, valuable, controlled, or destination-restricted goods | Acceptance and compensation may be limited even when transport is physically possible. |
View special-item details| Typical examples | Food, medicine, plants, animals, currency, jewelry, alcohol, tobacco, weapons, and culturally protected items. |
|---|
| Key condition/packaging | Licenses, temperature controls, permits, value declarations, and special packaging may apply. |
|---|
| Transport limitation | Origin, transit, and destination laws must all permit movement. |
|---|
| Possible tracking/delivery impact | Inspection, quarantine, document request, abandonment, return, or seizure. |
|---|
| Official rules | Check JND acceptance terms and government import and export requirements. |
|---|
|
Customer Service
Use the official JND website for carrier information and the seller for order-level remedies. If tracking identifies a destination carrier, that carrier is usually the operational contact for a local delivery attempt or pickup.
Customer Service
| Channel | Verified contact/link |
| JND official website | http://www.jndcargo.com/ |
View contact preparation for JND| Best for | Carrier information and links provided by JND. |
|---|
| Region/language | Use the region and language options presented on the official website. |
|---|
| Hours and time zone | Use operating information displayed by the selected official contact channel. |
|---|
| Information to prepare | Tracking number, ship date, sender and recipient details, service, last scan, contents, value evidence, and photos where relevant. |
|---|
| Important limitation | The website does not replace the seller’s responsibility for refunds or replacements. |
|---|
|
| Seller or marketplace support | Use the support link attached to the original order. |
View seller-support preparation| Best for | Correct tracking number, dispatch proof, transport investigation, reshipment, refund, or buyer-protection dispute. |
|---|
| Region/language | Depends on the seller or marketplace account. |
|---|
| Hours and time zone | Use the support information displayed in the order account. |
|---|
| Information to prepare | Order number, payment record, JND tracking number, promised delivery window, screenshots, and correspondence. |
|---|
| Important limitation | The seller may need to contact JND as the contracting shipper. |
|---|
|
| Destination carrier | Use the carrier name and verified link shown after destination acceptance. |
View destination-carrier preparation| Best for | Local delivery attempt, pickup, delivery evidence, access issue, or final-mile exception. |
|---|
| Region/language | Destination country or region. |
|---|
| Hours and time zone | Use the destination carrier’s current local contact information. |
|---|
| Information to prepare | Original and local tracking numbers, address, delivery date, event text, and identification where required. |
|---|
| Important limitation | The destination carrier may require the sender to authorize an address change or claim. |
|---|
|
Ecommerce and Business Tracking
Businesses can use 17TRACK’s documented multi-carrier API to register tracking numbers and build normalized shipment visibility. Merchant systems should retain the original JND number, order ID, service, promised window, and any partner number as separate fields.
Developer/API Comparison
| Option | Provider |
| Consumer tracking | 17TRACK |
View consumer tracking details| Carrier coverage | Multi-carrier tracking through the 17TRACK interface. |
|---|
| Primary use | Manual lookup of shipment events. |
|---|
| Authentication | Interactive website access. |
|---|
| Tracking/batch/webhook capability | Use developer products rather than the consumer page for system integration. |
|---|
| Current developer documentation | 17TRACK API documentation |
|---|
| Migration/deprecation note | Implement the version and endpoint described in the current documentation. |
|---|
|
| Multi-carrier tracking API | 17TRACK |
View 17TRACK API details| Carrier coverage | Multiple carriers through one integration. |
|---|
| Primary use | Registration, centralized visibility, normalized events, and merchant shipment monitoring. |
|---|
| Authentication | The registration example uses the 17token request header. |
|---|
| Tracking/batch/webhook capability | Use the documented API capabilities and account entitlement for production design. |
|---|
| Current developer documentation | 17TRACK API documentation |
|---|
| Migration/deprecation note | Pin the documented API version and review current documentation before deployment. |
|---|
|
| Direct JND integration | JND |
View direct integration guidance| Carrier coverage | Use only JND endpoints and credentials supplied through an authorized JND integration arrangement. |
|---|
| Primary use | Direct carrier operations where contractual technical access is provided. |
|---|
| Authentication | Implement only the authentication method supplied in current JND technical documentation. |
|---|
| Tracking/batch/webhook capability | Do not assume endpoint, batch, or webhook behavior from unrelated carriers. |
|---|
| Current developer documentation | JND official website |
|---|
| Migration/deprecation note | Validate version and lifecycle directly with JND before implementing or migrating an integration. |
|---|
|
FAQ
1. How do I track my JND package?Enter the carrier tracking number on 17TRACK and select JND if carrier detection is inconclusive. Read the latest event, timestamp, location, and named carrier together.
2. Where can I find my JND tracking number?Look in the seller’s dispatch email, marketplace order page, shipping label, receipt, or shipment manifest. If only an order number appears, ask the seller for the carrier tracking number.
3. What does a JND tracking number look like?Use the complete alphanumeric value identified as the carrier number in the shipment record. Do not infer a JND service from a prefix or length alone.
4. When will the first JND tracking update appear?The first physical update appears after collection, drop-off, or facility induction is scanned. Label creation may occur earlier and does not prove that the parcel has been handed over.
5. Why is my JND tracking not updating?A gap may reflect consolidation, line-haul movement, customs processing, partner transfer, backlog, or a missed scan. Identify the last physical event and compare elapsed time with the shipment-specific delivery window.
6. How long does JND delivery take?Use the delivery window attached to the purchased service and route. Order placement, label creation, physical acceptance, customs release, and final delivery are different milestones.
7. What should I do after a failed JND delivery attempt?Follow the verified instructions from the named destination carrier and act before return processing begins. The sender may need to authorize an address correction or rerouting request.
8. What should I do if JND tracking says delivered but I have no package?Check the delivery location, household members, reception, locker, safe place, and neighbors where appropriate, then request delivery evidence from the last-mile carrier and notify the seller promptly.
9. How do I report a lost or damaged JND shipment?Preserve the label, packaging, contents, photos, invoice, and tracking history, then ask the contracting sender to open the applicable investigation or claim. Use the seller’s process separately for a refund or replacement.
10. How do I contact JND?Use the JND official website. Prepare the tracking number, shipment date, service, addresses, latest scan, contents description, value evidence, and photos where relevant.
11. Why can a destination carrier track a JND shipment under another number?A destination carrier may issue or expose a local identifier when it receives pre-advice or accepts the parcel. Track both identifiers because the local number may provide more detailed final-mile scans.
12. Does partner pre-advice mean the partner physically has my JND parcel?No. Pre-advice means shipment data was sent electronically; physical custody transfers only when tender and acceptance occur, preferably supported by a receiving scan.
13. Does arrival at customs mean my JND shipment has cleared customs?No. Arrival, presentation, assessment, inspection, tax processing, and release are separate stages. Wait for an explicit release or onward-processing event and respond to verified document requests.
14. Can a JND delivery estimate be treated as a guarantee?Only an express guarantee in the purchased service terms creates a guaranteed commitment and remedy. A tracking estimate or seller delivery window is normally planning information, not proof of a guaranteed service.
15. Can businesses track JND shipments through an API?Businesses can use the documented 17TRACK multi-carrier API and retain JND as the carrier identity when appropriate. A direct JND integration should be implemented only with current endpoint and credential documentation supplied through an authorized JND arrangement.
Tracking API
The example below uses the documented 17TRACK registration endpoint. The JND carrier code is left as a placeholder so that an unverified code is not submitted. Confirm the current carrier code and API behavior in the 17TRACK API documentation before production use.
# 1. JND official tracking API
# Implement a direct JND endpoint only with current technical documentation
# and credentials supplied through an authorized JND arrangement.
# No assumed JND endpoint is included here.
# 2. 17TRACK multi-carrier API
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 CARRIER_CODE only after confirming the current JND carrier code
# in 17TRACK documentation or your authorized 17TRACK account.
Sources & References
17TRACK is an independent tracking platform and is not affiliated with JND.