> ## 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, Mercari > Listings Drifting from BC for Mercari 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** counts the SKUs whose Mercari listing no longer matches the source-of-truth BigCommerce (BC) record, in price, title, condition, or availability. It is a cross-channel card, so it measures the gap between two systems, not a single Mercari figure. The table breaks the drift down row by row so you can see exactly which SKUs are out of sync. | | | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | SKUs where the Mercari listing has diverged from the matching BigCommerce record on price, title, condition, or availability. | | **Sample type** | Backend API data from Mercari, refreshed on the standard data refresh. | | **Why it matters** | BC is your source of truth. Drift means buyers see stale prices or wrong details on Mercari, which leads to mispriced sales, refunds, and bad reviews. | | **Reading the value** | A count of drifting SKUs, shown as a table. Higher means more of your catalogue is out of sync. Above roughly 10 needs a sync. | | **Currency** | number | | **Time window** | `30D` | | **Alert trigger** | `>10 SKUs` | | **Sentiment key** | `mer_xc_catalogue_drift_vs_bc` | | **Roles** | owner, marketing, operations | ## Calculation Vortex IQ matches each Mercari listing to its corresponding BigCommerce SKU and compares the key fields, price, title, condition, and availability, between the two. Where any field disagrees, the SKU is counted as drifting and surfaced as a row in the table with the mismatched field shown. The comparison runs across the window so transient mid-sync states settle out. Because this is a two-system comparison, a clean Mercari listing can still appear here if BC has moved underneath it. ## Worked example *A representative reading of **Listings Drifting from BC** for a typical Mercari reseller.* On 21 Mar 26 the table shows 14 drifting SKUs, over the alert line of 10. Reading the rows, six show a price mismatch where BC was marked down for a sale but Mercari still carries the old higher price, five show a condition mismatch where an item was re-graded from 'Good' to 'Like New' in BC but not on Mercari, and three are marked sold-out in BC yet still live on Mercari. The reading tells you a recent BC price-and-grading pass never propagated to the marketplace. The action is to run a sync for the listed SKUs, prioritising the three availability mismatches first because they risk overselling. Cross-reference [`mer_xc_listed_but_oos_on_bc`](/nerve-centre/kpi-cards/mercari/active-mercari-listings-for-sold-elsewhere-items) for the items already gone elsewhere, and [`mer_xc_feed_rejection_vs_listings`](/nerve-centre/kpi-cards/mercari/listings-failing-feedonomics-validation) to check whether failed feed publishing is part of why the sync never landed. Vortex Mind traces upstream causes such as a BC bulk edit that bypassed the sync job, and Ask Viq answers plain-English questions like "which SKUs drifted on price in the last week". ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | | [`mer_xc_listed_but_oos_on_bc`](/nerve-centre/kpi-cards/mercari/active-mercari-listings-for-sold-elsewhere-items) | The most urgent drift: items live on Mercari but already sold elsewhere. | | [`mer_xc_feed_rejection_vs_listings`](/nerve-centre/kpi-cards/mercari/listings-failing-feedonomics-validation) | Failed feed validation often explains why a sync never reached Mercari. | | [`mer_xc_price_parity`](/nerve-centre/kpi-cards/mercari/same-item-priced-differently-vs-depop-vinted) | Extends the price-drift lens to rival resale apps. | | [`mer_listings_active`](/nerve-centre/kpi-cards/mercari/active-listings) | Sizes the drift against your total live Mercari catalogue. | | [`mer_revenue_at_risk`](/nerve-centre/kpi-cards/mercari/revenue-at-risk-live) | Quantifies the revenue exposure that drift contributes to. | ## Reconciling against Mercari **Where to look in Mercari's own dashboard:** Mercari shows you only what is live on Mercari, so it cannot reveal a gap against BigCommerce on its own. To see drift by hand you would open a SKU in Mercari and a SKU in BC and compare the two side by side. The comparison here is Mercari versus BC, which means the Mercari dashboard alone will never show the gap; you need both systems in view. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ----------------------------------------------------------------------------------------------------- | --------- | ------------------------ | | **Period boundary.** A SKU edited in BC near the window edge may not yet be reflected as drift. | Variable | Match the period range. | | **Time zone.** Edit timestamps in BC and Mercari may sit in different zones. | Marginal | Confirm time zone match. | | **Filter scope.** Only SKUs mapped between BC and Mercari are compared; unmatched items are excluded. | Variable | Match filter settings. | **Cross-connector reconciliation:** Because this is a Mercari-versus-BigCommerce comparison, always treat BC as the source of truth and sync Mercari toward it, not the reverse. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Listings Drifting from BC update?** It refreshes on the standard Vortex IQ data refresh, re-running the field comparison between each Mercari listing and its BigCommerce record. Resolved drift drops out of the table on the next refresh. **Q: Why does my Mercari dashboard show a different number?** Mercari has no view of your BigCommerce data, so it cannot show drift at all. The card exists precisely because the gap is invisible from inside either system on its own. **Q: Which field counts as drift?** Price, title, condition, and availability mismatches are all flagged, and the table row shows which field disagrees so you can prioritise availability and price fixes first. **Q: Can I customise the alert threshold?** Yes, sensitivity thresholds are configurable per profile in the Sensitivity 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 Mercari 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.