At a glance
Late Dispatches Risking DSR-Logistics counts the orders that have already passed their JD ship deadline and are now dragging on the Logistics axis of your detailed seller rating. JD sets buyer expectations around fast fulfilment - the JD Logistics 24-hour same-day-to-doorstep promise is a core part of the platform’s brand - so every order that ships late is a direct hit to the Logistics DSR axis and, through it, to your search placement. This card is the actionable backlog: the specific orders to dispatch right now before the rating damage compounds.
| What it counts | Open orders whose JD ship deadline has already elapsed without a dispatch scan, each of which is actively eligible to lower the Logistics axis of your DSR. |
| Sample type | Real-time order-level feed from the JD.com integration, comparing each order’s ship deadline against its current dispatch status. |
| Why it matters | The Logistics DSR axis governs buyer trust and search placement. A run of late dispatches pushes the axis toward the 4.5 safe-band floor, which can trigger the account-health tripwire and reduce visibility just as buyers are searching. |
| Reading the value | Any value above zero is a live backlog. Open the alert list to see each late order, how far past deadline it is, and which province it ships to, then prioritise the oldest first. |
| Currency | count |
| Time window | RT |
| Alert trigger | any order past ship_deadline |
| Sentiment key | jd_alert_dispatch_sla_miss |
| Roles | owner, operations |
Calculation
For every open POP self-fulfilled order, the card compares the JD-assigned ship deadline against the order’s current dispatch status. An order counts as a late dispatch when the deadline has passed and no valid dispatch scan has been recorded. The displayed value is the total count of such orders at refresh time. Orders fulfilled through JD Logistics (JD’s own warehousing and last-mile network) are handled to JD’s standard and are excluded from the seller-attributable count; this card focuses on the POP self-fulfilled orders where the seller controls dispatch and therefore carries the DSR-Logistics risk. The alert list orders entries by how far each is past deadline so the most damaging are cleared first.Worked example
A representative reading for a POP self-fulfilled seller on JD.com. At 09:00 on 18 Mar 26 the card reads 7. The alert list shows seven orders past their ship deadline: four are 2 to 6 hours late after a packing-line delay, two are a full day late and bound for Sichuan and Yunnan provinces where transit is already long, and one has been sitting for 36 hours because the SKU was oversold. The team triages: ship the six packable orders immediately to stop further axis erosion, and for the oversold SKU contact the buyer and arrange a substitution or refund before a dispute is opened. By midday the card reads 1, with only the oversold order outstanding. Watch the linked Logistics DSR axis over the following days to confirm it holds above 4.5. To trace why the packing line fell behind, use Vortex Mind; to ask which provinces see the most late dispatches in plain English, use Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
jd_dsr_summary | Shows the Logistics axis these late orders are eroding. |
jd_logistics_sla | The aggregate SLA figure that late dispatches pull down. |
jd_pop_dispatch_rate | The on-time dispatch rate for the orders you control. |
jd_pending_shipment | The full open-shipment queue, before deadlines elapse. |
jd_account_health | The tripwire that fires if late dispatches push the axis below 4.5. |
Reconciling against the vendor’s own dashboard
Where to look in JD.com’s own dashboard: JD surfaces overdue orders in the order-management area, typically under a pending-shipment or overdue-dispatch view, and the resulting impact in the logistics-performance section of the seller scorecard. Confirm you are looking at POP self-fulfilled orders rather than JD Logistics orders, since the two have different deadline rules. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Scan latency. A courier dispatch scan may not have synced to JD when Vortex IQ refreshed. | Vortex IQ higher | Allow for scan-sync lag before counting an order late. |
| Deadline timezone. Ship deadlines are set in JD’s account time zone; confirm the profile aligns. | Marginal | Match the reporting time zone. |
| Fulfilment scope. Vortex IQ excludes JD Logistics orders from the seller-attributable count; the vendor view may show all. | Vortex IQ lower | Filter to POP self-fulfilled orders. |