Skip to content
ZEST

Your restaurant, read every morning.

Your POS, invoices, and rota already know the story. ZEST joins them and prints what needs you before service.

Yesterday, on four tickets

09:00

ZEST · 09:00Act now

Labor leak

€45

  • 3 overtime shifts nobody approved
  • Fri late · bar + runner

Review before Friday’s rota

ZEST · 09:00Good

Sales record

+18%

  • Tuesday dinner vs. your own baseline
  • Covers 142 · avg. ticket €38.20

Keep Tuesday’s floor plan

ZEST · 09:00Watch

Food cost drifting

+2.3 pts

  • Last 4 weeks · produce line
  • Tomatoes +12% on the last invoice

Call the supplier, or re-cost the salad

ZEST · 09:00Good

Labor under 30%

7 days

  • Sales per labor hour €61.20
  • Best streak since March

Nothing to do. Enjoy it

Demonstration data from a fictional Berlin dinner service.

Month-end is an autopsy.Nine in the morning is a decision.

Every restaurant already produces the three numbers that explain it: what it sold, what it bought, and who worked. They just live in three places and meet once a month, at the accountant’s. By then the money has left.

Three systems, no conversation

The POS, the invoice folder, and the rota each know a third of the story. None of them can tell you that last Friday’s labor ate the whole night’s margin.

Reports instead of answers

More dashboards mean more charts to read. The only question at 09:00 is: what should I look at today?

Decisions made in hindsight

A price hike found in week six is a cost. Found on the day the invoice landed, it is a phone call.

One layer that joins the whole system.

ZEST takes the three flows every restaurant already has and reads them against your own history, never an industry average. The modules collect the data. The join is the product.

  • Sales

    POS totals, covers, dayparts

  • Costs

    Supplier invoices, prices, food & beverage cost

  • Labor

    Rota, clock-ins, overtime, tips

ZEST

Cross-checked against your own baseline

ZEST · 09:00

The tickets that matter

Prioritized. Explained. Auditable.

Deterministic, not guessed: every ticket traces back to the rows that produced it.

A service day with ZEST.

Not a dashboard you visit. A layer that shows up when a decision is due and stays out of the way when it isn’t.

  1. 09:00

    The morning briefing

    Yesterday in three lines, pushed to your phone. What moved, why, and whether it needs you.

    Morning briefing

    • Sales +18% vs. baseline, a Tuesday record.
    • Labor 29.6%, seventh day under target.
    • 3 unapproved overtime shifts: €45.
  2. 11:30

    The rota, checked before it costs

    Publish a week and ZEST checks rest hours, daily caps, and coverage against the forecast, then tells you what it would cost before you commit.

    Friday · week 36

    • Coverage gap 18:00-22:00 · 1 runner short
    • Labor forecast 31.4% · target 30%
    • Rest rule: 1 breach to justify
  3. 15:00

    The invoice, read the moment it lands

    Photograph a delivery note and ZEST files it, prices every line, and flags what moved against the last four weeks.

    Invoice · Produce supplier

    • 24 lines read · 2 need a look
    • Tomatoes 2.10 → 2.35 €/kg (+12%)
    • Food cost this week: 28.4%
  4. 23:30

    The close, without the spreadsheet

    Hours signed, tips pooled and split by the rule you set, the week frozen and ready for payroll. Every figure keeps its source.

    Close · Tuesday

    • Tips €412 · pooled 16 roles
    • Hours signed 14 / 14
    • Week ready for payroll

What’s on the menu

Four modules. One kitchen.

Use them together or start with the one that hurts. Each stands on its own; the intelligence only gets sharper as they meet.

  • Shifts

    Planning, clock-in, compliance checks, tips, payroll-ready weeks

  • Costs

    Invoices read by camera, live food & beverage cost, price drift

  • Sales

    POS totals, covers and dayparts, your own baseline

  • Insights

    The join: the morning briefing and the tickets that matter

Plus a phone app for the team: next shift, clock-in, swaps, hours and tips. One hand, mid-service.

Built to be trusted with your numbers.

Hosted in the EU
Frankfurt. Your data does not leave the European Union.
Privacy by design
Built for German data-protection law from day one, with the records and controls it expects.
Every figure keeps its source
Raw data is append-only and hash-chained. A number on a ticket traces back to the rows behind it.
It observes. It does not act
ZEST surfaces and explains. It never rewrites your rota or invents an hour on its own.

Simple, honest pricing.

Pricing on request

We are onboarding restaurants ahead of launch. Book a demo and we will walk you through pricing for your setup.

Request a demo

Your first ticket

See your own restaurant on the rail.

A 20-minute demo on data like yours, and what ZEST would have printed last month.

ZEST · Demo request

By requesting a demo you agree to be contacted about ZEST.