At a glance
Listings Failing Feedonomics Feed Validation is the share of items pushed through Feedonomics that Walmart rejects at ingestion. Rejected listings never reach the catalogue, so they stay hidden and earn nothing until the feed is cleaned. A rising rejection rate is an early sign that a feed mapping or attribute rule has broken, which is why this is a hero card.
| What it counts | The percentage of Feedonomics-distributed listings rejected at Walmart Marketplace ingestion in the window. |
| Sample type | Backend API data from Walmart Marketplace, refreshed on the standard data refresh. |
| Why it matters | Rejected items stay hidden until corrected, so a higher rate means sellable inventory is sitting offline and revenue is being left on the table. |
| Reading the value | Lower is better; a rising percentage points to a feed mapping or data quality problem. |
| Currency | percent |
| Time window | 7D |
| Alert trigger | >5% feed rejection rate |
| Sentiment key | wal_xc_feed_rejection_vs_listings |
| Roles | owner, operations, engineering |
Calculation
The value is derived by comparing the number of Feedonomics-distributed listings rejected at Walmart ingestion against the total submitted through the feed in the window, then expressing the result as a percentage. It is a cross-channel measure that depends on the feed pipeline being linked. See the At a glance summary for the window and unit, and the worked example below for how the figure reads in practice.Worked example
A representative reading of Listings Failing Feedonomics Feed Validation for a typical merchant on Walmart Marketplace. On 12 Mar 26 a seller pushing about 800 items through Feedonomics in the trailing 7 days sees the rejection rate climb to 7.5%, around 60 items, over the alert line. The rejections cluster on a single category where a required attribute mapping was dropped in the latest feed template. The action is to fix the mapping in Feedonomics, resubmit the affected batch, and confirm the rate falls back so the hidden items return to the catalogue. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
wal_suspended_listings | Rejected feeds often surface as item setup errors on the catalogue. |
wal_alert_listing_rejection_spike | Flags the sudden spike in rejected new listings. |
wal_attribute_completeness | Missing required attributes are a leading rejection cause. |
wal_xc_catalogue_drift_vs_bc | Failed feeds leave Walmart out of sync with BigCommerce. |
wal_active_listings | Shows how many items remain live while rejections are fixed. |
Reconciling against Walmart Seller Center
Where to look in Walmart Seller Center: Open the Item / Catalog feed status area, where Walmart reports ingestion results and item-level rejection reasons, and cross-check against the Feedonomics submission logs. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses 7D rolling by default; Seller Center may use calendar periods. | Variable | Match the period range. |
| Time zone. Seller Center uses the account time zone; Vortex IQ aligns to the merchant reporting time zone. | Marginal | Confirm time zone match. |
| Filter scope. Profile-level filters (fulfilment type, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. |