Stop silent food cost leakage before it eats your margin.
A Business Unit that runs a nightly three-way reconciliation between supplier deliveries, recipe BOMs, and POS sales — then sends one paragraph to your operator's morning coffee. No dashboards no one looks at.
Why does this problem persist in 2026?
Restaurants don't lack tools — they lack a closed nightly loop between three systems that have never spoken to each other.
Over-portioning
POS mis-rings
Recipe drift
The Wednesday-night problem no one in the kitchen owns.
A first-party view from running the loss-control diagnostic in dozens of independent and small-chain kitchens.
The instinct is to throw a chatbot or a generic forecasting tool at the problem. It doesn't work — because the problem isn't a question. It's a three-way reconciliation between what arrived from suppliers, what should have been used per recipe, and what was actually sold at the till.
Doing that reconciliation manually takes a controller two days a month. By the time the variance report lands, the bleeding ingredient is already last month's news. The kitchen has moved on. The supplier invoice is paid. The portion drift is now a habit.
The Unit automates the reconciliation nightly, ranks the top three variances by EUR impact, and writes a one-paragraph plain-language brief for the operator's morning coffee. No dashboard. No alerts at 2am. Just the three numbers that matter, with the receipts to back them up.
The brief must depersonalize the conversation. Variance attributed to a system is acted on. Variance attributed to a person is argued about.
Same kitchen, two operating models.
The change isn't software. It's the cadence at which the operator sees the truth.
Monthly stocktake reality
- Stocktake done last Sunday of the month, by hand, in the walk-in.
- Variance report compiled in Excel by week 1 of next month.
- By the time the report lands, the offending shift is 6 weeks old.
- Conversation with the kitchen turns into 'who left the door open'.
- Result: the leakage is a known cost line. Nothing changes.
Nightly closed loop
- Deliveries, recipes, POS reconciled automatically every night at 02:00.
- Top 3 EUR variances ranked, with the most likely cause identified.
- One-paragraph morning brief in operator's WhatsApp / email by 06:30.
- Specific actions: 'spot-weigh portions at grill station for 2 services'.
- Result: 1.5–4% of food cost back on the P&L within 90 days.
A nightly loop, four steps, one paragraph at the end.
Designed to fit the cadence of a working kitchen — not to add another screen the team has to check.
Ingest
Pulls supplier delivery notes (PDF / EDI / email), POS exports, and your recipe book nightly. Standard integrations: Lightspeed, Gastronovi, Vectron, Hypersoft, Square, Toast, plus CSV.
Reconcile
Matches sold dishes → recipe BOM → expected ingredient draw → actual stock movement. Identifies variance with EUR impact and confidence.
Rank & explain
Surfaces the top three EUR variances and the most likely cause in plain language: portioning, mis-ring, supplier short, recipe drift, or unknown.
Brief
Sends a 1-paragraph morning brief to the operator. WhatsApp, email, or printed at the espresso machine. No dashboard required.
Local vs EU cloud — the honest comparison.
Both options are GDPR-aligned. The choice is about cost, IT preference, and how multi-site your operation is.
| Local — Mac mini | EU cloud | |
|---|---|---|
| Hardware | Mac mini M4, 32 GB — supplied & racked | None on your side |
| Data residency | Your office, your jurisdiction | EU (Frankfurt, Hetzner / Scaleway) |
| GDPR alignment | Strongest — controller never releases data | Aligned via DPA + EU-only processors |
| Internet outage | Keeps reconciling locally | Pauses; resumes when online |
| Monthly running cost | ≈ €0 (electricity) | €180–€280 |
| Multi-site rollout | One Mac per site, or central VPN | Native — single tenant per group |
| Best for | Single-site to 6-site operators | Multi-site groups, hotels, canteens |
| Setup time | 5 weeks (hardware lead time) | 4 weeks |
| Ongoing IT need | Almost none — Mac ships pre-configured | We manage it |
What's the leakage worth in your kitchen?
Sliders default to median values from our pilot operators. Recovery range mirrors the first 90 days of live deployments.
Talk to the morning brief assistant.
A sandbox showing how the operator interacts with the Unit. Production deployment runs locally in your office and brief delivery goes to WhatsApp / email.
What lands in your office in week 5.
The local-deployment package, itemized.
Hardware: Mac mini M4 (32 GB)
Sized for a single-site or up to 6-site operation. Sits behind your existing router; needs 1× ethernet port and 1× outlet. We ship it pre-configured with the Unit installed and the integrations to your POS and supplier feeds tested.
- Apple M4 chip · 10-core CPU
- 32 GB unified memory
- 512 GB SSD storage
- Pre-installed Unit firmware
- Encrypted local store (FileVault)
- Auto-updates over your VPN
Week 5 schedule
- MonHardware delivered & racked
- TuePOS + supplier feed live
- WedFirst reconciliation run
- ThuOperator workshop (45 min)
- FriFirst morning brief sent
One Unit, three ways to pay.
Same scope, same support, same outcome target. Choose the cashflow shape that fits.
One-time
- Full Unit + integrations
- Mac mini included (local)
- Operator training (½ day)
- 12 months support
12-month installments
- Same scope as one-time
- No interest, no penalties
- Yours after month 12
- 12 months support
Rental
- Hardware loan
- Full support included
- Hardware refresh every 24 mo
- Convert to ownership anytime
Frequently asked questions
Claim the Restaurant Loss Control Unit.
A 15-minute call confirms fit. If your operation is too small or your friction lives elsewhere, we'll say so.
About 1 in 4 calls ends with us recommending you don't buy anything.