Skip to main content

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 money view - what a what-if scenario is worth over a year, the annual price impact on the Overview and Price impact tabs of CostingBrik's Reports page, and the starting sales volume in the Recipe Tuner - because a price change on a dish you sell five of a week is worth far less than the same change on your bestseller.

The figure comes from one of two places:

  • POS data - pulled automatically from your connected till, as an average over the last 52 weeks.
  • 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:

  1. Open the recipe (Recipes then click the recipe name).
  2. Find the Avg. weekly sales card in the Recipe information panel.
  3. Click the figure (or Set estimate) and type how many you sell in a typical week.
  4. 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 the yearly figures meaningful. You can refine it over time as you learn your sales patterns.

tip

Estimates are per recipe, so set them on your bestsellers first. Those are the dishes that move the yearly figures 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 an average of actual sales.

  • The average is what sold in the last 52 complete weeks, divided by 52, or by the weeks your till has been connected if that is fewer. Weeks with no sales count as zero, so a seasonal or slow seller is not flattered. 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 with "52-week avg from Square" beside it, so you can see it is real data, not an estimate.
  • A new item note shows on an item that first sold after your till's first recorded week and has been on sale for fewer than 8 weeks, counting the week it first sold and each complete week since. For example: "New item, only 3 weeks of sales, so this 52-week average reads low for now". Its average counts the weeks before it was on sale as zero, so it starts low and catches up. An item already selling in your till's first recorded week never gets this note, so a newly connected till does not mark its whole menu as new.
  • A limited-data note shows on any other item while your till has fewer than 8 complete weeks recorded (at that site, if you filter to one), until more weeks are recorded. An item never shows both: a new item gets the new item note.
  • A slow seller can average less than one a week. Under 1 the figure shows one decimal, for example 0.4 units/week, and anything below 0.05 shows as under 0.1 (<0.1/wk on the recipe list), never as 0.

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 with the Columns button). 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.

WhereWith weekly salesWith none
What If? resultsEstimated annual profit impact across the recipes with sales dataA 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 reviewAnnual profit impact for the affected recipesAn annual spend estimate from your purchases, or No sales data yet, with Set estimate on each recipe row. See Reviewing line items.
Reports, Overview tabAnnual price impact from confirmed price changesA 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 tabNet 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.
Recipe TunerSales volume starts at the recipe's weekly figure: its till sales once they cover at least two weeks, otherwise your estimate. The profit impact uses it. See Recipe Tuner.Sales volume starts at 100 a month. Type your own figure.
Estimates count from the next review onwards

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/wk at one site but 24/wk at another. A site that sells less than one a week shows the same way as the headline, for example 0.3/wk or <0.1/wk, never 0.

Each site is averaged over the weeks its own till has been connected, so a site that joined recently is not diluted by the weeks before it, and the site figures need not add up exactly to the combined total.

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).

info

The per-location breakdown is POS-only. A manual estimate is a single number for the recipe and cannot be split across sites.