At a glance
Required-Attribute Completeness is the share of your listings that have every Fruugo-required attribute populated, covering titles, descriptions, images, category mapping, and VAT metadata. Fruugo cannot localise or distribute a listing that is missing required fields, so this Listing Health metric is an early warning for rejections and poor cross-border reach. The default alert fires below 90%, the point at which incomplete listings start to drag on your distribution.
| What it counts | The percentage of your listings that have all Fruugo-required attributes populated and valid. |
| Sample type | Live snapshot across the active catalogue. |
| Why it matters | Missing required attributes block localisation and trigger rejections, quietly removing products from country marketplaces and depressing reach. |
| Reading the value | Higher is better, with 100% as the goal. Below 90% means a meaningful slice of the catalogue is at risk of rejection or poor localisation. |
| Currency | percent |
| Time window | RT |
| Alert trigger | <90% |
| Sentiment key | fru_attribute_completeness |
| Roles | owner, operations |
Calculation
The card checks each active listing against Fruugo’s set of required attributes - including title, description, imagery, category mapping, and VAT metadata - and counts a listing as complete only when none of those fields are missing or invalid. The metric is the count of complete listings divided by the total active listings, expressed as a percentage.Worked example
A representative reading of Required-Attribute Completeness for a typical merchant on Fruugo. Picture a merchant whose completeness sits comfortably at 97%, then slips to 88% overnight, tripping the 90% alert (illustrative figures). The drop is not random: a new product range was added to the source feed without HS commodity codes or category mapping. Because those are required, Fruugo would reject or under-distribute the whole range. Vortex Mind investigates and isolates the offending feed batch and the exact missing attributes, and Ask Viq lets you ask “which listings dropped my completeness this morning” to get the SKU list, so the fix happens before the rejections pile up rather than after.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
fru_listing_quality_score | Listing Health sibling: Listing Quality Score. |
fru_vat_compliance_gaps | Listing Health sibling: Listings Missing VAT Metadata. |
fru_rejected_listings | Listing Health sibling: Rejected / Reviewing Listings. |
fru_alert_listing_rejection_spike | Listing Health sibling: Fruugo Rejected Listings (24h). |
fru_xc_feed_rejection_vs_listings | Cross-channel sibling: Listings Failing Feedonomics Validation. |
Reconciling against Fruugo Merchant Portal
Where to look in Fruugo’s own dashboard: In the Fruugo Merchant Portal, open the listings or product quality area, where Fruugo flags listings with missing or invalid required attributes and shows rejection or review reasons. Filtering for incomplete or rejected listings gives you the portal’s view of the same gap this card summarises. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Snapshot taken between the twice-daily feed imports, before the portal re-validates | Either | Re-check after the next import; new feed data may resolve or introduce gaps. |
| Vortex IQ may count an attribute as required that Fruugo only enforces for certain categories or countries | Vortex IQ lower | Confirm whether the missing field is mandatory for that product’s category before treating it as a blocker. |
| Scope difference: this card measures the active catalogue, the portal view may include archived or draft listings | Either | Match the listing-status filter on both sides before comparing counts. |
fru_rejected_listings and fru_vat_compliance_gaps to see whether incompleteness has already turned into rejections, and let Vortex Mind trace the gap back to the source feed.
Known limitations / merchant FAQs
Q: How often does this number update? It refreshes in near real time as a snapshot, but the validated attribute state changes when Fruugo’s twice-daily feed import re-evaluates your listings, so a fix in your source feed shows up after the next import. Q: Why does the Fruugo Merchant Portal show a different completeness picture? Usually it is a scope or timing difference: the portal may include archived or draft listings, or it may have just re-validated after an import while this card was snapshotted moments before. Some attributes are also only required for specific categories or countries. Q: How does this relate to Listing Quality Score and Rejected / Reviewing Listings? Completeness is the upstream cause;fru_listing_quality_score and fru_rejected_listings are the downstream effects. A falling completeness figure usually precedes a quality-score dip and a rejection spike.
Q: Can I change the 90% alert threshold?
Yes. 90% is the default, but the threshold is configurable. Catalogues with thin margins for error often raise it, while merchants mid-onboarding may lower it temporarily so the alert is not always lit while they backfill attributes.