It's Monday morning. You have five restaurants and you want to know how yesterday went. You send WhatsApp messages to five managers. One doesn't reply. Two send Excel files — different formats, one with tax included, one without. The fourth gives you a number from memory. The fifth says "it went well."
By 10am you still don't know if Sunday was profitable. You don't know which location pulled the chain down. You don't know if the weekend promotion worked. A daily sales report for a restaurant chain shouldn't be an investigation — it should be the first thing you open in the morning.
The problem isn't that your managers are negligent. The problem is that data lives in three different systems and manual collection is slow by definition. There's a better way.
What a daily sales report should contain
A good report doesn't mean more numbers. It means the right numbers, in the right order. These are the six elements without which the report tells you nothing useful:
- Sales per location. Not the chain total — each location separately, so you can immediately see which one underperformed.
- Average check. If total sales grew but the average check dropped, you sold more volume at a lower margin.
- Top 5 products sold. Shows what's actually moving and what you're promoting for nothing.
- Daily gross margin. Sales minus cost of goods — the only number that tells you if the day was actually profitable.
- Sales vs. same day last week. Context makes the difference between a good day and a trend.
- Anomalies. A location down 30%, a product that vanished from sales, an unusually small average check — things that need attention today, not at month-end.
All six together give you a real picture. Any one of them in isolation can mislead you. Total sales look good? Maybe because you sold three times more of a product with an 8% margin.
Why manual reporting breaks at scale
With two locations, manual reporting is inconvenient. With five, it's an operational problem. With ten, it's a risk.
It takes too long. Collecting data from POS, accounting, and spreadsheets takes a minimum of 60–90 minutes per day. That's a full week of work per month spent just assembling a picture that's already outdated by the time you finish.
It arrives too late. Friday night's data arrives Saturday morning — if it arrives. The manager at location 3 is off on the weekend. The iiko POS export hasn't synced. You wait. Can you act on a problem that happened 14 hours ago?
You can't compare. Each manager delivers data differently — one includes tax, another doesn't, one sends net, another gross. Without a unified format, you can't put locations side by side and draw a conclusion in 30 seconds.
By the time you have the data, the day you could have acted on has already passed.
The structural reason is that POS data doesn't consolidate itself across locations. Each system is built for one outlet — not for chain-level reporting. Without a layer above them, manual collection is inevitable.
What automated reporting looks like for a HoReCa chain
At 8am you open one screen. All locations, side by side. Yesterday's sales, daily gross margin per location, top products, comparison with the same day last week.
If location 3 had a 12% margin drop versus last Monday, you see it immediately — without calling anyone, without waiting for a POS export. If the average check at location 2 grew by 18%, you know the upselling is working. If a product disappeared from sales at two locations simultaneously, it's a visible anomaly — not something you discover at the end-of-month inventory.
This is what a real operational dashboard for a HoReCa chain looks like — not a table of numbers, but a picture of yesterday you can read in five minutes. You're no longer dependent on manager availability. The data is there whether it's Monday or Sunday, peak season or vacation.
For a broader view of what the operational layer above your POS should do — beyond daily reporting — the HoReCa management platform guide covers the five numbers every F&B chain operator should see every morning.
How to implement this without replacing your POS
marql connects on top of the systems you already use. You don't replace anything.
It works with iiko, Poster, and R-Keeper for restaurants and HoReCa. For accounting, it integrates with SmartBill and Oblio. See all available integrations. If you want to understand exactly how data flows from your POS into your daily report, follow the data flow.
No data migration. No transition period. You don't change how your team works. The first consolidated view of all your location sales appears within 72 hours of the first call — the time it takes to map your POS configuration and activate connections.
For a step-by-step walkthrough of what actually happens in that first window, what happens in the first 72 hours after you connect marql covers the connection and configuration process in detail.
Pricing starts at €49/month. No long-term contract at the start, no implementation fees. If you want to understand how food cost control fits into this daily reporting picture, margin is one of its essential components.
The cost of a wrong — or late — daily report
Getting the daily report wrong is often worse than not having it. When managers send data in inconsistent formats, two types of errors compound quietly:
- Comparing the incomparable. Location 2 sends net revenue (VAT excluded). Location 4 sends gross revenue (VAT included). Your spreadsheet shows Location 4 performing 20% above Location 2 — an artifact of the format difference, not operational reality.
- Acting on stale data. A margin problem that started Tuesday afternoon appears in your consolidated view Thursday morning — after a data request to three managers, a delay waiting for one response, and manual assembly. The problem has been running for 40 hours before you see it.
- Missed anomalies. A product that stopped selling at Location 3 because a supplier delivery was short — this shows up as an average check drop, not as an out-of-stock alert. Without product-level visibility in the daily report, the signal is buried in aggregate numbers.
For a 5-location restaurant group doing €30,000/day in revenue, a 3pp margin problem running undetected for one week costs approximately €6,300 in preventable margin loss — just from the delay in detection.
Reading the morning briefing: a 5-location restaurant example
Here's what the daily briefing looks like for a 5-location restaurant group after connecting POS and accounting data. This is what the 8am view contains, every morning:
What's actionable from this view, before 8:30am:
- Westside — revenue down 14% vs last week and margin 6pp below chain average. This needs a call today, not at month-end review.
- Westside average check — €17.80 vs chain average €21.16. Consistent with informal discounting or promotion running without approval.
- City Center — 29.4% margin, best in network. What's different operationally? This is worth investigating to replicate.
You get to this level of clarity in five minutes. Without calling anyone. Without assembling a spreadsheet. The data is structured the same way for every location, every morning, from the moment you connect.
The right format for the daily report: what operators actually use
The format of a daily sales report matters as much as the content. Operators who act on daily data consistently tend to use the same delivery mechanisms:
- A morning briefing delivered automatically. Not a dashboard you have to open and navigate — a summary that arrives ready to read. The five critical numbers, per location, already calculated. You scan it in three minutes; anything that needs attention is already flagged.
- Per-location detail on demand. When a location's numbers look wrong, you drill in: product-level sales, hourly breakdown, anomalies for that location. The briefing surfaces the signal; the detail view lets you investigate.
- AI-answered questions. On the Growth plan, rather than drilling into charts, you can ask directly: "Why did Westside underperform yesterday?" and get an answer grounded in the actual POS and accounting data — which product categories dropped, whether margin or volume drove the gap, and how long the pattern has been running.
The format shouldn't require any configuration once set up. You configure it once — at connection — and it runs automatically every morning from that point.
For the full picture of how the daily operational view is structured beyond just the restaurant reporting layer, the dashboards overview shows every section in context.