Inventory & Expiry

Managing Stock Transfers Between Pharmacy Branches Without Spreadsheets

10/02/2026·6 min read

Multi-branch pharmacies eventually run into the same imbalance: one location has excess stock of something that is not moving, while another location is short of the exact same product and either turning customers away or over-ordering from a supplier unnecessarily. A stock transfer between branches solves this in minutes — if the system can actually record it properly.

Why spreadsheet-based transfers fall apart

  • A spreadsheet transfer log is disconnected from the actual stock levels at each branch, so it is easy for the two to drift out of sync.
  • There is no enforced approval step — stock can leave one branch without a clear record of who authorised it.
  • Batch and expiry information often gets lost in transit, since a spreadsheet line item rarely captures which specific batch moved.
  • Reconciling "what was supposed to transfer" against "what actually arrived" becomes a manual, after-the-fact investigation rather than something visible in real time.

Transfers should change stock levels at both ends automatically

The moment a transfer is recorded, the sending branch's stock should decrease and the receiving branch's stock should increase — not as two separate manual entries that can fall out of sync, but as a single linked transaction.

How stock transfers should actually work

PharmaPOS handles stock transfers between branches as a tracked transaction in its own right — specifying the product, batch, and quantity moving, with the sending branch's stock deducted and the receiving branch's stock increased as part of the same recorded event.

Because the batch travels with the transfer record, expiry tracking and FEFO picking continue to work correctly at the receiving branch — the product does not lose its history just because it changed location.

See PharmaPOS handle this in your own pharmacy.

Making transfers a routine operational tool

  1. Review stock imbalances across branches regularly, not only when a branch manager happens to notice and ask.
  2. Use near-expiry alerts as a trigger for transfer decisions — moving slow stock to a faster branch before it expires, rather than after.
  3. Require a recorded approval step for transfers above a certain value, to maintain accountability.
  4. Track transfer history per product to spot patterns — if the same item keeps needing to be transferred, it may be a sign that purchasing allocation across branches needs adjusting.

Stock transfers are one of the simplest tools a multi-branch pharmacy has for reducing both stockouts and write-offs at the same time — moving the right product to where it will actually sell. The only requirement is a system that records the movement accurately enough to trust it.

Frequently Asked Questions

Why do pharmacy stock transfers between branches often go wrong?

Spreadsheet-based tracking disconnects the transfer record from actual stock levels, loses batch and expiry detail in transit, and has no enforced approval step — all of which make transfers hard to trust or reconcile.

Does a stock transfer affect FEFO and expiry tracking?

Not if the batch information travels with the transfer record. The receiving branch should still see the correct expiry date and be able to apply FEFO picking as normal.

How can near-expiry stock be handled across branches?

Expiry alerts can be used as a trigger to transfer slow-moving, near-expiry stock to a branch with stronger demand before it becomes a write-off, rather than discovering the problem too late.

Ready to see PharmaPOS in your pharmacy?

Explore the full system with sample data, free, or talk to us about your pharmacy's setup.