At a glance
Listings Failing Feedonomics Feed Validation is a Cross-Channel: Revenue at Risk metric that reports the percentage of Feedonomics-syndicated B2B listings that Alibaba’s product-quality validation rejects. Feedonomics is the feed layer that pushes your catalogue into Alibaba, so a rejected listing never goes live and never earns an inquiry. A rising rejection rate is a direct leak of listing coverage and revenue opportunity. The card pairs with the other Cross-Channel: Revenue at Risk siblings below, and with listing-quality and catalogue cards, to keep your syndicated feed clean.
| What it counts | The percentage of B2B listings sent through the Feedonomics feed that fail Alibaba’s product-quality validation over the time window, versus those that pass and go live. |
| Sample type | Backend API data from Alibaba, refreshed on the standard data refresh. |
| Why it matters | Feedonomics is how your catalogue reaches Alibaba. A rejected listing is invisible to buyers, so a high rejection rate quietly shrinks your live storefront and starves your RFQ pipeline. |
| Reading the value | Read as a rejection percentage. Lower is better. Compare the current period to the prior period; an upward move signals a feed-mapping or attribute problem that needs fixing at the feed level. |
| Currency | percent |
| Time window | 7D |
| Alert trigger | >5% feed rejection rate |
| Sentiment key | ali_xc_feed_rejection_vs_listings |
| Roles | owner, operations, engineering |
Calculation
This is a cross-channel card: it joins the set of B2B listings pushed through the Feedonomics feed against the validation outcomes returned by Alibaba’s product-quality checks. It divides the count of rejected listings by the total submitted over the time window and expresses the result as a percentage. Because the feed is the upstream source, a rising rate points back to the Feedonomics mapping or to attributes that fall short of Alibaba’s listing requirements. See the worked example below for a typical reading.Worked example
A representative reading of Listings Failing Feedonomics Feed Validation for a typical Alibaba supplier. In the 7 days to 12 Mar 26, a supplier pushes 1,200 listing updates through Feedonomics. Alibaba rejects 84 of them, so the card reads 7 percent, above the 5 percent alert line. Drilling in shows most rejections cluster on a single category where a newly required attribute is not mapped in the feed, so those listings never go live and earn zero inquiries that week. Vortex Mind traces the spike to a recent Alibaba category-requirement change that the Feedonomics mapping has not caught up with, and Ask Viq lets the engineering owner pull the rejected SKU list and reason codes to fix the feed mapping in one pass.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
listings-drifting-from-bc-source-of-truth | Cross-channel sibling: drift from BC often surfaces as feed rejections. |
active-alibaba-listings-for-oos-skus-on-bc | Cross-channel sibling: another way the feed and BC fall out of sync. |
b2b-vs-retail-pricing-coherence-vs-aliexpress | Cross-channel sibling: pricing coherence across sister channels. |
required-attribute-completeness | Missing required attributes are a leading cause of feed rejection. |
active-listings | Rejections suppress this count; rejected listings never reach live. |
Reconciling against Alibaba Seller dashboard
Where to look in Alibaba’s own dashboard: Alibaba shows only its own side of this comparison. In your supplier workbench, open Product Management to see which listings were rejected and the reason codes Alibaba returned. Alibaba does not see your Feedonomics feed, so to reconcile the rate you compare the count submitted through Feedonomics against the rejections Alibaba reports. The card does that join; the workbench is where you read the rejection reasons. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses a 7-day window; the workbench may show a different rejection range. | Variable | Match the date range on both sides. |
| Time zone. Submission and validation timestamps differ between the account time zone and your merchant reporting time zone. | Marginal | Confirm the time zone match. |
| Filter scope. Profile-level filters (which feed or category is in scope) may narrow which submissions are counted. | Variable | Match the feed and category filters. |