Skip to main content
Card class: HeroCategory: Marketplace

At a glance

Active AliExpress Listings for OOS SKUs on BC counts SKUs that are out of stock in BigCommerce but still active and buyable on AliExpress. BigCommerce is the source of truth for stock, so a SKU sold out on BC has nothing to fulfil, yet the AliExpress listing keeps taking orders. On a cross-border marketplace this is the most dispute-prone kind of oversell: AliExpress buyers already accept long shipping lead times, so they will wait, but they will not tolerate a cancellation after waiting. Every listing in this count is a cancellation and a dispute waiting to happen, which damages seller ratings on top of the lost order. The alert fires the moment the count rises above zero, because even one of these is a live liability.
What it countsSKUs that are out of stock on the BigCommerce source yet still showing as active and buyable on AliExpress. Each such listing is one to the count.
Sample typeBackend API data from AliExpress reconciled against BigCommerce stock, refreshed on the standard data refresh in near real time.
Why it mattersThese listings can take orders they cannot fulfil. On a cross-border channel a forced cancellation triggers disputes and hurts seller ratings far more than a delay would.
Reading the valueTreat any value above zero as a worklist to clear immediately. The longer a SKU stays in this state the more oversold orders it can accumulate.
Currencycount
Time windowRT
Alert trigger>0
Sentiment keyaex_xc_listed_but_oos_on_bc
Rolesowner, operations, finance

Calculation

Vortex IQ cross-references each active, buyable AliExpress listing against the stock level of its BigCommerce source SKU and counts those where BC shows zero available stock. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A representative reading of Active AliExpress Listings for OOS SKUs on BC for a typical BC-to-AliExpress cross-border seller. On 17 Mar 26 the card reads 4, above the zero-tolerance threshold. A best-selling SKU sold out on BC overnight, but its stock update had not synced, so the AliExpress listing kept selling and took 3 orders it cannot fulfil. The operations team pauses the 4 listings at once, then decides whether to refund and apologise or to source replacement stock before the cross-border clock runs out. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq.

Sibling cards merchants should reference together

CardWhy merchants reach for it
aex_xc_catalogue_drift_vs_bcStock drift is the broad case; this card is its most dangerous, dispute-prone extreme.
aex_xc_feed_rejection_vs_listingsA stock update that fails feed validation is a common cause of OOS listings staying live.
aex_oos_listingsAliExpress-side OOS listings, the single-channel view of the same risk.
aex_dispute_rateThe downstream damage when oversold orders get cancelled.
aex_revenue_at_risk_liveQuantifies the revenue exposed by oversells and other live risks.

Reconciling against AliExpress Seller Center

Where to look in AliExpress Seller Center: In Product Management the affected SKUs will still show as active with stock available, because Seller Center only knows the AliExpress side. The out-of-stock truth lives in BigCommerce, and the stock sync usually runs through the Feedonomics feed layer, so confirm the BC stock level and the last successful sync rather than trusting Seller Center alone. Why the Vortex IQ value may legitimately differ:
ReasonDirectionWhat to do
Sync lag. A BC stock change may be mid-propagation, so the listing is briefly counted before AliExpress catches up.MarginalRecheck after the next refresh before pausing the listing.
Buffer or safety stock. Some merchants intentionally keep AliExpress sellable on a buffer beyond BC zero.VariableWhitelist intentional buffer SKUs so they stop counting.
Separate fulfilment stock. A SKU may be fulfilled from a warehouse BC does not track.VariableConfirm the true fulfilment source before treating it as an oversell.
Cross-connector reconciliation: reconcile the AliExpress listing state, the BigCommerce stock level, and the last Feedonomics sync to confirm a true oversell rather than a sync gap. For divergence investigations, use Vortex Mind.

Known limitations / merchant FAQs

Q: How often does Active AliExpress Listings for OOS SKUs on BC update? It refreshes in near real time on the standard data refresh, so a new oversell risk surfaces within a refresh cycle of the BC stock hitting zero. Force a manual refresh after a known sell-out to catch it immediately. Q: Why does my AliExpress Seller Center show a different number? Seller Center shows the listing as active with stock because it cannot see the BigCommerce source. The count reflects BC being out of stock, so reconcile against BC stock and the last Feedonomics sync, not Seller Center. Q: How does Active AliExpress Listings for OOS SKUs on BC relate to other metrics? It is the sharpest of the cross-channel revenue-at-risk cards. Pair it with Listings Drifting from BC for the broader stock-drift picture and with Dispute Rate to see the downstream cost of unfulfilled orders. Q: Can I customise the alert threshold? Yes, sensitivity thresholds are configurable per profile in the Sensitivity tab. Adjust to match your business baseline rather than relying on the generic default.

Tracked live in Vortex IQ Nerve Centre

Active AliExpress Listings for OOS SKUs on BC is one of hundreds of KPI pulses Vortex IQ tracks across AliExpress 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 or book a demo to see this metric running on your own data.