A build-to-order Odoo configuration that models eyewear retail the way optical shops actually run — prescription capture, lens and frame job routing, variant-heavy inventory, and an optical-aware point of sale. ECOSIRE scopes, builds, installs, and supports it for you. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $349.00 USD; request a quote for a scoped proposal.
ایپ مینی فیسٹ
آپ کے ورک فلو کے مطابق تیار کردہ
A build-to-order Odoo configuration that models eyewear retail the way optical shops actually run — prescription capture, lens and frame job routing, variant-heavy inventory, and an optical-aware point of sale. ECOSIRE scopes, builds, installs, and supports it for you.
خود سیٹ اپ کی ضرورت نہیں — ایک کام کرنے والی ایپ جو ECOSIRE بناتا، انسٹال اور سپورٹ کرتا ہے۔
ایک بار کی تعمیر کی قیمت سے آغاز کریں۔ آغاز پر ہم آپ کے ساتھ مل کر دائرہ کار طے کرتے ہیں۔
ECOSIRE اسے آپ کے Odoo پر بناتا، ترتیب دیتا اور انسٹال کرتا ہے۔
آپ تقریباً 2–4 ہفتوں میں لائیو ہو جاتے ہیں، لانچ کے بعد معاونت کی مدت کے ساتھ۔
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.
Runs one or two optical stores on Odoo and needs prescriptions, lab jobs and frame variants handled inside the ERP instead of paper and spreadsheets, without hiring a developer.
Oversees multiple branches and wants a consistent dispensing and lab-tracking workflow, shared patient history, and reporting that rolls up across stores.
Delivering Odoo to an eyewear client and needs a proven, well-structured optical module they can white-label and extend rather than building the prescription and lab logic from scratch.
Owns an existing Odoo instance and needs the optical layer added cleanly, respecting existing customizations, security and their 17/18/19 upgrade path.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Prescription capture (OD/OS, PD, axis) | Purpose-built prescription model with typed fields and validation | Whatever you spec and pay to build | Often partial or fixed schema you cannot change | |
| Frame variant handling | Native attribute/variant matrix tuned for optical SKUs | Depends on developer's approach | Usually generic variants, not optical-aware | |
| Lab / dispensing job tracking | State-machine job model with kanban queue and auto-linking | Built to order if budget allows | Rarely a full lab workflow | |
| Fit with your Odoo version | Built for your exact 17/18/19, Community or Enterprise | Whatever the team targets | Fixed version support; may lag releases | |
| Reports (dispensing slip, lab order) | QWeb PDF reports tailored to your forms | Made to order | Generic templates, limited tailoring | |
| Delivery model | Scoped, built, installed and UAT-tested for you | You manage the project and risk | Self-install; you configure and fix | |
| Support and code ownership | Post-go-live window plus full git repo handover | Depends on contract | Vendor support tiers; code is theirs | |
| Total cost predictability | Indicative from-price, then fixed written quote | Open-ended, effort-based | Low sticker price, high configuration effort |
No. Eyewear Shop is build-to-order. After a scoping call we confirm exactly which models, states, reports and integrations your shop needs, then build, test and install it for you. You receive installable source at handover, not an instant download.
Typical delivery is 2–4 weeks from confirmed scope. Timing depends on the complexity you request — a single-store base build lands toward the shorter end, while multi-branch rollouts, lab/insurance integrations or data migration extend it. We agree the timeline in writing before work starts.
Pricing starts from $349 as an indicative single-company base figure. After a short scoping call we send a fixed written quote for your exact requirements. Drivers such as multi-store setup, extra integrations, localization depth and data-migration volume increase the quoted scope — but the quote you approve is fixed, not open-ended.
We build for Odoo 17.0, 18.0 and 19.0, on both Community and Enterprise. The optical logic runs fully on Community; Enterprise mainly adds convenience features. We target the version you already run so it fits your upgrade path.
Every engagement includes a post-go-live support window for defect fixes and configuration tweaks. Because you receive the full git repository, you own the code and can extend it yourself or contract us for version upgrades and enhancements later. We do not lock you in.
Yes. We build it as a dependency-declared module against sale, stock, point_of_sale and product, with its own models and security files, so it layers onto your database without overwriting core or your existing customizations. UAT on staging confirms there are no conflicts before we touch production.
Yes. All models are reachable over Odoo's XML-RPC / JSON-RPC API, so we can wire lab-fabrication systems, an online store or insurance-claim exports into the dispensing workflow. Those integrations are scoped and quoted as part of your build.
A build-to-order Odoo configuration that models eyewear retail the way optical shops actually run — prescription capture, lens and frame job routing, variant-heavy inventory, and an optical-aware point of sale. ECOSIRE scopes, builds, installs, and supports it for you.