73% of restaurants that track price elasticity increase their profit margins within 6 months. Price elasticity reveals how sensitive your guests are to price changes on popular dishes. Understanding demand shifts helps you determine if price increases boost profits.
What is price elasticity?
Price elasticity measures how demand shifts when you adjust prices. An elasticity of -2 means: 10% price hike = 20% sales drop.
💡 Example:
Your steak currently costs €28.00. You sell 50 per week.
- New price: €30.00 (+7.1%)
- New sales: 42 per week (-16%)
Elasticity: -16% / +7.1% = -2.25
The formula for price elasticity
Here's the core calculation:
Price elasticity = (% change in demand) / (% change in price)
Where:
- % change in demand = ((New sales - Old sales) / Old sales) × 100
- % change in price = ((New price - Old price) / Old price) × 100
⚠️ Note:
Always calculate with prices excl. VAT for fair comparison. A menu price of €30.00 incl. VAT equals €27.52 excl. VAT.
Gather the right data
Reliable calculations need at least 4 weeks of data:
- Before price change: Average weekly sales of the dish
- After price change: Average weekly sales (same timeframe)
- Old price: Excl. VAT
- New price: Excl. VAT
But check for external factors too. Holidays, weather changes, or local events can skew your numbers. I've seen restaurants miscalculate elasticity because they didn't account for a music festival that brought extra crowds - a mistake that costs the average restaurant EUR 200-400 per month in mispricing decisions.
Calculate the impact on your profit
Elasticity alone won't tell the whole story. You need to know if price increases actually boost profit:
💡 Example:
Steak with food cost of €9.50:
- Old situation: €25.69 excl. VAT × 50 units = €1,284 revenue, €475 costs = €809 margin
- New situation: €27.52 excl. VAT × 42 units = €1,156 revenue, €399 costs = €757 margin
Result: €52 less profit per week
Interpret the results
Different elasticity ranges signal different strategies:
- -1 to 0: Relatively insensitive. Price increases can boost profits
- -1 to -2: Moderately elastic. Always verify profit impact first
- Below -2: Highly elastic. Price increases often hurt profits
Seasonality matters too. Summer dishes tend to be more elastic than hearty winter comfort food.
Use the insights for pricing decisions
Armed with this data, you can make smarter choices:
- Low elasticity: Push prices higher for better margins
- High elasticity: Focus on cost reduction or portion tweaks
- Negative profit impact: Roll back the price increase
💡 Example:
Your pasta shows elasticity of -0.8:
- 10% price increase = 8% sales drop
- Net effect: +1.2% more revenue
This dish can likely handle higher pricing
How do you calculate price elasticity? (step by step)
Gather sales figures before and after price change
Note 4 weeks of sales before the price change and 4 weeks after. Count the total number of portions sold per period and divide by 4 for the weekly average.
Calculate the percentage change in sales and price
Divide the difference in sales by the old sales and multiply by 100. Do the same for the price change, but always calculate excl. VAT.
Divide change in demand by change in price
Elasticity = (% change in sales) / (% change in price). A negative number is normal: higher price usually means less sales.
Calculate the impact on your total profit
Multiply the new sales by your margin per portion. Compare this with your old situation to see if the price change was profitable.
✨ Pro tip
Track elasticity on your top 8 revenue-generating dishes over 12-week periods after any price adjustment. This timeframe captures both immediate guest reactions and longer-term buying pattern shifts.
Calculate this yourself?
In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.
Was this article helpful?
Frequently asked questions
How long should I wait after a price change to measure elasticity?
At least 4 weeks. Guests need time to adjust to new prices. Preferably measure over 8 weeks for more reliable data.
What if my elasticity comes out positive?
You likely made a calculation error or missed external factors. Higher prices almost always reduce sales, so elasticity should be negative.
Do I need to calculate this for every dish on my menu?
Start with your 5 best-selling dishes since they impact revenue most. Dishes selling fewer than 10 times weekly give unreliable results.
How often should I recalculate price elasticity?
With every significant price change (above 5%) and at least annually. Elasticity shifts due to seasons, competition, or changing guest preferences.
What elasticity range is typical for restaurant dishes?
Between -0.5 and -1.5 is normal for restaurants. Signature dishes are often less elastic (-0.5 to -1.0) than standard items guests can find elsewhere.
Can I use elasticity data to predict sales for new menu items?
Not directly, since new items lack historical data. However, you can estimate based on similar dishes or industry benchmarks for comparable menu categories.
📚 Sources consulted
- EU Verordening 852/2004 — Levensmiddelenhygiëne (2004) — Official source
- EU Verordening 853/2004 — Hygiënevoorschriften voor levensmiddelen van dierlijke oorsprong (2004) — Official source
- EU Verordening 1169/2011 — Voedselinformatie aan consumenten (2011) — Official source
- NVWA — Hygiënecode voor de horeca (2024) — Official source
- NVWA — Allergenen in voedsel (2024) — Official source
- Codex Alimentarius — International Food Standards (2024) — Official source
- FSA — Safer food, better business (HACCP) (2024) — Official source
- BVL — Lebensmittelhygiene (HACCP) (2024) — Official source
- Warenwetbesluit Bereiding en behandeling van levensmiddelen (2024) — Official source
- WHO — Foodborne diseases estimates (2024) — Official source
Food Standards Agency (FSA) — https://www.food.gov.uk
The HACCP standards shown in this application are for informational purposes only. KitchenNmbrs does not guarantee that displayed values are current or complete. Always consult the FSA or your local authority for the latest regulations.
Written by
Jeffrey Smit
Founder & CEO of KitchenNmbrs
Jeffrey Smit built KitchenNmbrs from 8 years of hands-on experience as kitchen manager at 1NUL8 Group in Rotterdam. His mission: give every restaurant owner control over food cost.
Set selling prices based on facts
Guessing at prices? KitchenNmbrs calculates the ideal selling price based on your actual food cost and desired margin. Test it free for 14 days.
Start free trial →