Simulation Results
Step 3 runs the simulation engine and presents the estimated profit impact across all your affected recipes. This is where you see the numbers and decide whether to proceed, adjust, or go back and try a different approach.
Headline impact
At the top of the page, a prominent card shows the Estimated Annual Profit Impact - a single number summarising the total financial effect of your scenario across all recipes with sales data.
- A green positive number (e.g. +£2,450) means your scenario increases annual profit.
- A red negative number (e.g. -£1,200) means it reduces profit.
The subtitle shows how many recipes contributed to this figure. If some recipes have no sales data, an amber note tells you how many were excluded from the calculation.
The annual impact is calculated from each recipe's weekly sales volume multiplied by the per-unit profit change. Recipes without linked sales data cannot contribute to this figure - they appear in the results table but show a dash instead of an impact value.
Category breakdown
If your scenario spans two or more recipe categories, a set of summary cards appears below the headline. Each card shows:
- The category name
- The annual impact for that category (green or red)
- The number of recipes in that category
This helps you see which parts of your menu are most affected by the change.
Per-recipe results table
The main results table shows every recipe in the scenario. You can sort by any column header:
| Column | What it shows |
|---|---|
| Recipe | Recipe name and category |
| Current | The existing selling price |
| New Price | The proposed new selling price after all adjustments |
| Wk Sales | Weekly sales volume (annual volume divided by 52), or a dash if no sales data |
| Margin | The adjusted GP margin as a percentage |
| Annual Impact | The estimated annual profit change for this recipe (green/red), or a dash if no sales data |
The table is sorted by Annual Impact (descending) by default, so the biggest impacts appear first. Click column headers to change the sort.
Editing prices inline
You can click on any value in the New Price column to edit it directly. This lets you fine-tune individual recipe prices - for example, rounding a calculated price of £4.73 to a cleaner £4.75, or holding a specific recipe at its current price.
When you edit a price, an amber banner appears at the top of the table:
Prices have been edited. Update to recalculate margins and impact.
Click the Update button to re-run the simulation with your edited prices. The Review & Save button is disabled until you update, ensuring the numbers you see always reflect the current prices.
Price rounding
Instead of manually editing every price, you can use the Round prices checkbox to automatically round all new prices to a consistent step:
| Step | Example |
|---|---|
| 5p | £4.73 rounds to £4.75 |
| 10p | £4.73 rounds to £4.70 |
| 25p | £4.73 rounds to £4.75 |
Tick the Round prices checkbox, then select your preferred rounding step. Rounding is applied to the displayed new prices and carried through when you push the scenario live.
Many cafes and bakeries prefer prices ending in .00, .25, .50, or .75 for simplicity at the till. The 25p step works well for this. Restaurants may prefer 10p rounding for a cleaner look on menus.
Recipes without sales data
Recipes that have no linked sales data are listed separately at the bottom of the results. These recipes still receive the price and cost adjustments if you push the scenario live - they just cannot contribute to the annual impact calculation because Brikly does not know their sales volume.
What to do with the results
After reviewing the numbers, you have several options:
- Satisfied with the impact? Click Review & Save to proceed to Step 4 where you can name, save, and push the scenario live.
- Want to adjust? Click Back to return to Step 2 and add, remove, or modify adjustments. Then re-simulate.
- Need to start over? Use the Back button to return all the way to Step 1 and change the trigger type or recipe selection.
The simulation runs fresh each time you arrive at Step 3, so any changes you make in earlier steps are always reflected.