What is price elasticity modeling? A practical guide for retailers

By Elie Dufeu, CTO & Co-Founder, Metreecs. Published August 26, 2026.

Price elasticity modeling is the process of estimating how much demand for a product changes when its price changes, usually expressed as a single number: the percentage change in quantity demanded divided by the percentage change in price. Retailers use it to decide which products can take a price increase without losing volume, and which ones need a shallow markdown rather than a deep one to move.

If you plan pricing or markdowns for a product catalog of any real size, you already know the instinct-based version of this problem: some items fly off the shelf the moment they're discounted, others barely react, and a few actually sell better at a higher price because a low price makes buyers suspicious of quality. Price elasticity modeling replaces that guesswork with a number you can act on, product by product, location by location.

Key Takeaways

• Price elasticity of demand is calculated as percentage change in quantity demanded divided by percentage change in price; a result below -1 (in absolute value above 1) means demand is elastic, above -1 means it's inelastic.
• Retailers typically estimate elasticity using regression models on point-of-sale history, most commonly log-log regression because the price coefficient reads directly as the elasticity value.
• Cross-price elasticity measures how a price change on one product shifts demand for a related product, which matters most when a markdown on one line risks cannibalizing a substitute.
• Elasticity estimates degrade fast on new products, low-velocity items, and any period where a promotion and an external event overlap in the same data window.
• Elasticity numbers only change outcomes when they feed into a live demand forecast and a replenishment decision, not when they sit in a pricing spreadsheet detached from inventory planning.

What does price elasticity of demand actually measure?

Price elasticity of demand quantifies how sensitive a product's sales volume is to a change in its price. A product with high elasticity loses a lot of volume when price rises even slightly. A product with low elasticity barely moves.

The number itself is almost always negative, since price and demand typically move in opposite directions: raise the price and volume drops, cut the price and volume rises. Most retailers talk about the absolute value of that number instead of the sign, because the sign rarely changes and the magnitude is what drives the pricing decision.

A basic grocery staple like milk or bread tends to sit close to inelastic. Shoppers buy roughly the same amount whether the price moves a little in either direction, because there's no easy substitute and the purchase isn't optional. A discretionary product with close substitutes, like a mid-range handbag or a specific electronics accessory, tends to be far more elastic. Raise the price 10% and a meaningful share of buyers will simply choose a competing product or brand instead.

See how product x location demand forecasting turns an elasticity estimate into a live pricing and replenishment decision.

How to calculate price elasticity (formula and a worked example)

The standard formula is:

Price elasticity of demand = (% change in quantity demanded) / (% change in price)

Marisol, a buyer at a mid-market home décor retailer, tested this on a slow-moving ceramic vase line. The vase was priced at $40 and selling 100 units a week across the chain. She dropped the price to $34, a 15% cut, and watched weekly volume climb to 128 units, a 28% increase.

Elasticity = 28% / -15% = -1.87

The absolute value, 1.87, is well above 1, which puts this product firmly in elastic territory. A modest price cut generated a disproportionately larger volume gain, which likely made the markdown worth doing on a margin basis, assuming the unit economics still worked at the lower price. Marisol used that number to decide the next markdown depth for a related product line instead of guessing at another arbitrary discount.

Elastic vs. inelastic demand: what the number tells you

Once you have an elasticity value, the interpretation follows a simple threshold:

The practical use of this table is deciding markdown depth. An inelastic product doesn't need a 40% markdown to clear; a 15% cut likely won't move enough extra volume to justify the margin given up. An elastic product might clear at a much shallower discount than a planner's default markdown ladder assumes, which is where a lot of unnecessary margin gets left on the table across a season.

How retailers build a price elasticity model

Data requirements

A usable elasticity model needs price and unit-sales history at the product and location level, ideally spanning enough time to capture multiple price points for the same item. Twelve to twenty-four months of point-of-sale data is a reasonable minimum for a stable estimate. Beyond price and units, useful inputs include promotional flags (was this a markdown week or a regular-price week), competitor pricing where available, inventory position (a stockout during a high-demand week will distort the apparent elasticity), and seasonality markers. The same discipline applies to combining internal sales history with external demand signals for forecasting more broadly: an elasticity model built on internal data alone misses shifts in the competitive landscape that show up in the numbers only after the fact.

Common modeling methods

Linear regression treats quantity demanded as a linear function of price. It's simple to run and easy to explain to a merchandising team, but it assumes elasticity is constant across the whole price range, which rarely holds in practice.

Log-log regression is the more common approach in retail pricing teams, because taking the log of both price and quantity means the resulting price coefficient can be read directly as the elasticity value. It also handles the reality that demand response to price usually isn't a straight line.

Machine learning approaches (gradient boosting, tree-based models) can capture non-linear effects and interactions between price, seasonality, and promotions that a simple regression misses. These generally need at least two to three years of transaction history per product to outperform a well-specified regression, so they work best for established, high-volume lines rather than new introductions.

Marcus, a pricing analyst at a multi-brand electronics retailer, ran log-log regressions on his top 200 products by revenue and found that half of them clustered tightly around inelastic (-0.6 to -0.9), while a handful of accessory categories showed elasticity above -2. He used that split to stop applying a single markdown calendar chain-wide and instead set category-specific discount depths, which is a direct, low-cost outcome of running the model at all.

Cross-price elasticity: substitutes, complements, and cannibalization

Cross-price elasticity measures how a price change on one product affects demand for a different product. The formula mirrors the standard one, but the price change and the demand change apply to two different items:

Cross-price elasticity = (% change in quantity demanded of Product A) / (% change in price of Product B)

A positive cross-price elasticity means the two products are substitutes: cut the price of one and demand for the other falls, because buyers switch. A negative cross-price elasticity means they're complements: cut the price of one and demand for the other rises, because buyers purchase both together.

This matters most when a retailer plans a markdown without checking whether it will cannibalize a related, still-full-price product. Elena, who runs merchandising for a footwear chain, ran a deep markdown on last season's running shoe model expecting a clean clearance. Sell-through on the markdown item hit target, but sales on the current-season model in the same category dropped noticeably during the same window. A cross-price elasticity check beforehand would have flagged the two models as close substitutes and pointed toward a shallower discount or a longer clearance window instead.

Where elasticity models break down

Elasticity models are only as reliable as the data and the assumptions behind them, and there are a few recurring failure points worth knowing before trusting a number blindly.

Thin data on new or low-velocity products. A product with three months of sales history and one price point gives a model almost nothing to estimate from. Elasticity estimates on new introductions or slow-moving tail products should be treated as directional at best, not precise.

Confounded promotions. If a price cut happens during a marketing push, a competitor stockout, or a seasonal demand spike, the model can't cleanly separate how much of the volume lift came from price and how much came from everything else happening at the same time. One mistake we repeatedly see is a team reading a promotional-period sales spike as pure price elasticity when a chunk of it was seasonality or a paid campaign running in parallel.

Structural shifts. An elasticity estimated on last year's data may not hold if a new competitor entered the category, a substitute product launched, or the target customer segment changed. Elasticity is a snapshot of behavior under specific market conditions, not a permanent property of the product.

Category-level averaging. A model built at the category level (all dresses, all headphones) produces a category-level number that can mask wide variation between individual products within that category. Across Metreecs' work with retailers running granular demand models, the products that look "average" at the category level are often the ones losing the most margin to a discount depth that's wrong for that specific item.

Turning elasticity into a pricing and inventory decision

An elasticity number by itself doesn't change anything. It only pays off once it feeds a decision: what price to test next, how deep a markdown should go, or how a demand forecast should be revised when a price change is planned.

That link to the forecast matters more than it first appears. A markdown that performs better than the elasticity model predicted will draw down inventory faster than planned, which raises stockout risk on a product that's supposed to be clearing, not selling out mid-markdown. A markdown that underperforms leaves inventory sitting past the clearance window, tying up capital that could be deployed elsewhere, the same margin drag covered in more detail in the hidden cost of inaccurate sales forecasts. Metreecs' product x location forecasting can incorporate a planned price change directly into the demand signal for each store, so the reorder point and safety stock calculation adjust automatically instead of requiring a manual recheck after the fact.

Retailers without that connection tend to treat pricing and inventory as two separate systems: a pricing team runs the elasticity model, a planning team manages replenishment, and the price change shows up in the sales data days later as an unexplained forecast miss. Closing that loop, so a price change updates the demand forecast the same day a price goes live, keeps inventory optimization and pricing decisions working from the same number instead of two disconnected spreadsheets.

FAQ

What is a good price elasticity for a retail product?
There's no universal target, since elasticity varies by category, price point, and how many substitutes exist. The useful benchmark is relative, not absolute: knowing that Product A is more elastic than Product B in your own catalog tells you which one to discount first and which one can hold its price.

How much sales history do you need to model price elasticity?
Twelve to twenty-four months of point-of-sale data at multiple price points is a reasonable floor for a regression-based estimate. Machine learning approaches generally need two to three years of history to outperform a simpler regression model.

Can you calculate price elasticity without a statistical model?
Yes, for a single price test: divide the percentage change in units sold by the percentage change in price, as shown in the worked example above. This gives a rough point estimate from one price change, but a full model across many price points and products produces a more reliable, generalizable number.

Does price elasticity change over time?
Yes. Elasticity reflects buyer behavior under current market conditions, including competitor pricing and available substitutes. A model built on data from two years ago can be stale if the competitive set or the customer base has shifted since.

What's the difference between price elasticity and cross-price elasticity?
Price elasticity measures how a product's own price affects its own demand. Cross-price elasticity measures how one product's price affects a different product's demand, which is the number that flags cannibalization risk between substitutes or lift between complements.

Conclusion

Price elasticity modeling turns a guess about markdown depth into a number a planner can defend. The formula itself is simple: percentage change in demand over percentage change in price. The harder part is building a model on clean enough data, watching for the failure points (thin history, confounded promotions, category-level averaging), and connecting the output to the demand forecast and inventory position instead of leaving it in a pricing spreadsheet. Retailers that make that connection catch cannibalization risk before a markdown goes live and adjust safety stock automatically when a price change shifts the demand curve.

Book a demo to see how product x location forecasting factors planned price changes into the demand signal for every store.