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.00) means your scenario increases annual profit.
- A red negative number (e.g. -£1,200.00) means it reduces profit.
The line underneath says how many recipes contributed to this figure, for example "per year across 18 recipes with sales data". If some recipes have no sales data, an amber line says how many were left out ("3 recipes not in this total (no sales data)"), 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. Recipes What If? could not cost get their own amber line, for example "1 recipe not in this total (could not be costed)" (see Recipes What If? could not cost).
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." 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 (see Recipes without sales data).
Beside it, Average gross margin shows your margin before and after the change, and the points gained or lost (for example 64.2% → 65.8%, then +1.6pp gained). It is weighted by takings: each recipe with sales data counts by its selling price times its sales, so your best sellers count most. Margins need no sales data, so with none to weight by it shows a simple average across the recipes instead, with "A simple average, as no recipe has sales data to weight it by."
Under both figures the card says "What If? costs recipes the way the recipe page does: ingredients and dine-in packaging. Labour is held constant." Base recipes are costed too, as on the recipe page, and packaging used only for takeaway is left out, so the costs and margins match each recipe's main (dine-in) figures. Labour is not part of any scenario (see Labour in what-if scenarios).
When the scenario changes prices, the card also has one break-even line for the whole scenario, for example "Across the 12 recipes with new prices and sales data, if each lost the same share of its sales, you could lose 1 sale in 25 and still make the same profit." (see The whole scenario).
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 the recipes What If? could cost that have sales data span two or more recipe categories, a set of summary cards appears below the headline, the biggest impact first. Recipes that could not be costed don't count towards these cards. Each card shows:
- The category name
- The annual impact for that category (green or red)
- The number of recipes in that category with sales data
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:
| 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, for example 45/wk), from till sales or the recipe's weekly estimate |
| Margin | The adjusted GP margin as a percentage |
| Break-even | How many sales the new price could lose, or would need to gain, to make the same profit as now (see Break-even). Shown only when the scenario changes a price |
| Annual impact | The estimated annual profit change for this recipe (green/red) |
The margin shows as a tinted pill coloured by the recipe category's Target margin and Warning margin, as on the recipe list: green at or above the target, amber from the warning margin, red below it. A saved scenario follows the categories' targets as they are today. A recipe with no category, a category with no figures of its own, or a category renamed or archived since the scenario was run, uses 70% and 50%. A recipe selling below cost reads negative, for example -12.5%, in red. Like every margin in Brikly, it is worked out on the price without VAT.
When no recipe in the scenario has sales data, the table is not shown.
The table is sorted by Annual impact (biggest first) by default. Click Recipe, Wk sales, Margin or Annual impact to sort by that column, and click it again to reverse the order.
On a phone, the table keeps Recipe, New price and Margin as columns, so it fits the screen. Each recipe's current price, weekly sales and annual impact sit under its name instead, for example "Now £4.25 · sells 170 a week" and "+£736.08 a year" (green, or red for a loss), with its break-even words below them. A Sort by list above the table sorts it the same ways, in words: Biggest impact first, Smallest impact first, Most sold first, Least sold first, Highest margin first, Lowest margin first, Recipe A to Z and Recipe Z to A.
Break-even
A price rise makes more profit on each sale, but it might put a few customers off. The Break-even column tells you how many of them you could lose before the rise stops paying for itself. A price cut works the other way round: it tells you how many extra sales you would need to make up for it.
For example, "Could lose 1 sale in 38" means that if you sold 37 where you sell 38 today, you would still make the same profit as before.
It compares the profit on one sale before and after everything the scenario changes for that recipe: the new price (after any rounding or prices you typed in), any VAT change and any change to the cost. So a price rise that sits beside a bigger cost rise can still need more sales, and a price cut beside a bigger cost fall can still afford to lose some. Like margins, it is worked out on the price without VAT.
Break-even assumes a lost sale is lost entirely, so the customer buys nothing else instead. It never predicts what your customers will do: it tells you how much room the new price gives you, and you judge whether you would lose that many. The page says so too: "Break-even assumes a lost sale is lost entirely." When the scenario has a break-even line for the whole scenario (see The whole scenario), it sits under the headline card. Otherwise it sits under the table.
Worked example
A latte is £4.20 on the till and costs 45p to make. With VAT at 20%, the price without VAT is £3.50, so each latte makes £3.05.
You try a 10p rise to £4.30. Without VAT that is £3.58 (£3.583 to be exact), so each latte now makes £3.13. That is 8p more on every sale, which is about 2.7% of the new profit per latte. Losing 1 sale in 37.6 would cancel it out, so the column reads "Could lose 1 sale in 38".
If you cut the price to £4.00 instead, the price without VAT is £3.33 and each latte makes £2.88, 17p less than now. The column reads "Needs 1 more sale for every 17".
What it can say
| You see | What it means |
|---|---|
| "Could lose 1 sale in 38" | Each sale makes more than before. You could sell this many fewer and still make the same profit. A very small change reads "Could lose fewer than 1 sale in 1,000" |
| "Could lose over half its sales" | Each sale now makes more than twice as much as before |
| "Needs 1 more sale for every 17" | Each sale makes less than before, so you would need this many more sales to make the same profit |
| "Needs 60% more sales" | Each sale makes much less than before, so you would need over half as many sales again. Shown as a percentage from 50% up to 1,000% |
| "Needs more than ten times its sales" | Each sale makes so much less that you would need more than 1,000% more sales to make the same profit |
| "Loses money on each sale at the new price" | The new price, after VAT, is below the cost, so selling more would not help. Shown in amber |
| "Makes no profit on each sale at the new price" | The new price, after VAT, only just covers the cost. Shown in amber |
| "Now makes money on every sale" | The recipe made a loss or no profit before, and the new price puts it into profit |
| "Same profit per sale" | The scenario changes the price, but the profit on each sale stays the same, for example because the cost rises by as much |
A recipe whose price the scenario does not change shows a dash. On a phone, the break-even words sit under the recipe name instead of in a column of their own, so you can see them without scrolling the table sideways.
The figure is always rounded the cautious way: the sales you could lose are never more than the true figure, and the extra sales you would need are never fewer. In the latte example, 37.6 becomes 38, not 37, because losing 1 sale in 37 would leave you slightly worse off.
Break-even is about one sale, so it needs no sales data. Recipes without sales data get it too, in the list at the bottom of the results (see Recipes without sales data).
The whole scenario
The headline card adds one line for the whole scenario. It covers only the recipes that have both a new price and sales data, and works them out together as if each lost (or gained) the same share of its sales, so your best sellers count most. With two or more, it opens "Across the 12 recipes with new prices and sales data" (for example), then says one of:
- "if each lost the same share of its sales, you could lose 1 sale in 25 and still make the same profit" (or "over half of their sales", or "fewer than 1 sale in 1,000")
- "you would need 1 more sale for every 17, spread the same way, to make the same profit" (or "60% more sales", for example). Past 1,000% it reads "you would need more than ten times their sales, spread the same way, to make the same profit"
- "these recipes together move from a loss to a profit at current sales"
- "these recipes together lose money at current sales" (in amber)
- "these recipes together make no profit at current sales" (in amber)
- "total profit from these recipes stays the same"
With one such recipe, the line opens "For the one recipe with a new price and sales data" instead, for example "For the one recipe with a new price and sales data, you could lose 1 sale in 38 and still make the same profit." There is no line when the scenario changes no prices (a cost-only scenario, for example), or when none of the recipes with new prices has sales data.
Scenarios saved before break-even
A scenario saved before break-even was added has no break-even figures. When you edit it, the Results step shows "Saved before break-even was added. Select Run again to see it." with a Run again button, which runs the saved scenario again as it stands and adds them. Pushed scenarios cannot be edited, so they never show this note.
Editing prices inline
When the scenario has one price adjustment, each value in the New price column is a box you can type in. 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 two or more price adjustments are stacked, the new prices cannot be typed over, and the table says "Several price changes are stacked here. Edit them on the previous step." (see Flat price change).
When you edit a price, the box turns amber and an amber banner appears under the headline:
Prices have been edited. Update to recalculate margins and impact.
Click the Update button to re-run the simulation with your edited prices. A new price must be more than zero: a blank, zero or negative price reads "Enter a price above 0." under its box and keeps what you typed, and Update stays greyed out until you put it right. A recipe with no selling price shows its new price without a box, with "No selling price to change." To price a recipe that has none, set its selling price on the recipe first, then run the scenario again. 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 the nearest step:
| Step | Example |
|---|---|
| £0.05 | £4.73 rounds to £4.75 |
| £0.10 | £4.73 rounds to £4.70 |
| £0.25 | £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, and the rounding is saved with the scenario.
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.
Take the new prices to your till
When the scenario changes any prices, a list headed New prices for your till sits below the results table, with the number of recipes in brackets, for example "New prices for your till (14)". It lists every recipe whose price the scenario changes, including recipes with no sales data (marked "(no sales data)"), so you can change them on your till without copying them out by hand.
A recipe with no selling price yet is left out of the list, and of Copy list and Print, as there is no price on it to change on the till. A line under the list says how many, for example "1 recipe with no selling price yet is not in this list. Set the price on the recipe first." or "3 recipes with no selling price yet are not in this list. Set the price on the recipe first." Set the recipe's selling price, then run the scenario again to bring it in. If every recipe the scenario changes has no selling price yet, the list is not shown.
| Column | What it shows |
|---|---|
| Item | The recipe name |
| Price now | The recipe's selling price in Brikly. In a saved scenario it reads Price when saved (see below) |
| New price | The price the scenario gives it, after any rounding or prices you typed in |
| Break-even | The recipe's break-even, as in the results table (see Break-even). Shown on screen only, when the scenario has break-even figures. On a phone it sits under the item's name instead of in a column of its own |
The first 10 recipes are shown. With more than that, click Show all 14 (for example) to see the rest, and Show fewer to fold them away again.
Price now is the price on the recipe in Brikly, not a price read from your till. The list says so: "These are the prices in Brikly. If your till shows something different, check it first." If the two differ, check which is right before you change anything.
When you open a saved scenario, its list shows the prices as they were when it was saved, which may have changed since, so the column reads Price when saved. It reads Price now again as soon as the scenario is worked out afresh, for example after you click Update, change the rounding, or go back and simulate again. Copy list and Print use the same words as the screen.
Above the list, two buttons take it to your till:
- Copy list copies the item, price now and new price for each recipe, with a header row, ready to paste as a table into a spreadsheet or into your notes. Break-even is not copied. Brikly confirms with "Price list copied". If your browser does not allow it, you see "We couldn't copy the list. Select it and copy instead."
- Print opens a print page holding only the list: the scenario's name (or "New prices for your till" for a new scenario not yet named), today's date, the lines "Brikly never changes your till. Change these prices on your till." and "These are the prices in Brikly. If your till shows something different, check it first.", then the item, price now and new price for each recipe. If it does not open, your browser has blocked the pop-up, and Brikly says "We couldn't open the print page. Allow pop-ups for Brikly, or copy the list instead."
While you have typed a new price that is waiting for Update (see Editing prices inline), or while the simulation is running again, both buttons are greyed out, so you never copy or print prices that are out of date.
Brikly never changes your till from here. The list says "Brikly never changes your till. Change these prices on your till." If your till sends sales to Brikly, it adds "Your next sync picks them up." A till that is connected but does not send sales does not get that line.
The same list appears when you open a saved scenario (see Viewing saved scenarios).
Recipes What If? could not cost
A recipe What If? cannot cost is listed on its own, below the table, under "2 recipes could not be costed, so they are left out of every figure:" (for example), then each recipe's name (it opens in a new tab) and what is missing. For example: "Ham sandwich could not be costed: Bread dough is used by weight but has no finished weight. Add a finished weight to Bread dough to include Ham sandwich."
This happens when a base recipe anywhere under the recipe, at any depth, is used by weight or volume but has no finished weight or volume to go on, or is used in a unit Brikly cannot cost (the message then says to use it by portion, weight or volume). It can happen in any kind of scenario, a selling price change included. Such a recipe has no price, cost or margin in the results, and it is never counted as having no sales data. Fix the base recipe (see When a component has no weight to go on), then press Back and Simulate impact to run the scenario again.
Recipes without sales data
Recipes that have no till sales or weekly estimate are listed separately at the bottom of the results, under "3 recipes left out of the impact totals (no sales data):" (for example), each with its margin (before and after, where the scenario moves it), its selling price and cost per portion where the scenario changes them, and its break-even where the price changes (see Break-even). 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.
When a simulation cannot run
Some changes cannot be modelled as they are, for example a swap whose replacement cannot be costed in the unit a recipe uses, or a flat quantity change on an ingredient a recipe uses on two lines in different units (see Scenario triggers). What If? then does not run the simulation. The Results step shows Simulation failed with the reason in a plain sentence, naming the recipe and what to do, and offers only Back, because running the same change again cannot work. Go back, change the adjustment or leave that recipe out, and simulate again.
If the simulation fails for another reason, such as a lost connection or a problem on Brikly's side, Simulation failed shows what went wrong (for a problem on Brikly's side, "We couldn't run the simulation. Check your connection and try again.") and Retry is offered as well as Back.
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 and save the scenario.
- Want to adjust? Click Back to return to Step 2 and add, remove, or modify adjustments. Then click Simulate impact again.
- 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 come to Step 3 from Step 2, so any changes you make in earlier steps are always reflected. Going back from Step 4 to Step 3 keeps the results you had.