At a glance
Listings Failing Feedonomics Validation is a cross-channel surface showing the share of listings rejected at the Feedonomics validation stage before they ever reach Fruugo. Feedonomics sits between your BigCommerce source of truth and Fruugo’s twice-daily import, so a failure here is the upstream cause of many Fruugo rejections you would otherwise only see after distribution. Catching divergence at the feed layer lets you fix the source before listings fall out across 40+ locales. It alerts when more than 5% of listings fail validation, the configurable default.
| What it counts | The percentage of listings rejected by Feedonomics validation before submission to Fruugo. |
| Sample type | Cross-channel rate, failing listings as a share of submitted listings |
| Why it matters | Feedonomics is the upstream gate. Failures here are the root cause of many downstream Fruugo rejections and lost distribution. |
| Reading the value | Lower is healthier. The percentage is the share failing validation; a rising figure means a source or mapping fault is spreading. |
| Currency | percent |
| Time window | 7D |
| Alert trigger | >5% |
| Sentiment key | fru_xc_feed_rejection_vs_listings |
| Roles | owner, operations, engineering |
Calculation
The card compares the listings Feedonomics rejected at validation against the total listings submitted from the BigCommerce source over the trailing 7 days, expressed as a percentage. It measures the upstream gate between BC and Fruugo, so a listing that fails here never reaches Fruugo’s import at all. Reading this rate beside the Fruugo rejection cards shows how much of the downstream loss starts at the feed layer.Worked example
A representative reading of Listings Failing Feedonomics Validation for a typical merchant on Fruugo. On 12 Mar 26 the rate climbs to 8% (illustrative), above the 5% default, after a BigCommerce category restructure left required attributes unmapped in the Feedonomics transform. Those listings fail validation and never enter Fruugo’s import, so the catalogue quietly shrinks before any Fruugo rejection appears. Engineering sees the upstream cause directly. Vortex Mind investigates which mapping rule broke and which attributes are missing, and Ask Viq answers “what is the top Feedonomics failure reason this week” in plain English so the team fixes the transform once and clears the backlog on the next sync.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
fru_xc_catalogue_drift_vs_bc | Cross-channel sibling: Listings Drifting from BC. |
fru_alert_listing_rejection_spike | Nerve Centre alert: Fruugo Rejected Listings (24h). |
fru_feed_ingestion_health | Listing Health sibling: Feed Ingestion Success (last 24h). |
fru_vat_compliance_gaps | Listing Health sibling: Listings Missing VAT Metadata. |
fru_revenue_at_risk | Economics sibling: Revenue at Risk. |
Reconciling against Fruugo Merchant Portal
Where to look in Fruugo’s own dashboard: The Fruugo Merchant Portal only shows listings that passed validation and reached Fruugo, so the Portal cannot show what failed upstream. The canonical comparison is multi-source: this card reads Feedonomics validation output against the BigCommerce listings submitted, then sits beside Fruugo’s own rejection view to separate upstream failures from downstream ones. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Portal never sees validation failures; it only shows accepted listings | Portal silent | Use this card and the Feedonomics logs to see what failed before Fruugo. |
| A failing listing was fixed and re-validated within the window | Vortex IQ higher | Re-check the validation result; resolved items clear on the next sync. |
| BC submitted fewer listings than expected, shifting the denominator | Either | Confirm the BC export volume before reading the percentage. |
fru_alert_listing_rejection_spike to see how upstream validation failures translate into Fruugo rejections, and fru_xc_catalogue_drift_vs_bc for field-level divergence. Vortex Mind traces a rising rate back to the specific BC change or mapping rule.
Known limitations / merchant FAQs
Q: How often does this card update? It refreshes on each Feedonomics sync and keeps a rolling 7-day view of the validation failure rate. Q: Why might the compared source show a different picture? Feedonomics records the validation failures directly, while the Fruugo Merchant Portal never sees them - it only shows listings that already passed. That is exactly why this upstream card exists. Q: How does this relate to the sibling cards? This card is the upstream gate;fru_alert_listing_rejection_spike shows the downstream Fruugo rejections that often follow, and fru_xc_catalogue_drift_vs_bc shows field-level drift once listings are live.
Q: Can I customise the alert threshold?
Yes. The default trips above 5%, but you can adjust it to match how much validation churn is normal for your feed and catalogue size.