SKUs missing from the marketplace, or where Woo and the marketplace listing have diverged. Buyers compare and bounce.
At a glance
WooCommerce SKUs that are missing from a connected marketplace (Amazon, eBay), or where the Woo listing and the marketplace listing have drifted (price, title, image). Buyers compare and bounce.
| What it counts | COUNT(woo SKUs WHERE NOT IN marketplace_listings) + COUNT(woo SKUs WHERE woo.price != marketplace.price (>20% drift) OR woo.title != marketplace.title OR woo.image != marketplace.image). Joined by SKU / EAN / GTIN. |
| REST API endpoint | Woo: GET /wp-json/wc/v3/products. Amazon: SP-API getCatalogItem. eBay: Trading API GetItem. Joined client-side. |
| VAT / tax treatment | Price comparison is currency-aware; tax-inclusive vs exclusive can cause false drift on cross-region listings. |
| Status filter | Active products on Woo (status = publish) and active listings on the marketplace. |
| Refunds / cancelled / failed orders | Not applicable. |
| Currency | Multi-currency creates false positives. A Woo store in GBP listed on Amazon US in USD will always show price drift unless the join normalises FX. Configure currency mapping in workspace settings. |
| Channels / sources | Compares Woo against each connected marketplace separately (Amazon, eBay, Etsy via WooCommerce-Etsy plugin). |
| Self-hosted vs managed-Woo | Self-hosted with stale-data plugins (e.g. WP Rocket caching the product page for hours) can produce false-positive drift, the marketplace updates faster than the Woo source. Managed-Woo with proper cache headers is steadier. |
| Time window | RT (polled every 60 min) |
| Alert trigger | any SKU price / title / image mismatch >20% drift OR missing listing |
| Roles | owner, marketing, operations |
Calculation
Calculated automatically from your WooCommerce 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 US homewares brand on managed-Woo, listed on Amazon US via WooCommerce Amazon Connector. 1,840 active SKUs on Woo, 1,762 on Amazon. Polled 12 Apr 26.| Drift category | Count | Example |
|---|---|---|
| Missing from Amazon | 78 SKUs | Recently launched Woo SKUs not yet pushed |
| Price drift (>20%) | 12 SKUs | Woo running a 30% sale, Amazon at original price |
| Title drift | 6 SKUs | Woo updated to “Mushroom Mug 2.0”, Amazon still “Mushroom Mug” |
| Image drift | 3 SKUs | Woo updated lifestyle photo, Amazon still on white-bg |
| Total drift | 99 SKUs |
- Self-hosted variance is the recurring theme. Earlier this year on a slow shared host, Woo Amazon Connector took 6+ hours to push updates. Pressable’s faster API ceiling drops sync time to ~15 min.
- Plugin-induced data shape variance. WooCommerce Amazon Connector pushes Woo product changes to Amazon via SP-API on a 15-minute cron. WooCommerce eBay Connector uses a different cadence (5 minutes). Drift detection accounts for plugin-specific lag, but sales / promotion campaigns running on Woo without matching Amazon/eBay updates always surface here as price drift.
- Multi-region sales create false positives. This brand sells in USD on both Woo and Amazon US, so currency aligns. If they expanded to Amazon UK with GBP pricing, the drift card would flag every UK SKU as “price drift” because the join compares dollar values. The fix is per-region currency mapping in workspace config.
Sibling cards merchants should reference together
| Card | Why pair it with Marketplace Drift |
|---|---|
| WC Top Products | Drift on a top-10 SKU is materially worse than drift on a long-tail SKU. |
| WC Out of Stock | OOS state should sync to marketplaces; if Woo is OOS but Amazon is selling, you have a stockout-mismatch problem. |
| BC Channel Top Products | Cross-platform peer (BC has native marketplace channels). |
| Amazon Ads Wasted Spend | Ad spend on listings drifted from your store. |
Reconciling against the vendor’s own dashboard
Where to look in WooCommerce / marketplace consoles: Woo: WP Admin → Products. Amazon: Seller Central → Inventory → Manage Inventory. eBay: Seller Hub → Listings → Active. WooCommerce Amazon Connector status: WP Admin → WC → Status → Marketplace sync log. Why our drift count may differ from a manual spot-check:| Reason | Direction |
|---|---|
| Time-zone. Sync timestamps in UTC; merchant tools may use local. | Boundary effects |
| Self-hosted server uptime. Cron sync stalled during outage. | Either |
| Plugin-version compatibility. Amazon Connector and eBay Connector each have their own sync cadence. | Investigate per-merchant |
| Refund-restock cycle. Mid-sync inventory updates can flicker drift state briefly. | Self-resolves |
| Currency plugin behaviour. Multi-region pricing: configure currency mapping. | Material if not configured |
| Card | Expected relationship |
|---|---|
amazon_sp.asp_listing_health | Marketplace-side view of listing quality. Should track this card’s “missing” + “drift” sets. |
Known limitations / merchant FAQs
Self-hosted vs managed-Woo, why does it affect drift? Self-hosted Woo on slow hosting means marketplace plugins sync slower (cron jobs throttled, API calls timeout). Managed-Woo provides faster sync. Status-filter selection, why >20% price drift threshold? Below 20% price drift is usually intentional (regional pricing, marketplace fee absorption, planned promo). Above 20% is almost always unintentional and worth flagging. Refund-object accounting? Not directly applicable to drift; marketplace returns flow through their own systems. Plugin-induced data shape variance?- WooCommerce Amazon Connector: 15-min sync cadence by default, configurable.
- WooCommerce eBay Connector: 5-min cadence.
- WP-Lister for eBay: 30-min cadence.
- M2E Multichannel: hourly cadence on free tier, 5-min on paid.
- Custom in-house exporters: behaviour varies; verify.
- Confirm the SKU mapping is correct (Woo uses internal product ID; Amazon uses ASIN).
- Check the sync log for the last successful update.
- Verify currency mapping for cross-region listings.
- If gap persists, contact support.