Listings Drifting from BC, Bonanza

Listings Drifting from BC for Bonanza stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

Metrics type: Key Metrics • Category: Marketplace

At a glance

Listings Drifting from BC is a cross-platform 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-Platform: Revenue at Risk sibling: Price Drift vs eBay / Etsy via Importer.
bon_xc_listed_but_oos_on_bc	Cross-Platform: Revenue at Risk sibling: Active Bonanza Listings for OOS SKUs on BC.
bon_xc_feed_rejection_vs_listings	Cross-Platform: 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-platform 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.

Cross-connector reconciliation: complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind.

Known limitations / merchant FAQs

Q: How often does Listings Drifting from BC update? It follows the trailing 30-day window and refreshes on the standard data refresh, typically every 30 to 60 minutes. Because it reconciles two systems, both the Bonanza pull and the BC catalog read need to land before the count settles. You can also trigger a manual refresh.

Q: Why does my Bonanza dashboard show a different number? Bonanza alone cannot show drift, since it does not know your BC values. The count here exists only because Vortex IQ holds both systems side by side. Differences usually come from a recently re-pushed feed that has not yet been re-scanned, or from filter scope.

Q: A SKU is flagged but the price looks fine to me - why? Drift is flagged on any of price, title, stock, or status. A SKU can match on price yet differ on stock or status, which still counts as drifted. Open the table entry to see exactly which field diverged.

Q: Can I customise the alert threshold? Yes, alert thresholds are configurable per profile in the Alert Rules tab. Adjust to match your business baseline rather than relying on the generic default.

---

Tracked live in Vortex IQ Nerve Centre

Listings Drifting from BC is one of hundreds of KPI pulses Vortex IQ tracks across Bonanza 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.