At a glance
Rejected / Off-Shelf Listings counts every JD.com listing that the platform has rejected at review or pulled off-shelf (xia jia) so it can no longer be bought. On JD’s POP marketplace, listings come off-shelf for concrete, fixable reasons: a missing or expired brand authorisation in a controlled category, mandatory category attributes left blank, product images that fail JD’s image specification, or a compliance flag (3C certification, food/health licence, restricted keywords). Every off-shelf listing is lost shelf space and lost revenue until it is fixed and resubmitted, so this is a real-time firefighting card, not a trend card.
| What it counts | The number of JD listings currently in a rejected or off-shelf state, across both JD Logistics (warehoused) and POP self-fulfilled listings. A listing in draft or pending first review is not counted; only listings JD has actively rejected or removed from sale are. |
| Sample type | Backend API data from JD.com listing status, refreshed on the standard data refresh. |
| Why it matters | An off-shelf listing earns nothing and, if it sat live before removal, may signal a compliance or brand-authorisation gap that puts sibling listings at risk too. Repeated rejections in a controlled category usually point to one missing authorisation document rather than many separate faults. |
| Reading the value | Any value above zero is actionable. Read alongside the rejection reason in JD Seller Centre to batch fixes - one expired authorisation can off-shelf a whole brand’s catalogue at once. |
| Currency | count |
| Time window | RT |
| Alert trigger | >0 |
| Sentiment key | jd_rejected_listings |
| Roles | owner, operations |
Calculation
Calculated automatically from your JD.com data. The card sums all listings whose JD status is rejected (review failed) or off-shelf (removed from sale by JD or auto-removed for a compliance/attribute breach). Listings you have voluntarily set inactive are excluded; this card isolates involuntary removals. See the worked example below for a typical reading.Worked example
A representative reading of Rejected / Off-Shelf Listings for a mid-size POP seller on JD.com. The card shows 14 listings off-shelf as of 23 Jun 26, up from 3 the day before. Drilling in, 11 of the 14 share a single rejection reason: the brand authorisation letter (pin pai shou quan) for one cosmetics brand expired on 21 Jun 26, and JD auto-removed every SKU under that brand. The remaining 3 are image-spec failures (white-background main image missing). The fix is not 14 separate jobs - it is one renewed authorisation upload that restores 11 listings, plus 3 quick image swaps. Use Vortex Mind to group the off-shelf set by rejection reason and brand, and ask Ask Viq “which off-shelf listings share the same cause?” to triage before touching JD Seller Centre.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
jd_off_shelved_24h | The fresh removals in the last 24h - the leading edge of this count. |
jdc_brand_auth_coverage | Missing brand authorisation is the top off-shelf cause in controlled categories. |
jdc_brand_auth_expiring | Pre-empts the renewals that prevent the next mass off-shelf event. |
jdc_attr_completeness | Blank mandatory attributes are a frequent rejection reason at review. |
jdc_listing_quality | Low quality scores correlate with image and content rejections. |
jdc_revenue_at_risk | Quantifies the revenue exposed by the current off-shelf set. |
Reconciling against the vendor’s own dashboard
Where to look in JD.com’s own dashboard: In JD Seller Centre (Shang Jia Hou Tai), open Product Management and filter by status “off-shelf” (xia jia) and “rejected” (shen he wei tong guo). The rejection reason and the offending field are shown per listing. Confirm you are viewing the same shop ID and that no category filter is narrowing the list before comparing to the Vortex IQ count. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| State definition. Vortex IQ counts both rejected-at-review and off-shelf-after-live; a JD view filtered to only one state shows fewer. | Vortex IQ higher | Combine both JD status filters. |
| Refresh lag. A just-fixed listing JD has re-approved may still show on the card until the next refresh. | Vortex IQ higher | Force a manual refresh after bulk fixes. |
| Voluntary vs involuntary. Listings you set inactive yourself are excluded here but may appear under “off-shelf” in JD’s combined view. | Vortex IQ lower | Match the involuntary-only filter. |
Known limitations / merchant FAQs
Q: How often does Rejected / Off-Shelf Listings update? This is a real-time (RT) card and refreshes on the standard data refresh (typically every 30-60 minutes). After a bulk fix in JD Seller Centre, force a manual refresh to clear restored listings immediately.
Q: Why does my JD.com dashboard show a different number?
The usual cause is the JD status filter: this card combines rejected-at-review and off-shelf-after-live, whereas a single JD filter shows only one. Refresh lag after a fix and exclusion of voluntarily inactive listings also account for small gaps.
Q: A whole brand went off-shelf at once. Is that one problem or many?
Almost always one. JD removes every SKU under a brand when its authorisation expires or is revoked. Group the off-shelf set by brand and rejection reason first; one renewed document often restores dozens of listings.
Q: Can I customise the alert threshold?
Yes. The default fires above zero because any involuntary removal is revenue lost, but the threshold is configurable per profile in the Sensitivity tab if you want to suppress single-listing noise.