Revenue at Risk, Ecwid

Revenue at Risk: estimated revenue exposed by current operational risks. How to read it, why it matters, and how to act on it.

Metrics type: Key Metrics • Category: Ecommerce Platform

An executive roll-up of revenue exposed right now by live operational risks.

At a glance

A single currency figure estimating how much revenue is exposed by current operational risks: bestsellers out of stock, orders stuck in processing, inventory sync drift across storefronts, and similar live problems. It is an executive roll-up, the one number an owner can glance at to answer “is anything actively bleeding money right now”. For an Ecwid SMB merchant juggling the store alongside other work, this card surfaces the problems that warrant dropping everything.

What it counts	An estimated currency total of revenue exposed by active operational risks, rolled up across signals such as out-of-stock bestsellers, stuck or backlogged orders, awaiting-payment orders at risk of lapsing, and inventory sync drift. The value is an estimate, not booked or lost revenue.
API endpoint	Derived. Composed from the same underlying GET /v3/{store-id}/orders, GET /v3/{store-id}/products, and inventory data that feed the contributing risk cards; no single endpoint returns this figure.
How the estimate is built	Each contributing risk is converted to an approximate revenue exposure (for example, an out-of-stock bestseller’s recent daily run-rate, or the value of orders stuck past a processing threshold), then summed.
What it excludes	Healthy, on-track orders and in-stock products; already-refunded or already-cancelled revenue (that is realised, not at risk).
Currency	Single currency per Ecwid store, matching the store’s configured currency.
Time window	RT (real-time; the figure reflects current risk state, not a historical window).
Alert trigger	>$0. Any non-zero exposure raises the card, because for a small store even a modest figure can be a meaningful slice of the month.
Sentiment	Inverse. Higher is worse; the goal is to drive this to zero.
Roles	owner, finance.

Calculation

Calculated automatically from your Ecwid data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A small US home-fragrance merchant running an Ecwid widget embedded on a WordPress site, snapshot taken 22 May 26.

The owner runs the store solo around a day job. The card is showing a non-zero figure this morning, which is why it has surfaced.

Risk source	Detail	Estimated exposure
Out-of-stock bestseller	”Cedar + Sage” candle, ~$40/day run-rate, expected restock in 6 days	$240
Order processing backlog	4 paid orders stuck unfulfilled past the 48h threshold	$185
Awaiting-payment at risk	2 PayPal-pending orders nearing the auto-cancel window	$96
Inventory sync drift	1 SKU showing different stock on the Wix mirror store vs WordPress	$60
Revenue at Risk (this card)		$581

Out-of-stock bestseller:        $240
Order processing backlog:       $185
Awaiting-payment at risk:        $96
Inventory sync drift:            $60
Revenue at Risk (estimate):     $581

What it means for this merchant. $581 of estimated exposure on a store doing roughly$4,000 a month is material, around 14% of a month’s revenue tied up in fixable problems. None of it is lost yet, which is the point: this is the window to act before it becomes lost revenue or a cluster of “where is my order” emails.

The card is deliberately a single number because the Ecwid owner-operator does not have time to scan ten cards each morning. The exposure breaks into a clear priority order. The out-of-stock bestseller is the biggest and slowest to fix, so a restock chase to the supplier goes first. The processing backlog is the most controllable; four orders can be fulfilled today. The awaiting-payment orders need a nudge before they auto-cancel. The sync drift is small but the cheapest to close by re-syncing the mirror store.

The action playbook follows the breakdown: chase the restock, clear the four backlogged orders, send a payment reminder on the two pending PayPal orders, and re-sync inventory across surfaces. Re-check the card after each; it should fall toward zero as each risk clears. A persistently non-zero figure is a sign the store needs either more operating time or some automation.

Sibling cards merchants should reference together

Card	Why it matters next to Revenue at Risk	What the combination tells you
Out-of-Stock Products	A primary risk input.	Identifies which OOS SKUs are driving the exposure so you can prioritise restocks.
Order Processing Backlog	Stuck-order input.	Shows the orders contributing the backlog slice of the figure.
Awaiting Payment Orders	Lapsing-revenue input.	Surfaces orders at risk of auto-cancelling before they clear.
Inventory Sync Drift Across Storefronts	Multi-surface input.	Pinpoints SKUs mismatched across embedded surfaces.
Total Revenue	The denominator for severity.	Risk as a share of monthly revenue tells you how alarmed to be.
Revenue Trend	Direction context.	Rising risk during a falling trend compounds the urgency.
Top Products by Revenue	Concentration check.	If an at-risk SKU is also a top product, the exposure is understated, not overstated.

Reconciling against Ecwid

Where to look in Ecwid’s own dashboard:

Ecwid Control Panel (my.ecwid.com) has no single “revenue at risk” figure; this is a Vortex IQ roll-up. To verify the components, cross-check each input: Catalog -> Products for out-of-stock items, My Sales -> Orders filtered by unfulfilled and by awaiting-payment status, and your storefront inventory settings for drift.

For a sanity check, add up the exposure you would assign to each problem you can see in the Control Panel and compare to the card’s total.

Why our number may differ from your own mental estimate:

Reason	Direction	Why
Run-rate assumptions	Either	An out-of-stock SKU’s exposure uses its recent sales velocity; a slow week makes ours lower, a recent spike makes ours higher than your gut.
Thresholds	Either	What counts as a “stuck” order depends on the processing threshold; a different threshold shifts the figure.
Estimate, not actuals	Either	This is forward-looking exposure, not booked loss; the real outcome depends on how fast you act.
Sync lag	Marginal	The inputs are webhook and poll driven; the figure reflects the most recent sync.
Overlap handling	Ours lower	If one order is at risk for two reasons, we avoid double-counting; a naive sum would be higher.

Internal identity:

revenue_at_risk = SUM(estimated exposure of each active risk signal, de-duplicated)

Known limitations / merchant FAQs

Is this money I have already lost? No. This is revenue at risk, not revenue lost. It is an estimate of what is exposed by current operational problems if you do nothing. Act on the underlying risks and the figure should fall toward zero before any of it becomes a real loss.

Why does the alert trigger at any non-zero value? Because for a small Ecwid store even a modest exposure can be a meaningful slice of the month, and the problems behind it are usually quick to fix. Surfacing any non-zero figure keeps the owner-operator ahead of issues rather than reacting after the fact.

How is the dollar figure calculated? Each contributing risk is converted to an approximate exposure, for example an out-of-stock bestseller’s recent daily run-rate over its expected stockout period, or the value of orders stuck past a processing threshold. The components are then summed, with overlaps de-duplicated. It is an estimate, not an exact accounting figure.

Which risks feed into it? Typically out-of-stock bestsellers, order processing backlog, awaiting-payment orders nearing auto-cancel, and inventory sync drift across embedded storefronts. The exact mix can evolve as more risk signals are added. The contributing cards are linked in the siblings table.

Why might my number be higher than I expected? Usually a bestseller stockout combined with a recent sales spike, which inflates the run-rate used for exposure. Check the out-of-stock and top-products cards; if a high-velocity SKU is out, the exposure climbs quickly.

Why might it be lower than I expected? We de-duplicate overlapping risks, so an order that is at risk for two reasons is counted once. We also exclude already-refunded and already-cancelled revenue, since that is realised rather than at risk.

Does this update in real time? Yes, it reflects the current risk state rather than a historical window. As you clear a stuck order or restock a SKU, the figure updates on the next sync.

It says zero. Does that mean everything is perfect? It means no monitored risk signal is currently active. It does not cover every conceivable problem, only the operational risks that feed the roll-up. A zero is good news but not a guarantee; keep an eye on the trend and quality cards too.

My store is tiny; is this card useful for me? Especially so. For a solo Ecwid operator, this is the one number that tells you whether to drop other work and tend the store today. It collapses several cards into a single morning glance.

---

Tracked live in Vortex IQ Nerve Centre

Revenue at Risk is one of hundreds of KPI pulses Vortex IQ tracks across Ecwid and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.