Skip to content

How to Manage Multiple Shop Branches Without Losing Stock or Cash

How to manage multiple shop branches in Nigeria: one product catalogue, stock per branch, recorded transfers and a daily cash close, so nothing goes missing.

By Ajinex Team · · 9 min read

In this article

Opening a second shop is the moment most Nigerian business owners discover that the system which ran the first one was actually them. They knew every product, counted the drawer every night and noticed when a carton went missing. Learning how to manage multiple shop branches is really learning how to replace yourself with a system that works when you are not standing there.

The second branch is where the trouble starts. Stock "borrowed" from one shop to the other with no record, two different prices for the same product, a manager who reports sales by WhatsApp voice note, and an owner who cannot say which branch is actually making money.

This guide covers the structure that works: one product catalogue, stock per branch, transfers with a paper trail, clear roles, a daily cash close at every branch, honest branch comparison, and what happens when one branch has no light or internet.

Start with one centralised product catalogue

Every branch must sell from the same product list. One name, one code, one unit, one cost price and one selling price per product (or a deliberate, recorded price difference per branch). The catalogue lives in one place and branches read from it; nobody at a branch creates their own version of "Peak Milk".

  • Reports only work if the product is the same product everywhere. If Ikeja calls it "Indomie Chicken 70g" and Ojota calls it "Indomie small", you cannot compare sales or combine stock.
  • Price control is a theft control. If branch staff can set prices, the gap between the real price and the recorded price is where money leaks.
  • Reordering gets simpler. You see total demand across all branches and buy in one market trip instead of three.

Product creation and price changes are therefore owner or head-office tasks. Branch managers can request a new product; they cannot invent one. A central catalogue with per-branch stock is a core feature of inventory management software built for multiple locations; a spreadsheet per branch cannot give you this.

Hold stock per branch, not as one total

"We have 120 cartons of sugar" is useless if 100 are in Onitsha and the customer is in Awka. Stock must be tracked at the branch level: each branch has its own quantity for each product, its own reorder level, and its own stock count.

Product Onitsha branch Awka branch Nnewi branch Total
Dangote Sugar 50kg 100 12 8 120
Golden Penny Semovita 10kg 30 44 0 74
Kings Oil 5L 15 18 22 55

That one table tells you three things immediately: Nnewi has run out of Semovita, Awka is low on sugar, and Onitsha is sitting on most of the sugar stock. Without per-branch stock you would see "74 Semovita" and never know Nnewi had none.

Inter-branch transfers: the paper trail that saves you

Moving goods between branches is normal and healthy. Moving goods between branches without a record is the single most common way multi-branch businesses lose stock.

A proper transfer has four parts:

  1. A request or instruction: Nnewi needs 20 Semovita; the owner or manager approves it.
  2. A dispatch record at the sending branch: Awka stock drops by 20 the moment the goods leave, with the name of who released them.
  3. A receipt record at the receiving branch: Nnewi stock rises by 20 when the goods arrive, with the name of who received them, and a count. If only 19 arrive, the difference is recorded, not absorbed.
  4. A transfer number that links the two so the owner can see goods in transit.

Between dispatch and receipt, the 20 bags are "in transit" and belong to nobody's shelf. Software that handles transfers shows this explicitly, so a bag that leaves Awka and never reaches Nnewi is a visible gap rather than a mystery at the next count.

Branch managers vs owner visibility

Roles are what let you step back from the counter without losing sight of it. The principle is simple: each person sees and does only what their job requires, and everything they do carries their name.

Role Can do Cannot do
Cashier Sell, print receipts, take part payments, see their own sales See cost prices, delete sales, edit prices, see other branches
Branch manager Everything a cashier can, plus receive stock, approve returns, run stock counts, see branch reports Change the catalogue, see other branches, change their own permissions
Owner Everything, across all branches, on one dashboard Nothing, but every action is still logged

The owner dashboard is the pay-off. One screen showing today's sales by branch, cash in each drawer, low-stock products at each location and who is logged in where. You check it from Abuja while the branches run in Kano and Kaduna. That cross-branch view is exactly what Ajinex provides, with up to 5 branches and 20 users on the Basic plan and 10 branches and 50 users on Standard; see pricing for the full detail.

Give branch managers real authority inside their branch. A manager who must call you to approve every return will stop recording returns. Record everything and review the log weekly instead of approving every action live.

Cash reconciliation per branch, every day

Each branch closes its own day. No exceptions, no "we will do Monday together".

The daily close for a branch is one simple comparison: expected cash = opening float + cash sales - cash paid out (expenses, refunds). Count the drawer. The difference between the count and the expected figure is the variance, and it is recorded, with the manager's name, whether it is ₦0 or ₦40,000.

Then the non-cash side: transfer and POS terminal sales for the day should match the terminal settlement and the bank alerts. If the software says ₦310,000 came in by terminal and the terminal says ₦295,000, somebody recorded a cash sale as a terminal sale (or the reverse), and you find out tonight instead of at month end.

Three rules make this stick: the person who counts the drawer is not the only person who sold from it; a variance above a threshold you set (say ₦5,000) reaches the owner the same night; and every expense paid from the drawer needs a recorded reason. "Fuel for generator, ₦8,000" is fine. "Miscellaneous, ₦8,000" is not.

Our guide on how to prevent staff theft in your shop goes deeper into why the daily close, done consistently, removes most of the opportunity.

Comparing branch performance

Once every branch sells from the same catalogue and closes every day, you can finally compare them fairly. The useful comparisons are not just total sales.

Measure What it tells you
Sales per day Raw size of the branch
Gross margin Whether the branch is discounting too much or selling the wrong mix
Sales per staff member Whether a branch is overstaffed or a cashier is carrying everyone
Stock turnover (how many times stock sells through in a month) Whether money is sitting on shelves
Shrinkage (count vs expected, as a percentage of stock value) Where stock is disappearing
Cash variance (monthly total) Where cash control is weak
Debtors outstanding Which branch is too generous with credit

Two branches with the same sales can be in very different health: one selling at thin margins with high shrinkage, the other smaller but clean. Comparing only the sales figure rewards the wrong manager. Ajinex includes a per-branch comparison report, and the figures above are the ones worth watching month to month.

Common failure modes

These are the patterns we see repeatedly in multi-branch businesses across Nigeria. Each has a fix.

  • Branch A "borrows" from Branch B with no record. Classic. The driver carries 10 cartons across town, nobody enters a transfer, and both branches' counts are wrong for months. Fix: no goods move without a transfer record, and the driver carries a printed transfer slip.
  • Prices drift between branches. One manager "adjusts" prices to move stock. Fix: price changes are central, with recorded per-branch exceptions if you want them.
  • One manager reports by voice note. You get "sales were okay today, around 200k". Fix: the system reports; the manager explains the variance.
  • Stock counts happen only at head office. Branches are counted once a year, if ever. Fix: rolling counts, a section a week at every branch, as described in how to do stock taking in a shop.
  • The owner logs in with one shared account. Everyone uses "admin". Fix: one login per person, no exceptions, so the activity log means something.
  • Supplier deliveries go straight to the branch and never get entered. The goods are on the shelf but not in the system, so margins and counts are both wrong. Fix: receiving is a recorded step at every branch, not just the main one.

When one branch is offline: the role of sync

Nigerian branches do not all have light or internet at the same time. Kano may be fine while Aba has had no power since morning. A multi-branch system that needs every branch to be online to sell is a system that stops working somewhere every day.

What you need is offline-first software at each branch with sync between them:

  • Each branch keeps selling, receiving stock and printing receipts on its own machine, running on battery or generator, with no internet.
  • When the connection returns, that branch's sales, stock movements and cash records upload to the cloud and the owner dashboard updates.
  • Transfers dispatched while the receiving branch was offline simply wait in transit until that branch comes back and confirms receipt.

This is how Ajinex's desktop app works: it records everything locally and syncs when the network is available, so an offline branch is a delayed report rather than a lost day; the Inventory and POS software that works offline in Nigeria page explains the behaviour. The one thing sync cannot do is show you what a branch is doing right now while it is offline. Build your controls (transfer records, daily close, per-person logins) so that "afterwards" is enough.

Frequently asked questions

How many branches can one owner realistically manage?

With the structure above, the limit is your management time rather than the software. Many owners run three to five branches comfortably by reviewing the dashboard daily and the branch reports weekly. Beyond that, you typically need an area manager layer who reviews branches on your behalf, with their own login and permissions.

Should every branch have the same prices?

Usually yes, because it simplifies control and customers compare. There are legitimate reasons to differ, such as higher transport costs for a branch far from the market you buy in. If you do, set the difference centrally and record it, so a branch-level price change is always visible as a deliberate decision rather than a quiet adjustment.

What should the branch manager see that the owner sees?

Everything about their own branch, nothing about the others. Sales, stock, counts, their staff's activity and their own branch's reports. Cost prices are a judgement call; a manager who negotiates with suppliers needs them, a manager who only sells does not.

Can I manage branches in different cities from one place?

Yes, provided the software holds stock per branch and gives the owner a cross-branch dashboard. Ajinex supports branches in different cities with sync between them, and the same approach works whether the branches are in Lagos and Ibadan or Onitsha and Aba.

Next step

If you are running, or about to open, a second branch, set up the structure before the goods move: one catalogue, stock per branch, transfers with records, one login per person and a daily close everywhere. Ajinex gives you all of it in one system that keeps working when a branch loses light. Start the 30-day free trial with up to 3 branches included, or see how it fits a wholesale and distribution business with several outlets.

Ajinex Team

The people who build Ajinex, writing from what we learn supporting supermarkets, pharmacies, restaurants and wholesalers across Nigeria. Questions? Talk to us.

Chat with support