> ## 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. # Detailed Seller Ratings (Description / Service / Logistics), JD.com > Detailed Seller Ratings (Description / Service / Logistics) 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:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Marketplace](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Detailed Seller Ratings (Description / Service / Logistics)** shows JD's three-axis DSR score side by side. After a purchase, buyers rate the seller on three independent axes: Description (did the product match the listing), Service (how good was the seller's communication and support), and Logistics (how fast and well did it arrive). JD weighs all three into search placement and the buyer-trust premium that lifts conversion. This hero card puts all three axes in one view, compared against the prior period, so you can see at a glance which axis is healthy, which is slipping, and which is pulling your visibility down. | | | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The three JD detailed seller rating axes - Description, Service and Logistics - each a buyer-rated score, shown together and compared against the prior period. | | **Sample type** | Backend API data from JD.com, drawn from buyer post-purchase ratings and refreshed on the standard data refresh. | | **Why it matters** | The three axes drive search placement and the buyer-trust premium. Any axis below the 4.5 safe band can cut visibility and trips the account-health alert, so seeing all three together tells you exactly where to focus. | | **Reading the value** | Higher is better; each axis sits on JD's rating scale. Watch for any axis below 4.5 and for an axis trending down against the prior period even while the others hold. | | **Currency** | count | | **Time window** | `30D vsP` | | **Alert trigger** | `any DSR <4.5` | | **Sentiment key** | `jd_dsr_summary` | | **Roles** | owner, marketing, operations | ## Calculation The card reads JD's published detailed seller rating for each of the three axes over the trailing window and displays them as a grouped bar chart with a comparison against the prior period (`vsP`). Each axis is a buyer-rated average that JD maintains: * **Description** - how closely the delivered product matched the listing's description and images. * **Service** - the quality of the seller's communication, responsiveness and after-sales handling. * **Logistics** - the speed and condition of delivery, the axis most affected by late dispatches. The card does not recompute the ratings; it surfaces JD's own published figures so the displayed value always matches what JD uses for ranking. The period-over-period comparison highlights which axis is moving. ## Worked example *A representative reading for a POP marketplace seller on JD.com over the 30 days to 20 Mar 26.* The three bars read Description 4.78, Service 4.83, and Logistics 4.47. Against the prior period, Description and Service are flat, but Logistics has fallen from 4.61 to 4.47, dropping below the 4.5 safe band and tripping the account-health alert. The split diagnosis is immediate: the product and the service are fine, the problem is delivery. Cross-referencing the late-dispatch card confirms a run of orders shipped past deadline during a courier disruption. The fix is operational - clear the dispatch backlog and tighten cut-off times - rather than anything to do with the product or support. As on-time dispatch recovers over the following weeks, the Logistics axis climbs back above 4.5 and the alert clears. To trace which orders or provinces drove the Logistics slip, use Vortex Mind; to ask how each axis moved month over month in plain English, use Ask Viq. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | | [`jd_account_health`](/nerve-centre/kpi-cards/jd-com/dsr-brand-auth-logistics-sla-threshold-crossed) | The tripwire that fires when any axis falls below 4.5. | | [`jd_late_dispatch`](/nerve-centre/kpi-cards/jd-com/late-dispatches-risking-dsr-logistics) | The orders most directly dragging the Logistics axis. | | [`jd_logistics_sla`](/nerve-centre/kpi-cards/jd-com/jd-logistics-sla-compliance) | Logistics SLA compliance behind the Logistics axis. | | [`jd_seller_feedback`](/nerve-centre/kpi-cards/jd-com/seller-feedback-score) | The overall seller feedback score the DSR axes feed. | | [`jd_avg_review_rating`](/nerve-centre/kpi-cards/jd-com/avg-review-rating) | Product-level review rating, complementary to seller DSR. | | [`jd_shop_health`](/nerve-centre/kpi-cards/jd-com/jdcom-shop-health-score) | The composite shop-health score DSR contributes to. | ## Reconciling against the vendor's own dashboard **Where to look in JD.com's own dashboard:** JD shows the three DSR axes in the seller scorecard / store rating section, usually with the same period comparison. Because this card surfaces JD's own published figures, the numbers should match closely once the periods align. If they do not, the difference is almost always a period or refresh-timing issue rather than a real divergence. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | --------------------------------------------------------------------------------------------------------- | --------- | -------------------------------- | | **Recompute timing.** JD republishes DSR on its own cadence; Vortex IQ reflects the last published value. | Marginal | Allow for JD's recompute window. | | **Period boundary.** The `vsP` comparison window may differ from the vendor's chosen comparison period. | Variable | Match the comparison period. | | **Rounding.** Display rounding can differ by a hundredth between the two views. | Marginal | Compare to two decimal places. | **Cross-connector reconciliation:** when an axis slips, jump to the matching operational card (late dispatch for Logistics, buyer messages for Service) to find the cause. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Detailed Seller Ratings update?** The card refreshes on the standard data refresh and reflects JD's last published DSR figures. JD recomputes the axes on its own schedule, so a single new buyer rating moves the axis only marginally and with some lag. **Q: One axis dropped but the others held. What should I do?** That is exactly the value of a three-axis view. A Logistics drop with healthy Description and Service points to a fulfilment problem; a Service drop points to communication or after-sales; a Description drop points to listings overselling the product. Act on the axis that moved, not the average. **Q: I improved my operations but the axis has not recovered. Why?** DSR axes are trailing buyer-rated averages. New positive ratings take time to outweigh the older negative ones, so the axis lags the underlying improvement. Keep the operational fix in place and the axis recovers as fresh ratings accumulate. **Q: Can I customise the alert threshold?** The default alert fires when any axis falls below 4.5, matching JD's safe band. You can set an earlier warning threshold per profile in the Sensitivity tab to catch a slip before it reaches JD's floor. *** ### Tracked live in Vortex IQ Nerve Centre *Detailed Seller Ratings (Description / Service / Logistics)* 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.