At a glance
Revenue at Risk is the single executive number that rolls up every active account-health and listing problem into an estimated yuan figure of revenue currently exposed. On JD.com that exposure comes from concrete sources: listings JD has off-shelved, SKUs with a missing or expiring brand authorisation, listings still active and sellable for stock you cannot fulfil, and detailed seller rating (DSR) or JD Logistics SLA breaches that throttle search visibility. Rather than reading ten firefighting cards, an owner reads this one to know how much money is on the line right now.
| What it counts | An estimated CNY figure of revenue exposed by current issues: off-shelf listings (lost sales while down), brand-authorisation gaps (listings at risk of removal), active listings for out-of-stock SKUs (oversell and cancellation risk), and DSR / logistics SLA breaches (visibility throttling). It is a modelled exposure, not booked loss. |
| Sample type | Computed roll-up of JD.com listing, fulfilment, and account-health signals, refreshed on the standard data refresh. |
| Why it matters | It converts scattered operational faults into one prioritisation number an owner or finance lead can act on. A spike tells you something material broke; the contributing cards below tell you what. |
| Reading the value | Treat any non-zero value as a worklist, not a verdict. Open the largest contributing component first. Direction matters more than the absolute figure, which is modelled. |
| Currency | currency (CNY) |
| Time window | RT |
| Alert trigger | >0 |
| Sentiment key | jd_revenue_at_risk |
| Roles | owner, finance |
Calculation
Calculated automatically from your JD.com data. The card models exposed revenue by attributing a trailing-revenue estimate to each at-risk listing or breach: off-shelf listings carry their recent run-rate, OOS-but-active listings carry their cancellation-risk value, and authorisation gaps carry the run-rate of the listings they would remove. The components are summed into one CNY figure. See the worked example below.Worked example
A representative reading of Revenue at Risk for a JD.com seller. The card shows CNY 184,000 at risk as of 23 Jun 26, up from CNY 41,000 a week earlier. The breakdown: CNY 96,000 from 11 cosmetics listings off-shelved when a brand authorisation expired on 21 Jun 26; CNY 58,000 from 6 active listings for SKUs that went out of stock on the source catalogue and are now at oversell risk; and CNY 30,000 from two listings whose DSR slipped below JD’s threshold, costing search placement. The action order is clear: renew the one authorisation (recovers CNY 96,000), pause the 6 oversell-risk listings, then address the DSR. Use Vortex Mind to rank the components by recoverable value, and ask Ask Viq “what is driving revenue at risk this week?” for the plain-English breakdown.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
jd_rejected_listings | Off-shelf listings are usually the largest single contributor. |
jdc_xc_listed_but_oos_on_bc | Oversell-risk listings feed directly into the exposure figure. |
jdc_brand_auth_coverage | Authorisation gaps put whole brand catalogues at removal risk. |
jdc_dsr_threshold_crossed | DSR and SLA breaches throttle visibility and sales. |
jdc_shop_health | The account-health context behind the exposure. |
jdc_revenue_trend | Confirms whether at-risk revenue is already showing in the trend. |
Reconciling against the vendor’s own dashboard
Where to look in JD.com’s own dashboard: There is no single JD figure to reconcile against - this is a Vortex IQ roll-up. Instead, validate each component: check off-shelf listings under Product Management, authorisation status under Brand Management, and DSR / fulfilment SLA under the account-health (dian pu ping fen) section of JD Seller Centre. The card’s total should equal the sum of those component cards. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Modelled estimate. Exposure uses trailing run-rate, not realised loss; actual loss depends on how fast you fix each issue. | Variable | Treat as a priority signal, not a ledger figure. |
| Component overlap. A listing that is both off-shelf and OOS is counted once, not twice. | Vortex IQ lower than naive sum | Use the per-component breakdown, not addition of raw cards. |
| Refresh lag. A just-resolved issue may still contribute until the next refresh. | Vortex IQ higher | Force a manual refresh after fixes. |
Known limitations / merchant FAQs
Q: How often does Revenue at Risk update? This is a real-time (RT) card and refreshes on the standard data refresh (typically every 30-60 minutes). Force a manual refresh after resolving issues to see the figure drop.
Q: Is this real lost money?
No. It is modelled exposure - the revenue at risk if the underlying issues are left unfixed, valued at recent run-rate. Booked revenue lives on the revenue cards. Use this number to prioritise, not to reconcile your accounts.
Q: Why does the total not equal adding up the contributing cards?
Because a listing can be flagged by more than one card (for example off-shelf and OOS). The roll-up de-duplicates so each listing’s revenue is counted once. Read the per-component breakdown rather than summing raw cards.
Q: Can I customise the alert threshold?
Yes. The default fires above zero, but finance teams often raise the threshold to a material CNY figure per profile in the Sensitivity tab so the alert reflects exposure that matters at their scale.