At a glance
Revenue at Risk is the dollar value of sales exposed to a live issue right now on your Bonanza booth. It rolls up problems that quietly cost money, such as listings drifting out of sync, active listings for SKUs that are out of stock on the source, feed rejections, and late shipments. Any figure above $0 means there is revenue you could be protecting today. It is the headline number for the Executive Command Centre.
| What it counts | The dollar value of revenue exposed to live issues such as listing drift, out-of-stock-but-active SKUs, feed rejections, and late shipments. |
| Sample type | Backend API data from Bonanza, refreshed on the standard data refresh. |
| Why it matters | It puts a single dollar figure on problems that would otherwise stay scattered across cards, so you can see at a glance how much money is exposed and act before it is lost. |
| Reading the value | Read it as a dollar amount; 0 points to revenue worth protecting now. |
| Currency | currency |
| Time window | RT |
| Alert trigger | >$0 |
| Sentiment key | bon_revenue_at_risk |
| Roles | owner, finance |
Calculation
Vortex IQ rolls up the revenue tied to live issues across your booth and expresses it as a single dollar figure, refreshed in real time. It draws on the same signals as the underlying cards, such as listings drifting from the source, active listings for out-of-stock SKUs, listings failing feed validation, and late shipments, and attaches the at-risk revenue each represents. As issues are resolved the figure falls toward zero. See the At a glance summary above for the components and the worked example below for a typical reading.Worked example
A representative reading of Revenue at Risk for a typical merchant on Bonanza. On 14 Mar 26 a booth showed 0 alert, up from near zero a week earlier. Drilling in, most of it traced to a handful of best-selling listings still active on Bonanza for SKUs that had gone out of stock on the source catalogue, with a smaller slice from two late shipments. The interpretation was a sync gap leaving sellable-looking listings that could not be fulfilled, and the action was to pause those listings and clear the late orders. Vortex Mind traces the upstream cause, here the out-of-stock-but-active SKUs, and Ask Viq lets you ask “what is putting my revenue at risk right now” in plain English.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
bon_xc_catalogue_drift_vs_bc | Cross-connector sibling: Listings Drifting from BC. |
bon_xc_listed_but_oos_on_bc | Cross-connector sibling: Active Bonanza Listings for OOS SKUs on BC. |
bon_xc_feed_rejection_vs_listings | Cross-connector sibling: Listings Failing Feedonomics Validation. |
bon_marketplace_health_score | Executive sibling: Bonanza Booth Health Score. |
bon_on_time_ship_rate | Fulfilment sibling: On-Time Shipping Rate. |
Reconciling against Bonanza
Where to look in Bonanza’s own dashboard: There is no single Bonanza screen for this composite, since it spans listing, sync, and fulfilment signals. Reconstruct it by checking the selling and items area for drifting or out-of-stock listings, the Importer status for feed issues, and the order management area for late shipments. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ evaluates risk in real time; Bonanza dashboards may group by calendar periods. | Variable | Match the period range. |
| Time zone. Bonanza uses account time zone; Vortex IQ aligns to merchant reporting time zone. | Marginal | Confirm time zone match. |
| Filter scope. Profile-level filters (booth, channel, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. |