Which reports really help you run your restaurant

Start with a specific management question

Daily closing, transaction views, comparisons between periods and sales considered alongside costing are concrete starting points for managing your restaurant. Which reports really help you? Above all, the ones that let you make a concrete decision: whether to open earlier, trim the menu, review an unusual tip total, or find the cause of discrepancies in daily closing. Huge collections of numbers rarely help in day-to-day restaurant work. A report only becomes useful when it leads to a next action and when you can go back from the summary to the individual transaction if questions come up.

In BonZumo, that connection matters because the order, payment, tip, correction, and closing all sit on the same transaction basis. That means you do not have to treat an unusual amount as an isolated metric. You can move from daily closing or a transaction view back to the underlying payments, split payments, or voids. For running your restaurant, that is far more valuable than having as many colorful charts as possible, because you do not just want to see that something stands out. You want to understand why.

Set the right time period before you compare numbers

Many bad decisions do not come from bad data but from an unclear time period. If you want to know whether an early opening evening is worth it, comparing a busy Saturday with a quiet Tuesday will not help much. You need comparable time windows: similar weekdays, the same hours, and if possible similar operating conditions. Only then can you see whether early sales are truly additional business or whether they are simply shifting within the evening.

BonZumo helps here because reports and archive views can be used across time periods. So you are not limited to looking at the current day. You can open a selected period and apply the same view again and again. In practice, that means: do not draw conclusions too quickly from one strong evening. Look at three to six comparable evenings side by side and then check whether a pattern stays stable. In bar and counter business especially, weather, events, and holiday periods often influence results more than your gut feeling suggests.

Do not confuse revenue with business success

One of the most important reporting decisions is to separate revenue from economic performance. If you only look at revenue, you can easily think an evening went extremely well even though the result behind it was weak. That matters especially when you are thinking about a smaller drinks menu, new dishes, or price changes. High revenue does not automatically tell you which items are actually helping your business.

For that question, you also need your product and costing view. BonZumo can show material costs and recipe costs for items and recipes. That makes the decision more solid: you are not only comparing what sold often, but also which items make sense from the perspective of your offer. So if you are planning a smaller menu, do not simply keep the five highest-revenue items. It is better to check which items sell regularly, work well in service, and support their place in your costing. Revenue is the start of the analysis, not the end of it.

Read sales and payments as two different things

In restaurants, sales and payment are often thrown into one pot even though they answer different questions. Sales tell you what guests ordered. Payment shows how that sale was settled: in cash, by card, in parts, with tip, or with corrections in between. Especially when group bills are split, a vague reading quickly leads to misunderstandings. A table can be fully sold but still have an outstanding balance. The other way around, a high payment total may include tip and therefore not match the pure sales amount.

BonZumo keeps that separation intact. A simple example makes it clear: €100 sold plus a €5 tip becomes a €105 payment total. The tip is recorded separately from the sold amount. With split payments, this becomes even more important. Your team can see in the transaction what has already been paid and what is still open; the table is only closed once the outstanding balance is settled. For your reporting, that means: if you want to review shift quality, payment methods, or discrepancies, look at payment and transaction views. If you want to understand item popularity or evening patterns, start with sales.

Treat tips as their own information

An unusual tip total is a good example of why a metric has to be clearly defined. High tips can reflect a very good service experience, but they can also simply come from an evening with many card payments, large groups, or rounded total amounts. If you mix tips together with revenue or payment volume, it is easy to read too much into it. Above all, you should not use that to make quick judgments about individual employees.

In BonZumo, tip information is captured during the payment flow and remains visible in the context of the relevant transaction. That helps when questions come up later: was it one large table, many small payments, or a concentration at one station? That is exactly the distinction you need if a total in closing seems unusual. In practice, that means for management: look at tips separately, discuss unusual values with the team in a factual way, and always check the transactions first. A high or low total is an observation first, not a finished explanation.

When something looks odd, go back to the individual transaction

The most important quality of a good report is traceability. If a number in the Z report, daily closing, or a period view seems implausible, you need to move from the overview to the individual transactions. Otherwise you only discuss assumptions: was it a void, a split bill, the wrong payment path, an open remaining balance, or tip counted twice by mistake? Management becomes easier when you do not have to guess.

BonZumo supports exactly this work with transactions, closing views, saved Z reports, and archive functions. So you do not just see the summarized day; you can also find the related transactions again. That is especially useful after long shifts when nobody remembers every detail anymore. Organisationally, it helps to define a fixed rule for yourself: first review the total, then narrow down the time period, then open the affected transactions, and only then discuss it with the team. That helps you avoid blanket blame and reach the real cause faster.

Only compare evenings that were really comparable

If you want to decide whether an early opening evening should stay, whether a special menu is working, or whether a certain weekday has become weaker, a simple revenue comparison is not enough. You need to ask: was the same area open? Was it terrace plus indoor dining, or just the bar? Was there an event nearby? Were more bills split than usual? Even small differences change the picture. An evening with many groups often shows different payment and tipping patterns than one with mostly walk-in guests.

That is why a fair comparison across several similar evenings is worth more. For example, compare three early Thursdays with three normal Thursdays instead of using a single peak evening as your benchmark. In BonZumo, look at daily closings and time-period views for that, and check transactions as well if the totals swing too much. Your management question stays the same throughout: does the earlier opening bring real additional revenue, or does it simply move orders forward and lengthen the shift without a clear benefit? The report should support that decision, not just document activity.

Manage the menu with a few reliable numbers

If your question is whether to reduce the drinks menu or streamline the food menu, you do not need a huge landscape of metrics. You mainly need three angles: what actually sells, in which time periods those sales cluster, and how that fits your item costing. Everything else is secondary. An item that is ordered only rarely can still make sense if it matters to a specific guest group. A frequently ordered item, on the other hand, can still be a poor choice if it disrupts the workflow or is weak in costing terms.

Use sales, time periods, recipes and costing as your basis, and ask to see which item views you can use for this decision in your venue. Sales and time periods show you demand patterns, while recipes and costing show the economic background. The actual management work remains yours: which items keep the menu understandable, sell reliably, and fit your operation? A good test is to review every planned deletion with one specific question: does the item sell regularly enough, does it contribute to the menu, and does it justify its place in prep and service? If you answer that with real sales data instead of instinct, the menu usually becomes faster and clearer.

Use numbers with your team to find causes

Even the best report does not replace the conversation with your team. It should make that conversation better. If you see in closing that one evening had an unusual number of split payments, that may simply come from one group, not from a problem. If a tip value is far outside the norm, a large party may explain it. If a correction amount stands out, it may point to misunderstandings in ordering or unclear processes. Good management here means going into the conversation with a concrete observation, not with an accusation.

In practical terms, a simple sequence helps. You take one number from the report, show the affected period or transaction, and then ask about the situation in the operation. That works better than general statements like, something is wrong with the card payment revenue. Because BonZumo ties together transactions, payments, and closing, you can prepare that follow-up question much more precisely. That makes it clearer for your team what you are discussing, and it makes it easier for you to see whether you have a real process problem or just an unusual one-off case.

Build a few recurring reports into your week

What usually helps most is not having many reports, but using a few of them consistently and reading them cleanly. For many restaurants, three fixed angles are enough in everyday work: daily closing for an orderly review, the transaction view for questions and irregularities, and period comparisons for management decisions about opening hours, menu structure, or recurring patterns. Everything else should serve a specific question instead of being collected just because the system can display it.

If you want to use BonZumo well, do not build your routine around the maximum amount of data. Build it around real decisions. Check closing every day, review inconsistencies directly in the transactions, and once a week or every two weeks take one clean period comparison for a single management question. That keeps the numbers understandable, avoids overwhelming your team with metrics, and prevents a common mistake: drawing conclusions about profit, staff quality, or the future of the business from revenue alone. Reports are truly useful when they are clearly defined, traceable, and built for one concrete decision.