At a glance
Listings Drifting from BC finds the Newegg listings whose price, title, or attributes have fallen out of sync with the BigCommerce (BC) source catalogue. BC is your source of truth; Newegg should mirror it. When a SKU drifts, buyers see a stale price or wrong spec on Newegg that no longer matches your store, which causes confusion, cancellations, and compliance risk. Each table row names the drifted SKU and the field that moved. It sits in the Cross-Channel: Revenue at Risk Hero cluster so owners, marketing, and operations catch drift before it costs sales.
| What it counts | Newegg listings whose price, title, or attribute values no longer match the BigCommerce source catalogue, as compared by the Vortex IQ cross-channel integration. The table breaks the drift down row by row per SKU. |
| Sample type | Backend API data from Newegg Marketplace and BigCommerce, compared field by field and refreshed on the standard data refresh. |
| Why it matters | Drift means buyers on Newegg see something your BC store no longer shows: a stale price, an old title, or a wrong spec. That drives buyer confusion, return and cancellation risk, and MAP or compliance exposure when the drifted price is wrong. |
| Reading the value | Zero means Newegg mirrors BC cleanly. Any non-zero count means at least one SKU has drifted; open the table to see which SKUs and which fields moved, then re-sync from BC. |
| Currency | count |
| Time window | 30D |
| Alert trigger | >10 SKUs |
| Sentiment key | neg_xc_catalogue_drift_vs_bc |
| Roles | owner, marketing, operations |
Calculation
Calculated automatically by comparing your Newegg listings against the BigCommerce source catalogue. For each matched SKU the card checks price, title, and key attributes, and counts the listing as drifted when any monitored field diverges. The table lists each drifted SKU with the field that moved. 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 Listings Drifting from BC for a typical merchant on Newegg Marketplace. Suppose the card reads 7 drifted SKUs. Opening the table shows four where the BC price was cut for a promotion but Newegg still carries the old higher price, two where a title was tidied on BC and never re-pushed, and one where a graphics card’s memory spec was corrected on BC but stayed wrong on Newegg. The price-drift rows are the urgent ones: buyers comparing channels see an inconsistent price, and the higher Newegg figure could trip a brand’s MAP rules if BC was already at the floor. The merchant re-syncs all seven from BC and the count falls to zero. For deeper investigation, use Vortex Mind to trace which sync job or feed step let the drift through; for natural-language exploration, ask Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
neg_xc_listed_but_oos_on_bc | Cross-Channel sibling: Newegg listings live while OOS on BC. |
neg_xc_feed_rejection_vs_listings | Cross-Channel sibling: items failing feed validation before publish. |
neg_xc_price_parity | Cross-Channel sibling: MAP parity across Newegg, Amazon, and Walmart. |
neg_map_violations | Listing Health sibling: MAP violations drift can cause. |
neg_attr_completeness | Listing Health sibling: attribute gaps that surface as drift. |
Reconciling against Newegg Seller Portal
Where to look in the Newegg Seller Portal: Open the drifted SKU in the Seller Portal item management area and read its live price, title, and attributes. Then open the same SKU in your BigCommerce catalogue (the source of truth) and compare field by field. The drift is real when the two source-of-truth views disagree on a monitored field. Because this is a cross-channel card, always check both the Newegg Seller Portal and the BC catalogue, not just one. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Sync lag. A BC change may not have propagated to Newegg yet, or a re-sync may be mid-flight. | Variable | Allow for the sync cadence, then re-check both sources. |
| Field scope. Vortex IQ monitors a defined set of fields; a difference in an unmonitored field will not count. | Vortex IQ lower | Confirm which fields the profile compares. |
| Match key. SKU or identifier mismatches between BC and Newegg can mask or inflate drift. | Variable | Confirm the SKU mapping is correct in both channels. |