> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Listings Drifting from BC, JD.com > Listings Drifting from BC for JD.com stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Marketplace](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Listings Drifting from BC** is a cross-channel card. It treats your BigCommerce (BC) catalogue as the source-of-truth and lists the JD.com listings whose title, price, image, or attributes have fallen out of sync with it. Drift is the silent failure mode of a multi-channel setup: a price updated in BC that never propagated through the Feedonomics feed to JD, a renamed product on BC still showing its old hanzi title on JD, or an image swap that landed on one channel and not the other. Each drifted SKU means a JD buyer sees something different from your single source of truth, which erodes trust and, when it is price, erodes margin or credibility. | | | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | JD listings whose key fields (title, price, primary image, or mandatory attributes) no longer match the corresponding SKU in the BigCommerce source-of-truth catalogue, compared over the trailing 30 days. Each row is one drifted SKU with the field(s) that diverged. | | **Sample type** | Cross-channel comparison of JD.com listing data against the BigCommerce catalogue feed, refreshed on the standard data refresh. | | **Why it matters** | Drift means JD buyers see stale or wrong data versus your single source of truth. Price drift hits margin or buyer trust; title and image drift hurt search and conversion; attribute drift can trigger a JD compliance off-shelf. | | **Reading the value** | Read the table by drifted field. A cluster of price-only drift points at a feed propagation gap; scattered multi-field drift points at manual edits made directly in JD Seller Centre bypassing BC. | | **Currency** | count | | **Time window** | `30D` | | **Alert trigger** | `>10 SKUs` | | **Sentiment key** | `jd_xc_catalogue_drift_vs_bc` | | **Roles** | owner, marketing, operations | ## Calculation Calculated automatically by comparing each JD.com listing against its matched SKU in the BigCommerce source-of-truth catalogue. For every SKU the card checks title, price, primary image, and mandatory attributes; any field that diverges beyond the configured tolerance marks the SKU as drifted. The result is a table of drifted SKUs with the offending field(s) over the trailing 30 days. See the worked example below. ## Worked example *A representative reading of **Listings Drifting from BC** for a cross-channel JD.com seller.* The table shows 23 drifted SKUs as of 23 Jun 26, over the 10-SKU alert threshold. Sorting by field, 17 are price-only: BC raised list prices on 19 Jun 26 but the Feedonomics feed that pushes to JD failed validation for those rows, so JD is still selling at the old, lower price - quietly eroding margin on every sale. The other 6 are title drift, where someone edited the hanzi product name directly in JD Seller Centre and the change never went back to BC, so the two channels disagree. The price cluster is the priority because it costs money on every order. Use Vortex Mind to group drift by field and by the date BC last changed, and ask Ask Viq "which drifted SKUs are losing margin right now?" to act on the price set first. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- | | [`jdc_xc_feed_rejection_vs_listings`](/nerve-centre/kpi-cards/jd-com/listings-failing-feedonomics-validation) | Feed validation failures are a top cause of price and attribute drift. | | [`jdc_xc_listed_but_oos_on_bc`](/nerve-centre/kpi-cards/jd-com/active-jd-listings-for-oos-skus-on-bc) | Stock drift between BC and JD, the oversell sibling of this card. | | [`jdc_xc_price_parity`](/nerve-centre/kpi-cards/jd-com/china-domestic-vs-cross-border-pricing) | Price drift versus the cross-border price parity view. | | [`jdc_attr_completeness`](/nerve-centre/kpi-cards/jd-com/required-attribute-completeness) | Attribute drift can leave mandatory JD fields blank. | | [`jdc_total_listings`](/nerve-centre/kpi-cards/jd-com/total-listings) | The catalogue denominator the drift count sits against. | | [`jdc_revenue_at_risk`](/nerve-centre/kpi-cards/jd-com/revenue-at-risk) | Quantifies the margin and trust exposure from drift. | ## Reconciling against the vendor's own dashboard **Where to look in JD.com's own dashboard:** There is no single JD report for drift - this is a cross-channel comparison Vortex IQ runs between JD and BigCommerce. To validate a flagged row, open the SKU in JD Seller Centre Product Management, open the same SKU in BigCommerce, and compare the drifted field directly. Then check the Feedonomics feed log for that SKU to see whether the change failed to propagate or was edited out of band. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ----------------------------------------------------------------------------------------------------------------------------------- | ------------------------ | ------------------------------------------------ | | **Tolerance band.** Tiny rounding or formatting differences below the configured tolerance are not flagged as drift. | Vortex IQ lower | Tighten or loosen the tolerance per profile. | | **In-flight feed.** A change pushed from BC may be mid-propagation; it shows as drift until the feed completes. | Vortex IQ higher briefly | Re-check after the next feed run. | | **Intentional channel override.** Some sellers deliberately price JD differently; those should be excluded from drift, not flagged. | Vortex IQ higher | Add intentional overrides to the exclusion list. | **Cross-connector reconciliation:** always check the Feedonomics validation card alongside this one - most price and attribute drift originates from a failed or pending feed row. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Listings Drifting from BC update?** The card refreshes on the standard data refresh (typically every 30-60 minutes) and re-runs the BC-to-JD comparison each cycle. After a feed re-push, force a manual refresh to confirm the drift cleared. **Q: Why does a SKU show as drifted when I already fixed it in BC?** Because the fix has not yet propagated to JD through the Feedonomics feed, or the feed row for that SKU failed validation. The card compares the live JD value, not the intended BC value. Check the feed-validation card to see whether the push reached JD. **Q: We intentionally price some SKUs differently on JD. How do we stop false drift?** Add those SKUs to the intentional-override exclusion list in the profile settings. They will then be excluded from price drift while still being checked for title, image, and attribute drift. **Q: Can I customise the alert threshold?** Yes. The default fires above 10 drifted SKUs, but the threshold and the per-field tolerance band are both configurable per profile in the Sensitivity tab. Tighten the price tolerance if even small drift matters to your margin. *** ### Tracked live in Vortex IQ Nerve Centre *Listings Drifting from BC* is one of hundreds of KPI pulses Vortex IQ tracks across JD.com 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.