How to choose pharmacy software in 7 steps.
A practical selection process, a one-hour trial script and the red flags to watch for, so you choose once and choose well.
By the poso team · Updated
To choose pharmacy software: 1) write down your must-haves (batches and expiry, offline till, reorders, accounting, branches); 2) shortlist two or three systems that meet them; 3) test each with your own products on a free trial; 4) test offline selling and receiving a delivery; 5) check data export and backups; 6) compare the three-year total cost; 7) check support and references, then decide and plan the switch.
The 7 steps
- Write your must-havesStart from your problems, not a feature list. Expired stock? Stock-outs? Cash differences? Several branches? Write the five things the system must do.
- Shortlist two or threeUse the must-haves to cut the list. More than three trials is too many to do properly.
- Test with your own productsImport 50–100 of your real products, including ones with several pack sizes and batches.
- Run the real dayReceive a delivery with batches and expiry dates, sell (including a return), go offline mid-sale, close the till, run the reorder list.
- Check data and backupsExport products, sales and accounts to Excel. Ask how data is stored, backed up and restored.
- Compare three-year costLicence or subscription, setup, users, branches, hardware, support, upgrades.
- Check support and decideAsk a question during the trial and see how fast and well it is answered.
Must-haves for most pharmacies
- Batch and expiry dates captured on receipt
- First-expiry-first-out selling, automatically
- A list of what expires in the next 90 days
- A till that keeps selling offline
- Reorder levels and draft purchase orders
- Packs and single units from one stock
- Cash count at closing, per cashier
- Accounting connected, with tax per product
- User roles and a full history of actions
- Free export of all your data
Our pharmacy software buyer's guide explains why each of these matters and includes a scoring checklist.
A one-hour trial script
| # | Task | What to look for |
|---|---|---|
| 1 | Import 50 products from Excel | Was it easy? Were pack sizes and barcodes handled? |
| 2 | Receive a delivery of 5 products, 2 with two batches | Can one line have several batches and dates? |
| 3 | Sell 10 items including a single strip from a box | Speed, unit handling, batch chosen automatically |
| 4 | Disconnect the internet and sell 3 more | Does the till keep working? Do sales sync later? |
| 5 | Return one item | Stock and money go back correctly? |
| 6 | Close the till with a cash count | Differences shown by payment method? |
| 7 | Open the 90-day expiry list and reorder list | One click, or a hunt through menus? |
| 8 | Export products and today's sales | Excel or CSV, without asking support? |
Red flags
- No free trial, or a trial only with demo data.
- A large payment before you can test.
- Data export only on request, or for a fee.
- Offline mode that is "coming soon".
- Per-user prices that double your cost when you add two cashiers.
- Vague answers to "what doesn't it do?".
Planning the switch
Choose a quiet week, import products, count opening stock (batch-tracked items with batches and dates), train staff, and stop the old system on the go-live day. See how to get started with poso for a detailed plan.
Choosing pharmacy software
What should I look for in pharmacy software?
Batch and expiry tracking with FEFO, near-expiry alerts, an offline-capable till, reorder rules, packs and units, cash control, connected accounting, user roles and free data export.
How do I compare pharmacy software?
Test two or three systems with your own products using the same trial script, then compare must-haves, three-year cost, data export and support.
How long does it take to switch pharmacy software?
For a single pharmacy, usually a few days of preparation and one go-live day. Chains take longer and benefit from guided onboarding.
Should I choose cloud or desktop pharmacy software?
Cloud with an offline-capable till suits most pharmacies. See cloud vs desktop.
Last updated by the poso team.