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-channel 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).
| What it counts | For each SKU present in BOTH the Adobe Commerce catalogue (Catalog > Products) and Amazon Seller Central (via SP-API Catalog Items), compare: (1) price, flagged when diverged >20%; (2) title, hashed to detect mismatch; (3) hero image URL, flagged when different. Returns the list of drifted SKUs with the side-by-side. |
| API field | Adobe side: price (or special_price if active), name, media_gallery_entries[0].file from GET /rest/V1/products/{sku}. Amazon side: attributes.list_price.value, attributes.item_name.value, attributes.main_product_image_locator.media_location from GET /catalog/v0/items/{asin} (SP-API). |
| VAT / tax treatment | Mixed and worth understanding. Adobe price follows the merchant’s tax-display configuration (Stores > Configuration > Sales > Tax > Display Settings), tax-inclusive UK/EU stores show price inclusive of VAT; tax-exclusive US stores show price exclusive. Amazon list_price is what the customer sees on the listing, which is also tax-inclusive in Marketplace Facilitator regions. The card normalises both sides to tax-inclusive before comparison so a UK Adobe in tax-inclusive mode vs Amazon UK is apples-to-apples. Stores in tax-exclusive mode require a manifest tweak to gross up Adobe before comparison. |
| Shipping inclusion | Excluded on both sides. This card compares product prices, not delivered prices. Free-shipping at one channel and paid-shipping at the other is a separate concern; track it via Free vs Paid Shipping and equivalent Amazon fulfilment cards. |
| Discounts | Adobe side uses special_price if currently active (a Catalog Price Rule in flight), otherwise price. Amazon side uses the list_price (struck-through) if a Lightning Deal is live, otherwise the regular price. The card detects this and flags drift caused by a one-side-only promotion explicitly. |
| Credit Memo refund treatment | n/a, this is a catalogue card, not a transactional card. |
state machine inclusion | n/a, this card concerns product entities, not orders. |
pending_payment quirk | n/a, no order-state interaction. |
Multi-currency grand_total vs base_grand_total | n/a for the comparison itself. The card normalises currency: Adobe US Store View vs Amazon US uses USD; Adobe UK Store View vs Amazon UK uses GBP; Adobe DE Store View vs Amazon DE uses EUR. Stores running a single Adobe Store View in USD against Amazon UK GBP would generate spurious price-drift alerts; configure per-region matching. |
Store View scope (store_id) | The card matches Adobe Store Views to Amazon marketplaces by region (US Store View ↔ Amazon US, UK Store View ↔ Amazon UK, etc.). Multi-Store-View merchants need correct per-region mapping in the manifest, otherwise a US Store View vs Amazon UK comparison generates noise. The B2B Store View has no Amazon equivalent and is excluded from this card. |
| Time window | RT (real-time). Adobe price updates index within 5-15 minutes; Amazon catalogue sync is hourly. Expect slight lag on Amazon-side promotions. |
| Alert trigger | >3 SKUs diverged >20% on price OR title hash mismatch. Image URL drift is reported but doesn’t trip the threshold (image URLs often differ legitimately, CDN paths, hot-link variants). |
| Roles | owner, marketing, operations |
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.| SKU | Region | Adobe price | Amazon price | Drift | Cause |
|---|---|---|---|---|---|
SERUM-VIT-C-30 | US | $42.00 | $34.99 | -16.7% (Adobe higher) | Amazon Lightning Deal active until Sun 17 Apr |
SERUM-VIT-C-30 | UK | £36.00 | £36.00 | 0% | In sync |
MOIST-NIGHT-50 | US | $48.00 | $36.00 | -25.0% (Adobe higher) | Amazon listing has a forgotten 25% promo from a Q4 Prime Day |
CLEANSE-FOAM-150 | US | $24.00 | $24.00 | 0% | In sync |
MASK-CLAY-100 | US | (Adobe text: “Charcoal Clay Mask 100ml”) | (Amazon text: “Charcoal Detox Clay Mask, 100ml”) | Title hash mismatch | Marketing updated Adobe last week, Amazon listing not refreshed |
MASK-CLAY-100 | UK | (Adobe £18.00) | (Amazon £21.50) | +19.4% (Amazon higher) | Just below 20% threshold, not flagged but worth watching |
EYE-CREAM-15 | UK | £28.00 | £40.00 | +42.9% (Amazon higher) | Reseller listing on Amazon UK with markup, not the brand’s own listing |
| This card | 3 SKUs flagged (MOIST-NIGHT-50, MASK-CLAY-100, EYE-CREAM-15) | Plus 1 title-hash mismatch and 1 sub-threshold watch |
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:| Card | Why pair it with Catalogue Drift |
|---|---|
| Active Ads on OOS SKUs | Sister cross-channel card. Often one drives the other, an OOS SKU on Adobe with a still-priced Amazon listing is both a stock-side and a price-side problem. |
| Top Refunded SKUs | Drifted SKUs that customers buy on the cheaper side (Adobe) and later try to return at Amazon prices show up as refund-rate spikes. |
| Total Revenue | The denominator-of-context. Drift on a 500/order SKU. |
| Revenue at Risk from Incident | The roll-up. Drift incidents feed into this. |
| Amazon Revenue Share | High Amazon share + drift = strategic risk; customers will migrate to whichever channel is cheaper. |
amazon_sp.amazon_sp_buy_box_pct | If a SKU shows reseller-driven drift, Buy Box ownership has likely already dropped. Co-investigate. |
amazon_sp.amazon_sp_listing_health | Title/image drift directly affects Amazon listing-quality score. |
google_search_console.gsc_brand_impressions | Drift on titles can split brand-keyword authority across two listings; track the impression hit. |
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.
| Reason | Direction of divergence |
|---|---|
Sync lag. Adobe price indexes within 5-15 minutes; Amazon catalogue sync via SP-API is hourly. A price change made in one channel may be flagged as drift for up to 60 minutes before the other side catches up. | Card flags transient drift on legitimate updates |
Tax-display mode. Adobe’s price field follows the merchant’s tax-display configuration. Tax-exclusive Adobe stores (some US states) need the card to gross up before comparing to Amazon. The default manifest assumes tax-inclusive comparison. | Card may under-flag drift on tax-exclusive Adobe stores |
| Currency mismatch. Multi-Store-View merchants need correct per-region matching (US Store ↔ Amazon US, UK Store ↔ Amazon UK). Mis-mapped manifests generate noise. | Spurious flags on mis-mapped configs |
Catalog Price Rules. Adobe applies Catalog Price Rules at runtime; the card uses special_price if a rule is in flight, but custom-attribute price rules (rare) may not be picked up. | May miss rare custom drifts |
| Amazon variant ASINs. Some SKUs map to multiple ASINs (size variants, colour variants); the card matches by SKU and may pick the wrong ASIN if the variant relationship isn’t clean. Configure parent-child relationships explicitly in the manifest. | Spurious flags on ambiguous variant SKUs |
| Reseller / hijacker listings. If an Amazon listing has been hijacked by a reseller, the price on the Amazon side may not be the brand’s. The card flags it as drift; the right fix is brand-protection, not price-matching. | Card correctly flags but the cause is non-obvious |
| Pair | Expected relationship | What divergence tells you |
|---|---|---|
Adobe price vs SP-API list_price (this card) | Should match within 20% | Persistent >20% drift = stale promo, reseller hijacker, or wrong region mapping. |
amazon_sp.amazon_sp_buy_box_pct on a drift-flagged SKU | If Buy Box dropped recently, drift is reseller-driven | File brand-protection complaint, not a price update. |
google_ads.google_ads_spend on a drift-flagged SKU | Drift on a paid-ads SKU is dollar-for-dollar leak | Pause the ad until drift resolved, or accept the strategic price-match. |
google_analytics.ga_revenue_by_product | Drift on Adobe-higher SKUs typically depresses Adobe-side conversion | If Adobe conversions cratered for a SKU, drift may be the cause; verify with this card. |
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).