What Is Price Elasticity, Really?

Price elasticity of demand measures how much your customers' buying behavior changes when you adjust a price. An elasticity of -1.0 means a 10% price increase leads to roughly a 10% drop in units sold. An elasticity of -0.5 means that same 10% increase only costs you about 5% in volume—which means your revenue actually goes up.

For SMEs managing hundreds or thousands of SKUs, the problem isn't understanding the concept. It's measuring it reliably across a catalog where every product behaves differently. A fastener that your customers can source from five competitors will behave very differently from a proprietary component they can only get from you.

Why Most SMEs Don't Measure It

The traditional approach to elasticity analysis requires a trained econometrician, clean historical data, and statistical software like R or Stata. Most mid-market companies don't have this expertise in-house, and hiring a consulting firm typically costs €50-150K for a single engagement that takes 3-6 months.

The result? Pricing teams fall back on three default strategies: cost-plus (add a margin to your input costs), competitor-matching (charge what the market charges), or gut feel (the sales director thinks we should hold prices). None of these account for how your specific customers respond to your specific products at different price points.

A Practical Framework for Getting Started

You don't need to boil the ocean. Start with your top 50-100 SKUs by revenue contribution—these typically represent 60-80% of your total revenue. For each product, you need at least 12-18 months of transaction history with enough price variation (natural or intentional) to build a demand curve.

The key data points are straightforward: transaction date, SKU identifier, quantity sold, and unit price. If you have customer segment data (industry, size, region), that's a bonus—it lets you calculate segment-level elasticity, which is even more actionable.

Once you have clean data, the analysis follows a standard regression approach: model quantity as a function of price, controlling for seasonality, promotions, and other confounding factors. The coefficient on price is your elasticity estimate.

Turning Numbers Into Decisions

An elasticity score is only useful if it changes behavior. Here's a simple decision framework:

Inelastic products (elasticity between 0 and -0.8): These are your pricing power products. Customers aren't very sensitive to price changes, often because you have a differentiated offering or switching costs are high. These are candidates for price increases of 3-8%, depending on competitive dynamics.

Unit-elastic products (elasticity around -1.0): Price changes here roughly cancel out in revenue terms. Focus on margin optimization—can you reduce costs or bundle these with higher-margin products?

Elastic products (elasticity below -1.5): Be cautious with price increases here. These are often commoditized products where customers will switch quickly. Consider whether these products serve as traffic drivers or relationship anchors that justify lower margins.

Common Pitfalls to Avoid

The biggest mistake is treating elasticity as a fixed number. Elasticity changes over time as market conditions shift, competitors enter or exit, and customer preferences evolve. Plan to refresh your analysis at least quarterly.

Another common error is ignoring cross-elasticity—how changing the price of Product A affects demand for Product B. If you raise the price of a popular item, customers might substitute a similar product in your catalog rather than leaving entirely. This is especially important for retailers and wholesalers with overlapping product lines.

Finally, don't confuse correlation with causation. A price drop during a seasonal peak might look like elastic demand, but the volume increase was driven by seasonality, not your pricing. Proper econometric modeling controls for these factors, which is why simple spreadsheet analysis often produces misleading results.