> ## 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. # Total Listings, JD.com > Total Listings 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 > **Total Listings** is the full count of listings in your JD.com shop, active and inactive combined. It is the denominator behind almost every listing-health ratio on the dashboard: out-of-stock percentage, attribute completeness, quality score, and brand-authorisation coverage are all "X out of Total Listings". On JD's POP marketplace a single product can exist as several listings (different specs, bundles, or province-restricted variants), so this count is usually larger than the number of distinct products you would recognise from the source catalogue. Reading it on its own tells you catalogue scale; reading it against the active count tells you how much of your catalogue is actually selling. | | | | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Every listing in the JD shop regardless of state - active, off-shelf, rejected, out-of-stock, and inactive - across JD Logistics and POP self-fulfilled. It counts listings, not distinct products, so variants and bundles each add to the total. | | **Sample type** | Backend API data from JD.com listing inventory, refreshed on the standard data refresh. | | **Why it matters** | It is the baseline for catalogue scale and the denominator for every listing-health ratio. A sudden drop usually means a sync or feed problem upstream, not deliberate delisting. | | **Reading the value** | Compare against the active-listings count to see your sellable share. A widening gap between total and active points to off-shelf, OOS, or rejected listings piling up. | | **Currency** | count | | **Time window** | `RT` | | **Alert trigger** | `-` | | **Sentiment key** | `jd_total_listings` | | **Roles** | owner, operations | ## Calculation Calculated automatically from your JD.com data. The card counts all listings in the shop across every status. It is a real-time inventory count, not a deduplicated product count, so variant and bundle listings each contribute. See the worked example below for how to read it against the active count. ## Worked example *A representative reading of **Total Listings** for a JD.com seller.* The card shows 1,420 total listings as of 23 Jun 26, against 1,180 active. The 240-listing gap is the working set of problems: 60 out-of-stock, 14 off-shelf, and 166 deliberately set inactive while attributes are completed. That gap, not the headline number, is where the attention goes. A week earlier the total was 1,460, so 40 listings disappeared - worth checking, because deliberate delisting is rare and a drop this size more often means a feed sync dropped them. Use Vortex Mind to break the total down by status, and ask Ask Viq "why did total listings fall this week?" to rule out an upstream sync issue before assuming intent. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ------------------------------------------------------------------------------------------ | -------------------------------------------------------------- | | [`jdc_listings_active`](/nerve-centre/kpi-cards/jd-com/active-listings) | The sellable subset; the gap against total is the worklist. | | [`jdc_oos_listings`](/nerve-centre/kpi-cards/jd-com/out-of-stock-listings) | Part of the inactive gap and a direct revenue drag. | | [`jd_rejected_listings`](/nerve-centre/kpi-cards/jd-com/rejected-off-shelf-listings) | Involuntary removals that widen the total-to-active gap. | | [`jdc_listing_quality`](/nerve-centre/kpi-cards/jd-com/listing-quality-score) | Uses total listings as its denominator. | | [`jdc_attr_completeness`](/nerve-centre/kpi-cards/jd-com/required-attribute-completeness) | Completeness measured across the total listing set. | | [`jdc_xc_catalogue_drift_vs_bc`](/nerve-centre/kpi-cards/jd-com/listings-drifting-from-bc) | Flags when total drifts from the BC source-of-truth catalogue. | ## Reconciling against the vendor's own dashboard **Where to look in JD.com's own dashboard:** In JD Seller Centre, open Product Management with all status filters cleared - the unfiltered total is the figure to compare. JD's default view often pre-filters to on-shelf listings, which will undercount against this card. Confirm you are viewing the same shop ID and that no category or keyword filter is applied. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | -------------------------------------------------------------------------------------------------------------- | ---------------- | ------------------------------------------------ | | **Status filter.** JD's default product view shows only on-shelf listings; this card counts all states. | Vortex IQ higher | Clear all JD status filters before comparing. | | **Listings vs products.** This card counts listings (variants, bundles); a product-level JD view counts fewer. | Vortex IQ higher | Compare at the listing level, not product level. | | **Refresh lag.** Listings created or removed since the last refresh are not yet reflected. | Variable | Force a manual refresh. | **Cross-connector reconciliation:** pair with the active-listings card to interpret the total, and with catalogue-drift to confirm parity against the source catalogue. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Total Listings update?** This is a real-time (`RT`) card and refreshes on the standard data refresh (typically every 30-60 minutes). Bulk uploads or feed syncs are reflected at the next refresh; force a manual refresh to see them sooner. **Q: Why does my JD.com dashboard show a different number?** Most often because JD's product view is pre-filtered to on-shelf listings while this card counts every status. The listings-vs-products distinction also matters: variants and bundles each count here, so a product-level JD figure will be lower. **Q: Total listings dropped suddenly. What happened?** Deliberate mass delisting is rare, so a sudden fall usually means a feed or sync issue upstream dropped listings before they reached JD. Check the cross-channel drift and feed-validation cards before assuming the catalogue was intentionally cut. **Q: Can I customise the alert threshold?** This card has no default alert (`-`). If you want to be warned when the catalogue shrinks unexpectedly, set a downward-change threshold per profile in the Sensitivity tab. *** ### Tracked live in Vortex IQ Nerve Centre *Total Listings* 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.