Short answer. Excel is not built for three pharmacies, because it has no notion of batch, expiry date or transfer between shops. As long as each pharmacy has its own file, nobody sees that a product is missing here and expiring there. The solution is not a full ERP: it is a single stock per batch and date, shared by your three counters, with transfers between branches proposed before any supplier order, a counter alert on expiring batches, and a ten-minute daily rolling inventory instead of the closing day. AI comes after, to forecast stock-outs and propose the order. It all goes live in ten weeks, one branch at a time.
This guide answers a question a shop owner asked us in Arabic: "I want a system that manages stock for pharmacies, mini-markets and restaurants, with invoicing, sold by subscription". We answer here for the pharmacy, the most demanding case; the same reasoning applies to a mini-market or a restaurant chain with several outlets.
Why Excel breaks from the second pharmacy
Excel can count quantities. It does not know that one reference exists in three batches with three dates, that the oldest batch must go out first, that a box sold at the first pharmacy's counter must leave the stock the moment the receipt prints, nor that a transfer to the second pharmacy is more profitable than a supplier order. So each pharmacy ends up with its own truth, updated when someone remembers, and the money disappears between those three truths.
The pharmacists we meet know these five leaks. What they underestimate is their sum: an expired product is not a stock loss, it is a purchase paid to the supplier, stored, then thrown away, and stock-outs send loyal customers to the pharmacy across the street. With three shops, that sum far exceeds the cost of serious software.
«An expired product is not a stock loss. It is a purchase paid, stored, then thrown away.»
Tier 1 — What gets fixed in a week, before any software
Four rules, applicable on Monday, that stop the worst leaks and prepare the data import.
- 01One expiry date per row, mandatory. In each file, a batch column and a date column. A row without a date does not count. Tedious once, and the condition for everything else.
- 02The Monday expiry round. Each pharmacy lists what expires within ninety days and shares it with the other two. A product sleeping here and selling there changes shop within the week.
- 03No supplier order without checking the other two stocks. A message in the group before each order: "who has X?". Rudimentary, and yet half the overstock disappears.
- 04Receiving is logged the same day, batch and date included. A receipt logged the next day is a wrong receipt.
For a single pharmacy, these rules are enough for a long time. With three, they hold a few months, the time to choose and deploy the software. Do not skip them: files with batches and dates import in a week; files without dates never import.
Tier 2 — Multi-branch software: what it must do, and what is superfluous
What you need is not an ERP. It is pharmacy software that knows the batch, the date, the counter and the transfer, and runs on three sites with one product record. We detailed the modules of pharmacy and stock management software in Algeria; here is the minimum for three branches.
Two features pay for the software on their own. Transfers between branches, proposed automatically when a product is missing in one and sleeping in another, before any supplier order. The counter alert, which tells the assistant a batch expires in sixty days at the moment they scan it, and suggests serving it first. The rest, dashboard, rolling inventory, receiving by scan, consolidates. Third-party payment and the Chifa card must be handled at the counter from day one, otherwise the team keeps the old system alongside.
Off-the-shelf or custom? If your three pharmacies work in a standard way, a market pharmacy software, deployed properly, is enough. Custom is justified when you mix pharmacy, parapharmacy and mini-market, when you want to sell the software by subscription to other pharmacies, as the shop owner who asked wanted, or when transfers and purchasing rules are specific to your group. The guide to stock management apps in Algeria details that choice.
«Two features pay for the software: transfers between branches, and the counter alert on the expiring batch.»
Where AI helps a multi-branch pharmacy, and where it adds nothing
The AI question always comes first. It is settled third, and on two uses only.
Forecasting stock-outs and proposing the order, branch by branch, from six months of real sales, supplier lead times and seasons: flu, Ramadan, back to school. Proposing the transfer before the batch expires, by crossing each branch's sales velocity with the dates. These two uses require a stock per batch and date, up to date. On an approximate Excel, AI proposes transfers of products that no longer exist. Counter advice remains the pharmacist's act; we wrote about it in our report on digital transformation of pharmacy in Algeria.
What it costs and how long it takes
Custom software for three pharmacies, with counter, stock per batch, transfers, purchasing and dashboard, sits in category 2 of our price grid, with AI forecasting as an option. Market software is paid by subscription and deploys faster, with its vendor's limits. In both cases, the timeline that works is the same: one branch at a time, never all three at once.
The shop owner who wrote to us also asked whether he could know the total price in advance. Yes, from a written scope, we explain it in our dedicated answer to that question. For a pharmacy, the scope fits on one page: your product families, your suppliers, your third-party payment rules, and the state of your Excel files.
The mistakes we see in multi-branch pharmacies
- Deploying the three branches the same day. Three teams lost at once, and back to Excel within a week.
- Importing files without expiry dates. The software inherits a blind stock. Add the dates before, not after.
- Keeping one counter on the old system "for now". Two truths again. A branch switch is total or it is not.
- Buying a generic till software. It knows neither batch, nor date, nor Chifa. The assistant bypasses it at the first prescription.
- Starting with AI. It forecasts from sales you have not yet recorded properly. Six months of data first.
Frequently asked questions
- Do we have to close a pharmacy for the initial inventory?
- No. The initial inventory is done by product family, outside peak hours, over three to five days, while the pharmacy sells. Then the rolling inventory permanently replaces the closing day.
- Can our Excel files be imported?
- Yes, and it is mandatory, provided they contain the batch and the expiry date. The import includes cleaning duplicates and misspelled references. Count two weeks for three pharmacies.
- What about the Chifa card and third-party payment?
- They are handled at the counter from day one, otherwise the team keeps the old system alongside. Any serious pharmacy software in Algeria integrates them; check before signing.
- Market software or custom?
- Market if your pharmacies work in a standard way. Custom if you mix several trades, want to resell it by subscription, or if your transfer and purchasing rules are specific to your group.
- How long before the team really uses it?
- One pharmacy at a time, two weeks each, so ten weeks for three. The team adopts it the day the counter alert saves them from serving an expiring batch: usually the first week.