Weekly Sales
CostingBrik tracks roughly how many of each recipe you sell per week. Your margins do not need it: they come from the selling price on each recipe and the ingredient costs from your supplier invoices. What this figure adds is the yearly view - what a price change or a what-if scenario is worth over a year, and your weighted margin analysis - because a menu full of high-margin dishes only delivers those margins if the high-margin dishes are the ones actually selling.
The figure comes from one of two places:
- POS data - pulled automatically from your connected till, as a rolling average.
- A manual estimate - a number you enter yourself, used when no POS sales exist.
POS data always wins. Your manual estimate is the fallback for recipes (or whole sites) without till data.
Manual entry
If you have not connected a POS, or a particular recipe has no till sales yet, you can enter an estimate by hand:
- Open the recipe (Recipes then click the recipe name).
- Find the Avg. Weekly Sales card in the Recipe Information panel.
- Click the figure (or Set estimate) and type how many you sell in a typical week.
- Press Enter or click away to save.
Owners, admins and members can set an estimate. Viewers see the figure, or a dash, but cannot change it.
There is no need to be exact. A sensible guess - "we sell about 40 flat whites a week" - is enough to make your weighted margins meaningful. You can refine it over time as you learn your sales patterns.
Estimates are per recipe, so set them on your bestsellers first. Those are the dishes that move your weighted GP% the most.
POS data
When your POS (for example, Square) is connected and a recipe is linked to its till item, Brikly replaces the manual estimate with a rolling average of actual sales.
- The average covers the last 12 months of complete weeks (up to 52 weeks). The current part-week is excluded so the figure is not skewed by a half-finished week.
- The recipe detail card labels it, for example, "42 units/week - 52-week avg from Square" so you can see it is real data, not an estimate.
- Newer connections show a limited-data note until enough history builds up - the average becomes more reliable as more complete weeks are recorded.
You do not need to do anything to enable this beyond connecting your POS and linking each recipe to its till item. Once linked, the figure updates automatically.
On the recipe list
The recipe list has a Weekly Sales column (shown by default; you can hide it from the column toggle). Each row shows the best figure available:
- A POS-derived recipe shows its weekly average, for example 42/wk.
- A recipe with only a manual estimate shows the estimate with a small est. marker, so you can tell estimates from actuals at a glance.
- A recipe with neither shows a dash.
If you filter the list to one location, the Weekly Sales figure rescopes to that site, so you see how each recipe performs there rather than across the whole group.
Where weekly sales are used
Every yearly figure is weekly sales multiplied by the change per unit, added up over the recipes that have a weekly figure. A recipe with neither till sales nor an estimate is left out, and where nothing is left to add up, Brikly says so rather than showing £0.00.
| Where | With weekly sales | With none |
|---|---|---|
| What If? results | Estimated Annual Profit Impact across the recipes with sales data | A dash and "No recipes have sales data yet." Margins still show: an average across the recipes, and each recipe at the bottom with its margin and any new price or cost. Click one to open it in a new tab and set an estimate. See Simulation Results. |
| Price change review | Annual Profit Impact for the affected recipes | An annual spend estimate from your purchases, or No sales data yet, with Set estimate on each recipe row. See Reviewing Line Items. |
| Reports, Overview tab | Annual Price Impact from confirmed price changes | A dash with "needs weekly sales", and No sales data yet on the Price Impact shortcut. As on the Price Impact tab, a price change to an ingredient no recipe uses is not counted as missing: if every change was one of those, the card shows £0.00, which is then the real impact. |
| Reports, Price Impact tab | Net Annual Impact and the increases / decreases split. The Sales Data card counts the price changes that had sales data, for example 3 of 4, and says where those sales came from: till sales, weekly estimates, or both (for example "Till sales for 5 recipes, estimates for 2"). A price change to an ingredient no recipe uses can never have sales data, so the card says how many there were (for example "1 on an ingredient no recipe uses") and turns green once every other change had sales data. | A dash with "needs weekly sales", and Sales Data reading 0 of 4 price changes (for example). If none of the changes affected a recipe, the figures show £0.00, which is then the real impact. |
Reports are built from the figures each price change had when you confirmed its review, so setting an estimate today does not alter price changes you have already reviewed. It counts for the price changes you review after setting it. In What If? it counts as soon as you re-run the simulation.
While some price changes on the Price Impact tab affected a recipe but had no sales data, anyone who can set estimates sees a note under the cards on how to make future price changes count. With a till connected (a till waiting to be reconnected still counts), the note also suggests linking recipes to their till items in the Item Mapper, which works the same way: it counts for price changes reviewed after the link.
Multiple locations
For multi-site operators, the headline figure is the combined total across all your sites. Where a recipe sells at more than one location, an info icon next to the figure reveals a per-location breakdown - so you can see that your flat white does 18/week in Camden but 24/week in Soho.
To focus on a single site, either filter the recipe list to that location or, in the AI assistant, ask about a specific location (see Connector example questions).
The per-location breakdown is POS-only. A manual estimate is a single number for the recipe and cannot be split across sites.