Skip to main content
Metrics type: Cross-Platform Metrics • Category: Marketplace

​
At a glance

Estimated revenue at risk over the next 30 days from the ASINs flagged on Catalogue Drift vs DTC. Translates the count of drifting ASINs into a £/month figure by multiplying drift severity by trailing 30D velocity by ASP. The dollar size of unfixed drift, not just the number of ASINs.

​
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 mapped SKUs. The Catalogue Drift card is showing 17 drifting ASINs; this card translates that into £3,840/month at risk. The drill-down ranks the drift by $/month at risk: Five things to notice that are specific to Amazon:
  1. Price drift below DTC is the dollar driver. The first 2 ASINs (price-drifted) account for £3,750 of the £3,840 headline. Title and image drift, while real, are slow-burn issues and typically <£300/month each. Always prioritise price drifts; they translate to dollar risk roughly 5 to 10x faster than attribute drifts.
  2. Buy Box loss = sales loss, instantly, and price drift below DTC actively invites it. When B07OUT0001 sat 21% below DTC list, three EU resellers spotted it within 9 days and listed at slightly above the brand’s Amazon price (still below DTC). The brand lost Buy Box on the ASIN within 11 days. The £2,920/month at risk became actual revenue loss; the drift caused the loss it was forecasting.
  3. Commission erodes 12 to 15% of headline, but the drift fix is free. Fixing a price drift is a one-line change in Manage Pricing or via the Listings Items API. The recoverable revenue is the headline minus referral and FBA fee blends; the operational cost of the fix is essentially zero. Always close drift issues before discussing any other margin lever.
  4. Amazon-first buyers don’t migrate to your DTC site. A common merchant misread: “the Amazon price is 21% below DTC, so I’ll just push my Amazon customers to DTC for the higher margin”. They don’t move. Amazon shoppers buy on Amazon, period. The drift fix is to align prices, not to redirect customer flow.
  5. Out-of-stock can mask drift dollar value. When the drifting ASIN goes OOS, this card’s per-ASIN $/month entry temporarily drops to zero because trailing 30D velocity drops. The drift is still there; the card just doesn’t see the dollar impact while there’s no inventory. Don’t treat OOS as a “fix” for drift; the moment stock returns, the dollar impact resumes.

​
Sibling cards merchants should reference together

This card is the dollar size of the catalogue-drift problem. Pair with these to act:

​
Reconciling against the vendor’s own dashboard

Where to look in Amazon Seller Central: Amazon does not surface “drift vs DTC revenue at risk” anywhere natively (Amazon doesn’t know about your DTC site, so it can’t compute the comparison). Closest equivalents:
  1. Reports → Business Reports → Detail Page Sales and Traffic by Child Item shows traffic and conversion per ASIN. Drifted ASINs often show falling conversion despite steady traffic; that’s the symptom of unfixed attribute drift.
  2. Catalogue → Listing Quality and Help flags listings missing recommended attributes (bullets, A+ content, etc.). This is Amazon’s view of “the listing isn’t optimised”, which often correlates with our drift detection.
  3. Pricing → Manage Pricing shows your current price per ASIN. Reconcile manually against your DTC product list to spot price drifts.
Why our number may legitimately differ from anything you’d build manually: 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.

​
Known limitations / merchant FAQs

The card says £3,800/month at risk. How urgent is this versus other revenue-at-risk metrics? Less urgent than Revenue at Risk (live) (suppression / Buy Box loss) but more urgent than long-tail catalogue-quality issues. Drift translates to dollar risk on a 14 to 30 day horizon as Buy Box erodes; suppression and Buy Box loss are immediate. Treat suppression first, drift second, listing quality third. As a rule of thumb: drift dollar value above 5% of Total Revenue deserves a sprint to fix; below 5% can be batched into the next catalogue-hygiene pass. My intentional Amazon-only pricing shows up here. How do I exclude it? Toggle the per-ASIN “expected drift” allowlist in Nerve Centre → Drift Settings. Allowlisted ASINs still appear in the per-ASIN drill-down (with an “intentional” badge) but are subtracted from the dollar headline. The card then only flags unintentional drift dollar value. ACOS spiked when this card spiked. Why? Two reasons. (1) Title/image drift erodes organic conversion; you compensate with Sponsored Ads to maintain unit volume, raising ACOS. (2) Price drift below DTC invites resellers, who out-bid you on Sponsored Brands placements, again raising ACOS. Cross-check on Amazon Ads ACOS. The structural fix is to fix drift; throwing more ad spend at the symptom worsens ACOS without recovering rank. FBA fees and commission, do they enter the dollar calculation? The headline is gross, before referral and FBA fees. Net recoverable is roughly 87% of the headline. Don’t price the operational effort against the headline number; price it against the net. A £3,800/month gross drift is roughly £3,300/month net; if your fix takes 4 hours of catalogue-team time, the ROI is excellent. Multi-marketplace, do drift dollars sum across UK + DE + FR + IT + ES? Yes, in settlement currency. The drill-down splits by marketplace because drift is per-ASIN-marketplace (the same SKU may have different prices across marketplaces, intentionally or accidentally). When intentional (geographic pricing), allowlist; when accidental, it’s drift to fix. Settlement timing, does this affect cash flow? No directly. Drift is a forward-looking forecast of revenue you’d capture if drift were fixed; settlement timing applies to actual orders, not forecasts. Once you fix drift and the recovered orders flow through, they settle on the standard 14-day cycle. Pair with Pending Settlement only when reasoning about cash-flow impact of the recovery. Return-window confusion, do return-window mismatches between Amazon and DTC contribute to drift dollar value? Sometimes, on description-length drift (the DTC product page may describe a “60-day returns” promise; Amazon’s standard 30-day window applies regardless). The card flags this as drift but the dollar severity factor is low (description drift is rarely a Buy Box loss driver). Either align the description text or allowlist; it’s not usually worth the dollar risk. Why isn’t the Shopify-Amazon channel app the source of truth here? Because most brands don’t run it, and even those who do see partial-sync-related drift (channel app pushes price but not title, etc.). The SP-API is the source of truth for what’s currently live on Amazon; the DTC connector is the source of truth for what’s intended. The drift between the two is what this card measures. If you do use the channel app, configure full-attribute sync to minimise drift; partial sync is a guaranteed source of perpetual drift dollar value. Why does today’s number fluctuate when I haven’t changed anything? Two reasons. (1) DTC-side prices and product data update independently of Amazon; a Shopify-side promo flag flipping at 14:00 can spawn drift here within minutes. (2) Trailing 30D velocity inputs are recomputed daily; a strong Tuesday on a drifting ASIN can push its $/month at risk up by £40 to £80 even though the drift state hasn’t changed. The card is intentionally responsive to both inputs; treat day-to-day moves as informative, week-to-week trends as the planning view. Why is the buyer-cohort observation on this card the same as on Total Revenue? Because it’s a structural Amazon truth, not a card-specific point: Amazon-first buyers do not migrate to DTC sites at meaningful rates. So whenever this card forecasts drift-driven revenue loss, the merchant cannot recover the lost revenue by pushing the affected SKUs through DTC channels. The fix has to be on Amazon; treating drift as “well, the customer can buy on DTC instead” is wishful thinking.

​
Tracked live in Vortex IQ Nerve Centre

Catalogue Drift Revenue at Risk 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.