How to read your restaurant's daily sales report

Your POS prints numbers every night — but numbers without context are noise. Learning to read a restaurant sales report in Kenya turns closing time from anxiety into a five-minute review: did we hit target, where did money leak, and what do we fix tomorrow?

This guide walks through the lines on a solid daily report and shows how Bizflow presents them for Kenyan cash + M-PESA operations.

The report you should generate every day

At minimum, close with:

• Shift or daily sales summary
• Payment method breakdown
• Category or department mix (food vs drinks vs other)
• Discounts and voids
• Tax lines if your outlet displays VAT-style splits
• Per-waiter totals if you run table service

Bizflow produces these from local data — you do not need internet to print the report that secures your night.

Gross sales vs net sales

Gross sales — total value of items rung before discounts.

Net sales — gross minus comps, staff discounts, and promotional reductions.

Owners who only watch gross celebrate fake wins when comps are high. Net sales align with what should land in the bank after policy — not after theft.

If gross was KES 120,000 and net KES 108,000, investigate KES 12,000 of discounts before blaming slow traffic.

Payment mix — cash, M-PESA, card, other

Kenyan restaurants typically see heavy M-PESA alongside cash. Your report should show:

• Cash total
• M-PESA total (STK + matched Till/Paybill)
• Card or other electronic methods if used
• Split payments counted correctly

Compare payment mix to bank deposits:

• Cash → physical count vs report
• M-PESA → business statement vs report
• Card → processor settlement vs report

When restaurant sales report Kenya totals disagree with statements, fix process same week — not at month end.

Bizflow labels payment methods explicitly on shift close exports.

Voids, refunds, and discounts

Three different leak paths:

Voids — item removed before or after kitchen fire depending on policy. High void rate on premium alcohol = training or supervision issue.

Refunds — money returned after payment. Should be rare and manager-approved.

Discounts — intentional price reductions (staff meal, promo, regular customer).

Segment these on the report. Lumping them into "adjustments" hides whether you have a kindness policy or a theft problem.

Category and department performance

Food vs beverages vs retail merchandise — each line tells a merchandising story:

• Drinks outpacing food? Kitchen promo or happy hour working.
• Food up, drinks flat? Pairing or server suggest training opportunity.
• Retail SKUs spiking? Event or tourist weekend.

Bizflow department mappings feed category subtotals on daily reports so owners see mix without manual pivot tables.

Covers and average spend (if tracked)

Some outlets count covers (guests) or tables turned. Even manual cover counts entered at shift open improve:

• Average spend per cover = net sales / covers
• Benchmarking weekdays vs weekends

Low average spend with high covers → upsell or menu engineering. High average with low covers → marketing footfall problem.

Reading Bizflow daily sales report sections

Typical Bizflow close report structure:

1. Outlet and shift identifiers — date, shift name, manager
2. Sales summary — gross, discounts, net
3. Payment summary — cash, M-PESA, other
4. Tax summary — if enabled for your outlet
5. Waiter breakdown — sales per staff member
6. Void/discount audit — counts and values

Print or PDF this document and attach to the cash drop envelope. Accountants love consistent paper — or digital exports with the same structure.

Product sales report — what made money, not just what sold

Inside each timeline (shift), Bizflow adds a product sales view beyond the overview snapshot. For every product that moved in that shift you see:

• Cost price loaded in your catalog
• Units sold during the timeline
• Sales value (revenue)
• Profit estimate — sales minus cost for that line

The product demo shows a line with cost 170, two units sold, sales 560, and profit estimate 220 — enough to spot winners and losers without exporting to Excel. Read the full walkthrough in product sales and profit reports.

Use this report to:

• Push high-margin cocktails and dishes in server training
• Reprice or delist lines that sell often but barely profit
• Catch costing errors (zero cost price makes profit estimate meaningless)

Shift inventory report — stock reconciliation

The same timeline includes an inventory report: opening quantity at shift start, units sold during the shift, and expected closing count per SKU.

Example from the Bizflow demo: thirteen beers at open, two sold, expected closing eleven. If physical count finds ten, investigate one unit tonight — not at month-end.

Pair inventory report with product sales:

• Product sales → economic performance per line
• Inventory report → physical truth vs system expectation

Deep dive: shift inventory report guide.

Sellers and payment modes on overview

The overview report for the active shift shows:

• Top moving products — what's busy this service period
• Payment modes — separated M-PESA, cash, and other methods so you expect Ksh 30,000 on M-PESA and Ksh 20,000 in cash before counting
• Sellers — each waiter with order count and total value (Janet, James, etc.)

This is the screen managers use before close timeline — reconcile payments, sellers, and stock before naming the next shift. See custom shift timelines.

Weekly rhythms beyond the daily line

Monday: compare last week net vs same week prior month.

Mid-week: scan category mix — prep purchasing.

Friday pre-rush: check stock warnings from sales velocity.

Sunday: review cumulative M-PESA vs cash — adjust float for next week.

Daily reports are tiles; weekly review is the mosaic.

Common report mistakes owners make

Skipping net sales — cheering gross while comps balloon.

Ignoring unmatched M-PESA — report says paid but payments sit in unallocated queue.

Not reconciling voids to CCTV or kitchen tickets — policy without verification fails.

Comparing outlets on gross only — different discount cultures distort ranking.

Only cloud reports — if you cannot print locally at close, you are hostage to connectivity.

Bizflow keeps report generation on the device that ran the shift.

Educational trust — why this article exists

Software vendors that explain reports earn trust. Owners searching POS sales report Kenya want literacy, not jargon. When you understand gross vs net and payment mix, you evaluate any POS critically — and you see why integrated M-PESA and waiter totals matter.

Bizflow shows reports as operational tools:

• Shift close for managers
• Waiter performance for supervisors
• Daily net for owners
• Export for accountants

Practice exercise tonight

After service:

1. Print Bizflow shift report.
2. Circle net sales and M-PESA total.
3. Count cash drawer.
4. Open M-PESA business statement for the same window.
5. Note variance in one sentence in a logbook.

Repeat seven nights. Variance shrinks when staff know you read the report — not when you install fancier charts.

Understanding your restaurant daily sales report is one of the highest-ROI skills in hospitality. Bizflow gives you the numbers in plain language; this guide gives you the questions to ask them.