Skip to main content
Metrics type: Cross-Platform Metrics • Category: Ecommerce Platform
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.

​
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. What’s interesting:
  1. **The BED-LIN-K-IVR price gap of 10isenoughtolosetrust.∗∗Customerscomparingpricesacrosssurfacesfind10 is enough to lose trust.** Customers comparing prices across surfaces find 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.
  2. 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.
  3. 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.
  4. 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.
Action priority order:
  1. Fix the price drift first, smallest fix, biggest trust impact.
  2. Run Channel Manager → Force resync on the divergent SKUs to push current BC values to the marketplace.
  3. 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).
  4. 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

​
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.
Why our drift count may differ from a manual audit: Cross-connector reconciliation:

​
Known limitations / merchant FAQs

My drift count is high after a Channel Manager re-sync, did the sync break things? Probably not, the sync surfaced existing drift that was previously invisible. Channel Manager doesn’t always overwrite marketplace fields with BC values; some marketplaces preserve their own values (Amazon’s “Catalog Item” model). Drift detection runs on whatever is currently published on each surface, so a fresh sync revealing high drift means the sync isn’t propagating values cleanly. Why is price drift so common across stores? Three usual causes: (1) Manual price edits made directly on the marketplace seller portal that don’t propagate back to BC (Amazon Seller Central allows price overrides). (2) BC promotional pricing that doesn’t sync to marketplaces (the marketplace shows the regular price; BC shows the sale price). (3) Currency-rounding differences (BC stores 129.00,Amazon′sprice−ruleroundsto129.00, Amazon's price-rule rounds to 129.99). Address each at the workflow layer. Should I let prices drift across surfaces strategically? No, except for clearly-different fulfilment cost reasons. Amazon takes 8-15% commission, so some merchants list at +10% on Amazon to net the same margin. This is reasonable but should be intentional and consistent, not accidental drift. Document the rule and apply it uniformly via Channel Manager pricing rules. Title divergence isn’t really a problem, is it? It is for SEO and brand. Each surface optimises for its own search; Amazon ranks for keyword-stuffed titles while BC ranks for clean brand-first titles. Some divergence is intentional (different optimal title shapes per surface), but unintentional drift means you have a copy-management problem, not a strategy. Why does the image hash flag minor differences? Default tolerance is sensitive; minor compression changes (Amazon re-encodes uploaded images) can register as drift. Adjust the perceptual-hash threshold in Vortex Mind config if the false-positive rate is high. The trade-off: looser threshold misses genuine image-content changes (different colour, different pack size). Channel Manager auto-publishes BC changes to Amazon, why does drift still appear? Channel Manager publishes; Amazon doesn’t always accept. Amazon’s listing approval process may reject the new value silently (image fails compliance check, title contains banned terms, price violates marketplace pricing rules). The Channel Manager activity log shows publish attempts; cross-reference with this card to find Amazon-side rejections. My drift list is the same 30 SKUs week after week, what do I do? Audit those 30 individually. Common patterns: (1) Marketplace-specific variants you forgot you created (Amazon-only bundle SKUs). (2) Manually edited marketplace listings that BC keeps trying to overwrite, the marketplace edit “wins” each time. (3) Currency-rule rounding causing perpetual <$1 drift that the threshold flags. Configure exclusion rules in Vortex Mind for the chronic / intentional cases. Multi-marketplace stores: is this card aware of all marketplaces? The card consumes whichever marketplace integrations are connected (Amazon, eBay, Walmart, Facebook). Each is compared independently against BC catalogue. Drift on Walmart is shown separately from drift on Amazon for the same SKU. Should I cross-list drift between marketplaces (Amazon vs Walmart)? Currently the card compares each marketplace against BC catalogue (BC as source of truth). Marketplace-vs-marketplace drift is a more advanced view; some merchants want it, most don’t (BC is the canonical source for most). Reach out via Ask Viq if you need cross-marketplace comparison. Why doesn’t this card check Google Shopping feed values? It does, if the Google Ads merchant-feed connector is enabled. Google Shopping is an additional comparison target alongside BC catalogue. Confirm in Vortex Mind catalogue-drift configuration.

​
Tracked live in Vortex IQ Nerve Centre

Catalogue Drift (BC ↔ Amazon) is one of hundreds of KPI pulses Vortex IQ tracks across BigCommerce 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.