At a glance
Revenue at Risk (live) is an Executive Command Centre metric tracked from Alibaba data. It rolls several live exposures into one currency figure: the value of unresponded RFQ deadlines weighted by conversion rate and average selling price, plus Trade Assurance dispute escrow holds, plus the visibility cost of a slipping supplier badge. It is the single number an owner or finance lead checks first, and it pairs with the underlying driver cards (RFQ response, badge status, disputes) so you can see what is putting money at risk. Cross-reference the related cards below for context.
| What it counts | Estimated revenue exposure as exposed by the Alibaba integration: unresponded RFQ deadlines (conversion rate x average selling price) plus Trade Assurance dispute escrow holds plus badge-loss visibility cost. The metric is computed from the latest available data and refreshed on the standard data refresh. |
| Sample type | Backend API data from Alibaba, refreshed on the standard data refresh. |
| Why it matters | The metric appears in the Executive Command Centre category and complements the sibling cards listed below. It converts scattered operational risks into one currency figure leaders can act on immediately. |
| Reading the value | Read as a currency amount. Lower is better. Drill into the driver cards to see which component is contributing most to the total. |
| Currency | currency |
| Time window | RT |
| Alert trigger | >$0 |
| Sentiment key | ali_revenue_at_risk |
| Roles | owner, finance |
Calculation
Calculated automatically from your Alibaba data by combining three live exposures: open RFQ and inquiry deadlines that have not been answered (weighted by a conversion rate and your average selling price), Trade Assurance escrow amounts currently held against open disputes, and an estimated visibility cost where supplier badge metrics are trending toward a threshold. Inputs are drawn from the RFQ, Trade Assurance, and badge data the Alibaba integration exposes. The card reports a real-time currency figure. 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 Revenue at Risk (live) for a typical Alibaba supplier. Suppose on 12 Mar 26 the card reads 18,400 USD. Breaking it down: 9 RFQs are sitting past their response window, and at a typical conversion rate against an average order value of roughly 1,300 USD that line contributes about 11,000 USD; two Trade Assurance disputes have 5,400 USD of escrow on hold; and the response-rate trend toward the badge threshold adds an estimated 2,000 USD of visibility cost. The action is to clear the overdue RFQs first since that is the largest and most recoverable slice, then progress the disputes. For deeper investigation, use Vortex Mind to attribute the figure to its driver cards and trace what changed; for natural-language exploration, ask Ask Viq which RFQs and disputes are driving the number today.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
rfq-response-rate-30d | Driver: unanswered RFQs feed the largest slice of exposure. |
median-rfq-response-time-hours | Driver: slow responses push more RFQs past deadline. |
verified-gold-supplier-badge-status | Driver: badge slippage contributes the visibility-cost component. |
dispute-rate | Driver: disputes drive Trade Assurance escrow holds. |
trade-assurance-revenue-share | Context: how much revenue runs through escrow that can be held. |
Reconciling against Alibaba Seller dashboard
Where to look in Alibaba’s own dashboard: There is no single Alibaba screen for this figure since it is a Vortex IQ composite. Reconcile its parts: open RFQs under RFQ Market and Message Centre, escrow holds under Trade Assurance, and badge metrics under Data Insights / Business Analysis. Confirm period boundaries and filter settings match the Vortex IQ profile to reconcile cleanly. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ reports a live composite; Alibaba’s separate screens may show settled or calendar-period values. | Variable | Reconcile each component against its own screen. |
| Time zone. Alibaba uses account time zone; Vortex IQ aligns to your merchant reporting time zone, shifting RFQ deadlines across day boundaries. | Marginal | Confirm time zone match. |
| Filter scope. Profile-level filters (storefront, category, test orders) may narrow the Vortex IQ view. | Variable | Match filter settings. |