Skip to main content
Card class: HeroCategory: Marketplace

At a glance

Active Newegg Listings for OOS SKUs on BC counts the SKUs that are still active and sellable on Newegg while showing out of stock on the BigCommerce (BC) source. BC is your stock source of truth; when a SKU is sold out there but live on Newegg, every new Newegg order is one you may not be able to fill. That means oversells, cancellations, and order-defect penalties that hurt your Egg Badge. It sits in the Cross-Channel: Revenue at Risk Hero cluster so owners, operations, and finance shut the exposure fast.
What it countsSKUs that are active and sellable on Newegg but out of stock in the BigCommerce source catalogue, as compared by the Vortex IQ cross-channel integration. Each one is a live oversell risk.
Sample typeBackend API data from Newegg Marketplace and BigCommerce, compared on stock status and refreshed on the standard data refresh.
Why it mattersSelling stock you do not have leads to cancellations and order-defect penalties on Newegg, which feed seller health and can drop your Egg Badge. The longer the gap stays open, the more orders you take that you cannot fulfil.
Reading the valueZero is the safe state. Any non-zero count means at least one SKU is sellable on Newegg without backing stock on BC; pause or zero out those Newegg listings until BC stock returns.
Currencycount
Time windowRT
Alert trigger>0
Sentiment keyneg_xc_listed_but_oos_on_bc
Rolesowner, operations, finance

Calculation

Calculated automatically by comparing Newegg listing availability against BigCommerce stock status for each matched SKU. The card counts SKUs that are active and sellable on Newegg while the BC source reports zero or out-of-stock inventory. 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 Newegg Listings for OOS SKUs on BC for a typical merchant on Newegg Marketplace. Suppose the card reads 4. Opening the detail shows a popular SSD that sold out on BC this morning, two accessories whose BC stock hit zero overnight, and a CPU cooler that BC marked discontinued. All four are still live and buyable on Newegg because the stock sync had not caught up. Until it does, each new Newegg order on those SKUs risks a cancellation and an order-defect ding against the Egg Badge. The merchant pauses the four Newegg listings immediately and lets them re-activate when BC stock returns, dropping the card back to zero. For deeper investigation, use Vortex Mind to trace why the inventory sync lagged; for natural-language exploration, ask Ask Viq.

Sibling cards merchants should reference together

CardWhy merchants reach for it
neg_xc_catalogue_drift_vs_bcCross-Channel sibling: listings whose fields disagree with BC.
neg_xc_feed_rejection_vs_listingsCross-Channel sibling: items failing feed validation before publish.
neg_xc_price_parityCross-Channel sibling: MAP parity across Newegg, Amazon, and Walmart.
neg_oos_listingsListing Health sibling: Newegg listings already marked out of stock.
neg_egg_badge_statusExecutive sibling: the Egg Badge oversell penalties put at risk.

Reconciling against Newegg Seller Portal

Where to look in the Newegg Seller Portal: Open the flagged SKU in the Seller Portal item management area and confirm it is active with sellable quantity. Then open the same SKU in your BigCommerce catalogue (the stock source of truth) and confirm it reads out of stock. The risk is real when Newegg shows sellable and BC shows zero. Because this is a cross-channel card, always check both the Newegg Seller Portal and the BC stock view. Why the Vortex IQ value may legitimately differ:
ReasonDirectionWhat to do
Sync lag. A BC stock change may not have propagated to Newegg yet, or a sync may be mid-flight.VariableAllow for the inventory sync cadence, then re-check both sources.
Stock buffer. A safety-stock or buffer rule may keep a Newegg listing sellable below BC’s zero threshold.Vortex IQ higherConfirm the buffer policy matches intended behaviour.
Match key. SKU mismatches between BC and Newegg can mask or inflate the count.VariableConfirm the SKU mapping is correct in both channels.
Cross-connector reconciliation: because this card spans Newegg and BigCommerce, reconcile against both the Newegg Seller Portal and the BC stock source of truth. For divergence investigations, use Vortex Mind.

Known limitations / merchant FAQs

Q: How often does Active Newegg Listings for OOS SKUs on BC update? This is a real-time card. It re-compares Newegg availability against BC stock on every data refresh (typically every 30-60 minutes for live integrations) and can be forced with a manual refresh from the dashboard. Q: Why does my Newegg Seller Portal show a different number? The portal shows only the Newegg side, so it cannot reveal the BC mismatch on its own. Differences usually come from inventory sync lag, stock-buffer rules that keep a listing sellable below BC’s zero, and SKU match-key mismatches. Compare the same SKU in the Seller Portal and the BC stock view before assuming a real divergence. Q: How does this relate to the other cross-channel cards? It is the availability member of the Cross-Channel: Revenue at Risk cluster: this card is about stock you cannot back, while the drift card is about fields that disagree and the Feedonomics card is about items that never published. Pair with Egg Badge Status, since oversells and cancellations feed the badge directly. Q: Can I customise the alert threshold? Yes, sensitivity thresholds are configurable per profile in the Sensitivity tab. The default fires above zero because any oversell exposure matters, but you can adjust it to match your business baseline.

Tracked live in Vortex IQ Nerve Centre

Active Newegg Listings for OOS SKUs on BC is one of hundreds of KPI pulses Vortex IQ tracks across Newegg Marketplace 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.