By eight in the morning, an owner with four outlets in Dhaka has usually read four WhatsApp messages from four managers. One says "yesterday 2.4 lakh, alhamdulillah". One sends a photo of a handwritten register page. One says "slow day, rain". One has not messaged at all. None of the four numbers is comparable to the others, none of them mentions margin, and none of them tells you that the Mirpur outlet ran out of your best-selling rice at four in the afternoon and sold nothing after that.
That is not a reporting problem you fix by asking for better WhatsApp messages. It is fixed by looking at the same seven reports, in the same order, every morning, from one system that all outlets bill into. This guide names those seven reports and, for each one, gives you the single number to look at, what a bad reading looks like, and what to do about it before ten o'clock. There is a summary table, a cadence table for what to check daily, weekly and monthly, a section on getting all of this onto your phone, and a warning about the dashboard trap that kills most reporting projects in the second month. How multi-branch works.
Why the morning matters more than the month-end
A problem found at eight in the morning is an operational decision. The same problem found on the fifteenth of next month, when the accountant finishes the books, is history; you can write it up, but you cannot fix it. A cashier shortfall you spot the next day comes with a name, a shift and a memory. Six weeks later it is an unexplained figure that everyone denies. Stock that expires in sixty days can still be sold; stock that expired last week is a write-off with a disposal cost.
The whole routine below should take ten to fifteen minutes with tea. If it takes forty-five, the reports are wrong, not you. And one prerequisite matters more than any of the seven: every outlet has to be billing into the same system, so "yesterday's sales" means the same thing in Uttara and in Chattogram. If your branches keep separate books and send numbers up by phone, no report can be trusted, because the consolidation happens in someone's head.
The seven reports
1. Sales versus the same day last week, by outlet
What it shows. Yesterday's net sales for every outlet, side by side with the same weekday last week (Friday against Friday, Monday against Monday) plus bill count and average bill value for each. Never compare yesterday with the day before. Friday behaves nothing like a Tuesday, the first week after salary day behaves nothing like the last week of the month, and the day-on-day comparison will send you chasing ghosts.
The one number. The percentage change against the same day last week, per outlet. Average bill value is your tie-breaker.
A bad reading. One outlet down twenty per cent or more while the others are flat. That is local: a manager who opened late, a road dug up outside, a chiller that failed, a competitor's opening offer, a cashier who is not billing everything. When every outlet falls together, the cause is usually weather, a holiday, a hartal or the calendar, and there is nothing to chase. Also read the two halves separately: a fall in bill count is a footfall problem, a fall in average bill is a basket or a stock problem.
What to do. Call that one manager before nine and ask three questions: what time did the shutter open, what ran out yesterday, and did the POS or the printer go down. Nine times out of ten the answer is in one of the three.
2. Cash position and tender mix, including bKash and Nagad
What it shows. Yesterday's collection split by tender (cash, card, bKash, Nagad) per outlet, with expected cash in the drawer against counted cash, the MFS totals against the merchant statement, and what was deposited to the bank.
The one number. Cash variance in taka: counted minus expected, per outlet. The target is zero, every day.
A bad reading. Not the size of the variance but its pattern. A shortfall of a few hundred taka that appears every week, always on the same shift, is worse news than a one-off two-thousand-taka error that gets explained the same morning. Watch also for round-number variances, for a bKash total in the POS that does not match the bKash merchant statement, and for a deposit that has been "pending" for three days. Note that the sale and the bank credit run on different clocks: MFS settlement to your account happens on the settlement cycle in your merchant agreement, not at the moment of the sale, so reconcile the sale on the day it happened and the bank credit when it lands.
What to do. Set a variance rule and stick to it: anything above a fixed limit (say ৳100, illustrative, pick your own) is logged with a reason and the cashier's name the same day. Repeat shortfalls on one name or one shift move from an accounting question to a management one. Accounting and day-end.
3. Gross margin by outlet and by category
What it shows. Sales, cost of goods sold, gross margin in taka and gross margin per cent, broken down by outlet and by category. This is the report most shops never see, because their billing software knows the selling price but not a reliable cost price.
The one number. Gross margin per cent per outlet, against the same outlet last month. Then the one category that moved most.
A bad reading. Sales up and margin down. That combination usually means one of four things: discounting has gone unmanaged at the counter, a supplier raised the purchase price and the selling price never moved, the promotion that ended last Thursday is still running, or the mix shifted towards low-margin lines, cold drinks and cigarettes carrying the top line while groceries stall. The other bad reading is an impossible margin, a category showing sixty per cent when you know it earns twelve. That is a data problem: a missing purchase entry, a wrong cost price, or goods received without a bill.
What to do. Pull the top twenty lines by sales value for that outlet and compare purchase price this month against last. Check whether every running promotion has an end date the system enforces. If the numbers are impossible rather than bad, fix the purchase entries first, a margin report is only as honest as your goods-received discipline. Supermarket and grocery operations.
4. Stock-outs and the low-stock list
What it shows. Lines that hit zero yesterday and lines now below reorder level, per outlet, each with how many units sold in the last thirty days so you can tell a dead item from a fast one.
The one number. How many of your A-class lines (the top movers that make most of your sales) are out of stock right now.
A bad reading. The same items on the list every week. That is not bad luck, it is a reorder level set too low or a supplier who is quietly failing you. The other bad reading is a line at zero in one outlet while another outlet is sitting on three months of cover. That is a transfer problem, not a purchase problem, and it costs you twice: a lost sale in one branch, tied-up cash in another.
What to do. Transfer before you purchase. Then fix the reorder level once, with the supplier's lead time built in, rather than chasing the same item every Sunday. Auto-reorder rules turn this report from a to-do list into an exception list. Inventory and auto-reorder.
5. Near-expiry and ageing stock
What it shows. Batches expiring in the next 30, 60 and 90 days by outlet, and separately the stock that has had no sale in 60 or 90 days, valued at cost. Pharmacies need the first list by batch; a supershop needs both.
The one number. The taka value of stock expiring within sixty days.
A bad reading. That number growing month on month, which means you are buying faster than you sell. Or near-expiry concentrated in the one outlet with the slowest counter, which usually means goods were pushed to whichever branch had shelf space rather than to the branch that sells them.
What to do. Move it to the outlet that sells it, then discount early rather than late. A fifteen per cent discount today beats a hundred per cent write-off in six weeks, and this is the arithmetic most owners get backwards. Stop the next purchase order for those lines, and check what your supplier's return or replacement terms actually allow. For medicine, dispensing must follow FEFO (first expired, first out) not first in, first out.
6. The exception report: discounts, voids and returns by cashier
What it shows. Every discount above your threshold, every line voided or deleted after the bill was started, every return or refund, and every manual price override: grouped by cashier and shift, with the reason code entered at the time.
The one number. Exceptions per hundred bills, per cashier. A raw count punishes your busiest counter; a rate does not.
A bad reading. One cashier well above the outlet average on any of the four. Voids clustered in the last hour of a shift. Returns processed without an original bill. Discounts that always land on the same high-value items. The same customer phone number appearing on many refunds. None of these prove anything on their own, and that matters; this is a report you use to ask questions, not to accuse.
What to do. Require a reason code on every void and return, and manager approval above a set discount. Then watch whether the pattern changes once staff know the report exists, which is usually most of the fix. Our guide on reducing shrinkage in a supermarket goes deeper on this one.
7. Receivables and dues, if you sell on credit
What it shows. Total outstanding per customer, split into ageing buckets (0–30, 31–60, 61–90 and over 90 days) plus what was collected yesterday and against which invoices. Skip this report if you are pure cash retail; it is the most important of the seven if you are not.
The one number. The value sitting in the 90-plus bucket, and what share of your total dues that is.
A bad reading. The 90-plus bucket growing while total dues stay flat; that means you are collecting the new money and never the old. A single party over your comfort limit. Or, worst of all, fresh supply going out to a customer who is already past both their credit limit and their credit days, which means the limit is a number in the system that nobody enforces at the counter.
What to do. Hold supply until a part payment clears, put the top ten overdue parties on a named collection list with an owner for each, and make the credit limit a hard block rather than a warning. Reports and outlet P&L.
The seven reports at a glance
| # | Report | The one number | Bad reading | First action |
|---|---|---|---|---|
| 1 | Sales vs same day last week, by outlet | % change vs same weekday | One outlet down 20%+ while others flat | Call that manager before 9 am |
| 2 | Cash position and tender mix | Cash variance (counted − expected) | Small, repeated, same shift | Log with reason and cashier name |
| 3 | Gross margin by outlet and category | GM% vs same outlet last month | Sales up, margin down | Check purchase prices and live promos |
| 4 | Stock-outs and low stock | A-class lines at zero now | Same items every week | Transfer first, then fix reorder level |
| 5 | Near-expiry and ageing stock | Value expiring within 60 days | Number growing month on month | Move, then discount early |
| 6 | Discounts, voids and returns by cashier | Exceptions per 100 bills | One cashier above outlet average | Ask, with reason codes in hand |
| 7 | Receivables and dues | Value in the 90+ bucket | 90+ grows while total dues flat | Hold supply, name a collector |
How often to look
Not everything deserves a daily glance. Looking at a slow-moving number every day teaches you to ignore it, which is how reporting dies.
| Report | Daily | Weekly | Monthly |
|---|---|---|---|
| Sales vs same day last week | Yes, per outlet | Trend and best/worst weekday | Outlet ranking, growth vs last year |
| Cash and tender mix | Yes, variance only | Variance by cashier and shift | Tender mix shift, MFS reconciliation |
| Gross margin | No | Yes, by outlet | Yes, by category and supplier |
| Stock-outs and low stock | Yes, A-class only | Full list, reorder levels | Supplier fill rate, lost-sale estimate |
| Near-expiry and ageing | No | Yes, 60-day window | Full ageing, write-off decisions |
| Discounts, voids, returns | Yes, exceptions only | By cashier | By outlet, policy review |
| Receivables and dues | Yes, collections only | Ageing buckets | Credit limit review per party |
Monthly, add the two reports that are not part of the morning routine at all: outlet-wise profit and loss after rent, salary and utilities, and a stock-count variance report after physical counting. Those are decisions about the business rather than about yesterday.
Getting these onto your phone
Owners do not sit at a desk at seven in the morning, so the reports have to travel. Three things make that work.
- A scheduled summary, not a login. A single message at a fixed time each morning (email, SMS or WhatsApp) with sales by outlet, cash variance and the exception count. If you have to remember to open an app, you will stop by the third week.
- One screen, read-only. A mobile dashboard for the drill-down when a number looks wrong. If the morning view does not fit on one phone screen without scrolling, it is not the morning view.
- Access that matches the org chart. Each branch manager sees their own outlet, the owner sees all of them, and every change to a bill or a price leaves an audit trail with a name and a timestamp. Reports without an audit log are opinions.
One honest caveat for Bangladesh: consolidated reports are only as fresh as the last sync. If an outlet spent the evening on a dead broadband line and billed offline (which is exactly what should happen) its data reaches head office when the connection returns. A good report shows the last-synced time per outlet on the same screen, so you can tell "Mirpur sold nothing after 4 pm" from "Mirpur has not synced since 4 pm". Those are very different mornings. How offline billing and sync work.
The trap of too many dashboards
Every reporting project follows the same arc. Month one, someone builds a dashboard with forty tiles and everybody admires it. Month two, nobody opens it. The failure is not the software; it is that nobody attached a decision to a tile.
Four rules keep it alive. First, every report needs an owner and an action: if you cannot say what you would do differently based on this number, delete the report. Second, prefer exceptions to lists: do not show me 4,000 products, show me the eleven below reorder level. Third, set thresholds and let the system alert you, so the discipline lives in the rule rather than in your memory. Fourth, review the set every quarter and remove anything nobody has acted on, because a dashboard nobody trims becomes wallpaper.
Two numbers you act on every morning are worth more than thirty you show visitors.
Questions to ask at a demo
- 1Show me yesterday's sales for all outlets against the same weekday last week, on one screen.
- 2Ring up a bKash sale and a cash sale, run day-end, and show me the cash variance and the tender split.
- 3Show gross margin by category for one outlet, and tell me where the cost price comes from.
- 4Which items are below reorder level in outlet B but in surplus in outlet A, and can I raise the transfer from this screen?
- 5Show every void and discount by cashier for last week, with reason codes.
- 6Schedule the morning summary to my phone at 7:30 and show me what the message looks like.
- 7If an outlet is offline, what does the consolidated report say, and how do I know it is stale?
The bottom line
You do not need a business intelligence project to run a multi-branch shop. You need seven reports, one number in each, a habit of looking at them before the day starts, and a system where all outlets bill into the same place so the numbers mean the same thing. Sales against the same weekday, cash variance, margin, stock-outs, expiry, cashier exceptions and dues will catch nearly everything that quietly costs a growing retailer money, and each one comes with an action you can take before ten in the morning.
If you want to see these seven on your own outlets and your own products, book a demo or start free.
Frequently asked questions
- What reports should a retail shop owner check daily?
- Five of the seven, and only the exception part of each: sales against the same weekday last week by outlet, cash variance against expected, A-class stock-outs, discounts and voids by cashier, and yesterday's collections if you sell on credit. Margin and expiry are better weekly. The whole routine should take ten to fifteen minutes.
- How do I compare sales across branches fairly?
- Compare each outlet with its own same weekday last week rather than with the other outlets, since a Gulshan counter and a Mirpur counter will never share a baseline. For across-branch comparison, use sales per square foot, sales per staff member or average bill value, and always look at bill count and average bill separately.
- What does multi-branch POS software need to produce these reports?
- All outlets billing into one system, a reliable cost price on every item so margin can be calculated, tender types recorded at the till including bKash and Nagad, batch and expiry tracked at goods-receipt, reason codes on voids and returns, and a party ledger if you sell on credit. Without those inputs the reports exist but cannot be trusted.
- Can I see these reports if my branch has no internet?
- The outlet keeps billing offline and syncs when the connection returns, so the consolidated report catches up rather than losing data. Check that the report shows a last-synced time per outlet, so a branch that is offline never looks like a branch that stopped selling.
- What is a gross margin report and why does it matter more than sales?
- It compares selling price against the cost of the goods actually sold, by outlet and category, and shows what you kept rather than what you rang up. Sales can rise while margin falls (through unmanaged discounts, an unpassed purchase price rise or a shift to low-margin lines) and only the margin report makes that visible.
- How much does multi-branch POS software cost in Bangladesh?
- MondayPOS publishes per-outlet pricing, billed yearly: Business ৳3,500 per month covering POS, sales, purchase, stock and accounting, with each extra outlet at ৳2,450, and Growth ৳6,500 adding CRM, HR and payroll, with extra outlets at ৳4,550. A 14-day refund window applies. See pricing and our guide to choosing POS software.
