Listings Drifting from BC, AliExpress

Listings Drifting from BC for AliExpress stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

Metrics type: Key Metrics • Category: Marketplace

At a glance

Listings Drifting from BC counts the AliExpress retail SKUs whose live listing no longer matches its BigCommerce source record. In this merchant’s setup BigCommerce is the source of truth, and AliExpress retail listings are expected to mirror BC on price, title, images, and stock. When a listing drifts, a buyer sees a price, photo, or description that the source catalogue has already moved past. That mismatch drives buyer confusion, mispriced orders, and disputes when the delivered product or charged price does not match the listing. The card renders as a table so you can see exactly which SKUs drifted and on which fields.

What it counts	AliExpress retail SKUs that have diverged from their BigCommerce source record on price, title, images, or stock. Each drifting SKU is one row in the table.
Sample type	Backend API data from AliExpress compared against the BigCommerce source, refreshed on the standard data refresh over a rolling 30-day window.
Why it matters	Drift breaks the promise that AliExpress mirrors the source catalogue. It causes mispricing, buyer confusion, and disputes when the listing and the source no longer agree.
Reading the value	A non-zero count is a worklist. Open the table, sort by the drifted field, and prioritise price and stock drift over cosmetic title drift.
Currency	count
Time window	30D
Alert trigger	>10 SKUs drifting
Sentiment key	aex_xc_catalogue_drift_vs_bc
Roles	owner, marketing, operations

Calculation

Vortex IQ matches each live AliExpress retail listing to its BigCommerce source SKU and flags any where price, title, images, or stock no longer agree across the two channels. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A representative reading of Listings Drifting from BC for a typical BC-to-AliExpress syndicating merchant. On 19 Mar 26 the card reads 23 drifting SKUs, above the 10-SKU alert threshold. The table shows 14 with price drift (a BC price update did not propagate), 6 with stock drift (BC marked them low while AliExpress still shows full stock), and 3 with title drift after a BC copy refresh. The merchant clears the 14 price-drift rows first because those risk underselling, then chases why the feed step failed to push the updates. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq.

Sibling cards merchants should reference together

Card	Why merchants reach for it
aex_xc_feed_rejection_vs_listings	Drift often starts when an update is rejected at the Feedonomics validation step.
aex_xc_listed_but_oos_on_bc	A stock-drift extreme: listings still buyable on AliExpress but out of stock on BC.
aex_xc_price_parity	Another cross-platform pricing coherence check, this time against Alibaba B2B.
aex_listings_with_fx_pricing_drift	Price drift caused by currency conversion rather than a stale source value.
aex_total_listings	The denominator that puts the drift count in proportion to catalogue size.

Reconciling against AliExpress Seller Center

Where to look in AliExpress Seller Center:

Open a drifting SKU in Product Management and read its live price, title, images, and stock. The other half of the comparison does not live in Seller Center: the source values sit in BigCommerce, and the transform that should have synced them runs through the Feedonomics feed layer, so check all three to confirm a true drift.

Why the Vortex IQ value may legitimately differ:

Reason	Direction	What to do
In-flight sync. A BC update may be mid-propagation, so the listing looks drifted for one cycle.	Marginal	Recheck after the next refresh before acting.
Intentional channel override. Some merchants deliberately set AliExpress-only pricing or imagery.	Variable	Whitelist intended overrides so they stop counting as drift.
FX conversion. A price that looks drifted may simply reflect currency conversion, not a stale source.	Variable	Cross-check the FX pricing drift card before treating it as true drift.

Cross-connector reconciliation: reconcile the AliExpress listing, the BigCommerce source record, and the Feedonomics transform together, since drift can originate in any of the three. For divergence investigations, use Vortex Mind.

Known limitations / merchant FAQs

Q: How often does Listings Drifting from BC update? It recomputes on the standard data refresh across a rolling 30-day window, so newly drifted SKUs surface within a refresh cycle of the BC change. Force a manual refresh after a large BC catalogue update to recheck sooner.

Q: Why does my AliExpress Seller Center show a different number? Seller Center only shows the AliExpress side of the comparison, so it cannot show drift on its own. The count reflects a mismatch against the BigCommerce source, which lives outside Seller Center, so confirm both sides and the Feedonomics transform.

Q: How does Listings Drifting from BC relate to other metrics? It sits alongside the other cross-platform revenue-at-risk cards. Pair it with the Feedonomics validation card to see drift caused by rejected updates and with the OOS-on-BC card for the stock-drift extreme.

Q: Can I customise the alert threshold? Yes, alert thresholds are configurable per profile in the Alert Rules tab. Adjust to match your business baseline rather than relying on the generic default.

---

Tracked live in Vortex IQ Nerve Centre

Listings Drifting from BC is one of hundreds of KPI pulses Vortex IQ tracks across AliExpress 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.