Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

ERP for Opticians and Optical Chains: Lens Lab Orders, Third-Party Payment and Frame Inventory

Optician ERP and optical practice management software: third-party payment, lens lab orders, frame stock, multi-store and compliance. Criteria, decision table and 10 vendor questions.

ERP for Opticians and Optical Chains: Lens Lab Orders, Third-Party Payment and Frame Inventory

An optician does not just sell glasses. They record a prescribed correction, order custom-cut lenses from a lab, fit the finished eyewear, bill one part to the national health insurer, another to the supplementary insurer, and the balance to the customer. Once you go from one store to ten, this small cycle becomes an organisational problem that neither a point-of-sale system nor an off-the-shelf generalist ERP solves on its own.

This article is for executives and IT leaders of optical chains and growing independents (3 to 30 stores). It lists what an optician ERP must cover, what is genuinely industry-specific, and how to choose between vertical optical software and an adapted generalist ERP. The regulatory examples are drawn from France, where the third-party payment model is most developed, but the selection logic applies to any market where insurers co-pay for eyewear. It complements our analyses of omnichannel retail ERP and of the retail ERP comparison (in French), which stay generic about retail.

An Unusual Kind of Retail: Custom Medical Devices, Prescriptions and Insurers

Optical retail combines three particularities that explain why standard retail ERPs fit it poorly.

  • A custom medical device. Every pair of lenses derives from a prescription: correction, pupillary distances, fitting heights. The product sold is not in stock; it is manufactured after the sale.
  • A multi-payer financing path. The sale is split between the statutory health scheme, the supplementary insurer and the customer. France’s “100 % Santé” reform added a framework of prices and equipment classes: the Class A basket, for example, caps frames at €30 (Crédit Mutuel overview, in French), with an obligation to provide a standardised quote.
  • Health data at the heart of the customer file. The correction, the prescription and the history are health data, with the obligations that come with them.

These three points, not the till or the stock in themselves, make the difference between suitable software and software you have to bend into shape.

The Business Processes to Cover

The file must keep the (scanned) prescription, successive corrections, delivered equipment and appointments. It also feeds renewal reminders. On the GDPR side, health data is a special category under Article 9 of the regulation: check that the tool handles consent, access and erasure rights, traceability of consultations, and permissions by store and by profile (optician, sales assistant, accountant). See also our guide on GDPR compliance for ERP.

Third-Party Payment and Insurers: Electronic Claims, Rejections, Reconciliation

This is the knock-out criterion. The software must check entitlements, produce the invoice, transmit it electronically to the SESAM-Vitale standard, then process payment returns (Noémie flows) and rejections. One market comparison argues that optical software should be judged on three points: third-party payment without rejections, a correct 100 % Santé quote first time, and three-year cost (Hackceleration, in French). Note that, according to the same source, SESAM-Vitale transmission is often a separate paid option, for instance billed as an add-on by some vendors.

For a network, look in particular at:

  • automatic reconciliation of payments from health funds and insurers against invoices, including partial payments;
  • rejection tracking with reason, follow-up and handling time per store;
  • the link to accounting: unpaid third-party payment is a receivable, to be provisioned where needed.

If your network already runs a finance ERP, it is often this reconciliation that tips the decision. For the payer-side insurance context, see our article on mutual and insurance ERP.

Lab and Lens Orders: From Prescription to Fitting

The typical flow: prescription, lens selection, order to the lab, receipt, quality check, fitting, handover to the customer. The tool must:

  • send the order to the lab without re-keying (EDI exchanges: some vertical packages cite interfaces with Essilor, Zeiss or Luxottica, according to vendor pages reviewed by Hackceleration);
  • track the promised delivery date and alert on delays;
  • manage received lenses and their assignment to the right frame, including with centralised fitting or a lab shared between stores.

This flow is the least covered by generalist ERPs: it has no equivalent in a standard sales module.

Frame Inventory: References, Collections, Seasonality

Frames raise a problem of high SKU turnover: renewed collections, colour and size variants, unique pieces on display. The ERP must handle families and variants, labelling (barcode or RFID), cycle counts, supplier returns and shrinkage. This is where retail ERPs are comfortable: a variant-based stock management module covers the need well, provided it is configured properly.

Warranty, After-Sales, Breakage and Renewal

Breakage, adjustment, manufacturer warranty, the store’s own breakage cover: each after-sales case must be linked to the original sale (equipment, lab, date) to decide between warranty, goodwill gesture and billing. Equipment renewal, finally, is a revenue lever: the ERP must let you target customers whose eyewear is ageing, in compliance with GDPR consent.

Multi-Store: Inter-Store Stock, Central Purchasing, Private Labels

As soon as the network exceeds a few stores, three topics appear:

  • Inter-store stock: seeing what is available elsewhere, transferring a frame or a lens, avoiding local overstock.
  • Central purchasing and private labels: centralised listing, supplier terms, internal transfer prices, margin by collection.
  • Franchise or company-owned stores: with company-owned stores, steering is consolidated (one company, one ledger). With franchising, each point of sale is a separate legal entity: the tool must isolate data while still allowing network reporting. Some vertical vendors claim to handle both models, for example Cosium for “centralised franchises and branches” according to Hackceleration: have this confirmed in a demo.

For financial consolidation between entities, see our article on multi-site and multi-entity ERP (in French), and for branded networks our franchise ERP guide.

Integrations: Till, Labs, Accounting, E-Commerce, Appointments

IntegrationWhat to check
Point of saleCertified POS software, mixed payment (third-party payment + patient balance)
Lens labsEDI ordering, status tracking, invoice feedback
AccountingEntries per store, third-party payment receivables, VAT
E-commerceContact lenses, accessories, frame pre-orders; shared stock
Online appointmentsCalendar per store, reminders, automatic file creation

The architecture choice (single suite or assembly) is covered in detail in our analysis ERP vs best-of-breed.

Vertical Software vs Adapted Generalist ERP

In France there is vertical optical software, including CosiumOptic, MyEasyOptic, Osmose, IDM Optic and Winoptics, cited by Hackceleration. Among generalist ERPs, Odoo offers a dedicated page for eyewear stores. We do not rank them or quote market shares: no verifiable independent source allows us to. Check the exact functional scope on vendor sites and in demos.

CriterionVertical optical softwareAdapted generalist ERP
Third-party payment, SESAM-Vitale, 100 % Santé quoteNative (to be verified)To be built or integrated: main risk
Lab ordering and lab EDINativeCustom development
Finance, purchasing, consolidationOften limitedStrong point
Small network (1 to 5 stores)Suitable, contained costOften oversized
Network of 10 to 30 stores, multi-entityDepends on the vendorRelevant if finance is critical
BudgetSubscription per storeLicence + integration + custom work
RiskDependence on a niche vendorCustom-code debt on third-party payment

Rule of thumb: third-party payment cannot be fixed with custom development. If the generalist ERP does not include it, it must be coupled with a vertical module. Networks that choose a generalist ERP generally do so for finance and purchasing, with a vertical front end for the store.

Compliance: GDPR, Certified POS, E-Invoicing

  • GDPR and health data: legal basis, retention periods, permissions, subcontractors. Have your DPO check whether hosting health data requires a certified host in your configuration: the question is legal, not technical, and we do not settle it here.
  • Certified POS: in France, point-of-sale software must guarantee the inalterability and archiving of sales data, with a compliance certificate (see our section on NF525, in French). Demand the certificate for the exact version you deploy.
  • E-invoicing: the French timetable provides for reception by all companies on 1 September 2026, issuing for large companies and mid-caps on the same date, and for SMEs and micro-businesses on 1 September 2027 (service-public.fr). Sales to consumers fall under e-reporting. An optical network mixes B2C (the majority), B2B (companies, partner insurers) and supplier flows: the tool must handle all three.

Budget, Total Cost and Deployment Pitfalls

Most vertical vendors do not publish their prices (Hackceleration): demand a detailed quote, store by store, and reason in three-year cost rather than subscription price.

The cost lines to show in the comparison:

  • Subscription or licence per store and per workstation, and what it includes (electronic claims, regulatory updates, support).
  • Optional modules: 100 % Santé quote, lab interfaces, e-commerce, online calendar.
  • Hardware: till, card reader, label printers, payment terminals.
  • Data migration: customer files, prescriptions, equipment histories. This is the most underestimated item, because the quality of the starting data conditions the renewal campaigns.
  • Integration and custom work: very low with a complete vertical package, potentially dominant with a generalist ERP that must be completed on third-party payment.
  • Training: the lab, the counter and accounting do not use the same screen; plan role-based paths.

Three pitfalls recur in network projects:

  1. Deploying everywhere at once. A pilot store with a lead optician reveals third-party payment rejections and lab discrepancies before they hit the whole network.
  2. Neglecting the double-entry period. During cutover, invoices awaiting reimbursement stay in the old tool: decide who tracks payment returns and on which system.
  3. Forgetting after-sales. Warranties apply to equipment sold before the switch: the history must be migrated, otherwise after-sales loses track of the original sale.

On the steering side, define from the start the indicators the ERP must produce without reprocessing: third-party payment rejection rate per store, average lens delivery time, turnover by collection, receivables awaiting reimbursement. A tool that cannot output them natively condemns you to one more Excel sheet, which is exactly what the project aims to eliminate.

A 5-Step Selection Roadmap

  1. Map the flows: sale, third-party payment, lab, stock, after-sales, per store.
  2. Prioritise: separate what is industry-specific (third-party payment, lab) from what is generic (finance, purchasing).
  3. Choose the architecture: vertical software alone, generalist ERP, or coupling.
  4. Test with real cases: third-party payment files with rejections, a late lens order, an inter-store transfer.
  5. Manage the rollout: pilot store, customer file migration, training, cutover outside peak periods.

10 Questions to Ask Vendors

  1. Which version is certified for point of sale, and where is the certificate?
  2. Is SESAM-Vitale transmission included or optional, and at what cost per store?
  3. How are rejections handled and followed up?
  4. Which labs are connected via EDI, and which are manual entry?
  5. Is the 100 % Santé quote generated natively?
  6. How is data isolated in a franchise set-up?
  7. Where is health data hosted, and by whom?
  8. Which standard accounting interfaces (export, API) are available?
  9. How are existing customer files migrated, and at what cost?
  10. What is the total three-year cost for N stores, excluding custom work?

Going Further

To frame your project, start from our retail ERP comparison (in French) and the analysis of omnichannel and inventory. If you want an outside view of your requirements, contact us for an ERP needs audit: a map of your flows and a shortlist of options, with no vendor commitment.