Skip to main content
Card class: Hero • Category: Marketplace
ASINs whose price/title/image diverge from DTC siblings, brand consistency, MAP, SEO impact.

​
At a glance

Per-ASIN diff between your Amazon listing and your DTC (Shopify / BigCommerce / Adobe Commerce) listing for the same SKU. Surfaces ASINs whose price, title, image, or description has drifted out of sync with the canonical DTC version, a brand-consistency, MAP-policy, and SEO risk.
What it countsFor each SKU mapped to an Amazon ASIN AND a DTC product, compute a diff across price, title (first 80 chars), main image hash, and description length. Flag if any field exceeds a per-attribute threshold (>20% price gap, title hamming distance >12, image hash distance >8, description length delta >30%).
API endpoint + reportSP-API Listings Items API for Amazon-side fields, plus the connected DTC connector (Shopify Admin API, BigCommerce API, or Adobe Commerce REST) for the canonical version. Reconciled in our Vortex IQ Nerve Centre cross-channel index, not from Amazon Reports API.
ASIN vs account scopePer-ASIN with summary count, only ASINs with a corresponding DTC SKU are evaluated. Amazon-only ASINs (no DTC sibling) are excluded.
Buy Box impactIndirect. Drift on price below DTC violates MAP (Minimum Advertised Price) policies and can trigger reseller pricing wars that erode Buy Box. Drift on title or image hurts organic search rank.
FBA vs FBMBoth. Drift is catalogue-side; fulfilment channel doesn’t affect it.
Fees / commissionNot applicable.
RefundsNot applicable.
CancellationsNot applicable.
CurrencyPrice drift is computed in DTC-side currency, with Amazon’s settlement-currency price converted at the day’s FX rate before comparison. Stores that intentionally price differently across geographies (UK store in GBP, amazon.co.uk in GBP) compare directly.
Marketplace dynamicsDrift on Amazon below DTC list price is the most common trigger; it provokes resellers to undercut both channels and to fight you for Buy Box.
Return-window vs refund-windowNot applicable.
Time window30D (drift is a state, but the card shows the count of ASINs that have drifted in the last 30 days, allowing the merchant to see new drifts vs longstanding ones).
Alert trigger>10 ASINs drifting >20%, driven by sentiment_key: missing_attrs.
Rolesowner, marketing.

​
Calculation

Calculated automatically from your Amazon (Selling Partner) 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 hybrid Shopify + Amazon outdoor brand. 180 SKUs mapped between Shopify and amazon.co.uk. Card snapshot at 11:30 BST on 04 Apr 26 reads 17 drifting ASINs (12 over the 20% threshold). The drill-down ranks drift by severity:
ASINSKUField driftedDTC valueAmazon valueDeltaLikely cause
B07OUT0001TENT-3P-NAVYPrice£189 (DTC list)£149 (Amazon)-21%Stale Amazon price after DTC re-pricing 18 Mar 26
B07OUT0002JACKET-SHELL-LPrice£119£99-17%Same root cause, batch price update on DTC
B07OUT0003PACK-DAYHIKETitle”Day Hike Pack 24L""Day-Hike Backpack 24-Litre Hiking Bag Outdoor”Amazon title is keyword-stuffedAmazon title was edited for SEO 6 weeks ago, never synced back
B07OUT0004HEADLAMP-PROImage hash(clean studio shot)(older lifestyle shot)distance 14DTC image refreshed in Q1, Amazon not updated
B07OUT0005SOCK-MERINO-3PKDescription480 chars220 chars-54%Amazon listing imported from old supplier feed, never enriched
… 12 more…mixed…………
Five things to notice that are specific to Amazon:
  1. Price drift below DTC = MAP violation risk. The first 8 of the 17 drifting ASINs are all priced 15 to 25% below DTC. This is a textbook MAP violation; competing resellers will see your low Amazon price and either match it (forcing you into a price war) or report you to your own brand-agreement enforcement team. Cross-check on MAP Violation Risk (vs DTC).
  2. Buy Box loss = sales loss, instantly, but title/image drift compounds slowly. Price drifts that go unfixed lose Buy Box; title/image drifts erode organic search rank over weeks. The 17 ASINs above were silently shedding rank for 4 to 8 weeks before this card surfaced them. The lost rank rarely fully recovers; you can pay it back with Sponsored Ads but the organic recovery curve is slow.
  3. Commission erodes 12 to 15% of headline, but doesn’t drive drift. Drift is a pure catalogue-hygiene problem. Fees and commission are downstream and unrelated. The fix is a sync workflow (DTC-to-Amazon, ideally one-way from DTC as source of truth), not a pricing decision.
  4. Amazon-first buyers don’t migrate to your DTC site to find the right price. A common merchant misconception: “the customer can compare prices on our DTC site”. They don’t. Amazon shoppers buy on Amazon. If your Amazon price is wrong (high OR low), you eat the consequence; the customer never sees the DTC version.
  5. Out-of-stock can mask drift. When an ASIN goes OOS, Amazon hides the price from the search result and the drift is invisible to the algorithm temporarily. The card still flags the drift (it’s a state diff, not a behaviour-based signal), but resellers won’t notice the price gap until the ASIN is back in stock. Don’t use an OOS as an excuse to delay the fix.

​
Sibling cards merchants should reference together

Catalogue drift compounds slowly. Pair it with these to size the fix and trace consequences:
CardWhy pair it with Catalogue Drift
Catalogue Drift Revenue at RiskTranslates the count into £/month at risk. The dollar size of the drift, not just the number of ASINs.
MAP Violation Risk (vs DTC)The price-only subset, where Amazon is below DTC list price. Triggers reseller pricing wars.
Buy Box TrendDrift on price below DTC often correlates with Buy Box loss because resellers undercut both channels.
Suppressed ListingsDrift on attributes (title length, image policy) can flip an ASIN from drifted to suppressed if it crosses a hard policy line.
Top ASINs by RevenuePrioritise drift fixes on top-revenue ASINs first; the long tail can wait.
Listing Quality ScoreAmazon’s own score; drifts on title/bullet/image hurt this score and downstream search rank.
Shopify Total RevenueThe DTC counterpart; the source-of-truth side for most brands.
Channel Mix (Amazon vs DTC)Drift becomes a strategic problem if you’re highly Amazon-dependent (>70%); the price war becomes existential.

​
Reconciling against the vendor’s own dashboard

Where to look in Amazon Seller Central: Amazon does not surface “drift vs DTC” anywhere natively (Amazon doesn’t know about your DTC site). The closest equivalents:
  1. Inventory → Manage Inventory lets you eyeball your Amazon-side price, title, and image per ASIN. Compare manually to your DTC product list.
  2. Catalogue → Listing Quality and Help flags listings missing recommended attributes (bullets too short, no A+ content, etc.). This is Amazon’s view of “the listing isn’t optimised”, which often correlates with our drift detection (drifted from a richer DTC version).
  3. Reports → Business Reports → Detail Page Sales and Traffic shows traffic and conversion per ASIN. ASINs that drift on title/image often show falling conversion rate even with steady traffic; this is the symptom of unfixed drift.
Why our number may legitimately differ from anything you’d build manually:
ReasonDirectionWhy
Time zoneBoundary days onlyDrift detection runs on UTC stamps; DTC connectors run on shop-timezone. A price change made on DTC at 23:30 GMT shows up in our diff after Amazon’s next sync (up to 30 minutes); a manually-built reconciliation could land on either side of the boundary.
Settlement-period lagNot applicableDrift is a state, not a settlement-related metric.
API rate limitsOurs can lag by 30 to 60 minutesThe Listings Items API is rate-limited; for large catalogues the connector polls in batches. A freshly-fixed drift may persist on this card for up to an hour after the actual fix.
Reports API generation latencyNot applicableThis card uses the Listings API directly, not the Reports API. No async generation lag.
DTC source-of-truth choiceEitherThe card assumes the DTC connector (Shopify / BigCommerce / Adobe) is the canonical version. If the brand intentionally prices differently across channels (some DTC-only specials), those are flagged as drift here. Toggle the per-ASIN “expected drift” allowlist in Nerve Centre → Drift Settings to suppress intentional differences.
Cross-connector reconciliation: This card is inherently cross-connector. It does not exist without both an Amazon connector AND a DTC connector. The reconciliation IS the metric.
CardExpected relationshipWhat causes legitimate divergence
shopify.total_revenueDrift count rises when Shopify product data changes faster than Amazon listings sync.Shopify-side bulk price updates (sales, promotions) often trigger drift bursts here on the day of the change.
bigcommerce.total_revenueAs above for BigCommerce stores.Same dynamic.
amazon_ads.aads_acosIndirect: drift erodes organic conversion, often forcing higher ad spend to maintain volume, raising ACOS.Cross-check on a 30-day correlation between drift count and ACOS.
stripe.stripe_total_revenueNone directlyDrift is catalogue-side; Stripe is payment-side.

​
Known limitations / merchant FAQs

My Amazon prices are intentionally different from DTC. Why is this card flagging drift? Because by default the card treats DTC as the source of truth. Some brands legitimately have different pricing across channels (Amazon-specific bundles, exclusive variants, geographic pricing). Add those ASINs to the allowlist in Nerve Centre → Drift Settings. They’ll be excluded from the count but still visible on the drill-down with an “intentional” badge. The card will then only flag unintentional drift. My headline shows 17 drifting ASINs but I just fixed 5. Why hasn’t it dropped? The Listings Items API refreshes every 30 to 60 minutes. The DTC connectors update on their own webhook schedules (Shopify is near-real-time, BigCommerce is 2 to 5 minute polling, Adobe varies). Allow up to an hour for both sides to re-sync before the card recomputes. Persistent gap >2 hours after a fix is worth checking; the most common cause is one connector being mid-rate-limit-backoff after a bulk update. Does the card know about Amazon variations (parent / child ASINs)? Yes, drift is computed at child-ASIN level, not parent. Each variant has its own price, title, image, and description and each is diffed independently. If a parent has 6 colour variants, all 6 are evaluated separately. Common pattern: 1 colour variant drifts because the supplier renamed the SKU and the auto-mapper missed it; the other 5 stay clean. ACOS spiked when drift went up. Why? Two reasons. (1) Title/image drift erodes organic conversion rate; you compensate with Sponsored Ads to maintain unit volume, which raises ACOS (the same units cost more in ad spend). (2) Price drift below DTC invites resellers, who out-bid you on Sponsored Brands placements, again raising your ACOS. Cross-check on Amazon Ads ACOS. The structural fix is to fix the drift; trying to throw more ad spend at the symptom usually worsens ACOS without recovering rank. FBA fees, do they factor into drift? Not directly. Drift is a catalogue-state metric. But high FBA fees on a low-margin SKU sometimes tempt brands to raise the Amazon price relative to DTC to preserve margin, creating an “Amazon higher” drift. The card flags both directions (Amazon higher OR lower). Decide deliberately, don’t drift accidentally. See FBA Fees for the underlying cost driver. Multi-marketplace, does drift apply per marketplace? Yes. Each marketplace (UK, DE, FR, IT, ES, US, CA, JP, etc.) has its own catalogue and its own pricing in local currency. The card computes drift per ASIN-marketplace pair, with FX conversion to the DTC currency for price comparisons. A SKU live on UK at £28 and on DE at €34 (which converts to roughly £29) would NOT flag drift; the local prices are aligned post-FX. The drill-down splits by marketplace. Settlement timing, does this affect drift? No. Drift is a catalogue state and unrelated to disbursement cycles. Once you fix a drifted listing, the impact (recovered organic rank, restored Buy Box, fewer reseller wars) flows through normal Amazon timings. Pair with Pending Settlement only if you’re auditing whether a drift-related Buy Box loss caused a settlement-period revenue dip. Return-window confusion, do return-window mismatches cause drift? Sometimes, on description-length drift. If your DTC product page describes a “30-day no-questions-asked returns” policy and your Amazon listing description doesn’t (because Amazon has its own return policy displayed separately), you can end up with a description-length drift flagged here. This is usually a false positive; either suppress it via the allowlist or align the description text deliberately. Amazon’s actual return policy (30 days from delivery for most categories) overrides whatever you put in your description. Why are Shopify-Amazon channel app orders not feeding drift state? Because the channel app is a publishing tool; it pushes Shopify product data to Amazon at intervals. The Listings Items API tells us what Amazon currently shows. If the channel app is configured to sync price but not title, you’ll see persistent title drift even though the channel app is running. Most brands using the Shopify Amazon channel app have title drift on at least 30% of ASINs because of this partial-sync default; turning on full-attribute sync removes most drift, at the cost of overwriting any Amazon-specific SEO work you’ve done. Why does today’s count fluctuate? Because both sides update independently. A Shopify price change at 14:00 propagates through the Shopify webhook within minutes, but Amazon’s reflection of the equivalent ASIN price doesn’t update until you push (or until the channel app syncs, or until you manually edit). The card may briefly flag drift between 14:00 and (say) 14:35, then drop the flag when the Amazon side catches up. Wait an hour after any bulk DTC update before triaging this card; you’ll otherwise be chasing transient flags.

​
Tracked live in Vortex IQ Nerve Centre

Catalogue Drift vs DTC is one of hundreds of KPI pulses Vortex IQ tracks across Amazon (Selling Partner) 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.