
Define the unit of comparison
One location is not automatically comparable with a single dining area. Site A may open at lunch while site B only trades in the evening; a terrace may share a checkout area with the dining room. First describe which tables, sales and periods each figure includes. Bonzumo supports work areas and reports, but the unit still has to fit your question.
If you want to know whether the terrace needs more Sunday preparation, the whole venues total is of little use. Focus on the relevant area in the available report and check what was actually sold there. A missing separation is useful feedback for data setup, not an invitation to pretend the figures are more precise than they are.
Consider hours and capacity
A thirty-seat area open for three hours cannot sensibly be judged on absolute revenue against a large dining room open all day. Note seats, actual trading hours and unusual shifts. A site with much counter trade also has a different transaction mix from long table service. The number may be true while a naive comparison tells the wrong story.
Choose a clear period, perhaps four similar Saturdays, and state differences. If one site had fewer tables because of building work, that belongs in the interpretation. Fair analysis begins not with declaring a winner, but with a question that can guide preparation, range or handover.
Do not overlook range and prices
A bar sells different products from a restaurant. Higher spend per transaction may reflect a more expensive menu rather than better service. Look at items and categories before rating an area on revenue. A café with many small purchases may have high traffic but lower basket size. That work is not worse; it is different.
Check whether the same products use consistent names and categories across sites. If a cappuccino is “coffee” in one place and “other drinks” in another, category comparison is skewed. Bonzumo can bring sales information together, but the menu needs understandable upkeep. Shared naming helps without forbidding local specials.
Do not infer labour or goods directly from revenue
An outdoor area may need longer service routes than an equally sized indoor room. A high sales figure alone does not tell you the staff hours or stock needed. Bring reports together with rota, actual time and relevant goods information where they are sound. Keep observation separate from calculation: revenue is not profit and units sold do not automatically measure cost of goods.
Comparison can still help. If one site regularly has more collection delays on similar days, examine workstation, preparation and range. Find the bottleneck instead of immediately cutting staff or changing prices. The local team can explain work a report does not show.
Mark exceptional days visibly
A private event, town festival or closed outdoor area can strongly affect a sites figures. Mark these days and do not quietly compare them with normal weeks. Ask whether a promotion, voucher or revised menu changed the sales mix. An apparent improvement may reflect a one-off event; an apparent decline may simply record a partly closed terrace.
Write a one-sentence explanation so the next reader does not interpret the same report differently. Across several venues, data readers often change. A clear comment does not replace sound data, but it helps people understand its limits and make more realistic decisions.
Turn comparison into a local action
After a fair comparison, you need a next action rather than a league table. The terrace might test another collection point, or one site might tidy item categories. Name who will try it and which similar day will be reviewed. Do not change staffing, price and menu at once; otherwise you cannot tell what helped.
In a Bonzumo demonstration, use two example areas with different hours, menus and tables. Ask which available report supports the specific decision and what information is missing. When limits are stated openly, the venue gains an honest management aid. It helps ask the right questions at each site instead of hiding every difference in one total.



