Hospital and retail pharmacies live in the gap between a prescription and a dispensed pack. Odoo core gives you product, stock, lots and expiry dates, and account for invoicing — but it has no concept of a formulary, no prescription-to-dispense workflow, no drug-drug or allergy checking at the point of dispense, and no controlled-substance balance register. Pharmacists end up keying quantities into a sales order, tracking expiry on spreadsheets, and reconciling narcotics by hand. Out of the box, stock picks by whatever removal strategy is configured; it does not reason about "dispense the earliest-expiring lot for this Rx line and warn me about the interaction with the patient's other active medication." That clinical layer is exactly where native runs out of road.

We build a dedicated Clinical Pharmacy Dispensing module on top of your existing Odoo. A new pharmacy.formulary model maps generic to brand, strength, dosage form, and price, linked to product.product so every dispensable item stays a real stock-tracked product with a unit of measure from uom. Prescriptions flow in from the EMR: the module reads Rx lines from clinical-core-his-emr and opens a pharmacy.dispense document pre-filled with drug, quantity, and dosage instructions. A @api.depends-driven compute proposes lots by FEFO — earliest expiration_date first — using Odoo's native lot/serial tracking so stock stays accurate and traceable. At dispense time an automated check runs drug-drug and allergy rules against the patient's active medication and allergy list, surfacing alerts the pharmacist must acknowledge before confirming. Confirming the dispense posts the stock move (automatic deduction), triggers the reorder-point logic per drug, and generates a QWeb drug label with dosage instructions ready for the counter printer.

The workflow handles the messy reality of a pharmacy counter, not just the happy path. Partial dispense and generic substitution are first-class: a pharmacist can dispense part of an Rx line, swap a brand for an approved generic from the formulary, and the module tracks remaining refills so the next visit knows what is left. Regulated drugs post to a pharmacy.controlled.register with a running balance log — every issue and receipt writes an immutable ledger row for inspection. Billing is flexible: a counter dispense either posts to the patient's account.move invoice for hospital in-patients or rings up as a walk-in sale, respecting your existing chart of accounts and tax configuration. Security is enforced with ir.model.access.csv plus record rules so pharmacy technicians, pharmacists, and auditors see only what their role allows, and near-expiry and slow-moving stock reports give the pharmacy in-charge a weekly view of what to return or discount before it dies on the shelf. Everything is reachable over the standard XML-RPC / JSON-RPC API for integration with external label printers or POS hardware, and the build targets Odoo 17.0, 18.0, and 19.0 on Community or Enterprise (Enterprise adds native studio/e-sign niceties we wire to where relevant).

Because this is build-to-order, nothing ships until we agree the scope. We start with a short scoping call, confirm which formulary structure, interaction ruleset, controlled-substance regulations, and billing flow apply to your pharmacy, then build on a staging environment you can test against real prescriptions. Typical delivery is one working week from confirmed scope; you get UAT on staging, a rollback plan, and a defined go-live. Pricing starts from $999 (indicative, single-company base scope); multi-company or multi-branch pharmacy networks, deeper localization of controlled-substance reporting, and the volume of legacy drug/stock data to migrate increase the quoted scope.