At a glance
Listings Drifting from BC is a cross-channel diagnostic that compares each Bonanza item listing against its source record in your BigCommerce (“BC”) catalog and flags the SKUs that no longer agree on price, title, stock, or status. It is the canary for sync integrity across the two systems. When the count climbs past 10 SKUs, something in the feed pipeline has stalled or been overridden and your Bonanza booth is no longer a faithful mirror of BC. Treat it as a revenue-at-risk list, since drifted price and stock translate directly into lost margin or oversells.
| What it counts | The number of SKUs whose live Bonanza listing has drifted from the source BigCommerce (“BC”) record on price, title, stock, or status. |
| Sample type | Backend API data from Bonanza, refreshed on the standard data refresh. |
| Why it matters | Drift between the two systems means buyers may see a stale price or stock state, risking margin loss, oversells, and cancellations. |
| Reading the value | Lower is better; the target is zero. Each entry in the table is a SKU that needs reconciling between Bonanza and BC. |
| Currency | number |
| Time window | 30D |
| Alert trigger | >10 SKUs |
| Sentiment key | bon_xc_catalogue_drift_vs_bc |
| Roles | owner, marketing, operations |
Calculation
Each Bonanza listing is matched to its source SKU in the BigCommerce catalog, then the key fields - price, title, stock, and status - are compared. Any SKU where the two systems disagree on at least one field is counted as drifted and listed in the table. See At a glance for the window and the alert trigger, and the worked example below for a representative reading.Worked example
A representative reading of Listings Drifting from BC for a typical merchant on Bonanza. On 14 Mar 26 a seller wakes to 17 drifted SKUs against an alert trigger of 10. The table shows 11 with a stale price (BC raised prices overnight but Bonanza still shows the old figure), 4 marked in stock on Bonanza yet zero on BC, and 2 with an outdated title. The mismatched prices alone risk selling roughly 600 dollars of inventory below the new margin, so the action is to re-push the feed and reconcile the four stock-mismatched SKUs before they oversell. Vortex Mind traces upstream causes, such as a paused sync job or a manual Bonanza edit, and Ask Viq lets you ask in plain English which SKUs drifted on price this week.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
bon_xc_price_parity | Cross-Channel: Revenue at Risk sibling: Price Drift vs eBay / Etsy via Importer. |
bon_xc_listed_but_oos_on_bc | Cross-Channel: Revenue at Risk sibling: Active Bonanza Listings for OOS SKUs on BC. |
bon_xc_feed_rejection_vs_listings | Cross-Channel: Revenue at Risk sibling: Listings Failing Feedonomics Validation. |
bon_importer_sync_health | Operations sibling: Importer Sync Health. |
bon_revenue_at_risk | Revenue sibling: Revenue at Risk. |
Reconciling against Bonanza
Where to look in Bonanza’s own dashboard: In Bonanza, open the selling area and your item listings to inspect the flagged SKUs, then compare each against the source product in your BigCommerce catalog. Because this is a cross-channel card, the truth lives in two places: the Bonanza listing and the upstream BC record that should drive it. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses a trailing 30-day window 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. |