A pharmacy owner in Surat handed back a strip of a popular branded antibiotic last quarter because the hologram "felt off." The distributor argued. The owner held firm. Lab testing later confirmed the batch was adulterated. That owner avoided a potential drug-safety complaint, a possible licence suspension, and a fine that runs from ₹1 lakh to ₹10 lakh under Section 27 of the Drugs and Cosmetics Act. What he did not avoid was the two hours he spent that afternoon manually cross-referencing batch numbers against a printed CDSCO alert list that was already six weeks out of date.
Most retail counters in India have no live connection to CDSCO's spurious and not-of-standard-quality drug alerts. They rely on distributor assurances, paper records, and occasional WhatsApp forwards from trade associations. That gap — between what a licence holder is legally expected to catch and what a counter can practically check — is where counterfeit medicine India risk actually lives.
If you are reading this because a suspicious strip has already crossed your counter, or because a distributor is pushing unfamiliar brands at suspiciously low margins, the rest of this post is for you. The cost of doing nothing here is not just a fine. It is your licence.
The Batch Verification Problem Nobody Talks About Honestly
A distributor in Pune walks in with 200 units of a Schedule H antibiotic at 18% below the MRP you normally see. You check the packaging. The batch number looks right. The expiry is 14 months out. The hologram is present. You bill it.
Three weeks later, CDSCO publishes an alert — the batch number on that exact SKU was flagged as spurious drugs pharmacy-level action required. You now have 140 units in stock, 60 already dispensed. Under the D&C Rules (Rule 65), your Schedule H register must record every purchase and sale with batch detail, retained for three years. If an inspector walks in, the register is the first document they pull.
The problem is not that pharmacists are careless. The problem is that batch verification pharmacy workflows in India were designed for a paper era. Checking the CDSCO alerts portal manually — which is a public URL — takes four to six minutes per alert bulletin, and new bulletins appear without push notification. A pharmacy stocking 800 to 1,200 SKUs cannot realistically cross-reference every incoming batch against a live government list using a printed sheet or a WhatsApp group.
- CDSCO publishes alerts for adulterated, spurious, and not-of-standard-quality drugs at cdsco.gov.in, but there is no automated alert to pharmacy licence holders.
- The D&C Act §27 fine for stocking or selling spurious drugs is ₹1 lakh to ₹10 lakh per offence — not per batch, per offence.
- A single Schedule H1 register violation (missing batch entry, wrong date) can draw an inspection even when the medicine itself is genuine.
The regulatory expectation and the operational reality are far apart. That distance is where liability accumulates.
What a Counter Can Actually Catch — and What It Cannot
A trained pharmacist at the counter can catch certain physical markers: broken holograms, blurred print on foil, mismatch between batch number on the outer carton and the blister, abnormal tablet colour or smell on visual inspection. These are real catches. They happen.
What a counter cannot catch without system support: whether the batch number on an otherwise perfect-looking strip has already been flagged in a CDSCO alert issued 11 days ago; whether the same batch number is appearing across two different distributors in your city (a classic indicator of a counterfeit run); whether the MRP printed on the pack matches the current registered price for that formulation.
Industry estimates — based on pharmacy trade body surveys, not our own data — suggest that between 0.5% and 2% of medicines reaching retail in tier-2 and tier-3 Indian cities may have some form of quality or authenticity irregularity. That range is wide because good data is scarce, but even the lower end matters when you are stocking 1,000 SKUs and dispensing 80 to 120 strips daily.
The gap between physical checks and database-backed checks is not a training problem. It is an infrastructure problem. Most pharmacy software running Windows desktop applications — common across markets like Marg (per publicly listed features on Marg's website as of April 2026) — does not natively connect batch data to live regulatory alert feeds.
The Register Risk Nobody Prices Into Their Operations
A neighbourhood pharmacy in Thane was inspected after a patient complaint unrelated to spurious stock. The inspector's first action was to pull the Schedule H and H1 registers. Three entries had batch numbers that did not match the purchase invoices on file — a data entry error, not fraud, but indistinguishable from fraud on paper.
The pharmacy owner spent fourteen hours over two weeks reconstructing records, hiring a consultant at ₹4,500 per day, and appearing at the licensing office twice. The fine was avoided. The time was not recovered.
Under D&C Rules Rule 65, Schedule H1 registers must be maintained with purchase date, supplier name, batch number, expiry, quantity received, and quantity dispensed — and retained for three years. Getting this right manually across 300 to 500 Schedule H and H1 movements per month is a real operational cost. Getting it wrong is a liability that compounds.
The financial exposure here is not hypothetical. The ₹1 lakh floor on D&C Act §27 penalties is a statutory number. The real cost — legal fees, inspection response time, potential licence suspension — typically runs higher.
What Operations Look Like When the Verification Gap Closes
| Before | After |
|---|
| Batch numbers entered manually into a paper register or basic billing software | Every purchase entry auto-populates the Schedule H/H1 register with batch, expiry, supplier, and quantity |
| CDSCO alerts checked sporadically via manual portal visits | Incoming batch data cross-referenced against a regularly updated alert database at the point of entry |
| Suspicious strips identified only by physical inspection | Batch flagged at billing stage if the SKU-batch combination appears in the alert database |
| Register reconstruction during inspections is a multi-day exercise | Register is always current, exportable, and audit-ready |
When the verification infrastructure is in place, a pharmacist can focus physical inspection energy where it belongs — on the actual strip in hand — rather than on manual cross-checking that a system can do faster and without error.
The day-in-the-life shift is concrete: a consignment arrives at 10 AM from a C&F agent. The pharmacist scans or enters the batch number. The system flags one SKU against a known alert. The pharmacist calls the distributor before the stock is even shelved. The distributor replaces it. Nothing spurious enters the dispensing cycle. The Schedule H1 entry is complete, timestamped, and linked to the purchase record.
That is not a fantasy workflow. It is what happens when batch data and regulatory alert data are in the same place.
How Pharmacies Running Nesayo Handle This in Practice
Nesayo's medicine database carries 253,973 medicines indexed by composition, schedule, HSN code (HSN 3004 for finished pharmaceuticals), and batch-level attributes. When a pharmacist in Chennai enters a purchase — by voice, in Tamil, using Nesayo's voice billing — the batch number is recorded against the Schedule H or H1 register automatically. The register entry is not a separate step. It is the same action as the purchase entry.
The Expiry Guard agent (one of Nesayo's five AI agents, available on the AI Employee plan at ₹999 per month as of 2026-08-25; see current pricing at nesayo.com/pricing) monitors every batch in stock against expiry windows and surfaces alerts in the Morning Briefing each day. A pharmacist in Nagpur described it this way: the morning briefing tells them which batches are within 45 days of expiry, which purchase entries are missing batch detail, and which SKUs have had recent regulatory attention — before the shutter is fully up.
The FEFO (first-expiry, first-out) batch selection means that when two batches of the same SKU are in stock, Nesayo bills from the earlier-expiry batch automatically. This is not just good practice for wastage; it is directly relevant to spurious stock management, because older batches from suspect consignments do not sit quietly at the back of the shelf.
Billing itself is free, permanently, with no cap on invoices or SKUs (as of 2026-08-25; see nesayo.com/pricing for the current plan structure). The Schedule H1 register auto-population is part of the billing layer, not an add-on. Pharmacies that want the AI agents — Morning Briefing, Expiry Guard, Refill Radar, Stock Sense, Payment Advisor — move to the Starter plan at ₹399 per month or the AI Employee plan at ₹999 per month (prices as of 2026-08-25; nesayo.com/pricing).
For prescription intake, the AI Vision prescription scan reads handwritten scripts and maps medicines to the 253,973-medicine database, reducing the chance that a look-alike brand name slips through as a genuine product.
The Choice in Front of You Right Now
If you do nothing, your counter continues to rely on physical inspection, distributor assurance, and a paper register that is one rushed entry away from a compliance gap. The next CDSCO alert may or may not match something in your current stock. You will not know until someone tells you — or until an inspector asks.
If you put the right infrastructure in place, the batch data is always current, the register is always complete, and the flagging happens at the point of entry rather than after the strip is dispensed.
Spend 2 minutes at nesayo.com/demo — real pharmacy data is pre-loaded, no signup required. You can see exactly what your Schedule H1 register would look like, and what the Expiry Guard agent surfaces on a typical morning. No form to fill. No sales call triggered. Just the actual product, with your category of pharmacy data already in it.
FAQ
Will migrating to a new system mean I lose my existing purchase and sales history?
Nesayo accepts a CSV export from most billing software currently used in Indian retail pharmacies. Your historical data — purchase records, batch entries, customer ledgers — can be imported before you bill your first transaction on Nesayo. Nothing is deleted from your existing system; you keep both until you are confident. The migration is not instantaneous, but it is not a multi-week project either. Most pharmacies are billing on Nesayo within one working day of the data import.
My staff handles billing, and they are not comfortable with new software. What happens during an internet outage?
Nesayo runs as a Progressive Web App (PWA), which means it continues to function offline and syncs when connectivity returns. Staff who are used to voice-based workflows can bill in any of 10 Indian languages by speaking the medicine name — the system resolves it against the 253,973-medicine database. For staff who prefer typing, the interface is the same as any standard billing screen. Training time for a typical counter staff member is typically under two hours, based on onboarding data from pharmacies already using the system.
Can I really trust an AI system to catch counterfeit or spurious stock — isn't that a job for a trained pharmacist?
Yes, it is a job for a trained pharmacist — and