At a glance
This card counts new listings Walmart rejected with item setup errors in the last 24 hours. A sudden spike usually means a feed regression, schema drift, or a Walmart category-rule update that broke your listing pipeline. Sellers watch it because rejected listings never reach search, so every rejection is a product silently failing to go live.
| What it counts | New Walmart listings rejected with item setup errors within the trailing 24-hour window. |
| Sample type | Backend API data from Walmart Marketplace, refreshed on the standard data refresh. |
| Why it matters | Rejected listings never publish, so a spike means lost catalogue coverage and, often, a broken feed that will keep failing until fixed. |
| Reading the value | Zero is healthy; any non-zero value points to a listing-pipeline problem worth diagnosing today. |
| Currency | count |
| Time window | 24H |
| Alert trigger | >0 Item Setup errors |
| Sentiment key | wal_alert_listing_rejection_spike |
| Roles | owner, operations |
Calculation
Vortex IQ reads the outcome of new item setup submissions to Walmart Marketplace and counts those flagged with item setup errors over the trailing 24 hours. Each rejected item is tallied once for the window, so the value reflects the volume of listings that failed to publish recently rather than a cumulative backlog. Because the trigger fires above zero, even a single rejection surfaces, as shown in the worked example below.Worked example
A representative reading of Walmart Rejected New Listings (24h) for a typical merchant on Walmart Marketplace. On 12 Mar 26 the card spikes from 0 to a representative 18 rejections shortly after a Feedonomics feed change went live. Inspecting the errors shows most share the same missing required attribute, pointing to a single template regression rather than 18 separate problems. The reading means the feed broke a mandatory field, and the action is to correct the template, resubmit the batch, and confirm the count falls back toward zero. 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_xc_feed_rejection_vs_listings | Shows feed-side validation failures that often precede a rejection spike. |
wal_suspended_listings | Tracks existing listings already down due to item setup errors. |
wal_attribute_completeness | The most common rejection driver: missing mandatory attributes. |
wal_active_listings | Confirms how many listings actually reached published status. |
wal_xc_catalogue_drift_vs_bc | Flags source-of-truth drift that can corrupt the feed and cause rejections. |
Reconciling against Walmart Seller Center
Where to look in Walmart Seller Center: Open the Item or Catalog area and review the item setup or error log, where Walmart lists each rejected item alongside the specific error reason. The bulk upload or feed status view shows the submission batch the rejections belong to. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses 24H 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. |