Running a pharmacy on stock ERPNext means fighting the checkout instead of using it. The standard POS Profile does not enforce First-Expiry-First-Out, so counter staff can dispense a longer-dated batch while a near-expiry pack quietly ages into a write-off. There is no place to record who wrote the prescription, how many refills remain, or which schedule a controlled drug belongs to. Insurance claim references live in spreadsheets or the customer's memory. ERPNext gives you Item, Batch, Stock Ledger and Sales Invoice — a solid foundation — but the dispensing layer that a compliant pharmacy actually needs is simply not in the box, and bolting it on with a few Custom Fields never covers batch logic, refill state or an audit trail.

ECOSIRE builds this as a proper Frappe app installed into your ERPNext bench — not a themed spreadsheet and not a fork of core. We add first-class DocTypes such as Prescription, Dispense Entry, Refill Schedule and Controlled Drug Log, each with its own permissions, and we ship a custom POS screen (a Page/Portal or a POS Profile extension, chosen to fit your workflow) that suggests batches in true FEFO order using the Batch expiry_date. Dispensing quantity, batch and expiry are validated server-side inside hooks.py doc_events (before_submit/on_submit on Sales Invoice and Stock Entry) so the rule holds no matter whether the sale comes from the counter, the REST API or a bulk import — validation never lives only in the browser.

Technically, the substitute-suggestion engine is a whitelisted server method (@frappe.whitelist()) that reads a generic/molecule link field on the Item and returns in-stock alternatives with live batch availability, called from a Client Script on the POS screen. Controlled-drug schedules are captured on submit and written to an immutable log with the dispensing pharmacist, quantity and running balance. A scheduler_events hook runs a daily job to flag batches inside your configurable expiry window and to surface refills that are due, so near-expiry stock and lapsed patients are worked proactively rather than discovered at the till. Role Profiles and permission rules separate the counter cashier, the dispensing pharmacist and the manager who can void or adjust controlled entries. Everything targets ERPNext/Frappe v15 and v16 and is delivered as versioned, migratable source with fixtures.

Because this is build-to-order, nothing is auto-provisioned and there is no instant download. We start with a short scoping call to confirm your dispensing rules, controlled-drug schedules, insurance fields and reporting needs, then build against a staging bench, run UAT with your team, and cut over on a scheduled go-live. Typical delivery is one working week from confirmed scope. You receive the full git repository, install and configuration on your environment, technical and user documentation, a training session, and a post-go-live support window — you own the code and can host it anywhere ERPNext runs.