Skip to main content
Metrics type: Cross-Platform Metrics • Category: Ecommerce Platform
SKUs that diverge between Shopify and Amazon. Brand-trust killer + de-listing risk under MAP policies.

​
At a glance

A live count of SKUs whose Shopify listing diverges materially from the same SKU’s Amazon listing, on price (>20% gap), title (mismatch beyond minor wording), or stock status. Brand-trust killer + de-listing risk under MAP / RPM policies + a tax / regulatory red flag in regulated categories.

​
Calculation

Calculated automatically from your Shopify 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 Shopify Plus + amazon.com (FBA). 1,240 active SKUs across both. Reading taken on 12 Apr 26. The card reads 51 drifted SKUs, well above the >5 alert threshold. Six things to notice:
  1. The 14 “Amazon lower than Shopify” is the MAP / RPM risk. If this brand has a manufacturer agreement with MAP pricing, customers buying via Amazon at the lower price triggers a contract breach. Some manufacturers will revoke distribution rights for repeat offences. The drift may not be the brand’s fault (Amazon’s repricer chasing competitors) but the contractual liability sits with the seller.
  2. The 22 “Shopify in-stock, Amazon OOS” creates a bad customer-journey. A customer who saw a Meta ad, clicked through to Amazon (because Amazon was their search default), found OOS, and gave up. They might have bought from Shopify if directed there. Pair with Active Ads on Out-of-Stock SKUs to find the wasted ad spend on the Amazon side.
  3. The 5 “Shopify OOS, Amazon in-stock” is the worse oversell risk. Customers buying on Shopify when only Amazon has stock will face cancellation or delay, customer-trust hit on the brand’s primary channel.
  4. Title drift is the brand-equity issue. When the same SKU has different titles on Shopify (“Premium Linen Throw, Sage”) vs Amazon (“Linen Throw Blanket Green Premium 100% European Linen”), customers second-guess whether it’s the same product. Conversion suffers and review ratings on Amazon don’t transfer to Shopify reviews.
  5. The fix-cadence is uneven. Shopify is the “source of truth” for most brands; Amazon listing updates require Amazon’s slow approval workflow (24 to 72 hours for content changes). So drift naturally accumulates after every Shopify price update, then flushes when the merchant manually pushes to Amazon.
  6. Auto-sync apps reduce but don’t eliminate. Codisto, Shopify’s Amazon sales channel, and CedCommerce all sync prices and content automatically. They cut drift by 70 to 90% but don’t catch every case (custom Amazon listings, A+ content overrides, repricer interference). The card surfaces what auto-sync misses.

​
Sibling cards merchants should reference together

Catalogue drift is a hygiene card. Pair these to triage and prevent:

​
Reconciling against the vendor’s own dashboard

Where to look in Shopify Admin: Shopify Admin can’t surface this directly, it has no live link to Amazon catalogue data. The closest manual reconstruction is:
  • Shopify Products → export the catalogue.
  • Amazon Seller Central → Inventory → Manage All Inventory → export the catalogue.
  • VLOOKUP / merge in spreadsheet software, manually flag SKUs where price difference > 20% or titles differ.
This is the manual workflow most brands use today; it takes 2 to 4 hours per audit and is typically done quarterly. This card automates it continuously. Other views that look related but aren’t the same:
  • Shopify Amazon Sales Channel app: shows sync status of Shopify→Amazon listings but doesn’t surface drift after sync (e.g. when Amazon’s repricer overrides). Surfaces the act of pushing, not the resulting state.
  • Codisto / CedCommerce dashboards: similar to the Amazon channel app, focused on sync status not drift detection.
  • Amazon Brand Registry → Brand Health: shows hijacker / counterfeit issues, distinct from authorised-listing drift.
  • Amazon Reports → Manage Pricing: shows which of your prices are uncompetitive vs Buy Box. Useful for repricer tuning; doesn’t reconcile against Shopify.
Why our number may legitimately differ from a manual audit: Cross-connector reconciliation: This card IS a cross-connector data-quality check. The relationships:

​
Known limitations / merchant FAQs

Why is the card showing zero or N/A? Three causes:
  1. Amazon SP-API connector isn’t connected. The card requires both Shopify and Amazon connections. Connect in Settings → Connectors → Amazon SP-API.
  2. No SKUs are matching across the two catalogues. If your Shopify catalogue and Amazon catalogue use entirely different SKU naming and there are no GTINs / EANs on either side, the matcher can’t pair them. Check the “match-failed” tab on the card; if it shows your full catalogue, the matcher needs reconfiguration in Settings → Connectors → Amazon SP-API → SKU mapping.
  3. Catalogues are perfectly synced. Rare but possible if you use Codisto or the official Amazon channel app and update Shopify-only.
Why is my count rising every Monday morning? Because the brand probably ran a price update over the weekend (most retail price changes happen Sunday evening to ready Monday’s stock). The Shopify side updated; the Amazon side is on Amazon’s slow approval workflow which takes 24 to 72 hours. The Monday spike is structural and resolves by Wednesday for most brands. To eliminate, push the Shopify-side change AND the Amazon-side change simultaneously via the Amazon channel app. Is title drift always a problem? Almost always, yes. Differences in product titles between Shopify and Amazon hurt search ranking on both platforms (Amazon’s A9 algorithm rewards keyword consistency; Google’s Shopping ranking rewards consistency between Shopify metadata and ad copy), confuse customers (same product, different name?), and break review-import flows where Amazon reviews can’t be tied to Shopify products via fuzzy match. The exception is regulated categories (supplements, beauty, electronics) where Amazon’s compliance content rules force a slightly different format, in those cases, configure the title-similarity threshold higher in Settings → Card → Catalogue Drift. Why does the card flag price drift on items I deliberately price differently? Some brands legitimately price higher on Amazon to recover Amazon’s referral fee (15% of revenue), so a 15 to 18% price uplift is a strategic choice not a drift. The card uses a 20% threshold by default to allow for this; configure higher (e.g. 25 to 30%) if your brand intentionally runs Amazon at premium pricing. Check that this aligns with your MAP / RPM agreements with manufacturers, the contractual ceiling is usually 5 to 15% above MAP not 25%. Does the card include third-party sellers on my Amazon listings? No. The card uses the Buy Box price as the Amazon-side comparator. Third-party sellers competing on your ASIN don’t affect this card unless they win the Buy Box (in which case the price comparator becomes their price, often a MAP violator and worth a separate hijacker / counterfeit investigation via Amazon Brand Registry). Multi-region: does the card compare US Shopify against amazon.co.uk? No. The card skips cross-currency / cross-region pairs to avoid false positives from FX. For a multi-region brand, the card produces per-region drift figures (US Shopify vs amazon.com, UK Shopify vs amazon.co.uk). If either region is missing on either platform, that pair is silently skipped. My brand has different SKU naming on the two platforms. Can I still get drift detection? Yes if you have GTINs (EANs / UPCs / ISBNs) on both sides; the matcher uses GTIN before falling back to other fields. If you have neither GTIN nor consistent SKU naming, configure a custom mapping table in Settings → Connectors → Amazon SP-API → SKU mapping. This is often a one-time setup of an hour or two for brands with up to 1,000 SKUs. The alert is at >5 drifted SKUs. Is that the right threshold? For brands with 100 to 500 SKUs, yes, more than 5 active drifts is a real issue. For brands with 5,000+ SKUs, the threshold should sit higher (20 to 50) because some background drift level is structural. For high-MAP-risk categories (supplements, electronics, branded fashion under MAP), the threshold should sit lower (1 to 3) because each drift case has contractual and de-listing implications. Action playbook when this card alerts:
  1. Sort the drift list by Shopify revenue (highest first). Top SKUs cost the most.
  2. For price drifts: decide if the gap is intentional (premium-pricing strategy) or accidental (Amazon repricer, missed sync). Fix or accept per case.
  3. For MAP / RPM violations: fix immediately. Update Amazon price to MAP, document the breach in case the manufacturer audits.
  4. For title drift: pick the canonical title (usually the latest Shopify title). Push to Amazon via the channel app. Allow 24 to 72 hours for Amazon’s editorial review.
  5. For stock drift (Shopify in-stock, Amazon OOS): check FBA inbound shipments. If short-term, accept and let restock close it. If long-term, consider switching the SKU to FBM via Amazon Multi-Channel Fulfillment.
  6. For stock drift (Shopify OOS, Amazon in-stock): pause Shopify-side ads on the SKU; the Amazon listing carries the demand until Shopify restocks.
  7. Set up auto-sync in Codisto or the Amazon channel app to prevent recurrence. The card surfaces what auto-sync misses; fewer manual fixes are needed once auto-sync is running.

​
Tracked live in Vortex IQ Nerve Centre

Catalogue Drift vs Amazon is one of hundreds of KPI pulses Vortex IQ tracks across Shopify 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.