Pharmacy & Dispensary Management

ECOSIRE builds a dedicated Frappe app — a proper installed app with its own module, DocTypes, hooks.py doc events, server scripts, client scripts, and scheduler jobs — that layers pharmacy operations on top of ERPNext's native stock and selling engine rather than replacing it. We add a Drug Master DocType (generic/molecule name, brand names, strength, dosage form, schedule/controlled-drug flag, default pack size) linked to ERPNext Item, a Prescription DocType with dispensing lines, and a dispensing workflow that reserves stock by batch using FEFO. Every dispense and sale is validated on server-side validate and on_submit doc events registered through hooks.py: expired or near-expiry batches are blocked or flagged, controlled-substance lines require a prescriber and quantity check, and the batch actually consumed is written back so the Stock Ledger stays truthful.

At the counter, a client script on the POS/Sales Invoice form turns barcode input into a fast add-to-cart with automatic batch selection, so cashiers scan and bill without hunting through dropdowns. A scheduler_events hook runs a daily job that scans batches for near-expiry and items below reorder level, then raises ERPNext Notifications and a dashboard report for the pharmacy manager. Role profiles and permission rules separate the pharmacist, cashier, and store-manager roles so controlled-drug actions and cost visibility are scoped correctly. Everything is reachable through the Frappe REST API and a small set of @frappe.whitelist() methods, so a front-end scanner app, a mobile counter, or a hospital HIS can drive dispensing programmatically.

Because this is built specifically for how your pharmacy or chain actually works, we start with a short scoping call, confirm the DocType fields, dispensing rules, tax/label format, and roles in writing, then build against Frappe/ERPNext v15 or v16. Typical delivery is 2 to 4 weeks from confirmed scope. We install the app on a staging bench, run UAT with your real drug list and a few live prescriptions, then cut over to production with a rollback plan and hand over the git repository. This is a build-to-order engagement — not an instant marketplace download — so what ships matches your workflow instead of forcing your counter into a generic template.