Quantity is the wrong unit
Track a product and you know a number. Track a batch and you know a number with a date and an origin attached, which is the only form in which the number is useful. Forty units expiring across three different months is four different commercial situations depending on how they are distributed.
Expiry is the loss that makes this concrete. It is not a risk; it is a certainty on a known date, and the only question is whether you see it in time to sell the stock, return it or move it. Seen three months out it is a decision. Seen at the counter it is a write-off.
Then there is the part retail does not have at all: dispensing records. What was dispensed, against what, by which member of staff. That is a record the Pharmacy and Poisons Board expects, and it is far easier to produce as a by-product of serving customers than to assemble afterwards.
Want to see it running in your own business first?
Sign UpWhat to put in place
Five things, in the order they pay back.
- 1
Capture the batch and expiry at receiving
This is the step everything else depends on and the one most often skipped because it slows the delivery down. Stock received without its batch cannot be tracked by batch later, no matter what the system is capable of.
- 2
Deduct on the sale, automatically
A figure typed in by a person is right on the day it was typed. A figure that moves with each sale is right continuously, which is what makes the expiry warning meaningful: what stock software has to do.
- 3
Set the warning window to your return terms
If a supplier takes returns up to three months before expiry, a warning at four weeks is a warning that arrives after the option has closed. The window should be set by what you can still do about it.
- 4
Sell the oldest batch first, and make it the default
First-expiry-first-out is the rule, and it only holds if the system puts the right batch in front of the person serving. Left to the shelf, the newest delivery goes at the front.
- 5
Count in sections, while trading
A full annual count tells you something went wrong in twelve months. A section counted weekly tells you what went wrong in a week, to someone who still remembers it: pharmacy POS.
Where pharmacy stock control fails
Running expiry on a spreadsheet beside the POS
It is accurate for as long as someone maintains it, which is until the shop gets busy. That is the same weakness as counting by hand, moved to a different file.
Tracking the product, not the batch
A single expiry date per product is wrong the moment the second delivery arrives, and it is wrong in the direction that lets stock expire quietly.
Receiving stock without checking it in
Goods on the shelf that were never received are stock the system does not know about, and the variance they create looks exactly like theft.
Treating a variance as a typing error
The gap is the finding. A recurring variance on one line is breakage, mis-receiving, a pricing error or theft, and correcting the number discards the only evidence of which.
Ordering by looking at the shelf
Gaps show you what ran out, including lines that ran out because you only ever had two. Order from what sells, not from what is missing.
A worked example: the twelve units nobody saw
A pharmacy in Mombasa held a slow-moving but valuable line, reordered occasionally, with stock usually sitting several months. The system tracked quantity and the owner knew roughly what was there.
Three deliveries across a year meant three batches on the shelf, with expiry dates five months apart. Staff served from the front, which is where the most recent delivery had been put.
Twelve units from the oldest batch expired on the shelf behind the newer stock. The system had shown a healthy quantity throughout and had been correct about it. What it could not show was that part of that quantity had a date on it, and by the time anyone looked, the supplier return window had closed months earlier.
Stock you cannot see is stock you lose: dead capital sitting on slow shelves, empty shelves on your fast movers, and shrinkage no one can explain.
Veira tracks every item in and out with reorder alerts, so you hold the right stock and losses surface early.
How Veira handles it
Veira holds stock by batch with expiry dates captured at receiving, and deducts on the sale, so the count stays current without anyone maintaining it. Lines approaching expiry surface as a warning rather than as a discovery.
Each member of staff signs in as themselves, so dispensing records name a person as a by-product of serving customers rather than as a separate log.
And selling continues when the connection does not, which for a pharmacy is not a convenience: you cannot stop dispensing while a network comes back, and the eTIMS invoices queue and transmit on reconnect rather than being skipped.
Frequently asked questions
Why track by batch rather than by product?
How far ahead should the expiry warning be?
How often should a pharmacy count?
Can I manage expiry on a spreadsheet?
What dispensing records are expected?
What should I do about a recurring variance?
A pharmacy's stock problem is a dates problem wearing a quantities costume. Capture the batch at receiving, let the figure move with the sale, set the warning window to what you can still act on, and count in sections while the answers are still findable.
Need help, or want to talk it through first? Chat with us on WhatsApp