Nesayo’s Chain plan costs ₹3,998/month for 2 pharmacies (as of October 2026); stock transfers require the Chain plan at both stores. It adds ₹999 per additional pharmacy each month. Running two pharmacies is not running one twice. The billing screen is the same; the catalogue, the transfers, the registrations and who may do what at which branch are not.
Last reviewed 2026-10-14
Stock sits in the wrong branch. Each shop numbers its bills from one, so two invoices carry the same number. The day's figure arrives as three WhatsApp messages at night, one of them a guess.
Chain software is judged on different questions: whether the group can add its stores up at all, whether stock can move between them with a trail, whether each registration files its own return, and who may do what at which branch. This page takes those in order, with the arithmetic against a competitor whose published prices are cheaper than ours at every multi-store count.
One thing first, because it goes wrong quietly: a login shared by whoever is at the counter must never become the account that controls the whole group.
Every store starts from the same canonical catalogue — 2,54,034 medicines with schedule flags, HSN and pack data. The divergence is what each branch adds: one pharmacist enters Liv 52 Tablet, another types LIV-52 tab. Both are right at the counter, and no computer comparing strings can add them — which is all a group stock report is.
Two designs, a genuine choice. An enforced group item master codes every product centrally: nothing sells until head office has coded it. Or each store adds what it needs and the group matches afterwards: never blocks a branch, and loose names weaken your reports.
Nesayo takes the second. A medicine resolving to the canonical catalogue rolls up on that identity; otherwise stores match on a normalised name key, which collapses Liv 52 Tablet and LIV-52 tab into one row while keeping PAN 20MG and PAN 40MG apart.
Every chain moves stock between branches on a phone call and a scrap of paper. That works until somebody asks where forty strips went. The trail is not about mistrust: stock that left one shop and never arrived belongs on the books somewhere, a Schedule H1 pack has to be traceable, and a short count is unarguable without a record of who sent it.
Stores in different states hold different registrations, and each files its own return. A chain report adding every shop's sales into one figure is a management number, not a filing.
Each store's invoice series must be its own — consecutive, unbroken, never colliding with another branch's: two shops issuing the same number is two documents claiming to be one. And the registration on an invoice is the one in force when it was issued, not today's settings screen.
Nesayo keeps one series per store and groups the consolidated return by the registration each invoice was issued under, so three registrations give three returns, not one wrong one. If a store issued invoices under two registrations inside a month, we refuse to build a single return and we name the store.
Rates belong to the product, not the branch, so one flat rate across a catalogue files wrong at every store at once — and a group finds out later than a single shop, because nobody reads each branch's return line by line. Slab detail is on the buyer's guide; figures here are for reference; your CA should check any return before filing.
Owners phone each branch at closing because the alternative is five logins opened one at a time. The console has to answer on one screen:
Cost comes from the purchase price on the batch sold. If a branch imported its opening stock with no purchase prices, its margin is not low — it is unknown, and our reports name those stores rather than print a confident blank.
With branches the question is enumerable: may this person do this thing at this shop?
Four store roles. Owner holds everything, including the group's money controls. Manager runs a branch — billing, stock, purchases, reports, stock counts, transfers and the ordinary exports — without the group's settings. Pharmacist and staff cover counter work. Above them sits a group-level role, org admin, who can resolve a transfer discrepancy and send goods back to source — know it exists before handing it out.
Anything not listed is owner-only, so a capability nobody has decided about never defaults to "anyone in the shop". Committing the shop to buy is its own permission, separate from the purchase screens — only one of those is money owed. And the full customer contact list is owner-only even though a manager can pull invoice, expense and stock reports, because under the DPDP Act the pharmacy answers for that file.
There is no dispensing permission, and there should not be one. An account role is not a State Pharmacy Council registration. Confirming a Schedule H or H1 sale stays with the named pharmacist — the name a drug inspector reads in the register. See how the H1 register gets filled.
Most single pharmacies have one login everyone at the counter uses: a shop credential, not a person, often written on a note under the till. Older ones can be worse — a session created before a system recorded which individual signed in identifies nobody at all. Convert that shop into a group, and if the software promotes whichever session clicked the button, the account that can add stores, invite staff, approve transfers and pull the group's numbers is a credential half your staff already know.
Ask any vendor, ourselves included: when my shop becomes a group, which login becomes the owner, and what happens to the one my staff share?
Nesayo, as of October 2026:
BitMed publishes ₹1,999 per month for up to three stores and ₹3,999 per month for unlimited stores (per bitmed.in, read 6 September 2026). At two stores that is ₹1,999 against our ₹3,998; at three, ₹1,999 against ₹4,997; at four and above, their ₹3,999 unlimited tier against our ₹5,996 and ₹6,995.
They are cheaper at every multi-store count, and our own comparison post says so. If the monthly figure decides it, that is a real answer and it is not us. Beyond price, weigh whether transfers carry an approval trail and whether the consolidated return splits by registration.
Part of this market is not ours; pretending otherwise wastes your time. Buy something heavier if:
By about thirty stores, most groups have someone whose job is the software, and the deciding cost becomes the implementation, not the monthly figure. We are built for the owner still standing in one of the shops: two to roughly twenty branches, no IT department.
Software that runs several pharmacy branches as one group: a shared catalogue, stock visible across stores, transfers between them, consolidated reporting, and staff roles deciding who may do what at which branch. Each store still keeps its own Schedule H1 register.
Compare on your actual store count. Nesayo's Chain plan is ₹2,999 per month as of October 2026, plus ₹999 per extra pharmacy, so two stores is ₹3,998 and three is ₹4,997. BitMed publishes ₹1,999 per month for up to three stores and ₹3,999 per month for unlimited stores (per bitmed.in, read 6 September 2026), which is less than ours at every multi-store count. Nesayo billing is free forever at every store.
It should, and for stores in different states it must. Each store needs its own consecutive invoice series that never collides with another branch's, and the consolidated return has to be grouped by the registration each invoice was actually issued under.
Legally you are moving stock between two of your own licensed premises, so this is a records question. In Nesayo a manager cannot approve their own request — the approver has to be a different identified person, and approval comes from the branch the stock is leaving. The group owner is the one exception — the rule exists so an owner can trust staff, so enforcing it against the owner protects nobody — and that transfer is marked self-approved on the record.
Only if you give them that. A manager runs their own branch without the group's settings or money controls, and anything the permissions table does not explicitly grant is owner-only.
On Nesayo it cannot become the group owner. A session that cannot identify an individual is refused from the ownership flow, only the store's owner may hold the address receiving the group's confirmation codes, and converting a shop signs its other devices out first — if that fails, the group is not created.
Anything that resolves to our canonical medicine catalogue is matched on that identity, so spelling stops mattering. Names a store added itself are matched on a normalised key that collapses Liv 52 Tablet and LIV-52 tab into one row while keeping PAN 20MG and PAN 40MG apart.
Billing is free forever at every branch, with Schedule H1 sale logging and expiry blocking included. Add the Chain layer when the branches are actually on it.
Start free →