What Your Price Elasticity Score Actually Means

Most merchants who get an elasticity number do one of two things: act on it immediately without knowing if it's reliable, or ignore it because they're not sure what -1.4 actually means in practice. Neither is right. This guide walks through how to read the number correctly, how to know whether it's solid enough to act on, why your catalog shows wildly different scores across products, and whether elasticity or competitor pricing should be driving your decisions.

What Your Elasticity Score Is Actually Telling You

An elasticity score is a ratio. For every 1% you move your price, it tells you how much your sales volume moves in the opposite direction. The sign is almost always negative — higher price, lower demand — so what matters practically is the absolute value of the number and whether it falls above or below 1.

The revenue direction rule is the single most useful thing to take from an elasticity score:

• If the absolute value is above 1 (elastic): raising your price shrinks total revenue. Customers are responsive enough to price that the volume you lose outpaces the higher margin per unit. Lowering price increases total revenue because the volume gain more than compensates.
• If the absolute value is below 1 (inelastic): raising your price increases total revenue. Customers are not responsive enough to price for the volume loss to cancel out the margin gain. Lowering price decreases total revenue.
• If the absolute value is exactly 1 (unit elastic): a price change in either direction leaves total revenue roughly unchanged.

That rule answers the revenue question. It does not answer the profit question, which also requires knowing your margin — covered in the next section.

A plain-English elasticity reference table

Score range	Label	What a price raise does	What a price cut does	Typical products
0 to -0.5	Highly inelastic	Volume barely moves, revenue and profit both rise	Volume barely moves, revenue falls	Medications, essential consumables, strong brand loyalists
-0.5 to -1.0	Inelastic	Volume drops less than price rises, net revenue increases	Volume rises less than price drops, net revenue falls	Branded goods with moderate differentiation, niche categories
-1.0	Unit elastic	Revenue unchanged in either direction	Revenue unchanged in either direction	Rare in practice, theoretical boundary
-1.0 to -2.0	Elastic	Volume drops more than price rises, revenue falls	Volume rises more than price drops, revenue increases	Competitive categories, moderate substitutes available
Below -2.0	Highly elastic	Even a small price raise causes significant volume loss	Even a small price cut drives large volume gains	Commodity products, marketplace listings with direct competitors

A product at -1.4 sits in the elastic zone. If you raise the price 10%, you would expect roughly 14% less volume. Total revenue falls. The right move, from a revenue standpoint, is to hold or lower — not raise. But whether that's the right move for profit depends on your margin, which is where the full calculation lives.

Before You Act: How to Know If the Number Is Reliable

An unreliable elasticity estimate is worse than no estimate, because it produces false confidence. You might raise a price on a product that looks inelastic but whose estimate is based on three months of data during a seasonal spike — and the actual demand response turns out to be completely different.

Two failure modes make an elasticity number unreliable.

Insufficient data. An elasticity model needs enough observations of the same product at different price points to distinguish a genuine demand response from noise. Enterprise retail research from RELEX Solutions puts the minimum at two years of consistent pricing and sales history before calculations become reliable at that scale. For a smaller ecommerce catalog with less volume, the practical minimum is at least 6 months of sales data that includes genuine price variation — not a product that's been at the same price for every one of those months.

Contaminated data. Promotions, seasonal demand spikes, stockouts, and external demand shocks (a viral mention, a news cycle, a platform algorithm change) all distort the relationship between price and quantity during the period they occur. If your price dropped 20% during a flash sale while you were also running your biggest ad campaign of the year, the sales data from that period doesn't cleanly isolate the price effect. Using it in an elasticity calculation gives you a number that's partly measuring the price sensitivity and partly measuring the ad campaign — and you can't separate the two after the fact.

A well-known accuracy problem in elasticity modeling is applying a catalog-wide average to individual SKU decisions. If your overall store elasticity is -0.8, that average can mask individual products ranging from -0.3 to -1.6 within the same category. Acting on the average as if it applies to each product is one of the fastest ways to move the wrong products in the wrong direction.

This is what Zorin's confidence label is measuring. It's not a marketing feature — it's the model being honest about what the underlying data supports.

• Strong confidence means the model had sufficient sales history, genuine price variation across that history, and a clean enough data period to fit a reliable demand curve. Act on this.
• Moderate confidence means the model had enough data to produce a directionally useful estimate, but some limitation exists — lower volume, a shorter history, or a period with some noise. The direction is likely right; the exact magnitude is less certain.
• Weak confidence means the model doesn't have enough clean data to give a number worth acting on. The SKU either hasn't been at enough different price points, or the history is too short, or too much of the data is contaminated. Hold the price where it is and let more clean data accumulate.

If you see a Weak confidence label on a product, the right response isn't to find a way to override it. It's to wait, or to run a deliberate price test to generate the variation the model needs.

Once You Trust the Number: What to Do With It

Revenue direction is the first filter. Profit impact is the second. A product with an elasticity of -0.7 (inelastic) can absorb a price increase and grow total revenue — but whether that revenue growth translates to profit depends on how large the margin is on each unit and how much volume you lose.

The formal relationship between elasticity and optimal pricing comes from the Lerner pricing rule:

Optimal Price = (Elasticity / (Elasticity + 1)) × Marginal Cost

For a product with an elasticity of -2.0 and a marginal cost (COGS plus fulfillment) of $25:

Optimal Price = (-2 / (-2 + 1)) × $25 = (-2 / -1) × $25 = $50

For a product with an elasticity of -0.7 and the same $25 marginal cost:

Optimal Price = (-0.7 / (-0.7 + 1)) × $25 = (-0.7 / 0.3) × $25 = $58.33

The formula gives you the mathematically profit-maximizing price given the elasticity and cost structure. It's a starting point — your actual price also needs to account for competitor positioning, psychological price points, and minimum margin requirements. But it anchors the decision in demand data rather than intuition.

In practice, Zorin runs this calculation per SKU using your actual margin data and returns a specific raise, lower, or hold recommendation with an estimated profit lift attached. Instead of doing the Lerner calculation manually for each product, the output reads: "raise to $42, estimated 11% profit lift, Strong confidence." That number is the elasticity math plus your cost structure combined into a single actionable direction.

One thing the revenue direction rule doesn't tell you: the right size of the move. An inelastic product can absorb a price increase, but it can't absorb an unlimited one. Every product has a ceiling beyond which even inelastic demand breaks. The profit-lift estimate accounts for this — a recommendation to raise $2 on a $38 product reflects both the elasticity and the estimated point at which further raises stop adding profit and start losing it.

Why Different Products in Your Store Have Such Different Scores

A catalog of 50 products can have elasticities ranging from -0.3 to -2.5. That variation isn't random — it's driven by five factors that determine how sensitive a specific product's buyers are to price.

Availability of substitutes. The more easily a customer can get the same thing from someone else, the more elastic the demand. A commodity phone case on Amazon with 400 identical-looking competitors has highly elastic demand. A handmade leather wallet from a maker with a loyal following has few real substitutes, so demand is more inelastic. This single factor explains most of the variation in a typical catalog.

Degree of brand differentiation. Branded goods with strong identity and recognition hold price better than unbranded equivalents. Apple's iPhone elasticity sits around -0.6 to -0.8 despite being the premium-priced option in its category — brand loyalty insulates demand from price sensitivity. An unbranded equivalent in the same category might run -1.5 to -2.0.

Necessity vs discretionary. Products buyers need — consumables, replacement parts, essential supplies — tend to be inelastic because there is no "not buying" option. Products buyers want but don't need are more elastic because deferring or skipping the purchase is always available.

Price visibility. If a buyer can easily check three competitor prices before hitting your checkout button, your demand is more elastic because the comparison is frictionless. A product category with low price visibility (unusual specifications, niche use case, low search volume) tends to be less elastic because buyers have fewer comparison anchors.

Buyer intent and channel. As covered in the multi-channel pricing guide, the same product can have different elasticity depending on where it's sold. Amazon marketplace buyers arrive in a comparison context and tend to be more price-sensitive than DTC buyers who arrived through a brand-specific channel.

Two similar products, very different elasticity

Consider two moisturizers in the same Shopify store. The first is an unbranded basic formula — fragrance-free, simple ingredient list, no distinguishing story. The second is the store's own-branded hero SKU with 300+ reviews, a proprietary ingredient angle, and the product featured in two press placements.

Both are moisturizers. Both sit in the same category. But the first has elastic demand: buyers can find a dozen near-identical products at similar prices with a quick search, so a $3 price increase sends them elsewhere. The second has inelastic demand: the reviews, the brand story, and the perception of uniqueness mean buyers are willing to pay for this specific product rather than a generic alternative.

If you applied the same price move to both products because they share a category, you would grow revenue on the branded hero and lose it on the unbranded basic. Catalog-level elasticity averaging is precisely the mistake that per-SKU modeling exists to avoid.

Elasticity vs Competitor Pricing: Which Signal Should Drive Your Decision

Competitor pricing and elasticity answer different questions. Using one as a substitute for the other is one of the most common pricing mistakes in ecommerce.

Competitor pricing tells you what the market is charging. It's an externally visible reference point that reflects your competitor's costs, their brand, their audience, and whatever pricing strategy they happen to be running at this moment. It tells you nothing about how your specific customers respond to price.

Elasticity tells you how your customers respond to price. It's derived from your own sales history and reflects your actual buyers' behavior. It's specific to your product, your brand positioning, and your customer base.

The mistake that RELEX Solutions documents in their retailer research is common: merchants assume competitors have done the elasticity math correctly and that matching their price is equivalent to finding the optimal price for their own store. In practice, defaulting to competitor pricing as the primary signal creates pricing that doesn't reflect what your own customers will bear, often leaving margin on the table where you're actually differentiated and losing volume where you're not.

That said, competitor pricing is not irrelevant. It influences your elasticity: if a competitor drops their price significantly, your effective elasticity increases even if you haven't changed anything, because the substitution option for your buyers just got more attractive. Monitoring competitor prices is useful context. It just shouldn't be the decision rule.

The practical synthesis: use competitor pricing to understand the range your market operates in and to flag when a competitor move might have shifted your elasticity. Use your own elasticity data as the decision rule for where within that range to price. On true commodity SKUs on marketplaces where buy-box visibility is determined by price, the balance shifts — those products often need to match or beat the lowest visible competitor price to retain any sales at all. For everything else, particularly on your own DTC store with your own brand, elasticity is the more reliable signal. The price elasticity vs repricing software post covers this tradeoff in more depth if you're deciding between the two approaches.

Frequently Asked Questions

My price elasticity is -1.4 — what does that actually mean for my pricing decisions?

It means your product sits in the elastic zone: for every 1% you raise the price, you can expect roughly 1.4% less volume. Raising price shrinks total revenue; lowering price grows it. Whether lowering price actually improves profit depends on your margin — you need to gain enough additional volume to compensate for the lower margin per unit. An elasticity of -1.4 with a healthy gross margin may still support a price hold or modest raise if the profit math works out, which is why elasticity and margin need to be evaluated together rather than the elasticity number alone.

How do I know if my elasticity estimate is accurate enough to act on?

Check two things: how much data is behind it and how clean that data is. A reliable estimate needs at least 6 months of sales history with genuine price variation across that period. If most of that history was at the same price, the model is extrapolating rather than measuring. If the period included a major promotion, a viral traffic spike, or a stockout, those events distort the price-demand relationship in ways that are hard to separate afterward. Zorin's confidence label (Strong, Moderate, Weak) encodes this assessment directly — a Weak label means the data isn't there yet, and acting on it anyway is riskier than holding the price and waiting.

How do I run a price test on my Shopify store to measure my own elasticity?

The cleanest method is to move the price on a single product, hold it there for at least 4–6 weeks (long enough to smooth out week-to-week noise), and compare sales volume during that period to an equivalent prior period with the original price, controlling for any major seasonal differences. Change only the price during the test — don't run promotions, change ad spend, or modify the product listing at the same time, or the sales change will reflect all those variables, not just the price. A before-and-after test is less precise than a true A/B test (which would require showing different prices to different visitors simultaneously) but is operationally simpler and produces usable data for most SKUs within one to two months.

Why do different products in my store have such different price elasticity scores?

Five factors drive the variation: how many substitutes exist for the product, how strongly differentiated your brand or product is from alternatives, whether the product is a necessity or a discretionary purchase, how easily buyers can compare your price to competitors before buying, and which channel or platform the purchase happens on. Two products in the same category can have opposite elasticity profiles — a branded hero SKU with strong reviews and a loyal customer base often shows inelastic demand, while an unbranded equivalent in the same category can show highly elastic demand because buyers have no reason to prefer it at a higher price.

Should I use price elasticity or just match my competitors' prices?

They answer different questions. Competitor pricing tells you what others are charging — useful context, but based on their costs, their audience, and their strategy, not yours. Elasticity tells you how your customers specifically respond to price changes, which is the more relevant signal for your own store. In practice, use competitor prices as a range reference and to flag when a competitor move might be shifting your effective elasticity. Use your own elasticity data as the actual decision rule within that range. The exception is true commodity SKUs on marketplaces where buy-box position is determined by lowest visible price — there, competitor pricing matters more.

What's a good elasticity score for an ecommerce product?

There is no universally good score — it depends on your category and business model. A highly inelastic score (close to 0) means you have strong pricing power and can raise without significant volume loss, which is valuable. A highly elastic score (below -2.0) means price changes have an outsized volume effect, which makes pricing precision critical in both directions. Most independent ecommerce stores see product elasticities ranging from -0.4 to -1.8 across their catalogs, with the most differentiated and branded SKUs at the inelastic end and the most commodity-like SKUs at the elastic end.

Can elasticity change over time?

Yes, and ignoring this is a common mistake. A product that was highly differentiated (inelastic) when it launched can become elastic as competitors copy it, reviews accumulate on alternatives, and price comparison becomes easier. Seasonal shifts can temporarily move elasticity in either direction. A product that goes viral gets a burst of inelastic demand from people who want it specifically, then reverts to its baseline when the novelty fades. Best practice is to refresh your elasticity read at least every 6–12 months on high-volume SKUs, or any time there's a meaningful change in the competitive landscape.

What if my elasticity estimate is positive?

A positive elasticity is unusual and usually indicates a data problem rather than a genuine demand relationship. Positive elasticity would mean higher prices lead to higher demand, which can occasionally happen with Veblen goods (luxury items where higher price signals status and increases desirability), but is rare in typical ecommerce categories. More commonly, a positive estimate means the data period contained a confounding event — a promotion, a traffic spike, or a competitor stockout — that created an artificial correlation between a price change and a demand increase that had nothing to do with the price. Treat a positive elasticity as a signal to review the underlying data rather than an actionable estimate.

How does margin interact with elasticity when deciding whether to raise a price?

Elasticity tells you the revenue direction. Margin tells you whether the revenue change translates to a profit improvement. A product with an elasticity of -0.8 (inelastic) and a 60% gross margin has a lot of room to absorb a small volume loss from a price increase and still come out ahead on profit. The same elasticity on a product with a 15% gross margin has almost no room — the volume you lose from a price increase quickly erodes the thin margin on remaining sales. The profit margins by category guide covers what typical gross and net margins look like across ecommerce verticals, which gives you a reference for where your own products stand before running the elasticity math.

Knowing the number is step one. Trusting it is step two. Acting on it correctly — with the right price move, sized to your actual margin, on the SKUs where the data actually supports a decision — is what turns an elasticity score into a revenue improvement. Zorin shows the elasticity, the confidence, and the estimated profit lift in one place so none of those three steps require a separate calculation.