Scenario analysis
Scenario analysis re-runs a store's plan or P&L under several named sets of assumptions - typically a base, an upside and a downside case - to show the range of outcomes before money is committed. An ecommerce operator uses it to test a price change, an inventory buy or a budget move against the downside.
| Variable | What it covers |
|---|---|
| Assumption set | The named inputs that define the scenario - demand, AOV, costs, return rate. One coherent story per scenario. |
| Model output | The same P&L arithmetic run on those inputs. Only the assumptions change between scenarios - never the math. |
Worked example
Example numbers, per quarter. The A$27.60 contribution per order comes from the A$120 order stepped down on The Math.
What is a good scenario analysis?
There is no benchmark output - the quality lives entirely in the assumptions, and what a survivable downside looks like depends on your margin structure. A thin-margin store crosses into loss on a far smaller demand miss than a fat-margin one, so the spread matters more than the midpoint. Three tests: scenarios must be internally coherent (a downside where demand falls but ad efficiency conveniently holds is not a downside), few enough to act on, and anchored to a base case that has survived ledger reconciliation. Your own floor is computable: the break-even point tells you exactly how much downside the fixed-cost base can absorb.
Scenario analysis vs related metrics
| Metric | What it measures | How it differs from scenario analysis |
|---|---|---|
| Demand forecasting | Expected units per SKU per period. | Produces the base case; scenario analysis stresses that forecast up and down. |
| P&L statement | Revenue down to profit for a past period. | The model being re-run - scenario analysis is the P&L pointed at the future, several times. |
| Break-even point | The volume where contribution covers fixed costs. | One built-in threshold; scenario analysis shows the whole range around it. |
| Price elasticity | How demand responds to price changes. | Supplies the demand response inside any pricing scenario, rather than competing with it. |
Common mistakes
- Moving one variable at a time. Real downsides arrive together - demand falls while CAC rises and returns climb. A scenario is a coherent story, not a single slider.
- Anchoring on an unreconciled base case. If the base P&L has not tied out to the ledger, every scenario inherits its errors with confidence added.
- Only modelling the upside. The decision-changing case is nearly always the downside - it sets how much inventory and ad budget you can responsibly commit.
- Treating scenarios as forecasts. A scenario is a range to plan against, not a prediction to bet on. The output is a decision rule: what you do if the downside shows up.
- Building ten scenarios nobody can act on. Past a handful, scenarios stop informing the decision and start decorating it.
Scenario analysis FAQ
Related
Blufire S11 Planning & Forecasting ships a Scenario Lab that re-runs your reconciled P&L under the assumption sets you name, and S13 Experiments (geo-lift, email and ad-set holdouts) turns the biggest assumptions into tested facts.
Updated July 2026