What-If Scenarios: Testing a Price Change Before You Commit

Quick answer: What-if scenario modelling lets a restaurant test a price increase, a new promotion, or a staffing change on paper first, so it can see the likely impact before risking real money.

The simulation uses the restaurant's own data - not generic benchmarks - to project the likely outcome, so the decision has a basis beyond gut feel.

Every pricing or staffing decision a restaurant makes is a bet. Raise the price of the combo meal by AED 3 and you might earn more per order - or you might lose volume and end up earning less overall. Run a buy-one-get-one on the slow Tuesday slot and you might fill the room - or you might just subsidize orders that would have come in anyway. These are real money decisions made, most of the time, on intuition.

What is a what-if scenario model?

A what-if model estimates the impact of a specific business decision before you make it. You define the change (a price adjustment on an item or category, a new promotion, a staffing change) and the model projects the likely outcome from your own sales history, recipe costs and expected volume. A spreadsheet is enough to start.

The output is not a guarantee; it is a projection with a stated basis. It tells you, for example, how much volume a 10% price increase on your top-selling item can lose before the change stops paying for itself, and whether the net revenue effect is likely to be positive or negative. That projection gives the decision a foundation that gut feel alone cannot provide.

What kinds of decisions can a what-if model test?

The three most common use cases are price changes, promotions, and operational changes.

Price changes:

• Raising or lowering the price of a specific item or category
• Adjusting the service charge or a delivery surcharge
• Modelling the effect of a VAT-inclusive vs VAT-exclusive price display

Promotions:

• A discount on a specific item or category for a defined period
• A buy-one-get-one or combo bundle at a fixed price
• A loyalty multiplier for a weekend push

Operational changes:

• Reducing staffing hours during a consistently slow period
• Adding a session (extending opening hours) to capture an unserved evening slot
• Closing a delivery channel on certain days if the margin is negative

Each scenario produces a projected revenue and margin outcome - so the owner can compare "do nothing," "change A," and "change B" side by side before deciding.

How does the simulation use actual restaurant data?

A what-if model is only as good as the data behind it, so build it from your own restaurant's numbers, not industry averages. Past price changes on similar items show how sensitive your customers are. Recent sales by day give the baseline volume. The cost structure (from recipes and recent supplier invoices) determines how margin moves with volume.

This makes the projection materially more useful than a rule of thumb. "If you raise the price of a mid-range item by 10%, expect a 5% volume drop" might be a reasonable industry average. But if your specific restaurant's customers have historically shown low price sensitivity on that category - because your regulars order it regardless - the actual impact on your business will be different.

When should you run a what-if on a price?

When a dish's margin has eroded because an ingredient cost rose, the logical next question is: should I raise the price? A what-if model is where that question gets answered.

Put in the proposed new price and an estimate of the volume you might lose, based on how customers reacted to past price changes. The margin calculation shows whether the price increase recovers more than it loses to volume reduction. If the projection looks favorable, the owner makes the change with data behind it. If it does not, the owner explores other options: renegotiating with the supplier, adjusting the recipe, or accepting the lower margin for a defined period.

Does software choose the price for you?

No, and it should not. Software can show the inputs: recipe cost, current price, margin and sales by item. The judgement about how your regulars will react stays with the owner. A what-if model makes that judgement explicit, so you can compare it with what actually happens after the change.

What does "test on paper first" actually mean in practice?

It means no customers experience the change, no revenue is affected, and no negative outcomes happen before the owner has seen the likely result. The model lives in a spreadsheet or planning file and produces a projection. If the projection looks good, the owner implements the change. If it does not, the owner adjusts the inputs and tries a different version, or decides not to make the change at all.

The alternative - making the change and observing the real-world outcome - is also valid, but it comes with a cost. A price increase that drives away 20% of volume is a real loss during the time it takes to recognize the problem and reverse it. A staffing reduction that creates service pressure during peak hours is real damage to the customer experience before it gets corrected. Testing on paper first reduces the exposure.

---

Read next: How AI is changing restaurant management in the UAE (pillar) · How AI spots margin erosion before month-end · How to set and track sales targets for your restaurant