At a glance
Listings Drifting from BC is a cross-channel surface that catches SKUs where the live Fruugo listing has diverged from the BigCommerce source of truth on price, title, image, or stock. BigCommerce is where your catalogue is authored; Fruugo is where it sells across 40+ countries, with Feedonomics in between, so drift means the two no longer agree. Each drifted SKU risks oversell, mispricing, or buyer complaints in markets you cannot watch by hand. It alerts when more than 10 SKUs are out of sync, the configurable default.
| What it counts | SKUs whose live Fruugo listing differs from the current BigCommerce record on price, title, image, or stock. |
| Sample type | Cross-channel comparison table, one row per drifted SKU |
| Why it matters | Drift between the BC source of truth and the live Fruugo listing causes oversell, mispricing, and buyer complaints across locales. |
| Reading the value | Lower is healthier. The count is the number of SKUs out of sync; each row names the field that drifted and the two values. |
| Currency | count |
| Time window | 30D |
| Alert trigger | >10 SKUs |
| Sentiment key | fru_xc_catalogue_drift_vs_bc |
| Roles | owner, marketing, operations |
Calculation
The card matches each Fruugo listing to its BigCommerce source SKU and compares the key fields - price, title, image, and stock - between the two. Any SKU where the live Fruugo value no longer matches the current BC record is counted as drifted, with the specific field and both values recorded. The comparison runs across the trailing 30 days so transient mid-feed states settle before a SKU is flagged.Worked example
A representative reading of Listings Drifting from BC for a typical merchant on Fruugo. On 12 Mar 26 the table shows 14 drifted SKUs (illustrative), above the 10-SKU default. Nine show a price gap where a BC promotion ended but Fruugo still carries the old discounted price, three show stale stock counts after a manual BC adjustment never reached Feedonomics, and two show a title edit that did not propagate. The owner sees margin and oversell risk in one view. Vortex Mind investigates whether the drift clusters around a failed feed run or a manual BC change outside the feed, and Ask Viq answers “which drifted SKUs are underpriced versus BC” in plain English so the team re-syncs the highest-risk listings first.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
fru_xc_listed_but_oos_on_bc | Cross-channel sibling: Active Fruugo Listings for OOS SKUs on BC. |
fru_xc_price_parity | Cross-channel sibling: Price Drift vs Amazon EU / eBay EU. |
fru_xc_feed_rejection_vs_listings | Cross-channel sibling: Listings Failing Feedonomics Validation. |
fru_revenue_at_risk | Economics sibling: Revenue at Risk. |
fru_listing_quality_score | Listing Health sibling: Listing Quality Score. |
Reconciling against Fruugo Merchant Portal
Where to look in Fruugo’s own dashboard: The Fruugo Merchant Portal shows the live Fruugo side of each listing - the price, title, image, and stock currently published per locale. The canonical comparison, though, is multi-source: this card reads the Fruugo listing against the BigCommerce source of truth and the Feedonomics feed that connects them, so the Portal alone cannot show drift on its own. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| A BC change is mid-flight through Feedonomics and not yet on Fruugo | Vortex IQ higher | Wait for the next twice-daily import, then re-check before treating it as drift. |
| Fruugo deliberately localises a title or image per country | Vortex IQ higher | Mark intentional localisation as expected so it is excluded from drift. |
| BC record updated after the last feed snapshot was taken | Either | Re-run the comparison once the feed reflects the newest BC state. |
fru_xc_listed_but_oos_on_bc and fru_xc_feed_rejection_vs_listings to separate stock drift from feed faults, and let Vortex Mind pinpoint whether the divergence began in BC, in Feedonomics, or on Fruugo.
Known limitations / merchant FAQs
Q: How often does this card update? It re-evaluates after each twice-daily Fruugo import and as BigCommerce records change, comparing across a trailing 30-day window. Q: Why might the Fruugo Merchant Portal show a different picture? The Portal only shows the live Fruugo side. Drift is only visible when Fruugo is compared against the BigCommerce source and the Feedonomics feed, which the Portal does not surface. Q: How does this relate to the sibling cards? This card catches any field drift;fru_xc_listed_but_oos_on_bc isolates the stock case, fru_xc_price_parity compares price against rival marketplaces, and fru_revenue_at_risk quantifies the financial exposure.
Q: Can I customise the alert threshold?
Yes. The default fires above 10 drifted SKUs, but you can tune the count and choose which fields - price, title, image, stock - count as drift for your catalogue.