Listings Failing Feedonomics Validation, Bonanza

Listings Failing Feedonomics Validation for Bonanza 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 Failing Feedonomics Validation is a cross-platform diagnostic that measures the share of your Bonanza listings rejected during validation in the upstream Feedonomics feed, the pipeline that powers Bonanza’s distribution to Google Shopping. A listing that fails validation never reaches Google Shopping, so this is lost free reach, not a cosmetic warning. When the rate climbs above 5 percent, a meaningful slice of your catalog has gone dark on a major demand channel. Read it as a revenue-at-risk signal spanning the feed system and your live listings.

What it counts	The percentage of Bonanza listings failing validation in the upstream Feedonomics feed that distributes to Google Shopping.
Sample type	Backend API data from Bonanza, refreshed on the standard data refresh.
Why it matters	Listings that fail feed validation are excluded from Google Shopping, cutting off free reach and the orders it would have driven.
Reading the value	Lower is better; the target is near zero. Above 5 percent means a real share of your catalog is missing from Google Shopping.
Currency	percent
Time window	7D
Alert trigger	>5%
Sentiment key	bon_xc_feed_rejection_vs_listings
Roles	owner, operations, engineering

Calculation

The count of Bonanza listings rejected during Feedonomics validation is divided by the total listings submitted to the feed across the window, then expressed as a percentage. Common rejection reasons include missing required attributes, malformed values, or policy flags that the feed enforces before passing items to Google Shopping. See At a glance for the window and the alert trigger, and the worked example below for a representative reading.

Worked example

A representative reading of Listings Failing Feedonomics Validation for a typical merchant on Bonanza. On 14 Mar 26 a booth submits 1,200 listings to the feed and 84 are rejected, a 7 percent failure rate against a 5 percent trigger. Drilling in, most failures cite a missing GTIN or a blank product category, which Feedonomics requires before forwarding to Google Shopping. Those 84 items are invisible on Google Shopping until fixed, so the action is to backfill the missing attributes at source and re-run the feed. Vortex Mind traces upstream causes, such as a category mapping that broke after a catalog change, and Ask Viq lets you ask in plain English which rejection reasons are most common this week.

Sibling cards merchants should reference together

Card	Why merchants reach for it
bon_attribute_completeness	Catalog sibling: Required-Attribute Completeness.
bon_xc_catalogue_drift_vs_bc	Cross-Platform: Revenue at Risk sibling: Listings Drifting from BC.
bon_xc_listed_but_oos_on_bc	Cross-Platform: Revenue at Risk sibling: Active Bonanza Listings for OOS SKUs on BC.
bon_importer_sync_health	Operations sibling: Importer Sync Health.
bon_revenue_at_risk	Revenue sibling: Revenue at Risk.

Reconciling against Bonanza

Where to look in Bonanza’s own dashboard:

In Bonanza, open the selling area and your item listings to confirm the items are live on the booth, then check the upstream Feedonomics feed status to see the validation errors and the Google Shopping distribution result. Because this is a cross-platform card, the failure lives in the feed system even when the Bonanza listing itself looks healthy.

Why the Vortex IQ value may legitimately differ:

Reason	Direction	What to do
Period boundary. Vortex IQ uses a trailing 7-day window by default; Bonanza dashboards may use calendar periods.	Variable	Match the period range.
Time zone. Bonanza uses account time zone; Vortex IQ aligns to merchant reporting time zone.	Marginal	Confirm time zone match.
Filter scope. Profile-level filters (booth, channel, test orders) may narrow the Vortex IQ view.	Variable	Match filter settings.

Cross-connector reconciliation: complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind.

Known limitations / merchant FAQs

Q: How often does Listings Failing Feedonomics Validation update? It follows the trailing 7-day window and refreshes on the standard data refresh, typically every 30 to 60 minutes. Because it depends on the Feedonomics feed cycle, a fresh validation pass may need to run before the rate moves after a fix. You can also trigger a manual refresh.

Q: Why does my Bonanza dashboard show a different number? Bonanza alone does not surface Feedonomics validation results, so it will not show this rate. The figure here comes from Vortex IQ reading the upstream feed and the live listing set together. Differences usually trace to feed-cycle timing or filter scope.

Q: I fixed the attributes but the rate has not dropped - why? A fix at source only clears once the next Feedonomics validation pass runs and re-submits the item to Google Shopping. The rate lags the fix by one feed cycle, so allow a cycle before re-checking.

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 Failing Feedonomics Validation is one of hundreds of KPI pulses Vortex IQ tracks across Bonanza 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.