> ## 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 Off-Shelved Listings (24h), JD.com > JD Off-Shelved Listings (24h) 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 > **JD Off-Shelved Listings (24h)** counts the listings JD has taken off-shelf, that is removed from sale, in the last 24 hours. JD enforces category compliance aggressively: a listing can be pulled for a missing required attribute, a lapsed brand authorisation in a restricted category, a prohibited claim, a pricing-rule breach, or a qualification document falling out of date. An off-shelved listing earns nothing and loses its accumulated search ranking, so a sudden spike is both a revenue leak and an early signal of a deeper compliance problem. This card is the daily watch on JD's enforcement actions against your catalogue. | | | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The number of listings JD has moved off-shelf in the trailing 24 hours, removing them from sale to buyers. | | **Sample type** | Real-time listing-status feed from the JD.com integration, capturing transitions into the off-shelf state within the last 24 hours. | | **Why it matters** | Off-shelved listings stop selling immediately and forfeit their accumulated search ranking when restored. A spike usually points to a systemic cause - a category schema change, a brand-authorisation lapse, or a feed validation failure - that will keep pulling listings until fixed. | | **Reading the value** | Zero is the healthy state. Any positive value is lost revenue today; open the alert list to see each listing and JD's stated removal reason, then fix the root cause and request reinstatement. | | **Currency** | count | | **Time window** | `24H` | | **Alert trigger** | `>0` | | **Sentiment key** | `jd_alert_listing_rejection_spike` | | **Roles** | owner, operations | ## Calculation The card tracks each listing's status and counts every listing that transitioned into JD's off-shelf state during the trailing 24-hour window. A listing that was already off-shelf before the window opened is not recounted; the card measures new enforcement actions, not the standing total of off-shelf listings. Each entry in the alert list carries JD's stated removal reason where it is available - missing required attribute, brand-authorisation gap, prohibited content, pricing-rule breach, or expired qualification - so the team can group listings by cause and fix the systemic issue rather than reinstating them one at a time. ## Worked example *A representative reading for a POP marketplace seller on JD.com.* On 21 Mar 26 the card jumps from **0** to **9** overnight. Opening the alert list shows a clear pattern: seven of the nine were pulled for the same reason, a missing required attribute that JD added to a category schema the previous day, and the remaining two for a brand authorisation that lapsed at midnight. The fix is two distinct actions: bulk-populate the newly required attribute across the seven affected listings and resubmit, and renew the brand authorisation (or remove the two listings if the brand can no longer be sold). Because the seven shared a single root cause, one feed correction reinstates them together. By 23 Mar 26, with the attribute filled and the authorisation renewed, the card is back to **0** and the listings have returned to sale, though they take a few days to rebuild their search ranking. To find which other live listings are missing the same attribute before JD pulls them too, use Vortex Mind; to ask which categories changed schema recently in plain English, use Ask Viq. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | | [`jd_attribute_completeness`](/nerve-centre/kpi-cards/jd-com/required-attribute-completeness) | The most common off-shelf cause: missing required attributes. | | [`jd_brand_auth_coverage`](/nerve-centre/kpi-cards/jd-com/brand-authorisation-coverage) | Brand-authorisation gaps that trigger restricted-category removals. | | [`jd_rejected_off_shelf`](/nerve-centre/kpi-cards/jd-com/rejected-off-shelf-listings) | The standing total of off-shelf listings, beyond the 24h window. | | [`jd_feed_validation_fail`](/nerve-centre/kpi-cards/jd-com/listings-failing-feedonomics-validation) | Feed validation failures that often precede an off-shelf action. | | [`jd_active_listings`](/nerve-centre/kpi-cards/jd-com/active-listings) | The live count off-shelving directly reduces. | | [`jd_account_health`](/nerve-centre/kpi-cards/jd-com/dsr-brand-auth-logistics-sla-threshold-crossed) | The account-health tripwire a removal spike often accompanies. | ## Reconciling against the vendor's own dashboard **Where to look in JD.com's own dashboard:** JD lists off-shelved products and the enforcement reason in the product-management area, usually under a removed or off-shelf listings view, with compliance notices sometimes also surfacing in the seller message centre. Cross-check the reason codes shown there against the alert list to confirm the root cause. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | --------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------------------------------------------------- | | **Window definition.** Vortex IQ counts the trailing 24 hours; the vendor view may show all off-shelf listings regardless of when they were pulled. | Vortex IQ lower | Filter the vendor view to the last 24 hours. | | **Status sync lag.** A reinstatement processed in JD may not have synced when Vortex IQ refreshed. | Variable | Allow for status-sync lag, then refresh. | | **Seller vs JD action.** A listing you manually took off-shelf may or may not be counted depending on profile settings. | Variable | Confirm whether seller-initiated removals are included. | **Cross-connector reconciliation:** pair this with the attribute-completeness and brand-authorisation cards to predict the next wave of removals before JD acts. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does JD Off-Shelved Listings (24h) update?** It is a real-time card over a trailing 24-hour window. New off-shelf actions appear within the next refresh cycle, and entries roll off automatically once they fall outside the 24-hour window. **Q: I fixed and resubmitted a listing but it still shows here. Why?** The card counts the off-shelf event within the trailing window, so a listing can remain on the list until either the event ages out of the 24 hours or JD confirms the reinstatement and the status syncs. Reinstatement review on JD's side is not instant. **Q: The count dropped without me doing anything. Is that normal?** Yes. Because the window is trailing, entries fall off after 24 hours even if you took no action. That is not the same as a fix - the listing may still be off-shelf in the standing total. Check the rejected / off-shelf listings sibling card for the full picture. **Q: Can I customise the alert threshold?** The default alerts on any value above zero, since even one enforced removal is worth knowing. You can raise the threshold per profile in the Sensitivity tab if you only want to be alerted on a genuine spike. *** ### Tracked live in Vortex IQ Nerve Centre *JD Off-Shelved Listings (24h)* 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.