At a glance
Active JD Listings for OOS SKUs on BC is a cross-platform card and one of the most dangerous gaps in a multi-channel setup. It counts JD.com listings that are still active and buyable for SKUs that are out of stock on your BigCommerce (BC) source-of-truth. Every one of these is a sale you can take but cannot fulfil. On JD that does not just mean a refund - an unfulfilled or cancelled order damages your detailed seller rating (DSR) and can breach the JD Logistics or POP dispatch SLA, which throttles your search visibility well beyond the single lost order. The card exists so you can pause these listings before a buyer orders, not after.
Calculation
Calculated automatically by matching each active JD.com listing to its SKU in the BigCommerce source-of-truth and flagging any whose BC available stock is zero or below while the JD listing remains sellable. The card counts those listings in real time. See the worked example below for how to triage them.Worked example
A representative reading of Active JD Listings for OOS SKUs on BC for a cross-platform JD.com seller. The card shows 6 listings as of 23 Jun 26, up from 0 the previous day. Cross-referencing BC, all six SKUs hit zero stock on the morning of 23 Jun 26, but the stock decrement never propagated to JD because the Feedonomics feed run that carries inventory had not completed. Two of the six are fast movers selling several units an hour, so they are minutes from an oversell that will cost a cancellation and a DSR hit; the other four are slow and lower risk. The action is immediate: pause the two fast movers in JD Seller Centre now, then let the feed catch the rest. Use Vortex Mind to rank the listings by sales velocity, and ask Ask Viq “which OOS-but-active JD listings will oversell first?” to act on the urgent ones before a buyer does.Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in JD.com’s own dashboard: JD only knows the stock figure it was last told, so JD Seller Centre will show these listings as in-stock and active - it cannot see that BC has zero stock. That is exactly the gap this card exists to surface. To validate a flagged listing, open the SKU’s stock in BigCommerce (should be zero or below), then open the same listing in JD Seller Centre (still active and showing stock). The mismatch confirms the oversell risk. Why the Vortex IQ value may legitimately differ:
Cross-connector reconciliation: check the Feedonomics feed card first - a non-zero value here almost always traces to a stock feed that has not run or has failed validation. For divergence investigations, use Vortex Mind.
Known limitations / merchant FAQs
Q: How often does Active JD Listings for OOS SKUs on BC update? This is a real-time (RT) card and refreshes on the standard data refresh (typically every 30-60 minutes). Because oversell risk is time-critical, force a manual refresh after a stock feed run or after pausing listings.
Q: JD says the listing is in stock. Why is it flagged?
Because JD only knows the stock figure it last received. BC, your source-of-truth, shows zero, but the decrement has not yet propagated to JD. The listing stays buyable on JD until the feed catches up, which is the window where an oversell happens.
Q: We deliberately keep a stock buffer or sell on backorder. How do we avoid false flags?
Configure a safety-buffer rule or add backorder SKUs to the exclusion list in the profile settings. The card will then only flag genuine oversell risk where you can neither fulfil nor intend to backorder.
Q: Can I customise the alert threshold?
Yes. The default fires above zero because each listing is a potential DSR-damaging cancellation, but the threshold is configurable per profile in the Alert Rules tab if you operate with intentional buffers.