| Vose Software

Industry: Retail
Product: ModelRisk
Application: Understanding and Predicting Consumer Behavior


A +8% Price Rise: Coin-Flip Odds That Category Volume Drops More Than a Tenth

A category manager about to push list price up 8% wants one number: how much volume walks out the door? The pricing deck answers with a point estimate — plug the historical elasticity, get -9.5%, sign off. But that single figure hides the real exposure. When a multinational retail chain rebuilt the calculation in ModelRisk, treating the price elasticity as uncertain (it varies category to category) and adding a shared consumer-sentiment swing that moves every category at once, the answer became a distribution, not a digit. The mean still lands at -9.3%, almost exactly the point estimate — but the probability that volume falls by more than 10% is 46.7%, essentially a coin flip, and there is an 18.3% chance it falls more than 15%. The deck's tidy "-9.5%" gives no hint of that downside.

Distribution of category volume change after a price rise

This is a market-level behavioral question — how the aggregate category responds to a driver — not a question about any individual shopper. The driver here is price; the same machinery handles an income shift or a sentiment shock.

Why a point estimate fails

Aggregate demand follows the constant-elasticity (log-log) law D = D0 x (P/P0)^(-E). Feed it one "best" elasticity and you get one demand number. But elasticity is not one number — across the categories in this chain it is dispersed (modeled Normal, mean 1.30, sd 0.45, clipped positive so a price rise never raises volume), and a market-wide sentiment factor multiplies every category's response in any given quarter. Because that sentiment shock is shared, the category-level response does not average away to its mean by the law of large numbers — a jittery quarter is jittery for the whole shelf at once. The point estimate throws away both sources of spread and reports only the center, which is precisely the information a pricing committee does not need: they already know the average; they need the odds of a bad outcome.

The price-response curve

Sweeping the price move from 0% to 20% turns the single decision into a response surface, with the mean response and the P10-P90 band at every price point.

Mean and P10 to P90 volume response across price moves

  • At +0% price, mean volume change is +0.2%, P10-P90 band [-7.3%, +8.1%], and P(fall >10%) = 4%.
  • At +5%, mean -5.9%, band [-13.5%, +1.9%], P(fall >10%) = 25%.
  • At +10%, mean -11.4%, band [-19.6%, -2.9%], P(fall >10%) = 59%.
  • At +15%, mean -16.3%, band [-25.3%, -6.8%], P(fall >10%) = 81%.
  • At +20%, mean -20.7%, band [-30.8%, -10.1%], P(fall >10%) = 90%.

The band, not the line, is the decision content: at the chosen +8%, the worst-decile outcome is roughly twice the mean loss.

What drives the worst-decile loss

Ranking drivers by their effect on the mean is misleading — the average is nearly insensitive to spread parameters. The committee cares about the downside, so the tornado ranks each driver by its effect on the P10 (worst-decile) volume loss, baseline -17.2%.

Tornado of drivers of the worst-decile volume loss

  • Price-rise size (5%-11%): 7.2 percentage-point spread — the lever management actually controls.
  • Sentiment volatility (3%-10%): 6.2 pts — a jittery market doubles the tail risk of an identical price move.
  • Mean elasticity (1.0-1.6): 3.9 pts.
  • Elasticity dispersion (0.25-0.65): 1.6 pts.

The surprise is that sentiment volatility rivals the price move itself in setting the downside — a result invisible to any mean-based analysis, because sentiment volatility leaves the mean untouched and only fattens the tail.

How market mood changes the bet

At the fixed +8% price rise, the probability of losing more than x% of volume depends sharply on whether the market is calm or jittery.

Probability the price rise loses more than x percent of volume

  • P(fall >5%): 85.8% in a calm market, 67.7% in a jittery one.
  • P(fall >10%): 45.2% calm, 47.9% jittery — near-identical at the median threshold.
  • P(fall >15%): 8.6% calm versus 27.6% jittery.
  • P(fall >20%): 0.4% calm versus 12.2% jittery.

The two curves cross near the 10% threshold: sentiment volatility barely changes the typical outcome but transforms the tail. In a calm market a 20%-plus collapse is a 1-in-250 event; in a jittery market it is better than 1-in-9. Knowing which regime you are entering is worth more than refining the elasticity estimate.

What the model changed

  • Pricing sign-off moved from a point estimate to an exceedance probability. The committee now approves a price move against "P(volume falls >10%)" rather than a single forecast, and the 47% figure reframed the +8% proposal as a genuine coin flip rather than a safe -9.5%.
  • Sentiment regime entered the pricing calendar. Because sentiment volatility was shown to dominate the downside tail, the chain deferred discretionary price rises in categories during low-confidence quarters — a lever the old deterministic model could not even express.
  • Elasticity-measurement budget reallocated. The tornado showed that further refining the elasticity mean buys far less downside protection than tracking sentiment, so analyst effort was redirected to a real-time confidence indicator.

ModelRisk Functionality Used

  • Constant-elasticity (log-log) demand model with a Normal own-price elasticity drawn per category and a shared LogNormal sentiment factor common to all categories — the construction that prevents the aggregate response from collapsing to its mean.
  • Parameter sweep across candidate price rises to build the mean-and-band price-response curve, the chart that turns one decision into a response surface.
  • Sensitivity ranking on the P10 outcome rather than the mean, because the pricing risk lives in the downside tail where spread parameters bite and the average does not.
  • Threshold-probability outputs of the form "P(volume falls more than x%)" under two sentiment regimes, giving the committee a directly decision-relevant number.

The average response to a price rise is the question the pricing deck already answers. The question worth modeling is the probability of a damaging volume loss — and Monte Carlo turns that into a defensible percentage the category committee can sign against.