At a glance
Active Bonanza Listings for OOS SKUs on BC is a cross-channel diagnostic that counts the SKUs still live and sellable on your Bonanza booth even though they are out of stock in the source BigCommerce (“BC”) catalog. Every one of these is a sale waiting to misfire, because a buyer can purchase an item you cannot fulfil. Any count above zero is an immediate oversell and cancellation risk. Read it as a real-time revenue-at-risk gauge spanning Bonanza and BC.
| What it counts | The number of SKUs that remain active and sellable on Bonanza while showing out of stock in the source BigCommerce (“BC”) catalog. |
| Sample type | Backend API data from Bonanza, refreshed on the standard data refresh. |
| Why it matters | A live Bonanza listing for a SKU with no BC stock invites orders you cannot ship, leading to cancellations, refunds, and feedback damage. |
| Reading the value | The only safe value is zero. Any count above zero is a list of SKUs to pull or restock right away. |
| Currency | number |
| Time window | Real-time |
| Alert trigger | >0 |
| Sentiment key | bon_xc_listed_but_oos_on_bc |
| Roles | owner, operations, finance |
Calculation
Each active Bonanza listing is matched to its source SKU in the BigCommerce catalog and the current BC stock state is read. Any SKU that is sellable on Bonanza while its BC record shows zero available is counted and listed. Because the risk is immediate, this card reads in real time rather than over a trailing window. See At a glance for the alert trigger and the worked example below for a representative reading.Worked example
A representative reading of Active Bonanza Listings for OOS SKUs on BC for a typical merchant on Bonanza. On 14 Mar 26 a seller sees a count of 6 against a trigger of zero. The table lists six SKUs, all reading zero stock on BC after a busy weekend, yet still showing as buyable on the Bonanza booth because the stock decrement never reached the listing. At an average order value near 45 dollars, that is roughly 270 dollars of orders the seller could take but not fulfil, plus the feedback hit from cancelling. The action is to pause or zero those six listings immediately, then fix the stock sync. Vortex Mind traces upstream causes, such as a lagging inventory push, and Ask Viq lets you ask in plain English which SKUs went sellable while out of stock today.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
bon_xc_catalogue_drift_vs_bc | Cross-Channel: Revenue at Risk sibling: Listings Drifting from BC. |
bon_listings_oos | Catalog sibling: Out-of-Stock Listings. |
bon_cancellation_rate | Fulfilment sibling: Cancellation Rate. |
bon_revenue_at_risk | Revenue sibling: Revenue at Risk. |
bon_importer_sync_health | Operations sibling: Importer Sync Health. |
Reconciling against Bonanza
Where to look in Bonanza’s own dashboard: In Bonanza, open the selling area and your item listings to find the flagged SKUs still showing as available, then check the same SKUs in your BigCommerce catalog to confirm they read zero stock. Because this is a cross-channel card, the conflict only appears when you hold the Bonanza listing state and the BC stock state side by side. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ reads this in real time by default; Bonanza dashboards may use calendar periods. | Variable | Match the period range. |
| Time zone. Bonanza uses account time zone; Vortex IQ aligns to merchant reporting time zone. | Marginal | Confirm time zone match. |
| Filter scope. Profile-level filters (booth, channel, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. |