Buyers compare across channels. Price/title/image divergence either kills conversion or trains buyers to wait for the cheaper channel.
At a glance
Real-time table of SKUs whose price, title, or hero image differs materially between the Adobe Commerce catalogue and the Amazon Seller Central listing for the same SKU. Cross-platform buyers compare prices; significant drift either kills conversion (Adobe more expensive than Amazon) or trains buyers to wait (Adobe cheaper but customers learn the pattern and abandon Amazon).
Calculation
Calculated automatically from your Adobe Commerce 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 skincare brand on Adobe Commerce 2.4.6 with US (USD) and UK (GBP) Store Views, also selling on Amazon US and Amazon UK. Snapshot taken Tuesday 12 Apr 26, 14:00 GMT.
What this is telling the merchant:
MOIST-NIGHT-50is the urgent one. Adobe shows 36 promo live, customers comparing prices will buy on Amazon and the brand loses ~36.MASK-CLAY-100is a title-hash mismatch. Marketing updated the product name in Adobe but didn’t refresh the Amazon listing. Not a price problem, but Amazon SEO depends on the title; mismatched titles split keyword authority. Push the new title via SP-API or Vendor Central.EYE-CREAM-15UK is showing +43% on Amazon, but the listing is a reseller. This is the diagnostic that “drift” sometimes means “third-party hijacker”. Pair withamazon_sp.amazon_sp_buy_box_pct, if Buy Box ownership dropped, a reseller has overlapped the brand’s listing. File an Amazon brand-protection complaint.SERUM-VIT-C-30US is a healthy Lightning Deal. Drift is intentional and time-bounded. The card flags it (the threshold is dumb to context) but operations can dismiss after confirming.MASK-CLAY-100UK is +19.4%, just below the 20% threshold. Not flagged but listed in the “watching” sub-row. Drift creeping up over time often precedes a flag, set a calendar reminder to review.
Sibling cards merchants should reference together
Catalogue Drift surfaces a moment-of-action; pair with these for context:Reconciling against the vendor’s own dashboard
Where to look in Adobe Commerce Admin: Adobe Commerce doesn’t natively know about Amazon, so reconciliation is per-side. For the Adobe price/title/image side:Catalog > Products with a SKU search. The product edit page showsPer Store View overrides matter:Price,Special Price,Name, and the Images and Videos section’s primary image. These are the fields the card reads via the RESTCatalog Itemsendpoint.
Many Adobe Commerce merchants override price per Store View (US in USD, UK in GBP, with different markups). Use the Store View dropdown at the top-left of the product edit page to verify the correct per-region price.
For the Amazon side (in Seller Central, not Adobe Admin):
Catalog > Manage Inventory in Seller Central. Click the SKU’s Edit link, the Offer tab showsOther Adobe Commerce Admin views that look relevant but aren’t:Your PriceandList Price. The Description tab shows the product title. Compare against Adobe’s per-region values.
- Marketing > Catalog Price Rules: rules that may override
price. Check if a stale rule is depressing Adobe price. - Marketing > Cart Price Rules: cart-level discounts, not per-product. Don’t show on this card.
- Stores > Configuration > Sales > Tax > Display Settings: tax-display configuration, affects what the card sees on the Adobe side.
- System > Index Management: indexer status, useful only when troubleshooting sync lag.
Cross-connector reconciliation (when these connectors are connected for this merchant):
This card is a cross-connector contrast. Honest reads:
Known limitations / merchant FAQs
A SKU is flagged as drifted but I just changed the price 5 minutes ago, sync lag? Yes, very likely. Adobeprice indexes within 5-15 minutes; Amazon catalogue via SP-API syncs hourly. A price change made in one channel can show as drift for up to 60 minutes before the other side catches up. The card refreshes on the next sync; if the drift persists past the hour, it’s real.
What’s the difference between state and status and does it affect this card?
This card is purely about catalogue (product) data, not orders. Order state and status are irrelevant. The closest order-side concept is pending_payment: an order being created from a drifted-price page is still recorded with whichever price the customer saw at checkout, and Adobe’s grand_total reflects that. So drift gets baked into historical orders even after it’s corrected.
Why does the card flag drift on a Lightning Deal that’s intentional?
The card doesn’t know intent. A 25% Lightning Deal looks identical to a forgotten 25% promo at the data level. The breakdown shows the deal duration if Amazon SP-API exposes it, allowing operations to dismiss flagged-but-intentional drift. Set up an “ignore” rule in your Vortex IQ workspace for known scheduled promos.
My multi-currency Adobe Commerce, the card flags every SKU as drifted, why?
Mis-mapped region matching. The default manifest matches Adobe Store View to Amazon marketplace by region (US ↔ US, UK ↔ UK). If your Adobe is single-Store-View USD but you’re comparing to Amazon UK GBP, every SKU shows as drifted because USD and GBP figures differ even at parity. Configure per-region mapping in the manifest or limit the card to like-for-like regions.
grand_total vs base_grand_total, does either matter here?
Neither. This card uses price (catalogue list price), not grand_total (transactional). The card normalises to the customer-facing price per region.
My multi-store Adobe Commerce, can I see per-region drift?
Yes, by default. The card matches Store View to Amazon marketplace by region. Each region’s drift is reported separately so US-vs-AmazonUS and UK-vs-AmazonUK are evaluated independently.
Why doesn’t Adobe Commerce dashboard show catalogue drift?
Adobe Commerce doesn’t natively know about Amazon. Some merchants use the Amazon Sales Channel module (legacy, deprecated 2023) or third-party tools (M2EPro, Channel Advisor) that push the Adobe catalogue to Amazon, but those don’t pull Amazon’s actual displayed state back. This card is the only way to detect post-push divergence.
My Stripe revenue and price drift don’t reconcile, expected?
Yes, Stripe doesn’t see catalogue. Stripe is the Adobe payment processor; price drift is a marketplace listings concern. They don’t overlap.
Why doesn’t Google Analytics flag drift?
GA4 doesn’t see Amazon at all (Amazon shoppers never touch your site). GA4 may show a per-product conversion-rate drop on a drifted SKU (Adobe-higher pricing depresses Adobe conversion), but it can’t tell you why. This card is the diagnostic that explains the GA4 dip.
The Amazon listing is hijacked by a reseller, how do I tell the card to ignore it?
You can’t directly, the card flags any drift. The right action is to file an Amazon brand-protection complaint and reclaim the listing. Once you control the listing again, set the price back in line with Adobe and the flag clears. Pair with amazon_sp.amazon_sp_buy_box_pct, if Buy Box dropped at the same time as drift appeared, hijack is the likely cause.
Why is title hash mismatch flagged separately from price?
Different consequences. Price drift directly affects conversion; title drift affects Amazon SEO and brand consistency. Title hash mismatch typically means marketing updated one channel and forgot the other, a process problem rather than a strategic problem. The two flags drive different fixes (price-matching vs catalogue-resync).
Why does today’s number swing so much for image drift?
Image URL drift is reported but doesn’t trip the threshold; image URLs change frequently for legitimate reasons (CDN failover, hot-link variants, image-CDN compression URL changes). Treat image-drift entries as informational only; only act on them when the visual content actually differs (verify by viewing both listings side-by-side).