At a glance
Revenue at Risk is the estimated revenue exposed right now by suppressed or rejected listings, VAT blocks, stock-outs, and SLA breaches across your Fruugo footprint. Because Fruugo distributes localised listings across up to 46 country marketplaces, a single blocked feed or compliance gap can quietly pull money out of distribution in many countries at once. Sitting in the Executive Command Centre, it is the one “money currently in jeopardy” number owners and finance check before anything else.
| What it counts | The estimated revenue currently at risk from suppressed or rejected listings, VAT blocks, stock-outs, and fulfilment SLA breaches, summed into one figure. |
| Sample type | Real-time exposure estimate, recomputed continuously. |
| Why it matters | It converts scattered listing, compliance, and fulfilment problems into a single money figure, so the cost of inaction is impossible to ignore. |
| Reading the value | Zero is the goal. Any positive value means revenue is currently exposed; the larger it is, the more urgent the underlying issues. |
| Currency | currency |
| Time window | RT |
| Alert trigger | >$0 |
| Sentiment key | fru_revenue_at_risk |
| Roles | owner, finance |
Calculation
The card estimates the revenue tied to listings and orders currently impaired, by attributing recent earning power to listings that are suppressed, rejected, blocked on VAT metadata, out of stock, or attached to orders breaching a fulfilment SLA, then summing the exposure into one figure. It is an estimate of money in jeopardy rather than money already lost, so it falls as the underlying issues are resolved.Worked example
A representative reading of Revenue at Risk for a typical merchant on Fruugo. Suppose the card reads 6,400 at risk on 12 Mar 26, up from zero the day before (illustrative figures). The alert fires the moment it crosses above zero. Vortex Mind investigates and decomposes the figure: most of it is a dozen high-selling listings rejected on a missing HS commodity code after a feed refresh, with the rest from two stock-outs in your top German lines. Ask Viq “what is driving my revenue at risk right now” returns the ranked contributors and the fix for each in plain English, so you can clear the largest exposure first and watch the number fall back toward zero the same day.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
fru_marketplace_health_score | Executive sibling: Fruugo Merchant Health Score. |
fru_rejected_listings | Executive sibling: Rejected / Reviewing Listings. |
fru_vat_compliance_gaps | Executive sibling: Listings Missing VAT Metadata. |
fru_out_of_stock | Executive sibling: Out-of-Stock Listings. |
fru_alert_dispatch_sla_miss | Executive sibling: Late Shipments. |
Reconciling against Fruugo Merchant Portal
Where to look in Fruugo’s own dashboard: Open the Fruugo Merchant Portal and review the listing status and order or fulfilment report areas together, since this card is a composite. The portal will show which listings are rejected or reviewing, which are out of stock, and which orders are running late, but it does not roll these into a single revenue figure the way this card does. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Snapshot timing relative to the twice-daily feed import | Either | Re-check after the next import cycle; a block resolved by a refresh drops out of the estimate. |
| Estimation basis: Vortex IQ attributes recent earning power to impaired listings, which the portal does not compute | Vortex IQ only | Treat the figure as a prioritisation estimate, not a portal line item; reconcile the underlying issue counts instead. |
| A listing is impaired in one country but selling in others, so only part of its revenue is at risk | Either | Use the per-listing breakdown to see how much of each listing’s footprint is actually blocked. |
fru_rejected_listings, fru_vat_compliance_gaps, and fru_out_of_stock, then let Vortex Mind decompose the figure into its largest contributors.
Known limitations / merchant FAQs
Q: How often does this number update? It is recomputed in real time as listing status, stock, VAT, and fulfilment signals change, though the underlying listing and VAT states only shift when Fruugo’s twice-daily feed import re-evaluates your catalogue. Expect the figure to fall through the day as you clear issues. Q: Why does the Fruugo Merchant Portal not show this number? The portal reports the underlying problems separately, but it does not estimate the combined revenue exposure. This card is the composite Vortex IQ computes by attributing recent earning power to each impaired listing or order, so there is no single portal line to match it to. Q: How does this relate to the Merchant Health Score and the underlying issue cards? This card is the money view of the same problems the issue cards count individually, and it moves in step withfru_marketplace_health_score. When a component card such as fru_rejected_listings clears, this figure should fall.
Q: Can I customise the alert threshold?
Yes. The default fires as soon as the figure rises above zero, on the principle that any exposed revenue deserves attention, but the threshold is configurable. Larger catalogues sometimes set a floor so only material exposure pages the team, while smaller merchants keep the zero trigger.