At a glance
The money tied to listings that have drifted out of sync with your source of truth, usually your DTC catalogue, in a way that risks sales. Catalogue drift means the Amazon listing no longer matches the canonical product: a wrong price, a stale title or image, a changed pack size, a discontinued variant still live, or an attribute that no longer matches the DTC record. This card values the revenue exposed by that drift so an owner, marketing, or finance lead can see the cost of letting the Amazon catalogue fall out of step. It is a cross-channel card because the comparison is Amazon listing versus DTC source of truth.
| What it counts | The estimated revenue at risk from ASINs whose Amazon listing has drifted from the DTC source of truth in a sales-affecting way (price mismatch, content mismatch, pack/variant mismatch, or discontinued items still live). |
| Cross-channel basis | Compares the live Amazon listing against the canonical DTC catalogue. The drift is the delta; the revenue at risk is the value of the affected ASINs’ sales exposed by it. |
| Why it matters | Drift quietly erodes conversion and trust: a wrong image or stale title lowers conversion, a price mismatch can break margin or trigger MAP issues, and a discontinued variant still live invites returns and bad reviews. |
| Relationship to other drift cards | The catalogue-level comparison is Catalogue Drift vs DTC; the price-specific risk is MAP Violation Risk (vs DTC). This card is the money roll-up. |
| Chart | KPI value. |
| Unit | Currency. |
| Time window | 30D. |
| Alert trigger | >$1k/month (drift-exposed revenue above roughly one thousand per month in account currency). |
| Roles | owner, marketing, finance |
Calculation
Calculated automatically from your Amazon Seller Central 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 UK home-fragrance brand selling on amazon.co.uk and its own Shopify DTC store. Period: 01 Apr 26 to 30 Apr 26 (30D).| ASIN | Drift type | DTC source of truth | Amazon listing | 30D revenue exposed |
|---|---|---|---|---|
| B0XXXX1 | Pack size mismatch | Now a 3-pack | Still listed as single | £640 |
| B0XXXX2 | Price drift | £24 DTC list | Listed at £18 | £980 |
| B0XXXX3 | Stale content | New scent name + image | Old name and image | £410 |
| B0XXXX4 | Discontinued, still live | Removed from range | Still buyable | £290 |
| Catalogue Drift Revenue at Risk (this card) | £2,320 |
- Each drift type carries a different harm. The price drift (£980) is a margin and MAP problem, the pack mismatch (£640) drives wrong expectations and returns, the stale content (£410) suppresses conversion, and the discontinued-but-live item (£290) generates orders you cannot fulfil to spec. The total is one number, but the fixes are four different jobs.
- Price drift is the most urgent. Selling the £24 DTC product at £18 on Amazon erodes margin and undercuts your own channel, which can breach MAP and train customers to buy the cheaper Amazon offer. Cross-check MAP Violation Risk (vs DTC) and re-align the price first.
- The discontinued item is a returns and review trap. A product removed from your DTC range but still buyable on Amazon means customers receive something you no longer support, which invites returns and negative feedback. Close or update the listing before it costs more than the £290 of revenue it carries.
>$1k/month). The action: re-align the price drift, correct the pack-size and content mismatches against the DTC source of truth, and retire the discontinued listing. Use Catalogue Drift vs DTC to see the full list of drifted ASINs behind this figure.
Sibling cards merchants should reference together
This is the money roll-up. These give the detail and the specific risks:| Card | Why pair it with Catalogue Drift Revenue at Risk |
|---|---|
| Catalogue Drift vs DTC | The per-ASIN list of what has drifted, behind this money total. |
| MAP Violation Risk (vs DTC) | The price-specific slice of drift, where the Amazon price has fallen below your DTC list price. |
| Channel Mix (Amazon vs DTC) | Context on how much each channel matters, which scales how serious cross-channel drift is. |
| Revenue at Risk (live) | The account-wide roll-up of all live revenue-at-risk signals, of which drift is one. |
| Suppressed Listings | Severe drift (missing required attributes) can tip a listing into suppression, removing it entirely. |
Reconciling against Amazon Seller Central
Where to look in Seller Central: This card has no single native equivalent, because it compares Amazon against an external source of truth (your DTC catalogue). To verify it manually you compare two sources:Amazon side: Seller Central → Inventory → Manage Inventory, for each listing’s live price, title, images, and attributes. DTC side: your canonical catalogue (Shopify admin, PIM, or master spreadsheet) for the same SKUs.Where the two disagree in a sales-affecting way, that ASIN’s revenue is the exposure this card values. Amazon shows only its own side; the drift only exists relative to your source of truth. Timing and reporting-lag table:
| Topic | Detail |
|---|---|
| Source-of-truth freshness | The comparison is only as current as the DTC catalogue feed. A change made on the DTC side moments ago may not yet be reflected in the comparison. |
| Amazon listing freshness | Listing fields are read each sync; a correction you just pushed to Amazon takes a short while to clear from the drift list. |
| Revenue basis | Revenue exposed uses the affected ASINs’ recent sales as the value at risk; it is an estimate of exposure, not a settled loss. |
| Match quality | Drift detection depends on reliable SKU/ASIN mapping between Amazon and DTC. Unmapped products cannot be compared and are excluded. |
| Reason | Direction | Why |
|---|---|---|
| SKU mapping gaps | Ours can be lower | Products without a clean Amazon-to-DTC mapping are not compared, so genuine drift on unmapped SKUs is not counted. |
| Source-of-truth lag | Either direction | If the DTC catalogue feed is stale, the comparison reflects the last known DTC state, not the live one. |
| Revenue-at-risk is modelled | Estimate | The money figure is an exposure estimate based on recent sales, not an Amazon-reported loss. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
| DTC catalogue / Shopify product data | This card is the join. It only exists because Amazon and DTC are both connected; the drift is the difference between them. | If the DTC connector is not linked or SKU mapping is incomplete, the card under-reports because it cannot see the source of truth for some products. |