Optical retail breaks the assumptions baked into a generic ERP. A single sale is rarely one item off a shelf — it is a frame chosen from hundreds of SKU variants, a lens specification (index, coating, tint, prescription values), and a fabrication job tracked from order to fitting to collection. Odoo core gives you product.template/product.product, sale.order, stock, and Point of Sale, but out of the box there is nowhere to store a sphere/cylinder/axis/PD prescription, no link between a lens order and the physical job, and no clean way to model right-eye/left-eye differences on one order line. Shops end up abusing free-text notes and spreadsheets, and the data never reaches reporting.

Eyewear Shop is a build-to-order Odoo configuration that ECOSIRE assembles for your business. Technically it is delivered as a proper Odoo module with its own __manifest__.py, dependency-declared against sale, stock, point_of_sale and product. We add optical-specific models — for example a prescription model (models.Model) holding OD/OS sphere, cylinder, axis, add, PD and prism as typed fields.Float/fields.Char, with @api.depends compute fields deriving lens-power summaries and expiry validation — related back to res.partner (the patient/customer) and to the originating sale.order.line. Frame inventory is configured through Odoo's native variant engine (product.attribute and product.attribute.value for brand, colour, size and material) so one frame model explodes into its real SKU matrix without a product record per colour by hand.

The workflow layer is where the configuration earns its keep. We model a dispensing/lab job that moves through states (draft → in lab → ready → collected) using a status field plus ir.actions.server and automated actions so a confirmed sale line for a lens creates and links its job automatically, and SMS/email "your glasses are ready" notifications fire on the ready transition. Views are built in XML (form, list, kanban for the lab queue) with OWL components where a richer prescription grid helps, and we ship QWeb PDF reports — the dispensing slip, the lab order for the fabricator, and a prescription record for the patient. Access is locked down with ir.model.access.csv and record rules so front-desk staff, dispensing opticians and managers each see the right scope, and everything is reachable over the XML-RPC/JSON-RPC API if you need to feed a lab system or e-commerce front end.

Because this is build-to-order, nothing is pre-sold as a finished download. After a short scoping call we confirm the exact models, states, reports and integrations your shop needs, then build and test it against your target Odoo version, deliver on staging for UAT, and cut over to production. Typical delivery is 2–4 weeks from confirmed scope. We support Odoo 17.0, 18.0 and 19.0 on both Community and Enterprise (Enterprise adds studio-adjacent niceties, but the optical logic runs fully on Community). Pricing starts from $349 (indicative, single-company base scope); multi-store rollouts, insurance/lab integrations, deeper localization, and larger prescription/patient data migrations increase the quoted scope.