> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Listings Failing Feedonomics Validation, Newegg > Listings Failing Feedonomics Validation for Newegg Marketplace stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Marketplace](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Listings Failing Feedonomics Validation** is the share of your listings that fail Feedonomics feed validation before they ever reach Newegg. Feedonomics is the feed-management layer between your source catalogue and the marketplace; items that fail its validation rules never publish. The danger is that the failure is silent: nothing errors loudly, your catalogue coverage just quietly shrinks. It sits in the Cross-Channel: Revenue at Risk Hero cluster so owners, operations, and engineering catch a feed regression before it strips listings off Newegg. | | | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | The percentage of listings that fail Feedonomics feed validation before publishing to Newegg, as measured by the Vortex IQ cross-channel integration. Failed items do not reach the marketplace. | | **Sample type** | Backend API data from the Feedonomics feed pipeline and Newegg Marketplace, refreshed on the standard data refresh. | | **Why it matters** | Failed items never publish, so your live Newegg catalogue silently shrinks while your source catalogue looks complete. A rising failure rate quietly removes sellable SKUs and the revenue they would have earned. | | **Reading the value** | Lower is better; near zero is healthy. A rising percentage means more items are being rejected at the feed stage; open the detail to see which validation rules are failing and fix the data at source. | | **Currency** | percent | | **Time window** | `7D` | | **Alert trigger** | `>5%` | | **Sentiment key** | `neg_xc_feed_rejection_vs_listings` | | **Roles** | owner, operations, engineering | ## Calculation Calculated automatically as the share of listings that fail Feedonomics validation out of all listings submitted to the feed over the trailing window. The card divides validation failures by total feed items and expresses the result 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 on Newegg Marketplace.* Suppose the card sat near 1 percent for weeks, then jumps to 8 percent after a catalogue update. Opening the detail shows most failures share one cause: a required attribute that a new product template left blank, so Feedonomics rejected the items before they could publish to Newegg. Roughly 120 SKUs that look fine in the source catalogue never reached the marketplace, and the merchant only noticed because the failure rate breached threshold here rather than from a loud error. They correct the template at source, the feed reprocesses, and the rate falls back under 2 percent. For deeper investigation, use Vortex Mind to trace which validation rules and product templates drive the failures; for natural-language exploration, ask Ask Viq. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | --------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | | [`neg_xc_catalogue_drift_vs_bc`](/nerve-centre/kpi-cards/newegg/listings-drifting-from-bc) | Cross-Channel sibling: listings out of sync with the BC source. | | [`neg_xc_listed_but_oos_on_bc`](/nerve-centre/kpi-cards/newegg/active-newegg-listings-for-oos-skus-on-bc) | Cross-Channel sibling: Newegg listings live while OOS on BC. | | [`neg_xc_price_parity`](/nerve-centre/kpi-cards/newegg/map-parity-vs-amazon-walmart) | Cross-Channel sibling: MAP parity across Newegg, Amazon, and Walmart. | | [`neg_attr_completeness`](/nerve-centre/kpi-cards/newegg/required-attribute-completeness) | Listing Health sibling: missing attributes that drive validation failures. | | [`neg_rejected_listings`](/nerve-centre/kpi-cards/newegg/rejected-listings) | Listing Health sibling: items rejected at the Newegg side. | ## Reconciling against Newegg Seller Portal **Where to look in the Newegg Seller Portal:** Items that fail Feedonomics validation never reach Newegg, so the Seller Portal will not show them at all; their absence is the symptom. To reconcile, open the Feedonomics feed exports and error reports (the source of truth for feed validation) and compare the rejected-item list against the SKUs you expect to see live in the Seller Portal. Because this is a cross-channel card, check both the Feedonomics pipeline and the Newegg Seller Portal listing count. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ------------------------------------------------------------------------------------------------------------------------ | --------- | ----------------------------------------------------- | | **Pipeline timing.** A feed run may be mid-flight, so failures from the latest batch may not be counted yet. | Variable | Allow for the feed cadence, then re-check. | | **Denominator scope.** Vortex IQ measures the share of feed items; Feedonomics reports may count raw rule hits per item. | Variable | Confirm whether you are comparing items or rule hits. | | **Rule configuration.** Custom Feedonomics validation rules differ per account, so the failure set is account-specific. | Variable | Confirm the rule set matches your feed configuration. | **Cross-connector reconciliation:** because this card spans the Feedonomics feed pipeline and Newegg, reconcile against both the Feedonomics error reports and the Newegg Seller Portal listing count. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Listings Failing Feedonomics Validation update?** The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations), re-reading the latest feed validation results. For real-time signals, force a manual refresh from the dashboard, though a feed run may need to complete first. **Q: Why does my Newegg Seller Portal show a different number?** The portal cannot show this directly because failed items never publish; their absence is the evidence. Differences usually come from pipeline timing (a feed run mid-flight), denominator scope (items vs raw rule hits), and account-specific validation rules. Compare the Feedonomics error reports against the Seller Portal listing count. **Q: How does this relate to the other cross-channel cards?** It is the publish-stage member of the Cross-Channel: Revenue at Risk cluster: items here never reach Newegg, while the drift and OOS cards cover items that did publish but disagree with BC. Pair with Required Attribute Completeness, since missing attributes are a common failure cause. **Q: Can I customise the alert threshold?** Yes, sensitivity thresholds are configurable per profile in the Sensitivity tab. Adjust the percentage threshold 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 Newegg Marketplace 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.