SKUs where the BC listing and Amazon listing have diverged. Buyers compare and bounce, close the gap.
At a glance
The count of SKUs where the BigCommerce catalogue listing and the corresponding Amazon (or eBay, Walmart, Facebook) listing have diverged on price, title, image, or description. Cross-connector view: buyers shop both surfaces, find different facts, lose trust, and bounce. The card flags drift before customers do.
| What it counts | SKUs where the BC catalogue product (name, price, description, image_url) and the marketplace listing have absolute or relative differences exceeding configured thresholds (default: price drift >5%, title drift detected by token-overlap, image drift via hash mismatch). |
| VAT / tax treatment | Price comparisons are tax-exclusive at the catalogue layer (BC stores list price pre-tax in price); marketplaces have their own tax configuration. The drift detection compares list prices, not customer-paid prices. |
| Shipping | n/a, this is a catalogue-layer comparison. |
| Discounts | Excluded; promotional pricing is volatile and would generate noise. The card compares regular list prices. |
| Refunds | n/a. |
| Currency | Marketplace-currency-aware. Drift detection accounts for currency-locked marketplaces (Amazon UK = GBP) and uses the merchant’s BC list price in the equivalent currency for comparison. |
| Channels / sources | Cross-channel by definition; the whole point is comparing BC catalogue (channel_id = 1) against marketplace channels (Amazon, eBay, Walmart, Facebook). |
| Drift dimensions detected | Price (numeric % difference), title (token-overlap < 70%), image (perceptual-hash mismatch), description (keyword presence loss > 30%). Each surfaces a separate row per SKU. |
Incomplete / Declined orders | n/a, not order-related. |
| Why drift matters | Customers price-shop across surfaces; finding a 42 on Amazon erodes trust (“which is the real price?”). Title divergence breaks brand consistency; image divergence triggers Amazon listing-suppression algorithms. |
| Time window | RT (real-time, refreshed each catalogue sync; typically every 30-60 minutes) |
| Alert trigger | any SKU price/title/image mismatch >20% drift, fires on the most material drift. |
| Roles | owner, marketing, operations |
Calculation
Calculated automatically from your BigCommerce data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US homewares brand on BigCommerce Enterprise, with Amazon Channel Manager. Snapshot at 09:00 UTC on 13 Apr 26.| SKU | BC value | Amazon value | Drift type | Severity |
|---|---|---|---|---|
| BED-LIN-K-IVR | $129.00 | $139.00 | Price +7.8% | Material |
| TWL-6PK-IVR | ”Towel Set 6pk Ivory" | "6 Towels Cream / Off-White” | Title divergence | Brand inconsistency |
| THR-CSH-18-NVY | image_v3.jpg | image_v1.jpg | Image mismatch (12 weeks old on Amazon) | Listing-suppression risk |
| RUG-3X5-GRY | 349 (match) | n/a | n/a | Healthy |
| CDLE-3PK-VNL | ”Vanilla scent, soy wax” | (description blank) | Description gap | Discoverability loss |
| Total drifted SKUs (alert: >20% drift) | 2 SKUs above 20% threshold |
- **The BED-LIN-K-IVR price gap of 129 on BC and $139 on Amazon and conclude the merchant either inflates Amazon prices or runs deceptive sales. Price consistency across channels is non-negotiable for brand-aware buyers.
- The TWL-6PK title divergence breaks brand search. A customer searching “Towel Set 6pk Ivory” finds the BC listing; the Amazon variant ranks for different terms (“6 Towels Cream”). The store loses dual-surface SEO power because each surface optimises for different keywords on the same product.
- The THR-CSH image mismatch is 12 weeks old. Amazon’s algorithm penalises listings whose images haven’t refreshed in over 8 weeks for some categories; the listing’s BSR may already have slipped. Image syncs are the most commonly broken Channel Manager job.
- The CDLE description gap costs Amazon SEO. Amazon’s search algorithm uses description keywords; a blank description means the product doesn’t rank for “vanilla soy candle” even though BC’s listing is fully optimised.
- Fix the price drift first, smallest fix, biggest trust impact.
- Run Channel Manager → Force resync on the divergent SKUs to push current BC values to the marketplace.
- Audit the description-gap SKUs for marketplace-specific content rules (Amazon strips HTML tags from descriptions; if your BC description uses HTML, the marketplace version is empty by default).
- Set up automated drift monitoring so this doesn’t happen again, the Vortex Mind catalogue-drift report includes a daily-export option for ops review.
Sibling cards merchants should reference together
| Card | Why pair it with Catalogue Drift |
|---|---|
| BC XC Amazon Revenue Share | Revenue context, drift on a high-revenue Amazon channel matters more than on a small one. |
| BC Channel OOS per Channel | The other big Channel Manager hygiene issue. Pair for a complete catalogue-health view. |
| BC Top SKUs | If your top SKUs appear in the drift list, that’s a high-priority fix. |
| Top Products | Same intent, revenue side. |
amazon_sp.amazon_listing_suppressions | Amazon-side listing-quality signals; correlate with drift detection. |
| BC Channel Revenue Mix | Concentration context, drift on a 30%-of-revenue channel is more urgent. |
| Missing Descriptions | The catalogue-side gap that often shows up here as drift. |
| Missing SEO | Same intent for SEO-relevant fields. |
Reconciling against the vendor’s own dashboard
Where to look in BigCommerce Control Panel: Channel Manager → per-channel listings shows current marketplace values. Products → View shows the BC catalogue side. BC does NOT compare them automatically; you have to read each separately and spot drift manually. Other BC views that look adjacent:- Channel Manager → Sync activity log: shows when each SKU last synced; gaps suggest drift might exist.
- Listings → Listings status: shows publication state per channel, not value drift.
| Reason | Direction |
|---|---|
| Threshold tuning. Our default 5% price drift may be tighter or looser than a merchant’s manual audit threshold. | Variable |
| Currency normalisation. We compare per-currency; manual audits sometimes compare USD-equivalent and call FX swings “drift”. | Variable |
| Image hash sensitivity. We use perceptual hashing; minor crops or compression changes register as differences depending on configured tolerance. | Could over-flag |
| Description tokenisation. Our token-overlap rule is configurable; aggressive settings flag minor edits as drift. | Variable |
| Sync lag. A SKU just updated in BC may still show old marketplace values until the next Channel Manager sync. | Vortex IQ flags transient drift |
| Card | Expected relationship | Notes |
|---|---|---|
amazon_sp.amazon_listings | Amazon-side listing data; the marketplace half of the drift comparison | Direct dependency |
google_ads.ga_merchant_feed | Google Shopping feed values; an additional surface to compare BC against | Same drift logic, different target |