> ## 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. # Active Alibaba Listings for OOS SKUs on BC, Alibaba > Active Alibaba Listings for OOS SKUs on BC for Alibaba 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:** [Cross-Channel: Revenue at Risk](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Active Alibaba Listings for OOS SKUs on BC** is a Cross-Channel: Revenue at Risk metric that counts Alibaba B2B listings still taking RFQ inbox traffic and orders for SKUs that are out of stock on the BigCommerce store. Every one of these listings invites an inquiry you cannot fulfil, which wastes RFQ-response time and quietly erodes supplier credibility. The card pairs with the other Cross-Channel: Revenue at Risk siblings below, and with stock and buyer-message cards, so you can pull these listings before they generate dead-end conversations. | | | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The number of currently active Alibaba B2B listings whose SKU is out of stock on the BigCommerce store, evaluated in real time. | | **Sample type** | Backend API data from Alibaba, refreshed on the standard data refresh. | | **Why it matters** | An active listing on an unstocked SKU keeps drawing RFQs and orders you cannot honour. That burns your team's response time and damages the supplier trust that drives repeat B2B business. | | **Reading the value** | Read as a count of exposed listings. Any value above zero is actionable; the listed SKUs should be paused or restocked. The card is the leak you want to close fastest. | | **Currency** | number | | **Time window** | `RT` | | **Alert trigger** | `>0` | | **Sentiment key** | `ali_xc_listed_but_oos_on_bc` | | **Roles** | owner, operations, finance | ## Calculation This is a cross-channel card: it joins your active Alibaba B2B listings against the live stock position of the same SKUs on the BigCommerce store. A listing counts when it is active on Alibaba but its matching SKU shows zero available stock on BigCommerce. The card reports the current count in real time, because the cost of one of these listings is a fresh inquiry that lands the moment a buyer reaches out. BigCommerce is treated as the stock source of truth. See the worked example below for a typical reading. ## Worked example *A representative reading of **Active Alibaba Listings for OOS SKUs on BC** for a typical Alibaba supplier.* At 09:00 on 12 Mar 26 the card reads 6, above the alert line of 0. Drilling in shows two of those six SKUs each received an RFQ in the last day, so the sales team spent time quoting wholesale orders the warehouse cannot ship. The other four sit live, waiting to draw the next inquiry. Because the alert fires on any value above zero, this should be cleared the same day: pause the six Alibaba listings or restock the SKUs on BigCommerce. Vortex Mind traces whether the out-of-stock event was a sales spike on the retail side or a supply gap, and Ask Viq lets operations pull the exact SKU list to action in one pass. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | | [`listings-drifting-from-bc-source-of-truth`](/nerve-centre/kpi-cards/alibaba/listings-drifting-from-bc-source-of-truth) | Cross-channel sibling: another way Alibaba falls out of sync with BC. | | [`listings-failing-feedonomics-feed-validation`](/nerve-centre/kpi-cards/alibaba/listings-failing-feedonomics-feed-validation) | Cross-channel sibling: feed-level mismatches between BC and Alibaba. | | [`b2b-vs-retail-pricing-coherence-vs-aliexpress`](/nerve-centre/kpi-cards/alibaba/b2b-vs-retail-pricing-coherence-vs-aliexpress) | Cross-channel sibling: price coherence across sister channels. | | [`out-of-stock-listings`](/nerve-centre/kpi-cards/alibaba/out-of-stock-listings) | Shows Alibaba's own out-of-stock view alongside the BC join. | | [`buyer-messages-unread`](/nerve-centre/kpi-cards/alibaba/buyer-messages-unread) | Dead-end RFQs from OOS listings pile up here. | ## Reconciling against Alibaba Seller dashboard **Where to look in Alibaba's own dashboard:** Alibaba shows only its own side of this comparison. In your supplier workbench, open Product Management to see which listings are active, and check the RFQ Market / Message Centre for inquiries arriving on them. Alibaba has no view of your BigCommerce stock, so to reconcile you compare each active Alibaba listing against the SKU's stock in your BigCommerce admin. The card does that join; the workbench is where you pause the offending listings. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ----------------------------------------------------------------------------------------------------------------------------------- | --------- | ------------------------------------------------------------- | | **Period boundary.** The card is real time, but a very recent BigCommerce stock change may not yet have synced to the Alibaba view. | Variable | Allow for sync lag before treating a SKU as a false positive. | | **Time zone.** Stock-change and listing timestamps differ between the account time zone and your merchant reporting time zone. | Marginal | Confirm the time zone match when checking recent changes. | | **Filter scope.** Profile-level filters (which catalogue or warehouse stock is in scope) may narrow which SKUs are compared. | Variable | Match the catalogue and stock-location filters. | **Cross-connector reconciliation:** because this card spans Alibaba and BigCommerce, reconcile the listed SKUs against live BigCommerce stock rather than Alibaba alone. For divergence investigations across channels, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Active Alibaba Listings for OOS SKUs on BC update?** The card is real time and refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). Because it joins two channels, allow brief sync lag after a BigCommerce stock change before treating a SKU as cleared. **Q: Why does my Alibaba dashboard show a different number?** Alibaba's workbench shows your active listings but cannot see BigCommerce stock, so it has no equivalent count. Differences usually come from sync lag on recent stock changes, time-zone alignment, and which catalogue or warehouse is in scope. Reconcile against live BigCommerce stock. **Q: How does this relate to the other cross-channel cards?** This is the most urgent of the cross-channel set because each listing draws an inquiry you cannot fulfil. Read it next to Out-of-Stock Listings for Alibaba's own view and Buyer Messages Unread for where the dead-end RFQs land. **Q: Can I customise the alert threshold?** Yes, the alert fires above 0 by default, since any exposed listing is actionable, and that threshold is configurable per profile in the Sensitivity tab. Most suppliers keep it at zero and clear the list as soon as it appears. *** ### Tracked live in Vortex IQ Nerve Centre *Active Alibaba Listings for OOS SKUs on BC* is one of hundreds of KPI pulses Vortex IQ tracks across Alibaba 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.