At a glance
Listings Missing VAT Metadata is the count of listings missing the VAT data Fruugo requires, such as per-country VAT registration, OSS threshold flags, or HS commodity codes. Because Fruugo handles VAT remittance on many cross-border flows and will not distribute a listing that lacks this metadata, every entry here is a listing Fruugo blocks until the data is populated. Sitting in the Listing Health category, it is the compliance queue owners, finance, and operations clear fast, since each gap silently removes a product from the markets it should reach.
Calculation
The card counts the listings whose required VAT metadata is incomplete, checking for the per-country VAT registration, OSS threshold flags, and HS commodity codes Fruugo requires before it will distribute a listing cross-border. A listing missing any required piece counts once, and it drops out of the count when the missing data is populated and re-imported.Worked example
A representative reading of Listings Missing VAT Metadata for a typical merchant on Fruugo. Suppose the card reads 38 on 12 Mar 26, tripping the configurable above-zero alert (illustrative figures). At first it looks like 38 unrelated products, but compliance gaps usually cluster. Vortex Mind investigates and finds 34 of them are missing the same HS commodity code for a single product category that was added without it in the source feed, while four lack an OSS threshold flag for one country. Ask Viq “which VAT field is most often missing and which products are affected” returns the dominant gap and the SKU list in plain English, so the team fixes one feed column and restores distribution for most of the blocked listings in one pass.Sibling cards merchants should reference together
Reconciling against Fruugo Merchant Portal
Where to look in Fruugo’s own dashboard: Open the Fruugo Merchant Portal and review the listing or compliance area where VAT and tax metadata is shown against each product, including VAT registration, OSS flags, and commodity codes. Listings flagged as blocked on tax or VAT data there are the authoritative source for this count. Why the Vortex IQ value may legitimately differ:
Cross-connector reconciliation: Because a VAT gap removes a listing from distribution, cross-reference
fru_rejected_listings, fru_active_countries, and fru_revenue_at_risk, then let Vortex Mind trace the missing field back to the source feed column.
Known limitations / merchant FAQs
Q: How often does this number update? It refreshes in near real time as a live snapshot, but a gap only clears once the missing VAT data is populated and re-imported through Fruugo’s twice-daily feed import, so fixes show up at the next import cycle. Q: Why does the Fruugo Merchant Portal show different VAT gaps? The usual cause is field scope and timing. This card checks per-country VAT registration, OSS threshold flags, and HS commodity codes together, while the portal may surface only the single field blocking a given listing, and data you just populated clears here after the next import. Q: How does this relate to Rejected / Reviewing Listings and Active Country Marketplaces? A VAT gap is one of the reasons a listing ends up blocked, so this card often overlaps withfru_rejected_listings, and clearing it can restore markets counted in fru_active_countries. Read together they connect the compliance gap to the lost distribution.
Q: Can I customise the alert threshold?
Yes. The default fires whenever the count is above zero, because a VAT gap actively blocks distribution and remittance, but the threshold is configurable. Most finance teams keep the zero trigger given the compliance stakes, while very large catalogues may set a small tolerance to avoid noise from transient feed timing.