Skip to main content

Saving & Pushing

Step 4 is where you save your scenario. You can then push it live from the scenario list to apply the changes to your recipes and POS system.

Naming your scenario​

Give your scenario a clear, descriptive name so you can find it later. The name field is required before you can save.

FieldRequiredExample
Scenario NameYes"Spring Menu Price Review"
DescriptionNo"5% increase across hot drinks to offset dairy supplier rise"
Use descriptive names

A name like "Spring Menu Price Review" is much easier to find later than "Test 1". Include the date or season if you run scenarios regularly.

Change summary​

Before saving, the page shows a summary of everything in the scenario:

  • Headline impact - the same annual profit impact figure from the simulation results.
  • Price changes - a list of recipes with their current and new selling prices (up to 10 shown, with a "+N more" note if there are more).
  • Recipe changes - any ingredient swaps, batch portion changes, recipe cost overrides, or VAT rate changes, shown as labelled cards.

Review this summary carefully to confirm the changes are what you expect.

Saving a scenario​

Click Save Scenario to save. The scenario is stored with a Simulated status and appears on the What If? list page. You can:

  • Reopen it later to review the results
  • Edit and re-simulate if circumstances change
  • Push it live when you are ready

Saving does not make any changes to your live recipe data or POS system.

Pushing changes live​

From the scenario list, click on a saved scenario to open the detail modal. Click Push Changes to reveal a confirmation panel with an important warning:

This will update prices in your POS system and recipe data in Brikly. This action cannot be undone.

If you have a POS integration connected, the push updates both Brikly and your POS. If not, only Brikly recipe data is updated.

Before you push​

The confirmation panel includes a checklist of things to consider:

  • Have you updated your printed menus?
  • Have you briefed your team on the new prices?
  • Are you ready to apply these changes now?

These are reminders rather than hard requirements - use them as a final sanity check before committing.

What happens when you push​

  1. Selling prices are updated on the affected recipes in Brikly.
  2. Recipe changes (ingredient swaps, batch portion changes) are applied to the recipe data.
  3. If a POS integration is connected, the new prices are pushed to your POS catalogue.
  4. The scenario status changes from Simulated to Pushed.
  5. The scenario becomes read-only - you cannot edit or delete it.
Pushing cannot be undone

Once pushed, the changes are live. If you need to reverse a change, you would need to create a new scenario that applies the opposite adjustment. Make sure you are confident in the numbers before pushing.

Managing scenarios​

Viewing saved scenarios​

Navigate to CostingBrik > What If? to see all your scenarios. Each card shows:

  • Scenario name and creation date
  • Status badge - grey for Simulated, green for Pushed
  • Annual profit impact - the headline figure in green (positive) or red (negative)
  • Recipe count
  • Adjustment type chips - labels showing which types of adjustments were applied (e.g. "Flat Price Change", "Supplier Price Change", "Recipe Adjustment")

Click any card to open the scenario detail modal.

Deleting a scenario​

Click the trash icon on a scenario to delete it. Only scenarios with a Simulated status can be deleted, and only by owners or admins. Pushed scenarios are permanent records and cannot be removed.

Editing an existing scenario​

Open a Simulated scenario, click Edit Scenario, and navigate through the wizard steps to make changes. You can modify the recipe selection, adjust values, and re-run the simulation. Save again when you are done.

Worked example​

Here is a complete workflow from start to finish:

  1. Your dairy supplier announces an 8% price rise starting next month.
  2. Navigate to CostingBrik > What If? and click New Scenario.
  3. Select Supplier Price Change, find your dairy supplier, and set 8% across all ingredients using Apply to all selected.
  4. Continue to Step 2. You see 23 recipes are affected. Add a Percentage Price Change of +3% as an additional adjustment to partially pass the cost on.
  5. Click Simulate Impact. The results show an annual impact of +£1,850 (the price rise more than offsets the ingredient cost increase).
  6. Round prices to the nearest 25p for a clean menu.
  7. Review a few key recipes - adjust the Flat White from the calculated £3.75 to £3.50 since it is your most popular item.
  8. Click Update to recalculate with your edit, then Review & Save.
  9. Name it "Dairy Supplier Price Rise - March 2026", add a description, and click Save Scenario.
  10. Share the results with your team. When everyone agrees, reopen the scenario from the list and click Push Changes.