At a glance
Listings Drifting from BC is a cross-channel metric tracked from Vinted data alongside your BigCommerce catalogue. It lists items whose Vinted listing has diverged from the source BigCommerce record, in price, title, condition, or availability, so the same product tells two different stories on two channels. Drift erodes trust, creates pricing arbitrage against you, and risks selling something on Vinted that is no longer correct on BigCommerce. Each drifting SKU is a small revenue-at-risk item.
| What it counts | The number of SKUs where the Vinted listing has drifted from the BigCommerce source record over the selected period, broken down by row so you can see the field that diverged. |
| Sample type | Backend API data from Vinted compared against the BigCommerce catalogue, refreshed on the standard data refresh. |
| Why it matters | When the two channels disagree, you can oversell, mis-price, or misrepresent condition. Drift left unchecked becomes refunds, complaints, and reconciliation work. |
| Reading the value | Lower is better. A count above the safe number of SKUs means catalogue sync is slipping and the divergent items need to be re-aligned to the BigCommerce source. |
| Currency | count |
| Time window | 30D |
| Alert trigger | Fires when more than the configured number of SKUs have drifted from BigCommerce. |
| Sentiment key | vin_xc_catalogue_drift_vs_bc |
| Roles | owner, marketing, operations |
Calculation
Calculated automatically from your Vinted and BigCommerce data. Vortex IQ matches Vinted listings to their BigCommerce source records and flags those where a tracked field, price, title, condition, or availability, has diverged beyond tolerance. 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 Pro seller on Vinted. The card shows 14 SKUs drifting, past the safe number. The breakdown reveals the pattern: eight have a price on Vinted that no longer matches a BigCommerce price change, four were marked sold or discontinued on BigCommerce but are still live on Vinted, and two have title edits that never propagated. The action is to re-sync the eight prices, pull or update the four availability mismatches before one oversells, and align the two titles. The structural fix is to tighten the sync cadence between BigCommerce and Vinted so drift does not accumulate. For deeper investigation, use Vortex Mind to see which field drifts most often; for natural-language exploration, ask Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
vin_xc_listed_but_oos_on_bc | Cross-channel sibling: items live on Vinted but sold elsewhere. |
vin_xc_feed_rejection_vs_listings | Cross-channel sibling: feed validation failures behind drift. |
vin_xc_price_parity | Cross-channel sibling: price gaps versus other resale platforms. |
vin_revenue_at_risk | Executive sibling: revenue exposed by drifting SKUs. |
vin_total_listings | Listing-health sibling: the catalogue base being compared. |
Reconciling against Vinted
Where to look in Vinted’s own dashboard: Vinted shows the current state of each listing, but it has no view of your BigCommerce source, so it cannot show drift on its own. Reconcile by opening a flagged SKU on Vinted and comparing the named field against the same product in BigCommerce. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Sync timing. A recent BigCommerce change may not have propagated to Vinted yet, so brief drift is expected. | Higher right after a change | Allow a sync cycle before treating drift as a problem. |
| Tolerance. Vortex IQ flags drift beyond a tolerance; tiny rounding or formatting differences may sit below it. | Variable | Confirm the tolerance for each field. |
| Match basis. Drift detection relies on matching Vinted listings to BigCommerce SKUs; unmatched items are excluded. | Variable | Confirm the SKU match coverage. |