Optical Store & Lab Management (ERP + POS)

ECOSIRE builds a dedicated optical layer on top of your Odoo. We add a patient prescription model (an optical.prescription record linked to res.partner) that captures OD/OS values — sphere, cylinder, axis, add, prism, PD — with @api.constrains validation so an impossible axis or out-of-range power is caught at entry, and computed @api.depends fields that derive the reading vs distance breakdown. Frames and lenses live in a properly attributed catalog: frame material, shape, color and size as product.attribute variants, and lens options (index, coatings like anti-reflective or blue-light, tint, photochromic) modeled as configurable line options so a single lens SKU generates the right variant and price at point of sale.

The POS is where it comes together. We extend the Odoo POS (OWL frontend + pos.order backend) so a cashier picks the patient, pulls the active Rx onto the order line, configures the lens, and the system prices frame + lens + coatings together. When the order confirms, an optical.lab.order job is created automatically via an automated action, moving through a status pipeline — queued, surfacing/edging, fitting/mounting, QC, ready for collection — with the lab technician assigned and the target date computed. Insurance is handled as a split on the order: an insurer/scheme portion routed to a claim journal and the patient co-pay taken at the till, with a QWeb spectacle-order/collection ticket and the clinical Rx printed for the lab bench. All of it is guarded by ir.model.access.csv plus record rules so front-desk, optometrist and lab roles see only what they should, and the same data is reachable over the XML-RPC/JSON-RPC API if you want to feed a website booking form or an external edger.

Because this is build-to-order, nothing ships blind. We start with a scoping call to map your exact Rx fields, lens catalog, lab stages and insurance schemes, then build against your Odoo edition and version (17.0, 18.0 or 19.0; we flag anything that needs Enterprise such as full MRP or advanced accounting versus what runs on Community). You get the work on a staging instance for UAT first, a documented __manifest__.py-defined module with migration-safe data, and a defined go-live with rollback. Typical delivery is 2–4 weeks from confirmed scope, and the module is yours — handed over as a git repository you own.