At a glance
Listings Failing Feedonomics Validation is the share of your BigCommerce feed that Feedonomics rejects before it ever reaches AliExpress. Feedonomics is the feed-management layer that transforms and validates the BC source catalogue, mapping fields and enforcing AliExpress requirements, before syndicating listings to the marketplace. Anything that fails validation at this stage never goes live, so it is a silent revenue gap rather than a visible error in Seller Center. The card expresses these failures as a percentage of the feed, so you can judge whether rejection is a handful of edge cases or a systemic mapping problem. A rising rate usually points to a schema change, a missing required attribute, or a category remap on the AliExpress side.
| What it counts | The percentage of feed rows that fail Feedonomics validation and therefore never reach AliExpress as live listings. |
| Sample type | Backend API data from AliExpress reconciled against the Feedonomics feed status, refreshed on the standard data refresh over a rolling 7-day window. |
| Why it matters | Failed rows are silent: they do not appear in Seller Center because they never went live. A high rejection rate is lost catalogue coverage and lost sales. |
| Reading the value | Read it as a proportion of the feed. A low single-digit percentage is usual churn; a climbing rate signals a mapping or required-attribute break worth investigating. |
| Currency | percent |
| Time window | 7D |
| Alert trigger | >5% rejection rate |
| Sentiment key | aex_xc_feed_rejection_vs_listings |
| Roles | owner, operations, engineering |
Calculation
Vortex IQ divides the number of feed rows rejected at the Feedonomics validation step by the total rows in the feed for the period, expressed as a percentage. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A representative reading of Listings Failing Feedonomics Validation for a typical merchant syndicating BC to AliExpress through Feedonomics. On 11 Mar 26 the rate jumps from a steady 2% to 8%, tripping the 5% alert. The merchant opens the Feedonomics feed log and finds 410 of roughly 5,100 rows failing on a newly required AliExpress attribute that the BC catalogue does not populate. Because these rows never went live, Seller Center showed nothing wrong; the gap was invisible until this card flagged it. Engineering adds the attribute mapping and the rate falls back under 2% within two refresh cycles. 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 |
|---|---|
aex_xc_catalogue_drift_vs_bc | Rejected updates leave the live listing stale, which shows up as drift from BC. |
aex_xc_listed_but_oos_on_bc | A stock update failing validation can leave an OOS SKU still buyable on AliExpress. |
aex_required_attribute_completeness | Missing required attributes are a leading cause of feed validation failures. |
aex_rejected_listings_24h | Listings AliExpress itself rejects after they pass the feed layer. |
aex_total_listings | The catalogue size that the failed-feed percentage is measured against. |
Reconciling against AliExpress Seller Center
Where to look in AliExpress Seller Center: By design these failures do not appear in Seller Center because the rows never reached AliExpress. The authoritative record is the Feedonomics feed status log, and the source rows sit in the BigCommerce catalogue, so reconcile against those two rather than Seller Center. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Retry timing. Feedonomics may retry a failed row on the next feed run, so a momentary failure clears itself. | Marginal | Recheck after the next feed run before treating it as a hard failure. |
| Warning vs hard reject. Some Feedonomics rules warn without blocking; only hard rejects count here. | Variable | Confirm the rule severity in the feed log before acting. |
| Window mismatch. This card uses a rolling 7-day window; the Feedonomics log may default to a single run. | Variable | Align the log date range to the 7-day window before comparing. |