Multi-Branch Pharmacy Inventory: How to Share Stock Across Branches

Multi-branch pharmacy inventory goes wrong in a predictable way. Each branch buys for itself, counts for itself and hides its own problems. One branch sits on 120 units of a product that sells 20 a month while another has none and sends patients elsewhere. Nobody sees both shelves at once, so nobody moves the stock.

This article is a practical companion to our guide to pharmacy inventory management. It covers how to run multi-branch pharmacy inventory so that stock follows demand: a central view, agreed levels per branch, recorded transfers, branch-scoped permissions and the regional points that matter in Nigeria and similar markets.

Why branches drift apart

Branches are different even when they carry the same range. A pharmacy near a clinic sells more chronic medicines. One near a school sells more paediatric lines. A tourist area swings with the season. If every branch uses the same reorder rules, some will overbuy and others will run short, and the group pays for both.

Distance makes it worse. The longer it takes to see a problem at another site, the longer it lasts. A supplier article on multi-location procurement makes the point that even when most locations run lean, a single location that orders excessively or lets stock spoil makes a noticeable dent in the results of the whole chain. Multi-branch pharmacy inventory is a visibility problem first and a buying problem second.

Seasonal swings add another layer. A branch in a business district may be busy on weekdays and quiet on holidays, while one near residential areas shows the opposite pattern. A branch near a hospital may see a surge in specific lines when a clinic changes its prescribing. Headquarters rarely sees these patterns in time unless it looks at stock and sales by branch side by side every week.

What a central view changes

A central view means the owner or head office can see stock by product, by batch and by branch in one place. It does not mean branches lose control. It means a buyer deciding whether to reorder can first check whether another branch already holds the item, and a branch manager facing a short-dated batch can see where it might still sell.

Pharmacy software vendors in several markets describe the same pattern: stock is visible across locations, and stores can look up inventory held elsewhere and transfer it to fill a need. The benefit is that duplicate ordering falls and patients are served from existing stock. The condition is that every receipt, sale, return and transfer is recorded, or the central view will simply be wrong in a more convenient place.

Decide what the weekly review looks at, so the central view turns into action. Four lists are enough: products with surplus at one branch and shortage at another, batches expiring within 90 days by branch, products that sold out at any branch this week, and transfers that were requested but not yet received. Assign each list to a named person, and keep the meeting short.

A worked example: one product, two branches

Take a product that costs $8 a unit. Branch A holds 120 units and sells 20 a month, which is six months of cover. The batch expires in four months. Branch B sells 40 a month and holds 5 units, so it will run out within days.

Moving 40 units avoids a $320 write-off at Branch A and a $320 emergency purchase at Branch B. The transfer takes a few minutes to record. This is the whole case for multi-branch pharmacy inventory in one product. Repeat it across hundreds of lines and the saving becomes visible in cash and in patient service.

Set levels per branch, not one rule for all

Reorder points and maximum levels should be set for each branch from its own sales and its own supplier lead time. A branch that sells 6 packs a day with a 3-day lead time needs a reorder point of 18 plus safety stock. A branch selling 2 a day needs 6. Using the group's average for both leaves one overstocked and one exposed.

Lead times differ by branch too. A branch in a major city may get supplier deliveries the next day, while one in a smaller town waits three or four days. A product selling 3 a day needs a reorder point of 9 with a 3-day lead time and 15 with a 5-day lead time, before safety stock. Setting one rule for both would leave the remote branch short or the city branch overstocked.

Agree the rules centrally, then let each branch tune them within limits. Review them quarterly and after any seasonal change. When one branch consistently needs transfers in, its levels are probably too low, and when it consistently sends stock out, they are probably too high. Transfers are a useful signal, not just a fix.

How to run a transfer properly

A transfer is a stock movement between two sites, so it needs a record at both ends. Keep the process short enough that staff will actually follow it.

1. The receiving branch or head office raises a request with product and quantity.
2. The sending branch checks stock and expiry, and picks the earliest expiry that still leaves useful shelf life for the receiver.
3. Record the batch number, expiry date and quantity leaving, with the date and user.
4. The receiving branch checks the delivery against the record and books it in with the same batch and expiry.
5. Both branch counts change, and the movement is visible in both histories.

The batch and expiry must travel with the stock. If a transfer drops that information, the receiving branch cannot rotate by expiry and the next recall or expiry review will be guesswork.

Transfer or buy: a simple rule

Before any branch places a supplier order above a set value, check whether another branch holds enough of the same product with enough shelf life. If it does, transfer. If it does not, buy. Set a minimum transfer value so that staff do not spend an hour moving a $3 item, and decide who pays for transport when branches are in different cities.

Make the rule specific so staff do not have to guess. For example, transfer when the sending branch's surplus covers at least three months of the receiving branch's sales and the batch has at least six months of shelf life left. Otherwise buy. Numbers like these are arbitrary, so adjust them to your range and your suppliers, but write them down and apply them consistently.

This rule only works if the central view is trustworthy. That means counts need to be accurate, which is why we recommend a regular pharmacy stock take with cycle counts at every site. A transfer from a branch whose records are wrong creates a problem at two locations instead of one.

Branch-scoped permissions

Multi-branch pharmacy inventory needs permissions that match the structure. A branch manager should see and change stock for their own branch only. A buyer might see all branches but only create orders. The owner sees everything. Without this, one wrong click at one branch can change another branch's stock, and nobody can tell who did it.

Think in roles rather than names. A cashier needs to sell and process returns at one branch. A pharmacist needs to receive stock, adjust it with a reason and approve transfers out. A buyer needs to see all branches and raise orders. A branch manager needs reports for their site. An owner needs everything. Mapping these on paper first makes setup in any system faster and avoids giving one person too much access.

Record every adjustment with a user, a time and a reason, and avoid permanent deletion so that a mistake can be undone. These controls are not extra bureaucracy. They are what let you trust a central view of several sites run by different people.

What the vendors report

Vendors publish results, and they should be read as claims rather than benchmarks. One US inventory vendor quotes a pharmacy that returned about $100,000 of stock in its first three to four weeks and cut overall inventory by $320,000 without a large rise in unfilled orders. A POS vendor says modern analytics can cut excess stock by 15 to 20 percent.

Neither of these is an independent study, and your own result will depend on your range, your suppliers and your discipline. They do point the same way: the biggest early gain in multi-branch pharmacy inventory comes from finding surplus that already exists inside the group. Read the SureCost procurement piece if you want the vendor's own account of how that works across locations.

Regional notes for Nigeria and similar markets

In Nigeria and other markets where branches can be hours apart by road, the cost and time of moving stock matter. Set a minimum transfer value, agree a regular transfer day for each route, and prioritise high value or urgent lines. Where power is unreliable, include cold-chain products in the plan only if both ends have working refrigeration.

Where a track and trace system exists, each licensed site is often registered on its own. Treat each branch as a separate site, keep dated records of what left and what arrived, and confirm with your regulator how transfers between sites must be recorded or reported, especially across state or provincial lines. Keep the paper or screen record for as long as your regulator requires, because an inspector will ask for the movement history of a single batch before they ask for anything else.

One caution on scope. Moving stock between branches in the same country is a transfer. Moving it across a border is an import and export, with customs, registrations and documentation of its own, and it should not be handled as a routine transfer. If you operate in more than one country, set up each country's branches as a separate group with its own rules and suppliers.

How Synapse handles multi-branch pharmacy inventory

Synapse by Plemora is a self-hosted pharmacy management system with centralised multi-branch inventory and inter-branch transfers, batch tracking with expiry alerts, dual retail and wholesale pricing on every SKU, five roles with branch-scoped access, and a full audit trail with soft-delete recovery. That covers the central view, the recorded transfer, the batch that travels with stock and the permissions that keep branches separate. Pricing starts from $39 a month, or from $899 for a perpetual self-hosted licence. Compare pricing or sign up free and see it live.

A 30 day setup checklist

Common mistakes are worth avoiding from the start. Do not launch transfers before counts are accurate. Do not let branches set their own rules with no group review. Do not skip the receiving check, because an unconfirmed transfer leaves stock in limbo. And do not measure success by the number of transfers, since fewer transfers can also mean better buying.

1. List every branch and its sales profile, and note which products each one struggles with.
2. Record batch and expiry for current stock, starting with the top sellers.
3. Set reorder points and maximum levels for each branch's A items.
4. Write a one page transfer procedure and train every branch on it.
5. Run a weekly review of surplus and short items across all branches.
6. Check your first month of transfers against write-offs and stockouts.

For the wider picture, read the full guide to pharmacy inventory management, or browse all insights.