Retail pharmacies live and die by traceability, yet Odoo's core point_of_sale treats medicines like any other product. Stock POS lets a cashier ring up a strip of tablets without ever recording which lot it came from, whether that lot expires next week, or whether the item is a scheduled drug that legally requires a prescription number and pharmacist sign-off. Odoo Enterprise adds lot/serial tracking on the inventory side and even lets you sell tracked products from POS, but the checkout screen was never designed to force FEFO (first-expiry-first-out) batch selection, block near-expiry stock, or capture a doctor and Rx reference against the sale line. When a regulator or an insurer asks "which batch did you dispense to this patient, and who prescribed it," native Odoo has no clean answer.

This build-to-order module turns Odoo POS into a compliant dispensing terminal. We extend pos.order.line and stock.lot so that every regulated product forces a batch pick at the register, defaulting to the soonest-expiring saleable lot and hard-blocking lots past a configurable expiry buffer via a @api.constrains guard. New models — a prescription record linked to the order, and a controlled-substance schedule on product.template — capture prescription number, prescribing doctor, and patient reference, while a @api.depends compute enforces per-transaction and per-period quantity limits on scheduled items. A substitution helper surfaces generic or same-molecule alternatives from a configurable equivalence group directly in the POS UI so staff can offer a cheaper generic without leaving the sale. Insurance and co-pay handling splits a single dispense into a patient-paid portion and a payer-billed portion as distinct payment lines, so the till reconciles and the claimable amount is reportable.

Technically, the work ships as a proper Odoo addon: a versioned __manifest__.py declaring dependencies (point_of_sale, stock, and Enterprise lot tracking where present), server-side models.Model extensions, an OWL/JS POS screen extension for the batch/prescription/substitution flow, ir.model.access.csv plus record rules so only pharmacist roles can override a controlled-substance block, and QWeb reports for a compliant dispensing label and a controlled-drug register. Automated actions flag lots crossing the expiry threshold, and everything is exposed over Odoo's JSON-RPC/XML-RPC API so the prescription and dispensing data can feed an external regulator portal or a third-party insurance clearinghouse. We build against your exact Odoo 17.0, 18.0, or 19.0 database and reconcile Community vs Enterprise differences (Community lacks native POS lot selling, so we implement the batch-picking layer accordingly).

Because this is build-to-order, nothing is auto-downloaded. After a short scoping call we confirm your Odoo version, edition, drug-schedule rules, and insurance workflow, then build and unit-test the addon against a staging copy of your database. You get the installable source, UAT on staging with a rollback plan, and a go-live support window. Typical delivery is one working week from confirmed scope, depending on how many regulatory and payer-specific rules you need encoded.