Reports
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.
Included in · Main & Chef’s Table
On a busy night
How Owner actually uses it.
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.
02
Monday is a heatmap
Which hour died. Which dish is a puzzle. Which source you should stop paying.
03
Someone asks for a file
CSV. The partner, the accountant, you in another city. The database does not change dialect.
01
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.
02
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.
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.
What's inside
Everything you get with Reports.
- 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
“I used to have four exports and a lie in the middle. Now the Monday number is the same number the drawer closed on.”
Same role, next screen