Choosing a pharmacy inventory management system: what to test before you buy
Every pharmacy inventory system demos well. A short list of features to test yourself, and the questions that separate a real system from a stock spreadsheet with a login.
Engineering·12 September 2026·7 min read
Pharmacy inventory software is unusually easy to demo and unusually hard to evaluate. Every product shows a clean stock list, a low stock alert and a chart. The differences only appear in the situations that occur weekly in a real pharmacy and never in a sales demo.
This is a list of what to test, written from the side that builds these systems. Use it to structure your own evaluation rather than accepting the vendor's tour.
Batch and expiry, or nothing else matters
Ask whether stock is held per batch with an expiry date, or only as a quantity per item. This is the question that determines whether the system can grow with you, because batch handling cannot be retrofitted onto a data model that never had it.
Then ask what the system does with that data. Does it propose the correct batch at dispensing, or merely store the dates? Can it produce a list of everything expiring in the next ninety days, per location? Can it isolate a single batch across every store and ward when a recall arrives?
Ward issue against a patient
This is the feature that separates a pharmacy system from a store system. When a nurse takes stock for a patient, one action should reduce inventory and add to that patient's bill.
If the system can only issue to a location, the ward becomes an unmeasured second store and the billing has to be re-entered from a paper note. That single gap accounts for a large share of the leakage described in hospital revenue leakage.
The awkward cases to demand in the demo
- A partial return: a patient is issued five units, uses three, and two go back. Does stock recover the right batch, and does the bill reduce?
- A transfer between wards, without routing it back through the main store on paper.
- A batch recall: find every unit of one batch, wherever it is, including what has already gone to a ward.
- A controlled drug reconciliation, with a running balance the system will not let anyone silently correct.
- A substitution at the shelf, where the dispensed item is not the one prescribed, recorded as such rather than overwritten.
- A stock adjustment, showing who did it, when, and the reason code they had to choose.
Reporting you will actually open
Ignore the dashboard. Ask for four reports and check that each can be produced without asking the vendor: stock on hand by location and batch, consumption per item over a chosen period, items expiring within a window, and slow moving or dead stock.
Those four support the methods in inventory control methods. If a system cannot produce consumption per item, it cannot support a reorder point, and you are back to ordering by feel with a nicer interface.
Permissions, audit trail and the shared login problem
Ask who can adjust stock, who can write off, and who can change a price, and then ask to see the audit record of each. The answer you want is named roles and an immutable log. The answer you often get is that everyone uses the same login on the pharmacy counter machine.
A system whose audit trail can be edited is not an audit trail. For controlled substances this is not a preference, it is the whole point of the record.
Integration is the product, not a feature
A pharmacy system that does not receive prescriptions from the clinical record and does not push dispensing to the bill is three systems with a human in between. The human is where the data loss happens.
If you are buying standalone pharmacy software, the integration work is the real scope. Ask specifically how prescriptions arrive, how charges reach the invoice, whether the link is live or a nightly file, and what happens to a charge if the link fails for an hour.
Questions about the vendor, not the software
- Who owns the data, and can you export all of it, including batches and audit history, in a usable format?
- What happens at renewal if you decline to renew: does the system keep running, or stop?
- What is the response time commitment when dispensing is down, in writing?
- Which existing hospital of similar size can you call, and may you speak to their pharmacy staff rather than their administrator?
Where we sit
BBB HMS keeps pharmacy inventory inside the hospital system for exactly the reasons above: prescriptions arrive from the clinical record, dispensing updates stock and the patient bill in one action, and ward issue is recorded against a patient rather than a trolley. The trade-off is honest, which is that it is a hospital system with a pharmacy in it rather than a specialist pharmacy product.
Whatever you buy, insist on running your own cases in the demo. Every one of the awkward situations above happens in your pharmacy most weeks, and every one of them is where a system either helps or quietly creates a second paper process.
Frequently asked questions
Should pharmacy inventory be a separate system or part of the hospital system?
Part of it, if you can. A standalone pharmacy system means dispensing does not reach the patient bill without an interface, and interfaces are where revenue quietly stops flowing. If it must be separate, treat the billing integration as the main thing you are buying, not an add-on.
What single feature matters most?
Batch level stock with expiry, because almost everything else depends on it. Without batches you cannot do first expiry first out, cannot recall a batch, and cannot explain a write-off. A system that tracks only quantity per item will not grow into one that tracks batches.
How do we test a system properly before buying?
Make the vendor run your own awkward cases in the demo: a partial return to stock, a batch recall, an issue to a ward then a transfer between wards, a controlled drug reconciliation, and a bill that must show what was actually dispensed. Do not accept a scripted tour.
Is cloud or on-premise better for a hospital pharmacy?
Whichever keeps dispensing possible when the internet is down. That usually means local operation with sync, or a solid offline mode. A pharmacy that cannot dispense during an outage will keep paper records in parallel, and then your system is decorative.