Listings Drifting from BC, Depop

Listings Drifting from BC for Depop 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: Cross-Platform: Revenue at Risk

At a glance

Listings Drifting from BC is the cross-platform card that flags Depop listings whose price, title, description or availability has drifted out of sync with the same item in your BigCommerce catalogue, treated as the source of truth. For sellers running Depop as a secondary channel off a BigCommerce backbone, drift is where money leaks: a stale price, an outdated title or a still-live listing for a withdrawn product. The card lists the drifting SKUs so you can realign them.

What it counts	Depop listings whose key fields no longer match the source BigCommerce record, listed row by row with the drifting field.
Sample type	Cross-platform comparison of Depop integration data against the BigCommerce catalogue, refreshed on the standard data refresh.
Why it matters	When Depop drifts from the BigCommerce source, buyers see wrong prices or buy items you no longer sell, creating refunds, disputes and manual cleanup. Drift is silent until an order forces the issue, so surfacing it early protects both revenue and reputation.
Reading the value	Each row is a SKU to reconcile. A handful is normal churn; a count above roughly ten SKUs signals a sync gap worth fixing at the process level, not item by item.
Currency	count (drifting SKUs)
Time window	30D
Alert trigger	> 10 SKUs
Sentiment key	dep_xc_catalogue_drift_vs_bc
Roles	owner, marketing, operations

Calculation

The card compares each Depop listing to its matching BigCommerce record across key fields, price, title, description and availability, and lists those that have diverged. Vortex IQ reads both sides through their integrations and matches on the shared product identifier. Which fields count as drift is configurable in the Alert Rules tab.

Worked example

A representative reading of Listings Drifting from BC for a typical multi-channel resale brand on Depop. The card listed 14 SKUs, above the 10-SKU line. Vortex Mind grouped them: nine had a price that had been cut on BigCommerce but not on Depop, three carried an old title from before a rebrand, and two were live on Depop despite being discontinued on BigCommerce. Because the pattern was a one-way sync gap, the seller fixed the export job rather than editing 14 listings by hand. Drift fell back under the threshold within a sync cycle. To pull the list, ask Ask Viq for Depop listings whose price differs from BigCommerce.

Sibling cards merchants should reference together

Card	Why merchants reach for it
dep_xc_listed_but_oos	Cross-platform sibling: availability drift in its most costly form.
dep_xc_feed_rejection	Cross-platform sibling: feed errors that cause drift.
dep_xc_price_parity	Cross-platform sibling: price drift across marketplaces.
dep_revenue_at_risk	Outcome sibling: drift feeds revenue at risk.
dep_total_listings	Catalogue sibling: the listing base being compared.

Reconciling against Depop

Where to look in Depop’s own dashboard:

Depop shows each listing’s current fields, but it has no view of your BigCommerce source, so drift is invisible there by definition. Reconcile by opening a flagged listing in Depop and comparing it field by field to the same product in BigCommerce.

Why the Vortex IQ value may legitimately differ:

Reason	Direction	What to do
Match key. Drift detection depends on a reliable shared identifier between channels.	Variable	Confirm SKU mapping is clean.
Field scope. Which fields count as drift is configurable.	Variable	Check your Alert Rules settings.
Sync timing. A recent BigCommerce edit may not have propagated yet.	Variable	Allow one sync cycle before acting.

Cross-connector reconciliation: this card only exists because Vortex IQ reads both channels. Read it with the sold-elsewhere and price-parity cards for the full cross-platform risk picture. For divergence investigations, use Vortex Mind.

Known limitations / merchant FAQs

Q: How often does Listings Drifting from BC update? The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations), comparing both channels each cycle.

Q: Why is BigCommerce the source of truth and not Depop? Because most multi-channel sellers manage master product data in their commerce platform and treat marketplaces as outlets. You can change which side is authoritative in your profile if your setup differs.

Q: Most of my drift is price. What does that mean? A one-way price sync gap, usually a price change on BigCommerce that did not propagate to Depop. Fix the export or sync job rather than editing listings individually.

Q: Can I customise the alert threshold? Yes, both the SKU count threshold and which fields count as drift are configurable per profile in the Alert Rules tab.

---

Tracked live in Vortex IQ Nerve Centre

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