
Start with a precise question
A report about drinks may show units sold, revenue or share of total sales. These answer different questions. Before acting, ask precisely: which products were ordered often, which category generated revenue, and what changed against a comparable shift? Bonzumo offers reports in the sales context. Their value depends on having a clear question behind the number.
A high item revenue does not itself reveal contribution margin. Purchase cost, portion and staffing are not automatically present in the same figure. Separate the observation “sells often” from the judgment “financially worthwhile”. A report can start an investigation without forcing a menu or price decision from an incomplete metric.
Item setup determines readability
If the same lemonade is sold under three slightly different names, a report shows three lines although you want to understand one demand. A catch-all “other” item hides different products. Useful reporting therefore begins with a clear menu. Decide when a product should be a separate item and when it is a variant of an existing one.
Review important categories before interpreting figures. Are food, drinks and promotions grouped in a way the venue actually uses? A counter may ask different questions from a dining room. Bonzumo keeps item and sales information together; staff must maintain names and assignments so later comparisons remain understandable.
Read volume and revenue together
A low-priced coffee may sell often yet generate less revenue than a small number of set menus. One bottle sold may also replace several glasses. Look at units and amounts side by side and ask what work each line represents. This avoids undervaluing a popular entry item because its revenue is small or overvaluing an expensive item without considering demand.
Take a sample from last week: 100 coffees and 15 menus. What are you trying to learn? Staffing may depend on the number of individual preparations; sales mix depends on amount; profitability needs costs and portions too. A report helps with the first questions but does not answer everything automatically. Keeping them separate makes the report useful.
Choose comparable periods
An event Saturday is not a fair benchmark for an ordinary Tuesday. Shorter opening hours, weather and a changed menu also affect item figures. Record which days, hours and areas a comparison includes. To judge a new dessert range, compare similar services before and after the change rather than unequal calendar months.
Check when an order and a payment appear in the report you use. A table orders at seven and pays later; a group split may create several payments. Payment time is not direct evidence of kitchen workload time. Bonzumo connects the contexts, but for each analysis you need to know which event the figure describes.
Investigate unusual figures at source
A category suddenly declines. Perhaps fewer products sold; perhaps new items were assigned to another group by mistake. Check individual lines and menu changes first. Only when item setup is sound should you draw a conclusion about guest preferences. Unusual discounts or cancellations may also affect reported sales.
This is not about blaming an employee. It connects report and work: which items were available, which areas opened and did a technical or process change occur? Record the explanation when you find it. The next similar shift can then distinguish a demand signal from changed data entry more quickly.
Turn a figure into a testable action
An item report is most valuable when it leads to one small action. You might merge duplicate item names, review the food cost of a popular dish or discuss a slow-moving product with kitchen. Name an owner and a date to look again. A dashboard that is opened and closed without a decision has not improved the venue.
In a Bonzumo demo, ask for a report based on understandable sample sales. See which items and categories it includes and how the period is chosen. Then ask what information is still missing for a cost or staffing decision. This shows the reports real value to a restaurant: less guesswork on questions that can be checked and a shared basis for service, kitchen and management.



