In a pharmacy, the stock that expires is not just money lost, it is trust lost, and sometimes a regulatory problem. A medicine's journey from supplier to patient has a batch number, an expiry date, a price controlled by market habit, and occasionally a recall notice. General retail software treats all of that as optional; a pharmacy POS must treat it as the core. This guide sets the non-negotiables, the daily routine, and the questions that expose weak vendors in one demo.

The three non-negotiables
1. Batch and expiry, not just stock counts
"Paracetamol: 120 units" is a retail number. A pharmacy needs 120 units across 4 batches: batch A (9,000 units, expires March), batch B (2,000, expires next week), and the counter must dispense the earliest expiry first (FEFO). Without batch logic, the shop silently rotates losses: fresh stock bills first, old stock expires at the back of the shelf. Near-expiry alerts belong in the morning report, not in a yearly panic.
2. Recall-ready traceability
When a supplier (or the regulator) recalls a batch, you need the answer in minutes: which batches you received, from which invoice, how many sold, to which customers if records allow, and how many remain, then the ability to flag remaining units so they cannot bill. Test this exact scenario in any demo before you buy. A vendor who improvises the answer is showing you your next crisis.
3. Compliance fields on the invoice
Drug license number, pharmacist details where required, batch and expiry printed per medicine line, controlled-item rules enforced at billing (schedule-wise sale limits and register entries where regulation demands). These are features to configure once and audit monthly, and they are the difference between a pharmacy system and a grocery system wearing a white coat.
The counter workflow that saves lives and margins
| Moment | What the POS should do | Failure mode without it |
|---|---|---|
| Prescription billed | Batch selection auto-FEFO, expiry printed on receipt | Oldest stock stays behind; expires |
| Brand unavailable | Suggest alternative brands with price and salt composition | Lost sale or wrong substitution |
| Supplier invoice arrives | Scan batch + expiry at purchase entry (or import) | Batches enter stock blind |
| Recall notice received | Filter stock by supplier + batch, flag remaining units | Hand-shelf search for hours |
| Month-end audit | Near-expiry report + slow-mover report per category | Silent expiry losses discovered late |
Daily and monthly routine
- Morning (5 min): near-expiry report (this month + next 60 days), low-stock per essential list, items on order vs supplier lead times.
- Every purchase entry: batch + expiry + cost price, no exceptions, no "we'll fix it later".
- Weekly: category-level dead stock (expired-never-sold candidates) and discount decisions before expiry, not after.
- Monthly: full expiry audit with the printable sheet (this guide's free resource), supplier-wise purchase review, and margin check on your 50 fastest movers.
- On every recall: the traceability drill: minutes, not days.
What about pricing and "cheap" pharmacy software?
Pharmacy-grade batch management is where most cheap systems quietly fail: they keep a total quantity but not per-batch detail, or expiry lives in a spreadsheet next door. MrPOS Retail prices the complete platform at PKR 5,000/month or PKR 30,000 lifetime (~$108): batch tracking, recalls, reports and credit ledger included, no per-feature unlocks. Compare that against the cost of one month of unnoticed expiry losses across a 2,000-item pharmacy and the decision usually makes itself. The general upgrade math (register vs POS leaks) is the same as any retail: see POS vs cash register.
Vendor questions that expose weak batch support
- "Show me a stock card with 4 batches and different expiries, how does the counter pick?"
- "A supplier recalls one batch: walk me through finding sold vs remaining units."
- "Where does expiry print, on the receipt line or not at all?"
- "Show the near-expiry report with discount-marking in one click."
- "How do purchase entries capture batch and expiry: manual typing or scan/import?"
Five crisp answers mean the vendor has real pharmacy deployments. Hesitation anywhere means the demo was grocery software with a pharmacy name on the box.
Frequently asked questions
What is FEFO in pharmacy POS?
First-Expiry-First-Out: the counter dispenses the batch expiring earliest first. A POS with batch logic picks FEFO automatically and prints batch/expiry on the receipt.
How does a POS help with medicine recalls?
With batch + supplier traceability, you filter your stock by the recalled batch, see what was sold and what remains, and flag remaining units so they cannot be billed: minutes instead of shelf-by-shelf searching.
Do pharmacies need batch tracking by law?
Requirements vary by jurisdiction, but traceability is the professional standard everywhere, and regulators increasingly expect it. Even where not strictly mandated, recall readiness protects patients and your license.
What does pharmacy POS software cost in Pakistan?
Complete platforms like MrPOS Retail run PKR 5,000/month or PKR 30,000 lifetime (~$108), with batch/expiry, recalls and reports included. Beware cheaper tools that lack true per-batch stock.
Can pharmacy POS suggest alternative brands?
Yes. MrPOS suggests alternatives by salt composition with prices, so the counter can offer a substitute instead of losing the sale.
Next step: see it on your own data
MrPOS offers a free live demo (no card required): setup typically completes in one day, including data import. WhatsApp us at 0316 6132742 or message us for a free demo.
Explore the products: MrPOS ERP · MrPOS Retail · MrPOS RMS, or use the Your Number calculator to estimate how much your current setup is leaking.