At a glance
JD Logistics SLA Compliance is the share of your JD-Logistics-enabled orders that hit JD’s headline delivery promise, the 24-hour same-day-doorstep standard that Chinese buyers expect from the JD brand. It is the single most watched fulfilment signal on the platform because JD’s reputation is built on logistics, not price. Drift below the 95% line and you risk losing Premium Buyer (PLUS) eligibility, search ranking weighting, and the Logistics axis of your DSR (detailed seller rating). This card sits in the Fulfilment family and reads best alongside the Pending Shipment backlog, the POP self-fulfilled dispatch rate, and the Logistics DSR threshold cards listed below.
| What it counts | The percentage of orders routed through JD Logistics (warehoused-by-JD or JD-pickup) that met the committed delivery window, typically the 24-hour same-day or next-day doorstep promise, within the period. |
| Sample type | Backend API data from JD.com, refreshed on the standard data refresh. |
| Why it matters | JD’s whole value proposition to Chinese shoppers is speed. Falling below the promise window erodes the Logistics DSR, removes the order from Premium Buyer guarantees, and quietly demotes your listings in search. A compliance dip is an early warning of a warehouse or carrier problem before reviews turn negative. |
| Reading the value | Read it as a gauge against the 95% floor. Above 98% is healthy, 95% to 98% is a watch zone, below 95% is action territory. Compare the 30-day figure to the prior period to catch a slide before it becomes a trend. |
| Currency | percent |
| Time window | 30D vsP |
| Alert trigger | <95% (24h-promise breach) |
| Sentiment key | jd_logistics_sla_compliance |
| Roles | owner, operations |
Calculation
Compliant JD-Logistics orders divided by total JD-Logistics orders in the window, expressed as a percentage. An order is compliant when the delivery scan lands inside the promised window for the buyer’s province (same-day for in-network metros, next-day or 24-hour for most of the rest). Orders that miss the window, whether through late merchant handover, warehouse delay, or carrier exception, count against the rate. Cross-border and POP self-fulfilled orders are excluded here because they run on a different SLA, the POP self-fulfilled dispatch rate card covers those.Worked example
A representative reading of JD Logistics SLA Compliance for a typical merchant on JD.com. Say 4,000 of your 4,200 JD-Logistics orders in the last 30 days were delivered inside the promised window. That is 95.2%, just inside the floor and down from 97.8% the prior period. The gauge sits amber and the vs-prior arrow points down. Drilling in, the misses cluster in two inland provinces where a regional carrier ran behind during a festival surge, and a handful trace to late evening handovers from your own warehouse missing the cut-off scan. Two fixes follow: move the handover cut-off earlier so orders make the same-day truck, and check whether those inland provinces should fall back to next-day rather than same-day promises. For deeper investigation, use Vortex Mind to trace the misses by province and carrier; for natural-language exploration, ask Ask Viq “which provinces breached the 24-hour promise last week”.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
jdc_pending_ship | Fulfilment sibling: a backlog of paid-but-unshipped orders is the leading cause of SLA breaches. |
jdc_pop_dispatch_rate | Fulfilment sibling: the parallel speed metric for orders you ship yourself rather than via JD Logistics. |
jdc_late_dispatch_dsr | Fulfilment sibling: late dispatches that directly threaten the Logistics DSR axis. |
jdc_dsr_threshold | Reputation sibling: the DSR/SLA threshold-crossed alert that this rate feeds. |
jdc_orders_per_day | Fulfilment sibling: order volume context for interpreting a compliance dip. |
Reconciling against the vendor’s own dashboard
Where to look in JD.com’s own dashboard: In JD’s Seller Centre (商家后台), this lives under the logistics and fulfilment performance reports, usually as a timeliness or on-time delivery rate alongside the Logistics DSR. Confirm the report is scoped to JD-Logistics orders only and that the date range matches the Vortex IQ 30-day window. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Promise window definition. JD may blend same-day and 24-hour promises by province; Vortex IQ reports against the committed window per order. | Variable | Confirm whether the vendor report uses a single flat window or per-province promises. |
| Period boundary. Vortex IQ uses a 30-day rolling window; the Seller Centre often defaults to calendar weeks or months. | Variable | Match the date range before comparing. |
| Order scope. JD reports may fold in POP or cross-border orders; this card isolates JD-Logistics fulfilment. | Variable | Exclude POP and cross-border in the vendor filter. |
| Time zone. JD reports in China Standard Time; confirm your reporting profile aligns. | Marginal | Confirm time zone match. |