> ## 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. # JD Logistics vs POP-Fulfilled Revenue, JD.com > JD Logistics vs POP-Fulfilled Revenue 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 > **JD Logistics vs POP-Fulfilled Revenue** splits your JD.com revenue by who shipped the order: JD Logistics (warehoused or picked up by JD) versus POP self-fulfilled, where you, the marketplace seller, handle dispatch. The mix matters because the two channels behave differently on the P\&L. JD Logistics orders typically carry a premium average order value and convert better thanks to the trusted 24-hour promise, but they also carry JD Logistics fees that compress margin. POP self-fulfilled revenue keeps more margin in your pocket but leans on your own dispatch speed to protect the Logistics DSR. This card sits in Revenue & Sales and reads best beside the net-revenue-after-commission, SLA compliance, and dispatch-rate cards below. | | | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Total revenue in the window split into two slices: orders fulfilled by JD Logistics and orders self-fulfilled under POP (the marketplace seller-fulfilled model). | | **Sample type** | Backend API data from JD.com, refreshed on the standard data refresh. | | **Why it matters** | The two fulfilment routes trade margin against AOV and conversion. Watching the mix shift tells you whether your revenue is leaning toward higher-cost, higher-trust JD Logistics or higher-margin, speed-dependent self-fulfilment, and lets you steer the balance deliberately. | | **Reading the value** | Read the donut as a share split. A growing JD Logistics slice usually means higher AOV but thinner margin; a growing POP slice means more margin exposure to your own dispatch performance. Pair with net revenue after commission to see the margin consequence. | | **Currency** | currency (CNY) | | **Time window** | `30D` | | **Alert trigger** | `-` | | **Sentiment key** | `jd_logistics_vs_pop_revenue` | | **Roles** | owner, finance, operations | ## Calculation Revenue is grouped by the fulfilment route attached to each order: JD Logistics (JD-warehoused or JD-pickup) versus POP self-fulfilled. Each slice sums the order value of its group over the window, in CNY. The donut shows the share split; the underlying totals are available on hover. Returns and cancellations net out against their original slice so the mix reflects realised, not gross, revenue. ## Worked example *A representative reading of **JD Logistics vs POP-Fulfilled Revenue** for a typical merchant on JD.com.* Suppose the 30-day window shows CNY 1.8M total: CNY 1.2M (67%) through JD Logistics and CNY 600K (33%) self-fulfilled. The JD Logistics slice carries a higher AOV (say CNY 310 vs CNY 240 for POP) because buyers trust the same-day promise on bigger baskets, but after JD Logistics fees and category commission the net margin on that slice is tighter. A quarter ago the split was 55/45. The shift toward JD Logistics has lifted top-line revenue and conversion but quietly squeezed blended margin. The decision: keep the higher-margin SKUs on POP self-fulfilment where your dispatch rate is strong, and reserve JD Logistics for the trust-sensitive, time-critical lines. For deeper investigation, use Vortex Mind to trace margin by fulfilment route; for natural-language exploration, ask Ask Viq "what is my blended margin on JD Logistics orders versus self-fulfilled". ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------- | | [`jdc_net_revenue`](/nerve-centre/kpi-cards/jd-com/net-revenue-after-jd-commission) | Revenue sibling: shows the margin consequence of the JD Logistics vs POP mix after commission and fees. | | [`jdc_total_revenue`](/nerve-centre/kpi-cards/jd-com/total-revenue) | Revenue sibling: the combined top-line this card splits in two. | | [`jdc_logistics_sla`](/nerve-centre/kpi-cards/jd-com/jd-logistics-sla-compliance) | Fulfilment sibling: the delivery performance of the JD Logistics slice. | | [`jdc_pop_dispatch_rate`](/nerve-centre/kpi-cards/jd-com/pop-self-fulfilled-dispatch-rate) | Fulfilment sibling: the dispatch performance of the POP self-fulfilled slice. | | [`jdc_commission_pct`](/nerve-centre/kpi-cards/jd-com/jd-commission-of-revenue) | Economics sibling: the commission drag that differs by fulfilment route. | ## Reconciling against the vendor's own dashboard **Where to look in JD.com's own dashboard:** JD's Seller Centre reports revenue by fulfilment model in the sales and settlement views, where JD-warehoused and seller-shipped orders are tagged separately. Confirm the report distinguishes JD Logistics from POP self-fulfilment and that the window matches the Vortex IQ 30-day default. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ----------------------------------------------------------------------------------------------------------------------------------------- | --------- | ----------------------------------------------- | | **Gross vs net of returns.** Vortex IQ nets returns and cancellations against the originating slice; vendor sales views may show gross. | Variable | Compare against the settled, not gross, figure. | | **Period boundary.** Vortex IQ uses a 30-day rolling window; JD often defaults to calendar months. | Variable | Match the date range. | | **Fulfilment tagging.** Mixed-cart orders (some lines JD Logistics, some POP) may be split or assigned wholesale depending on the report. | Variable | Confirm how mixed carts are attributed. | | **Currency and time zone.** Both report in CNY and China Standard Time; confirm profile alignment. | Marginal | Confirm currency and time zone match. | **Cross-connector reconciliation:** read alongside net revenue after commission to confirm that a richer JD Logistics mix is not eroding blended margin. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does JD Logistics vs POP-Fulfilled Revenue update?** The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). Settlement-side revenue can lag dispatch by a settlement cycle. For real-time signals, force a manual refresh from the dashboard. **Q: Why does my JD.com dashboard show a different split?** The common causes are gross-vs-net treatment of returns, period boundaries (30-day rolling vs calendar months), and how mixed-cart orders are attributed between the two routes. Match those before assuming a real divergence. **Q: Should I move more revenue to JD Logistics?** Not automatically. JD Logistics lifts AOV, conversion, and the delivery promise but adds fees that compress margin. Use this card with the net-revenue-after-commission card to see whether the trust premium outweighs the fee drag for each category. **Q: Can I customise the alert threshold?** This card has no default alert because the ideal mix varies by category and strategy. You can add a sensitivity rule in the Sensitivity tab if you want to be notified when either slice moves beyond a chosen band. *** ### Tracked live in Vortex IQ Nerve Centre *JD Logistics vs POP-Fulfilled Revenue* 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.