At a glance
Active JD Listings for OOS SKUs on BC is a cross-channel 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.
| What it counts | The number of JD.com listings that are active and sellable right now but whose matched SKU shows zero or negative available stock in the BigCommerce source-of-truth. Each one is an oversell waiting to happen. |
| Sample type | Cross-channel comparison of live JD.com listing status against BigCommerce stock levels, refreshed on the standard data refresh. |
| Why it matters | An oversold JD order leads to cancellation or late dispatch, both of which hurt DSR and can breach the dispatch SLA. The reputational and visibility cost far exceeds the single order’s revenue, so any non-zero value is urgent. |
| Reading the value | Treat every listing in the count as a pause-now candidate. Prioritise by recent sales velocity - a fast-selling OOS listing will convert an oversell within hours, a slow one gives you breathing room to restock or delist. |
| Currency | count |
| Time window | RT |
| Alert trigger | >0 |
| Sentiment key | jd_xc_listed_but_oos_on_bc |
| Roles | owner, operations, finance |
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-channel 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
| Card | Why merchants reach for it |
|---|---|
jdc_xc_catalogue_drift_vs_bc | Stock drift is one face of broader BC-to-JD catalogue drift. |
jdc_xc_feed_rejection_vs_listings | A stalled stock feed is the usual cause of this gap. |
jdc_oos_listings | The JD-side OOS view; this card adds the BC stock truth. |
jdc_dsr_threshold_crossed | Oversell cancellations are a leading cause of DSR breaches. |
jdc_late_dispatches | Unfulfillable orders show up here as late dispatches. |
jdc_revenue_at_risk | Rolls the oversell exposure into the executive risk figure. |
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:| Reason | Direction | What to do |
|---|---|---|
| Feed in flight. A stock decrement mid-propagation may already be clearing; the listing shows here until JD updates. | Vortex IQ higher briefly | Re-check after the next inventory feed run. |
| Buffer stock policy. Some sellers hold a deliberate JD safety buffer above BC zero; those should be excluded, not flagged. | Vortex IQ higher | Configure the buffer rule per profile. |
| Backorder allowed. SKUs you intentionally sell on backorder are not true oversell risk. | Vortex IQ higher | Add backorder SKUs to the exclusion list. |
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 Sensitivity tab if you operate with intentional buffers.