The night, in numbers the owner can argue with.

Revenue, covers, occupancy, no-shows, dishes, sources, tenders, ticket times. A heatmap of the week. CSV when the accountant asks. One database, so the Z and the book finally agree.

Explore the example

Included in · Main & Chef’s Table

ReportsBRASA
14–20 / 09Sales · EUR
Sales€7,936.00
Guests248

Selected period: 14–20 / 09 · Total / Guests: €32.00

Compare daily sales within the same period.

Usage example · illustrative data

The same truth as the floor

Covers from reservations that sat. Revenue from tickets that paid. Occupancy from the plan you drew. No import from a till that speaks another dialect.

Where the week hides

A heatmap of hours and days. The dish mix. The booking source that actually fills Tuesday. Kitchen time on the pass. You stop managing by anecdote.

How it works during service

  1. 01

    The night writes the row

    Book, tickets, drawer, pass. Reports are a view, not a second job for a waiter who can use Excel.

  2. 02

    Monday is a heatmap

    Which hour died. Which dish is a puzzle. Which source you should stop paying.

  3. 03

    Someone asks for a file

    CSV. The partner, the accountant, you in another city. The database does not change dialect.

Reports / 03

Leave with a file

CSV for the accountant, the partner, the group. Your data. The screen is for the morning; the file is for the month.

ReportsBRASA
14–20 / 09Sales · EUR
Sales€7,936.00
Guests248

Selected period: 14–20 / 09 · Total / Guests: €32.00

Compare daily sales within the same period.

Usage example · illustrative data

What you can manage

  • Revenue, covers, occupancy, average spend
  • No-shows and source of booking
  • Dish mix and menu engineering hooks
  • Tenders, tips and the cash Z
  • Pass times from the KDS
  • Export CSV when you need a file

Open the restaurant on Tablerooms.

Tell us about your venue and we'll show you your own site, floor plan and menu inside Tablerooms, before you pay anything.

Try the live demo