Picture a pharmacist running a busy counter in Shyambazar who types a customer's name in English, hunts for the Bengali medicine nickname in a dropdown built for Delhi, and misses entering the batch number entirely. That one slip — repeated across 40 invoices a day — leaves the Schedule H1 register incomplete for three consecutive months, until a Drug Inspector walks in for a routine check. The register was right there on paper. The software just never asked for it in a way his counter staff could work with confidently.
That is the quiet cost of running a Kolkata pharmacy on billing software designed for a North Indian workflow. This post names that cost — in hours and in compliance risk — and shows what the counter looks like when the software fits the way a Bengali counter works.
If you keep billing the way you are today, you are almost certainly leaving money on the table and accumulating regulatory exposure you cannot see until an inspector arrives. That is what this post is about.
The Hidden Cost of English-Typing Billing at a Bengali Counter
A customer in Gariahat asks for "Crocin" but your counter boy types "Paracetamol 500 mg" — or forgets to type anything and hands it over anyway, billing it as a miscellaneous line. Every one of those lines is revenue that either disappears into manual correction time or never gets reconciled at all.
The problem is not that your staff cannot do the job. The problem is that a lot of billing software was built assuming the person at the counter thinks and speaks in Hindi. In West Bengal pharmacy counters, the working language is Bengali. When the software and the worker operate in different languages, micro-errors compound silently.
The annual cost is not dramatic in any single transaction. It is a mislabelled line here, a missed batch entry there, a duplicate invoice corrected by hand at 10 PM. Over twelve months, that friction is worth far more than most owners calculate.
Incomplete Schedule H1 Registers and the Compliance Exposure That Follows
Rule 65(3)(h) of the Drugs and Cosmetics Rules requires every pharmacy to enter each Schedule H1 supply in a separate register — the prescriber's name and address, the patient's name, the drug and its quantity — kept for three years. Selling a Schedule H1 drug without a prescription is punishable under Section 27(d) of the Drugs and Cosmetics Act, 1940: imprisonment of one to two years and a fine of not less than ₹20,000.
Here is what typically goes wrong at a Bengali-medium counter: the staff member receives a verbal prescription for a Schedule H1 drug, looks at a software interface in English or Hindi, hesitates on which field to fill, and either leaves the prescriber field blank or enters it incorrectly. This is not negligence — it is a language mismatch producing a compliance gap.
The risks compound across a year:
- Incomplete H1 entries across hundreds of invoices
- No automatic alert that a controlled medicine was billed without a valid register entry
- Manual audits required before every inspection, eating into the owner's time every quarter
A reminder nobody reads in the moment does not help. The check has to be part of the bill itself.
GST Filing Friction When Medicine HSN Codes Are Guesswork
Most medicines classified under HSN 3004 attract GST at 5% (from 22 September 2025, after the 56th GST Council meeting). That is a clear rule. The execution at the counter level is often anything but clear, especially when a pharmacist in Howrah is billing 150 SKUs a day on software that does not fill the HSN code at the point of sale.
When a counter staff member is unsure whether a particular Ayurvedic formulation or combination product falls under HSN 3004 at 5% or a different code, they either guess or leave it for the owner to sort out during the monthly GST return. A single misclassified batch of 200 units billed at the wrong GST rate generates a discrepancy that surfaces during reconciliation — if it surfaces at all. Owners who file their own returns end up correcting exactly this kind of invoice-level mismatch every month.
DPDPA 2023 adds another layer: patient prescription data that flows through billing software must be handled with basic data protection discipline. If your current system is storing patient names and prescription details in an unencrypted local database on a Windows desktop, you are carrying a compliance liability that many owners have not yet priced into their risk calculation.
What a Bengali-Language Counter Looks Like When the Friction Is Gone
The before picture is familiar: a queue of six customers, a staff member squinting at an English dropdown, an owner on the phone with the accountant about last month's GST mismatch, and a Schedule H1 register that is two weeks behind.
The after picture is specific. Here is a side-by-side of the same counter:
| Moment | Before | After |
|---|
| Customer asks for medicine by name | Staff types phonetic English, finds wrong SKU | Staff says the name aloud; voice billing matches it against the shop's shelf and a catalogue of more than 2.5 lakh medicines |
| Schedule H1 drug billed | Field often left incomplete | Sale logged at billing (patient, prescriber, medicine, batch, quantity); the pharmacist adds the prescriber's address |
| End of day GST reconciliation | Manual check at day's end | HSN and GST filled at billing; reports built from the bills |
| Monthly expiry check | Owner walks the shelf with a notebook | Expiry Guard agent flags approaching batches before the morning shift starts |
The owner is not doing anything heroic. The software is doing the work it should have been doing all along.
How Nesayo's Voice Billing Works at a Kolkata Counter
Nesayo runs as a Progressive Web App, so counter staff with no software training beyond basic mobile use can start on a phone or any computer. On the paid plans, voice billing (beta) works in Hindi and English today; Bengali is not supported yet. It matches spoken brand names against the shop's own shelf and a catalogue of more than 2.5 lakh medicines that includes both branded names and generic alternatives, plus Ayurvedic therapeutic alternatives where applicable.
Schedule H1 sales are logged automatically at billing: date, medicine, batch, quantity and bill number, with the patient and prescriber names entered on the bill. Nesayo does not record the prescriber's address yet, so the pharmacist adds it to complete the Rule 65(3)(h) register. On the Full plan, the Expiry Guard agent flags batches entering the 30-day expiry window, so the owner can review them on a mobile screen before unlocking the shutter.
The five AI agents — Morning Briefing, Expiry Guard, Refill Radar, Stock Sense, and Payment Advisor — are on the Full plan at ₹549/month as of October 2026 (see current pricing at https://nesayo.com/pricing), which also includes a Tally export file (no live integration bridge). The Essential plan at ₹249/month adds voice billing, prescription scanning and Refill Radar. Billing itself is free, permanently, with no invoice cap. Prescription scanning reads a handwritten prescription and queues the medicines for the pharmacist to confirm.
The Choice in Front of You Right Now
If you keep the current setup, the language friction at your counter continues to generate billing errors, H1 gaps, and GST mismatches at a rate you cannot see clearly because no one is measuring it. The Drug Inspector visit is not a hypothetical — it is a routine enforcement mechanism that becomes relevant the moment your register has a visible gap. On the other hand, trying voice billing costs nothing — new pharmacies get the Full plan free for their first month, with no card — and ₹549 a month (as of October 2026) if you want every AI agent working your inventory while you sleep.
Go to https://nesayo.com/demo right now — a sample pharmacy is pre-loaded, no signup required. Bill three medicines your counter sells every day and see whether the catalogue knows the names, and how a Schedule H1 sale is logged. The whole test takes under two minutes.
FAQ
Will I lose my existing data when I migrate to Nesayo?
No data migration is required to start. You can begin billing on Nesayo from day one while your historical data remains in your existing system. If you want to bring your stock across, Nesayo's onboarding team works through a CSV or Excel import with you, free. Your old system does not need to be switched off immediately.
What happens if the internet goes down mid-billing?
Nesayo is built as a Progressive Web App with offline billing capability. If your connection drops, the counter keeps billing locally and the invoices sync when connectivity returns — keep the billing page open until it does. Your staff does not need to stop, switch to paper, or call anyone. This is the primary reason we built PWA rather than a browser-only tool — counter uptime cannot depend on BSNL or Jio being stable at 6 PM on a Saturday.
What is the catch with free billing — will the price change later?
Billing is free with no invoice cap, and that is a stated product commitment, not a trial period (see https://nesayo.com/pricing for current terms as of October 2026). The paid plans (Essential at ₹249/month, Full at ₹549/month, Chain at ₹2,999/month + ₹999/month per additional pharmacy, all as of October 2026 per https://nesayo.com/pricing) are for voice billing, prescription scanning and the AI agents that run inventory intelligence, expiry alerts, refill prediction, and payment follow-up. If you only need billing, GST invoices, FEFO batch selection and Schedule H1 logging at billing, you pay nothing; voice billing starts with Essential, and new pharmacies get the Full plan free for their first month, with no card. The AI features are where the rupee value is for a busy Kolkata pharmacy — but that choice is yours to make after you have seen the billing layer work.