> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # POP Self-Fulfilled Dispatch Rate, JD.com > POP Self-Fulfilled Dispatch Rate for JD.com stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Marketplace](/nerve-centre/connectors#connectors-by-type) ## At a glance > **POP Self-Fulfilled Dispatch Rate** measures, for the orders you ship yourself rather than through JD Logistics, the share you dispatched inside JD's ship-deadline window. This is the speed metric you control directly. JD Direct (1P) and JD-Logistics orders are handled by JD, but for POP marketplace orders fulfilled in-house, JD holds you to a dispatch clock, and your hit rate against it feeds the Logistics axis of your DSR. Fall below roughly 90% and you are accumulating late dispatches, eroding ratings, and risking Premium Buyer eligibility. It sits in the Fulfilment family and reads best beside the pending-shipment, SLA, and late-dispatch cards below. | | | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | For POP orders the merchant self-fulfils, the percentage dispatched within JD's ship-deadline window during the period. | | **Sample type** | Backend API data from JD.com, refreshed on the standard data refresh. | | **Why it matters** | This is the fulfilment speed you fully own. It directly feeds the Logistics DSR, and a rate below the floor turns into late dispatches, weaker ratings, and lost Premium Buyer standing. It is the clearest read on whether your own warehouse is keeping its promises. | | **Reading the value** | Read the gauge against the 90% floor. Above 95% is healthy, 90% to 95% is a watch zone, below 90% is action territory. Compare the 30-day figure to the prior period to catch a slide early. | | **Currency** | percent | | **Time window** | `30D vsP` | | **Alert trigger** | `<90%` | | **Sentiment key** | `jd_pop_dispatch_rate` | | **Roles** | owner, operations | ## Calculation POP self-fulfilled orders dispatched within JD's ship-deadline divided by total POP self-fulfilled orders in the window, as a percentage. An order is on-time when its dispatch scan is recorded before the deadline JD sets for that order. Orders shipped after the deadline count against the rate; cancelled-before-dispatch orders drop out. JD Logistics and JD Direct (1P) orders are excluded, because JD, not you, controls their dispatch, the JD Logistics SLA card covers those. The result is a clean read on your own dispatch performance. ## Worked example *A representative reading of **POP Self-Fulfilled Dispatch Rate** for a typical merchant on JD.com.* Suppose 1,800 of your 2,000 self-fulfilled orders shipped before their deadline last 30 days. That is 90%, right on the floor and down from 94% the prior period. The gauge sits amber with a downward arrow. Cross-referencing pending-shipment shows a backlog that built during a promotion, and the late dispatches cluster on orders placed late in the day that missed the same-day handover cut-off. Two fixes follow: move the dispatch cut-off earlier so late-day orders still make the deadline, and add capacity during promotion peaks. Recovering the rate above 90% protects the Logistics DSR before it slips. For deeper investigation, use Vortex Mind to find the time-of-day pattern in late dispatches; for natural-language exploration, ask Ask Viq "what share of my self-fulfilled orders missed the JD ship-deadline last week". ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | | [`jdc_pending_ship`](/nerve-centre/kpi-cards/jd-com/pending-shipment) | Fulfilment sibling: the backlog that drives the dispatch rate down when it builds. | | [`jdc_late_dispatch_dsr`](/nerve-centre/kpi-cards/jd-com/late-dispatches-risking-dsr-logistics) | Fulfilment sibling: the late dispatches a sub-90% rate produces. | | [`jdc_logistics_sla`](/nerve-centre/kpi-cards/jd-com/jd-logistics-sla-compliance) | Fulfilment sibling: the parallel speed metric for JD-Logistics-fulfilled orders. | | [`jdc_orders_per_day`](/nerve-centre/kpi-cards/jd-com/orders-day) | Fulfilment sibling: daily intake context for interpreting a dispatch-rate dip. | | [`jdc_dsr_threshold`](/nerve-centre/kpi-cards/jd-com/dsr-brand-auth-logistics-sla-threshold-crossed) | Reputation sibling: the Logistics DSR threshold this rate feeds. | ## Reconciling against the vendor's own dashboard **Where to look in JD.com's own dashboard:** In JD's Seller Centre, the on-time dispatch or ship-rate metric under fulfilment performance is the direct equivalent, scoped to seller-fulfilled orders. Confirm the report isolates POP self-fulfilment (excluding JD Logistics and 1P) and that the period matches the Vortex IQ 30-day window. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | --------------------------------------------------------------------------------------------------------------------------------------- | --------- | ------------------------------------------------- | | **Dispatch vs delivery.** This card measures on-time dispatch, not on-time delivery; do not compare it against a delivery-based figure. | Variable | Confirm the vendor metric is dispatch-based. | | **Order scope.** Vortex IQ isolates POP self-fulfilment; JD reports may fold in JD Logistics orders. | Variable | Exclude JD Logistics and 1P in the vendor filter. | | **Deadline basis.** JD sets per-order ship-deadlines; ensure the vendor report uses the same deadline definition. | Variable | Confirm the deadline definition. | | **Period and time zone.** Vortex IQ uses a 30-day rolling window in China Standard Time. | Marginal | Match the date range and time zone. | **Cross-connector reconciliation:** read with pending-shipment to see whether a falling rate is caused by a backlog, and with the late-dispatch card to confirm the DSR impact. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does POP Self-Fulfilled Dispatch Rate update?** The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). Dispatch scans can lag the physical handover by a short window. For real-time signals, force a manual refresh from the dashboard. **Q: Why does my JD.com dashboard show a different number?** The common causes are dispatch-versus-delivery basis (this card is dispatch-based), order scope (whether JD Logistics and 1P orders are folded in), and the deadline definition. Match those three before assuming a real divergence. **Q: My delivery times look fine but this rate dropped. Why?** This card measures dispatch against the ship-deadline, not delivery. You can dispatch late but still have parcels arrive on time if the carrier moves fast. The dispatch clock is what JD scores for the Logistics DSR, so a late dispatch counts against you even when delivery lands well. **Q: Can I customise the alert threshold?** Yes, the floor (default 90%) is configurable per profile in the Sensitivity tab. Tighten it if you compete on dispatch speed, or align it to JD's current ship-rate requirement for your category rather than relying on the generic default. *** ### Tracked live in Vortex IQ Nerve Centre *POP Self-Fulfilled Dispatch Rate* is one of hundreds of KPI pulses Vortex IQ tracks across JD.com and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.