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 left out of the calculation, followed by "Set a weekly sales estimate on the recipe page to include them." If your till sends sales to Brikly, it reads "Link them to their till items in the Item Mapper, or set a weekly sales estimate on the recipe page, to include them." instead.
If none of the recipes has sales data, there is nothing to add up, so the card shows a dash rather than +£0.00, with the line "No recipes have sales data yet. Set a weekly sales estimate on a recipe to see its yearly impact." If your till sends sales, the line instead reads "No recipes have sales data yet. Link a recipe to its till item in the Item Mapper, or set a weekly sales estimate on it, to see its yearly impact." Margins need no sales data, so the Average Margin still shows, as a simple average across the recipes rather than weighted by sales. The recipes are still listed at the bottom of the results, each with its margin and its current and new price and cost where the scenario changes them, and every change still applies when you push (see Recipes without sales data).
The annual impact is calculated from each recipe's weekly sales volume multiplied by the per-unit profit change. Weekly sales come from till sales or a weekly estimate on the recipe. Recipes with neither cannot contribute to this figure: they are left out of the results table and listed at the bottom instead (see Recipes without sales data).
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 that has sales data. 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), from till sales or the recipe's weekly estimate |
| Margin | The adjusted GP margin as a percentage |
| Annual Impact | The estimated annual profit change for this recipe (green/red) |
When no recipe in the scenario has sales data, the table is not shown.
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. Only prices the scenario changes are rounded - recipes whose price stays the same are left exactly as they are. The annual impact is recalculated at the rounded prices, the rounding is saved with the scenario, and the rounded prices are what get pushed to Brikly and your POS.
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 till sales or weekly estimate are listed separately at the bottom of the results, each with its margin (before and after, where the scenario moves it), and its selling price and cost per portion where the scenario changes them. These recipes still receive the price and cost adjustments if you push the scenario live, and the save step lists their new prices among the price changes, marked "(no sales data)". They just cannot contribute to the annual impact calculation, because Brikly does not know their sales volume.
To bring one into the total:
- Click its name. The recipe opens in a new tab, so the scenario you are working on stays where it is.
- Set a weekly sales estimate on the Avg. Weekly Sales card (see Weekly Sales).
- Back in the scenario tab, press Back, then Simulate Impact. The simulation runs again with the new estimate.
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.