About JL
JL is the carrier identity associated with the supplied official website. Use the shipment identifier supplied by the sender or merchant to check available tracking events. Operational scope, named services, corporate details and partner arrangements should be taken from the shipment record or a current response from JL rather than inferred from the website address.
JL Overview
| Field | Verified entry |
| Official display name | JL |
| Official website | http://jinliexpress.cn/ |
| Tracking input | The shipment identifier issued or supplied for the parcel |
Carrier Entity Relationships
| Entity | Relationship |
| JL | JL is the canonical carrier identity used on this page. |
View all details for the JL carrier identity
| Entity type | Carrier identity |
| Why it matters to tracking | Selecting the correct carrier helps prevent a valid shipment number from being queried against an unrelated network. |
| Official evidence | Official website supplied for JL |
|
| Shipment identifier | A sender, merchant or logistics system supplies the identifier used to retrieve shipment events. |
View all details for the shipment identifier
| Entity type | Tracking product |
| Why it matters to tracking | An order number or payment reference may not retrieve carrier scans. |
| Official evidence | The applicable identifier is the one shown in the shipment confirmation, label or dispatch record. |
|
| 17TRACK | 17TRACK independently aggregates tracking events that participating data sources make available for JL shipments. |
View all details for the 17TRACK relationship
| Entity type | Independent tracking platform |
| Why it matters to tracking | 17TRACK can present available events but does not transport parcels, change addresses, release customs items or decide claims. |
| Official evidence | 17TRACK tracking platform |
|
Quick Answer
Enter the shipment identifier exactly as supplied by the sender on the JL website or use 17TRACK. If no result appears, first remove accidental spaces, confirm that the identifier is not an order number, and allow time for the first physical acceptance scan.
Pro Tip: A label or electronic shipment record can exist before JL physically receives the parcel. Contact the sender first when tracking remains at a pre-shipment stage.
17TRACK is an independent tracking platform. It cannot transport the parcel, change delivery instructions, approve a refund or decide a loss or damage claim.
How to Track JL Packages
Use either the official JL website or 17TRACK, and submit the shipment identifier rather than a store order number.
- Copy the identifier from the dispatch email, shipping label, receipt or merchant order page.
- Open the official JL website and locate its tracking function, or open 17TRACK.
- Paste the identifier without added punctuation or surrounding spaces.
- Review the latest event, event time, location and current delivery stage together.
- If the result is empty, compare the identifier with the original label and ask the sender to confirm the carrier and physical handoff date.
Where to Find the Correct Identifier
| Identifier | How to use it |
| Tracking number | Use this first for parcel tracking. |
| Order number | Use it with the merchant; it may not retrieve carrier events. |
| Merchant reference | Ask the merchant to map it to the shipment identifier. |
| Last-mile number | Use it if the shipment record explicitly identifies a separate final-delivery number. |
Tracking Statuses and Meanings
Read a status together with its timestamp and location. The following lifecycle interpretations are decision aids; the exact event text shown in the shipment record controls.
Status Quick Lookup
| Status | What it means |
| Shipment information received | An electronic record exists, but physical acceptance may still be pending. |
View all details for shipment information received| Lifecycle stage | Pre-shipment |
|---|
| Current responsible party | The sender remains responsible for completing the physical handoff until an acceptance event appears. |
|---|
| What happens next | A collection, acceptance or processing scan should follow. |
|---|
| What you should do | Ask the sender to confirm the handoff if the status does not progress. |
|---|
|
| Accepted or received | The parcel has entered the network represented by the event. |
View all details for accepted or received| Lifecycle stage | Accepted |
|---|
| Current responsible party | The network named in the event. |
|---|
| What happens next | Sorting or departure processing. |
|---|
| What you should do | Monitor the next scan unless the expected delivery window is exceeded. |
|---|
|
| In transit or departed facility | The parcel is moving between processing points or awaiting the next scan. |
View all details for in transit| Lifecycle stage | In transit |
|---|
| Current responsible party | The line-haul or processing network holding the parcel. |
|---|
| What happens next | An arrival, processing or handoff event. |
|---|
| What you should do | Compare the gap with the route and expected delivery window before escalating. |
|---|
|
| Customs or clearance processing | The shipment is undergoing a border-related review or awaiting information, assessment or release. |
View all details for customs or clearance processing| Lifecycle stage | Customs and handoff |
|---|
| Current responsible party | The border authority, broker or logistics party identified in the event. |
|---|
| What happens next | Release, a request for information, payment assessment or return decision. |
|---|
| What you should do | Respond only through a verified channel if documents or charges are requested. |
|---|
|
| Out for delivery | The local delivery unit has assigned the parcel to a delivery route. |
View all details for out for delivery| Lifecycle stage | Out for delivery |
|---|
| Current responsible party | The local delivery operation. |
|---|
| What happens next | Delivery, an attempted delivery or another exception event. |
|---|
| What you should do | Keep the address accessible and follow verified delivery instructions. |
|---|
|
| Delivered | A final-delivery scan was recorded at the stated time or location. |
View all details for delivered| Lifecycle stage | Delivered |
|---|
| Current responsible party | The local delivery operation records the event; the recipient should verify the delivery location. |
|---|
| What happens next | The shipment lifecycle usually closes unless a delivery dispute is opened. |
|---|
| What you should do | Check the mailbox, entrance, reception, household members and safe locations before reporting non-receipt. |
|---|
|
| Delivery exception or attempt | Delivery could not be completed because of an address, access, recipient or operational issue. |
View all details for a delivery exception| Lifecycle stage | Exception |
|---|
| Current responsible party | The delivery operation manages the next attempt or hold; the sender or recipient may need to provide information. |
|---|
| What happens next | Reattempt, pickup, correction or return. |
|---|
| What you should do | Follow the exact instruction shown in tracking and verify requests through an official channel. |
|---|
|
| Returning to sender | The parcel has entered a reverse movement toward the sender. |
View all details for returning to sender| Lifecycle stage | Return |
|---|
| Current responsible party | The network carrying the return. |
|---|
| What happens next | Reverse processing and delivery to the return address. |
|---|
| What you should do | The buyer should contact the merchant; the sender should monitor the return and decide replacement or refund handling. |
|---|
|
Services and Delivery Times
Use the service name and delivery estimate shown in the booking or shipment record. A tracking estimate is a planning value unless the purchased terms explicitly identify a guarantee.
Service Comparison
| Service | Best for |
| Service named on the JL shipment record | The parcel, route and service level booked by the sender. |
View all details for the booked JL service
| Service type | Use the exact type stated in the booking confirmation. |
| Coverage | The origin and destination accepted in the shipment record. |
| Tracking level | Depends on scans supplied for the booked route and any handoff stages. |
| Key size/weight condition | The sender should verify the booked shipment against the applicable acceptance rules. |
| Included protection/extra service | Only the protection or add-on stated in the sender’s contract or booking applies. |
| Main limitation | The tracking page alone does not establish contractual service terms. |
|
Delivery Time
| Service | Published delivery standard |
| Booked JL service | Use the shipment-specific estimate or contractual service terms supplied at booking. |
View all delivery-time details for the booked JL service
| Business or calendar days | Apply the day-count convention stated in the booking terms. |
| Guarantee status | Treat the date as an estimate unless the purchased terms explicitly state a guarantee and its remedies. |
| Starts counting from | Use the contractual start event, commonly physical acceptance rather than label creation. |
| Main delay factors | Late handoff, routing, weekends, holidays, weather, address quality, customs review and partner transfers can affect delivery. |
| Official source date/validity | Confirm against the terms attached to the current shipment booking. |
|
Destination Country Delivery Times
| Destination Country / Region | Estimated Delivery Time Range |
| Destination shown in the shipment record | Use the route-specific estimate attached to the shipment rather than a generic country average. |
View all destination delivery details
| Primary Service Type | The exact service selected by the sender. |
| Average Delivery Days | Assess from the shipment-specific estimate and comparable completed shipments using the same route and service. |
| Last-Mile Partner / Handoff Carrier | Use the carrier named in the latest handoff event, if one appears. |
| Customs & Clearance Tips | Ensure recipient details, contents descriptions, values and requested documents are accurate; a border-arrival scan does not mean customs release. |
|
Country-level transit averages should not be invented when route, service, acceptance date and historical scan evidence are absent. For a useful estimate, compare shipments with the same origin, destination, service level and handoff pattern.
Common Tracking Problems and Solutions
Start with the latest event, responsible party and physical handoff status. Escalation timing should follow the purchased service terms and the shipment-specific delivery window.
Problem & Solution
| Problem/status shown | Immediate action |
| Invalid number or no result | Copy the identifier again, remove surrounding spaces and confirm it is a tracking number rather than an order reference. |
View all details for an invalid number or no result| Likely cause | Typing error, wrong identifier type, early data submission or incorrect carrier selection. |
|---|
| Check first | The dispatch email, label or merchant shipment page. |
|---|
| When to escalate | When the sender states that physical handoff occurred but the identifier still cannot be validated. |
|---|
| Who to contact | The sender or merchant first. |
|---|
|
| Shipment information received only | Ask the sender whether the physical parcel has been handed over. |
View all details for shipment information received only| Likely cause | A label or electronic record was created before acceptance. |
|---|
| Check first | Whether any acceptance or facility event follows the initial record. |
|---|
| When to escalate | After the sender’s stated handoff time has passed without an acceptance event. |
|---|
| Who to contact | The sender. |
|---|
|
| Long gap or stuck in transit | Check the route, weekends, holidays, customs stage and whether a handoff is underway. |
View all details for a long tracking gap| Likely cause | Movement without intermediate scans, backlog, transport disruption or partner transfer. |
|---|
| Check first | The most recent physical location and the shipment-specific delivery window. |
|---|
| When to escalate | When the stated delivery window has passed or the event requests action. |
|---|
| Who to contact | The sender for a transport inquiry; use the current custodian if the event names one. |
|---|
|
| Address or delivery exception | Follow the instruction in tracking and verify the complete address with the sender. |
View all details for an address or delivery exception| Likely cause | Incomplete address, inaccessible location, recipient absence or local operational issue. |
|---|
| Check first | Postal code, unit number, recipient name and any attempted-delivery instruction. |
|---|
| When to escalate | Immediately if the event requires information or the parcel is entering return processing. |
|---|
| Who to contact | The current delivery party and the sender. |
|---|
|
| Customs hold | Check for a verified request for documents, recipient identification, declaration details or payment. |
View all details for a customs hold| Likely cause | Routine review, missing information, valuation, restricted goods review or assessed import charges. |
|---|
| Check first | The exact event and any verified notice. |
|---|
| When to escalate | When a response deadline is stated or the responsible authority requests action. |
|---|
| Who to contact | The broker, border authority or logistics contact named in the verified notice. |
|---|
|
| Delivered but not received | Check every delivery location, household member, reception desk and nearby safe place before opening a dispute. |
View all details for delivered but not received| Likely cause | Safe-location delivery, reception by another person, location mismatch or an incorrect final scan. |
|---|
| Check first | Delivery time, address, mailbox, entrance, reception, household members and any delivery evidence. |
|---|
| When to escalate | Promptly after local checks fail. |
|---|
| Who to contact | The local delivery party shown in tracking and the sender or merchant. |
|---|
|
| Lost or damaged parcel | Preserve the parcel, contents, packaging, label, photos and proof of value; ask the sender to start the applicable inquiry. |
View all details for a lost or damaged parcel| Likely cause | Transport loss, damage, missing contents or delivery dispute. |
|---|
| Check first | The purchased protection, merchant policy and booking terms. |
|---|
| When to escalate | Within the filing window stated in the applicable contract or merchant policy. |
|---|
| Who to contact | The sender for a carrier claim and the merchant for the purchase remedy. |
|---|
|
International Shipping, Customs and Carrier Handoffs
When a JL shipment crosses a border, tracking may include electronic pre-advice, export processing, line-haul, import review and a final-delivery handoff. Physical custody changes only when the parcel is actually transferred, not merely when electronic data is sent.
International Flow
| Stage | What is happening |
| Electronic pre-advice | Shipment data is created before or around physical handoff. |
View all details for electronic pre-advice| Physical custodian/responsible entity | The sender may still hold the parcel. |
|---|
| Typical tracking event | Shipment information received. |
|---|
| Can the tracking number change? | A partner identifier may later be linked. |
|---|
| Normal visibility gap | Until the first physical scan. |
|---|
| What the customer should do | Confirm handoff with the sender if no acceptance event follows. |
|---|
|
| Origin acceptance and export processing | The parcel is received, sorted and prepared for international movement. |
View all details for origin processing| Physical custodian/responsible entity | The origin logistics network named in tracking. |
|---|
| Typical tracking event | Accepted, processed or departed origin facility. |
|---|
| Can the tracking number change? | The original identifier may continue while additional identifiers are linked. |
|---|
| Normal visibility gap | Between processing and the next gateway scan. |
|---|
| What the customer should do | Monitor unless an exception requests action. |
|---|
|
| Export review and line-haul | Security, export formalities and transport to the destination region occur. |
View all details for export review and line-haul| Physical custodian/responsible entity | The export processor or line-haul operator. |
|---|
| Typical tracking event | Export processing, departure or transport event. |
|---|
| Can the tracking number change? | Operational references may be added without replacing the customer-facing identifier. |
|---|
| Normal visibility gap | Movement may occur without public intermediate scans. |
|---|
| What the customer should do | Use the delivery window and latest physical event to judge progress. |
|---|
|
| Import processing and customs | The shipment reaches the destination gateway and may undergo import review. |
View all details for import processing and customs| Physical custodian/responsible entity | The gateway operator, broker or border authority according to the event. |
|---|
| Typical tracking event | Arrival at destination, clearance processing or release. |
|---|
| Can the tracking number change? | A destination identifier may be associated with the shipment. |
|---|
| Normal visibility gap | Review periods may have limited public scans. |
|---|
| What the customer should do | Respond to verified requests for documents or charges; do not treat destination arrival as customs release. |
|---|
|
| Partner handoff | Electronic pre-advice, physical transfer and the receiving party’s first scan can occur at different times. |
View all details for partner handoff| Physical custodian/responsible entity | Custody remains with the dispatching party until physical transfer is completed. |
|---|
| Typical tracking event | Handoff prepared, tendered or received. |
|---|
| Can the tracking number change? | A linked local-delivery identifier may appear. |
|---|
| Normal visibility gap | Between dispatch, physical receipt and the first local scan. |
|---|
| What the customer should do | Check both identifiers when the shipment record explicitly supplies them. |
|---|
|
| Final delivery | The destination delivery operation sorts the parcel and attempts delivery or pickup. |
View all details for final delivery| Physical custodian/responsible entity | The delivery party identified by the latest local event. |
|---|
| Typical tracking event | Received locally, out for delivery, attempted or delivered. |
|---|
| Can the tracking number change? | The local identifier may become the most useful number for delivery support. |
|---|
| Normal visibility gap | Between gateway release and local induction. |
|---|
| What the customer should do | Follow local delivery instructions and retain both identifiers. |
|---|
|
Delivery Management and Post-shipment Options
A delivery change is valid only when offered for the specific shipment through a verified JL or current-delivery-party channel. Tracking visibility does not itself create a right to reroute, intercept or hold a parcel.
Delivery Management
| Option | Who can request |
| Address correction or rerouting request | The sender should initiate the request unless the shipment-specific delivery channel authorizes the recipient. |
View all details for an address correction or rerouting request| Eligibility | Depends on service, identity checks, shipment restrictions and current processing stage. |
|---|
| Deadline/available stage | Request before final delivery or return processing begins. |
|---|
| Fee | Apply the fee shown by the verified service channel. |
|---|
| Guaranteed? | No; operational acceptance is required. |
|---|
| Official action link | JL official website |
|---|
|
| Redelivery, pickup or delivery instruction | The eligible recipient or sender shown by the shipment-specific delivery channel. |
View all details for redelivery, pickup or delivery instructions| Eligibility | Depends on the attempted-delivery event and current custodian. |
|---|
| Deadline/available stage | Follow the deadline stated in the delivery notice or tracking event. |
|---|
| Fee | Use the charge, if any, shown in the verified channel. |
|---|
| Guaranteed? | No; capacity, identity and access conditions may apply. |
|---|
| Official action link | JL official website |
|---|
|
Lost, Damaged, Claims, Insurance and Refunds
A tracking inquiry, transport investigation, insurance claim and merchant refund are separate processes. The sender usually holds the carrier contract, while the buyer normally seeks a purchase remedy from the merchant.
Claims and Refunds
| Process | Use when |
| Tracking inquiry or transport investigation | Use when scans stop, the delivery window passes or the shipment has an unresolved exception. |
View all details for a tracking inquiry| Who files | The sender should generally open the carrier-side inquiry; the recipient can supply delivery facts. |
|---|
| Earliest/latest filing time | Follow the current booking terms and shipment-specific support instructions. |
|---|
| Required evidence | Tracking number, shipping date, service, addresses, contents description and last event. |
|---|
| Possible outcome | Status clarification, trace, request for evidence or claim guidance. |
|---|
| Official link | JL official website |
|---|
|
| Loss, damage or missing-contents claim | Use when covered loss or physical damage is alleged under the purchased service terms. |
View all details for a loss or damage claim| Who files | The contracting sender or another party authorized by the applicable terms. |
|---|
| Earliest/latest filing time | Use the filing window stated in the purchased service contract. |
|---|
| Required evidence | Tracking record, value proof, photos, contents details, packaging and label; retain all materials until the case closes. |
|---|
| Possible outcome | Investigation, request for more evidence, settlement or denial under the applicable terms. |
|---|
| Official link | JL official website |
|---|
|
| Merchant refund or replacement | Use when a buyer seeks a remedy under the sales agreement. |
View all details for a merchant refund or replacement| Who files | The buyer contacts the merchant or marketplace. |
|---|
| Earliest/latest filing time | Follow the merchant’s purchase-protection deadline. |
|---|
| Required evidence | Order number, tracking record, delivery dispute details, photos and correspondence. |
|---|
| Possible outcome | Replacement, refund, investigation or denial under the sales policy. |
|---|
| Official link | Use the support channel attached to the purchase record. |
|---|
|
17TRACK cannot approve a claim, refund postage, replace an item or change the outcome of a transport investigation.
Shipping Restrictions and Special Handling
The sender must verify the current rules for the booked service, transport mode, origin, destination and contents before tendering a shipment. The summary below is general risk guidance rather than a complete acceptance rule.
Shipping Restrictions
| Category | Prohibited or restricted |
| Dangerous or hazardous materials | May be prohibited or accepted only under service-specific transport rules. |
View all details for dangerous or hazardous materials| Typical examples | Flammable, explosive, corrosive, toxic or pressurized materials. |
|---|
| Key condition/packaging | Classification, documentation, approved packaging and service eligibility may apply. |
|---|
| Transport limitation | Transport mode and route restrictions can prevent acceptance. |
|---|
| Possible tracking/delivery impact | Inspection, rejection, hold or return. |
|---|
| Official rules | JL official website |
|---|
|
| Batteries, liquids and powered devices | Commonly subject to classification, packaging, quantity and routing conditions. |
View all details for batteries, liquids and powered devices| Typical examples | Rechargeable cells, devices containing batteries, aerosols and liquid products. |
|---|
| Key condition/packaging | Prevent short circuits, leakage, accidental activation and movement inside the package. |
|---|
| Transport limitation | Some routes or modes may exclude the item. |
|---|
| Possible tracking/delivery impact | Security screening, routing change, rejection or return. |
|---|
| Official rules | JL official website |
|---|
|
| Perishable, regulated or high-risk goods | May require permits, temperature controls, special packaging or prior acceptance. |
View all details for perishable, regulated or high-risk goods| Typical examples | Food, biological material, medicine, plants, valuables or controlled goods. |
|---|
| Key condition/packaging | Comply with origin, transit and destination requirements. |
|---|
| Transport limitation | Route, storage and border controls can limit carriage. |
|---|
| Possible tracking/delivery impact | Inspection, document request, delay, seizure or return. |
|---|
| Official rules | JL official website |
|---|
|
Customer Service
Start with the sender for pre-shipment, booking, address and claim issues. Use the current physical custodian for delivery-stage questions when the tracking record identifies that party.
Customer Service
| Channel | Verified contact/link |
| Official website | http://jinliexpress.cn/ |
View all details for the JL official website| Best for | Checking current official tracking and support options presented by JL. |
|---|
| Region/language | Use the options presented on the website. |
|---|
| Hours and time zone | Follow any hours stated on the current contact channel. |
|---|
| Information to prepare | Tracking number, shipping date, service, sender and recipient addresses, latest scan and issue description. |
|---|
| Important limitation | Verify contact details on the official website before sharing personal or payment information. |
|---|
|
| Sender or merchant | Use the support channel attached to the order or shipping confirmation. |
View all details for sender or merchant support| Best for | Missing tracking numbers, label-only status, booking corrections, purchase disputes and carrier claims. |
|---|
| Region/language | The order’s sales channel. |
|---|
| Hours and time zone | Follow the merchant’s published support schedule. |
|---|
| Information to prepare | Order number, tracking number, payment record, delivery address and supporting images. |
|---|
| Important limitation | The merchant may need to contact JL as the contracting shipper. |
|---|
|
For efficient escalation, prepare the shipment identifier, order reference, dispatch date, service name, sender and recipient addresses, latest event, contents description, value evidence, packaging photos and damage photos where relevant.
Ecommerce and Business Tracking
Businesses should store the merchant order ID, customer-facing shipment identifier and any handoff identifier as separate fields. 17TRACK can support multi-carrier tracking workflows, while carrier-side operational requests remain with JL or the current delivery party.
Developer/API Comparison
| Option | Provider |
| Consumer shipment tracking | JL |
View all details for JL consumer shipment tracking| Carrier coverage | JL shipment records accepted by its official tracking interface. |
|---|
| Primary use | Manual lookup of individual shipments. |
|---|
| Authentication | Follow the current official interface. |
|---|
| Tracking/batch/webhook capability | Use only capabilities displayed in the current official interface or contract. |
|---|
| Current developer documentation | JL official website |
|---|
| Migration/deprecation note | Do not implement an endpoint copied from an undated third-party example. |
|---|
|
| Multi-carrier tracking API | 17TRACK |
View all details for the 17TRACK API| Carrier coverage | Multi-carrier tracking through supported carrier integrations. |
|---|
| Primary use | Registration, normalized tracking workflows and business shipment visibility. |
|---|
| Authentication | The request uses the 17token header. |
|---|
| Tracking/batch/webhook capability | Use the capabilities and limits documented for the selected API product. |
|---|
| Current developer documentation | 17TRACK API documentation |
|---|
| Migration/deprecation note | Use the current documented API version and review change notices before deployment. |
|---|
|
FAQ
1. How do I track my JL package?Enter the shipment identifier on the official JL website or use 17TRACK to view available events. Copy the value from the dispatch record and remove only accidental surrounding spaces.
2. Where can I find my JL tracking number?Look in the dispatch email, shipping label, receipt or merchant shipment page. If only an order number appears, ask the merchant to provide the carrier-facing shipment identifier.
3. What does a JL tracking number look like?Use the complete identifier shown in the shipment record rather than relying on a guessed prefix or length. A merchant reference or partner number may look similar but serve a different system.
4. When will the first JL tracking event appear?The first physical event appears after acceptance or processing, while electronic shipment information may appear earlier. Ask the sender to confirm handoff when only pre-shipment information is shown.
5. Why is my JL tracking not updating?A tracking gap can occur during transport, backlog, customs review or a partner transfer. Check the latest physical event and shipment-specific delivery window before escalating.
6. How long does JL delivery take?Use the estimate attached to the booked service and route. Label creation, customs processing, weekends, holidays, address issues and handoffs can change the actual arrival date.
7. What should I do after a failed JL delivery attempt?Follow the instruction in the tracking event or delivery notice and verify the address and access details. Act before the parcel enters return processing.
8. What should I do if JL says delivered but I cannot find the parcel?Check the mailbox, entrance, reception, safe locations, household members and delivery address first. Then contact the local delivery party shown in tracking and notify the sender or merchant.
9. How do I report a lost or damaged JL shipment?Preserve the packaging, contents, label, photos and proof of value, then ask the sender to begin the applicable transport inquiry or claim. Buyers should separately follow the merchant’s refund or replacement process.
10. How do I contact JL?Use the current contact or tracking options presented on the official JL website. Prepare the tracking number, shipping date, addresses, service and latest event before contacting support.
11. Does an electronic JL shipment record mean JL has the parcel?No. Electronic data can be submitted before physical acceptance, so look for an acceptance or facility scan before assigning physical custody to JL.
12. Can a JL shipment have more than one tracking number?Yes, a merchant reference, carrier-facing identifier and handoff identifier can coexist. Keep each value in a separate field and use the one associated with the current transport stage.
13. Does arrival in the destination country mean a JL shipment cleared customs?No. Destination arrival, customs review and customs release are distinct events, and the parcel may still require documents, assessment or payment before onward movement.
14. Who is responsible during a JL partner handoff?The dispatching party retains physical custody until transfer occurs, and the receiving party normally assumes operational responsibility after receipt. Electronic pre-advice alone does not prove that the parcel changed hands.
15. Can businesses track JL shipments through an API?Businesses can use the 17TRACK multi-carrier API for supported shipment registration and tracking workflows. Confirm JL carrier support and the applicable carrier code in current 17TRACK documentation before production use.
16. Can 17TRACK change or refund a JL shipment?No. 17TRACK displays available tracking information but cannot reroute a parcel, approve a claim, refund postage or issue a merchant refund.
Tracking API
For a multi-carrier implementation, use the current 17TRACK API documentation. Confirm the current JL carrier code before registration; the placeholder below must not be deployed unchanged.
# 1. JL official tracking API
# Use only current endpoint, method and authentication details supplied
# directly through the official JL website or a current JL business agreement.
# 2. 17TRACK 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 JL code
# in the 17TRACK documentation or your 17TRACK account.
Sources & References
17TRACK is an independent tracking platform and is not affiliated with JL.