At a glance
DSR / Brand-Auth / Logistics-SLA Threshold Crossed is the single account-health tripwire for your JD.com shop. It fires the moment any one of the three pillars JD uses to judge a POP marketplace seller falls out of its safe band: a detailed seller rating (DSR) dropping below 4.5 on any axis, brand-authorisation coverage slipping below 98% of your restricted-category listings, or your JD Logistics SLA compliance dropping below 95%. Any one breach can throttle your search placement, suspend listings, or in severe cases freeze the shop, so this card is designed to be the first thing an owner sees each morning.
| What it counts | The number of JD account-health thresholds currently breached across three pillars: detailed seller rating (Description, Service, Logistics axes), brand-authorisation coverage on restricted categories, and JD Logistics SLA compliance. Zero is the healthy state. |
| Sample type | Real-time roll-up from the JD.com integration, combining DSR feeds, brand-authorisation records and logistics dispatch data into one alert list. |
| Why it matters | Each pillar feeds JD’s seller scorecard directly. A sustained breach can cut search visibility, off-shelf listings, withhold the buyer-trust premium, and trigger JD audits. This card collapses three independent risks into one tripwire so nothing slips. |
| Reading the value | Any value above zero is an active incident. Open the alert list to see which pillar tripped, by how much, and which listings or orders are implicated. Treat a non-zero reading as same-day work. |
| Currency | count |
| Time window | RT |
| Alert trigger | any DSR<4.5 OR brand-auth-coverage<98% OR JD-Logistics-SLA<95% |
| Sentiment key | jd_alert_account_health_drop |
| Roles | owner, operations, finance |
Calculation
The card evaluates three independent conditions on every refresh and counts how many are currently in breach:- DSR axis check - reads the latest detailed seller rating on each of the three JD axes (Description, Service, Logistics) and flags any axis below the 4.5 safe band.
- Brand-authorisation coverage - divides the count of restricted-category listings that hold a valid brand authorisation by the total restricted-category listings, and flags coverage below 98%.
- JD Logistics SLA compliance - measures the share of orders dispatched within the JD ship deadline and flags compliance below 95%.
Worked example
A representative reading for a typical POP marketplace seller on JD.com. On the morning of 14 Mar 26 the card reads 2. Opening the alert list shows two breaches: the Logistics DSR axis has slipped to 4.42 after a run of late dispatches during a regional courier delay in Guangdong province, and brand-authorisation coverage has fallen to 97.1% because three restricted-category listings inherited a brand whose authorisation lapsed overnight. The Service and Description axes remain healthy at 4.81 and 4.76. The fix is twofold: clear the late-dispatch backlog to lift the Logistics axis back above 4.5, and renew or remove the three unauthorised listings to restore coverage above 98%. By 16 Mar 26, with the backlog cleared and authorisations renewed, the card returns to 0. For deeper investigation into why the Logistics axis dropped, use Vortex Mind to trace the upstream dispatch delays; to ask which orders caused the slip in plain English, use Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
jd_dsr_summary | Breaks the DSR pillar into its three axes so you can see which one tripped. |
jd_brand_auth_coverage | The live coverage gauge behind the brand-auth pillar of this alert. |
jd_logistics_sla | The SLA compliance figure behind the logistics pillar. |
jd_late_dispatch | Shows the late orders that drag down the Logistics DSR axis. |
jd_expiring_brand_auths | Early-warning sibling so coverage never lapses unexpectedly. |
jd_shop_health | The composite shop-health score this tripwire protects. |
Reconciling against the vendor’s own dashboard
Where to look in JD.com’s own dashboard: The three pillars live in different places in JD’s seller backend. DSR axes appear under the seller scorecard / store rating section, brand authorisations under the brand qualification and category-permission area, and logistics SLA under the order-fulfilment and shipping-performance reports. This card reconciles against all three at once, so when you cross-check, open each section separately. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| DSR refresh lag. JD recomputes DSR axes on its own cadence; Vortex IQ reflects the last published figure. | Marginal | Allow for JD’s recompute window before assuming divergence. |
| Coverage scope. Vortex IQ counts only restricted-category listings in the denominator; the vendor view may include all listings. | Variable | Match the restricted-category filter. |
| SLA window. JD may compute SLA over a different trailing window than the Vortex IQ profile. | Variable | Confirm the SLA measurement window matches. |