Catch food-cost variance the day it happens, not a month late.

Each café ran its own POS and spreadsheet, and head office stitched them together once a month, by which point the food was already wasted. This is the same group with stock, sales, and food cost reconciled across all five sites in real time.

5% → 2%food-cost variance, caught same-day
Real timelocation P&L, per site and group
3-5 daysto close the books, down from two weeks
Before & after

One system replaces the stack.

Before
POS per siteSales
SpreadsheetsConsolidation
QuickBooksAccounting
Inventory sheetsStock
EmailInter-site transfers
After
Opser
  • Inventory & par levels
  • Sales & location P&L
  • Finance (multi-entity)
  • Purchasing & food cost
  • Reporting
The trigger

The third location was the wall.

Two cafes ran on instinct and a shared spreadsheet. The third broke it. Each site ordered its own way, counts came in on emailed spreadsheets a week late, and a 6% food-cost gap had been running for a month before head office saw it.

Every location had its own POS and its own stock sheet, stitched together once a month in QuickBooks. By the time the group could see a problem, the food had already been wasted and the margin was already gone.

What they did with Opser

One system across every location, doing the work between counts.

Inventory & par levels

Stock tracked per site against par levels, with transfers between locations handled in-system instead of over email.

Sales & location P&L

Each location's sales land in real time next to a live per-site P&L, so there is nothing to export and reconcile.

Finance (multi-entity)

One ledger across the locations, so the books close in 3 to 5 days instead of a two-week monthly stitch.

Purchasing & food cost

Theoretical-vs-actual food cost per site, so recipe drift and supplier price creep show up where they happen.

AI inside the system

The operator reconciles the counts and the invoices, so variance surfaces the day it happens.

Because every site's stock, sales, and invoices live in one system, an operator works them between the monthly closes, under approvals head office sets.

  • Matches each supplier invoice line-by-line to its PO and goods received, and flags price creep or a short delivery the same day
  • Reconciles each site's counts against par levels nightly and surfaces variance before it compounds
  • Flags theoretical-vs-actual food-cost gaps by location, instead of head office finding them at month-end
  • Reshapes a variance check or a new site's par levels in hours when you describe it
What changes

From a monthly stitch to variance caught the day it happens.

  • Food-cost variance modeled from around 5% down toward 2%, because invoices and counts are reconciled daily, not monthly
  • Stock, sales, and a live P&L roll up across all five locations in real time
  • The monthly spreadsheet consolidation is gone, and the books close in a few days instead of two weeks
  • Head office sees per-site and group numbers without chasing each manager
  • A new location joins by switching it on and describing its par levels, not by rebuilding a spreadsheet

See every location on one system.

Book a demo and we'll model your group: real-time location P&L and food-cost variance caught the day it happens.

Book a demo