Book a demo
Platform overview

One costing engine under every operational decision

Margin is not a set of tools that happen to share a login. Counts, purchases, invoices, recipes and sales all write into one ledger, and every report is traceable to the transaction that created it.

  • Multi-location by default — locations, roles and permissions
  • Mobile-first where staff work, deep where analysts work
  • Traceable: every number opens to its underlying records
Good morning, Alex
Downtown · Tue, Oct 10 · updated 2m ago
Last 30 days
Command barSearch or ask about costs…
⌘ K
Sales
$248k
+4.2%
Food cost
28.4%
−1.1 pts
Prime cost
57.1%
Variance
$12.5k
Needs review
Margin trendActual · Target
Value delivered$18,420 recovered · 37 actions closed
Needs attention
3 invoice exceptions
Airport count overdue
Ribeye price +11.4%
AI insight

Airport food cost is 3.2 points above group. Beef usage explains most of the gap.

01Architecture

Six operating areas, one accountable record

Inventory, purchasing, kitchen, finance, planning and reporting share the same source records, so each decision can be traced back to what happened.

01

Inventory

Item master, units of measure, storage areas, locations, vendors and GL mapping — validated by data-health checks.

02

Purchasing

Counts, receipts, transfers, production, waste and sales. Every movement is signed, timestamped and attributable.

03

Kitchen

Prep runs, recipes, yields, checklists and labels connect kitchen work to finished inventory and batch cost.

04

Finance

AP, pay runs, cash planning, GL, reconciliation and period close connect operating detail to the books.

05

Planning

Budgets and rolling forecasts put location targets beside current actuals and emerging variance.

06

Reporting

Daily briefs, data-health alerts, scheduled reports and Copilot focus each role on the next action.

03Reporting

Standard reports for the period, a builder for everything else

A catalog of operator-grade reports covers close. When leadership asks a question the catalog doesn't answer, build it once and schedule it.

  • Period COGS, AvT variance, menu engineering, vendor spend
  • Custom report builder with saved views and scheduling
  • Exports to CSV and accounting-ready formats
  • Role-scoped: managers see their location, leadership sees the group
Insights
Reports catalog
Search reports
DashboardReportsTools
Actual vs Theoretical
Open report →
Menu Engineering
Open report →
Vendor Spend
Open report →
Inventory Valuation
Open report →
Count Review
Open report →
Data Health
Open report →
Actual vs Theoretical
All locations · Period 9
Saved views Filters
Actual usage
$425k
Theoretical
$412k
Variance
$12.5k
2.9% of sales
ItemActualTheoreticalVarianceVariance $
Ribeye 12oz1,284 lb1,070 lb+214 lb+$3,120
Heavy cream428 qt401 qt+27 qt+$650
Romaine hearts183 cs190 cs−7 cs−$214
Fryer oil92 ea81 ea+11 ea+$416
Location roll-up · 4 locationsAsk AI about this variance →
04Governance

Numbers people can defend

Counts get reviewed before posting. Invoices get approved before they hit the GL. Everything is versioned and logged, so a disputed number ends in a record, not an argument.

  • Review and approval steps on counts and invoices
  • Full audit log of who changed what and when
  • Data-health and UOM checks that surface bad inputs early
  • Import monitoring and exception handling for configured data feeds
05Scale

Built for groups, not single units

Unlimited
Locations

Grouped by brand, region or entity

Granular
Permissions

Role and location scoped, per screen

Offline
Mobile counts

Walk-ins and basements included

Audited
Every change

Immutable history for disputes