Manufacturing · Healthcare, Life Sciences and Precision Products
EDI and API Integration for Eyewear and Optical Product Manufacturers
Eyewear and optical makers sell frames, lenses and contact lenses through optical retailers, labs, distributors and online sellers, with many style, color and size variants. ECOM connects orders, item data, lab orders, returns and invoices to your ERP.
What this covers
Products and business models in eyewear and optical product
Products
- Frames and sunglasses
- Prescription lenses and coatings
- Contact lenses and solutions
- Cases, accessories and instruments
Business models
- Brands selling to optical retailers and independents
- Lens labs and wholesalers
- Vertically integrated brands with retail
Scenarios
Where eyewear and optical product manufacturers lose time and margin
Recurring problems for this kind of business, how ECOM connects the systems and documents involved, and what you gain. Bring your own example and we will work through it with you.
-
Style, color, size variants
- The problem
- Frames have style, color, size and temple variants.
- How ECOM helps
- ECOM sends frame catalogs (832) with style, color and size and maps orders back to variants.
- What you gain
- Retailers order the exact variant.
Talk to an EDI/API Expert about style, color, size variants Share a sample 832 Price/Sales Catalog and 850 Purchase Order, or describe what goes wrong, and we will show how it would map to your ERP.
-
Lab and prescription flows
- The problem
- Lens orders carry prescription data to a lab, then ship to the retailer or patient.
- How ECOM helps
- ECOM carries lens prescription data to the lab connection where the lab accepts it and returns shipment confirmations.
- What you gain
- Lens orders flow to the lab and back without re-keying.
Talk to an EDI/API Expert about lab and prescription flows Share a sample 850 Purchase Order and 856 Advance Ship Notice, or describe what goes wrong, and we will show how it would map to your ERP.
-
Returns and remakes
- The problem
- Remakes and warranty returns are routine.
- How ECOM helps
- ECOM links remake and warranty returns (180) to the original order.
- What you gain
- Remakes are researched against the original order.
Talk to an EDI/API Expert about returns and remakes Share a sample 180 Return Merchandise Authorization and Notification and 850 Purchase Order, or describe what goes wrong, and we will show how it would map to your ERP.
Who you connect with
Trading relationships for eyewear and optical product manufacturers
Typical relationships. Which of them apply, and how each one wants to connect, depends on your business.
- Optical retail chains and independents
- Order frames, lenses and accessories, with item setup per retailer.
- Laboratories
- Order lenses and process prescription jobs on their own order formats.
- Distributors
- Resell to independent practices.
- Frame and lens suppliers
- Supply products and components with long lead times.
- Carriers
- Ship fragile goods to practices and labs.
Partner guides: Retailer guides · Distributor guides · Healthcare guides
Typical workflow
Where ECOM connects your systems and trading partners
The pattern below is typical for eyewear and optical product manufacturers, not one partner's confirmed requirements. Each trading partner publishes its own guide; confirm the details with that partner.
- Your plant and ERP→Optical retailer or lab 832 Price/Sales Catalog Frame style, color and size catalog.
- Optical retailer or lab→Your plant and ERP 850 Purchase Order The customer order: items, quantities, prices, ship-to and requested dates.
- Optical retailer or lab→Your plant and ERP 860 Purchase Order Change Request Changes to open orders: quantities, dates or cancellations.
- Your plant and ERP→Optical retailer or lab 855 Purchase Order Acknowledgment The order acknowledgment: confirms the order or reports differences from what was requested, including dates.
- Your plant and ERP→Optical retailer or lab 856 Advance Ship Notice Describes what is shipping, how it is packed and how it is labeled.
- Your plant and ERP→Optical retailer or lab 810 Invoice Bills for what was shipped, tied to the order and the ship notice.
- Optical retailer or lab→Your plant and ERP 180 Return Merchandise Authorization and Notification Remake and warranty returns.
- Your plant and ERP→Optical retailer or lab 846 Inventory Inquiry/Advice Shares available inventory so the customer can order against it.
- Your plant and ERP→Frame or lens supplier 850 Purchase Order Purchase orders for frames, lenses and coatings with quantities and requested delivery dates.
- Frame or lens supplier→Your plant and ERP 856 Advance Ship Notice Frame, lens and coating shipments with quantity and lot, used to plan receiving ahead of finishing.
Publish frame and lens catalogs
Item data (832) lists styles, colors and sizes.
Take orders
Orders (850) and changes (860) post by variant.
Ship
The 856 describes cartons and items.
Invoice
The 810 follows shipment.
Handle returns and remakes
Return authorizations (180) link remakes and warranty returns to the original sale.
EDI and API exchanges
The documents behind the workflow
X12 transaction sets typical for this workflow, with what each carries here. Select a code for the full transaction reference.
| Document | Direction | What it carries for eyewear and optical product manufacturers |
|---|---|---|
| 832 Price/Sales Catalog | You send | Frame style, color and size catalog. |
| 850 Purchase Order | You receive | The customer order: items, quantities, prices, ship-to and requested dates. |
| 860 Purchase Order Change Request | You receive | Changes to open orders: quantities, dates or cancellations. |
| 855 Purchase Order Acknowledgment | You send | The order acknowledgment: confirms the order or reports differences from what was requested, including dates. |
| 856 Advance Ship Notice | You send | Describes what is shipping, how it is packed and how it is labeled. |
| 810 Invoice | You send | Bills for what was shipped, tied to the order and the ship notice. |
| 180 Return Merchandise Authorization and Notification | You receive | Remake and warranty returns. |
| 846 Inventory Inquiry/Advice | You send | Shares available inventory so the customer can order against it. |
| 850 Purchase Order (supplier side) | You send | Purchase orders for frames, lenses and coatings with quantities and requested delivery dates. |
| 856 Advance Ship Notice (supplier side) | You receive | Frame, lens and coating shipments with quantity and lot, used to plan receiving ahead of finishing. |
Other exchanges you may meet
- Lab ordering portals and software
- Retailer portals
Where a trading partner offers an API, a portal or file exchange instead of EDI, ECOM scopes that connection alongside the EDI ones. Functional acknowledgments (997 or 999) report validation results, including rejection; they do not prove business acceptance or ERP posting. Which acknowledgments and business responses each partner expects is confirmed with that partner.
Operational detail
Variants, labs and remakes
Frames come in style, color, size and temple variants, and lenses in prescriptions. Lab orders have their own formats, separate from standard purchase orders, and remakes and warranty returns are routine.
Contracts, pricing and distribution
Contract pricing, chargebacks and distributor reporting are part of how many healthcare products are sold.
Style, color and size items
Frames and accessories are set up as separate items by style, color and size, and retailers need orders and ship notices to carry the same item numbers.
Connected systems
Systems that send and receive this data
Documents are only useful when they reach the systems that run the business.
- ERP
- Lab management software
- Warehouse management
- Retailer portals
ERP integration guides: SAP S/4HANA · Oracle NetSuite · Microsoft Dynamics 365 Business Central · Infor CloudSuite Industrial (SyteLine) · QAD MFG PRO · Epicor Kinetic · All ERP guides
Onboarding and monitoring
From first requirement to daily exception handling
Confirm the requirement
Obtain each partner's implementation guide or specification, for example from your optical retailer or lab, and agree which documents, versions and data are in scope.
Map to your systems
Map each document to the fields in your ERP and lab management software so the data posts without re-keying.
Test with the partner
Exchange test documents and review the results with the partner before go-live, including changes, cancellations and error cases, not only the simple order.
Validate, acknowledge and monitor
A 997 or 999 reports the validation result of the document as received, including rejection; it does not show that the business accepted the content or that your ERP posted it. Business responses are separate: an 855 for orders, an 824 for application errors. Monitoring can show what is late, missing or rejected, once it is set up with you.
Resolve exceptions
Which failures and late documents are watched, who is alerted and how each is resolved are agreed during onboarding. Rejected or unacknowledged documents can then go to the people who can fix them, with the document and the reason in view.
Example exceptions for eyewear and optical product manufacturers
| Exception | Example handling, once configured |
|---|---|
| Frame variant discontinued but still ordered | An order line for a discontinued frame variant can be held for review with a replacement shown. |
| Remake not linked to its original order | A remake can be researched against the original order so cost and credit are tracked. |
Illustrative examples of exceptions a team in this industry may need to review. Each check compares data from your ERP, WMS, trading partner documents or scans, where those are available. Which conditions are checked, who is alerted and what happens next are configured with you during onboarding. This is not a screenshot of a live system or a list of built-in checks.
How ECOM helps
ECOM products and services that apply
Each partner connects in the way it can support. These products cover the connections and visibility manufacturers need most.
-
PRISM-EDI
Exchange of schedules, orders, ship notices and invoices with customers and suppliers in X12 or EDIFACT, translated to and from your ERP.
-
PRISM-WebEDI
Browser-based purchase orders, acknowledgments, ship notices and invoices for suppliers without EDI systems.
-
PRISM-SmartConvert
Supplier confirmations, invoices and customer orders that arrive as PDFs, emails or scans converted into ERP-ready data.
-
PRISM-SCV
Monitoring of transactions and exceptions across customer and supplier documents.
Services: Trading partner onboarding · ERP integration · API integration · Fully managed EDI · Supply chain visibility · Mapping and translation
Frequently asked questions
Can lab ordering systems connect?
Lab ordering systems vary, so each is scoped as its own connection to your ERP, separate from your standard purchase orders.
Does ECOM process prescription data?
Where a lab flow carries it, ECOM scopes it as part of that connection. Privacy and clinical obligations stay with your teams.
Does ECOM provide regulatory or serialization compliance?
ECOM exchanges the business documents and data that trading partners require and works from their published guides. Regulatory, quality and serialization obligations remain with your quality and compliance teams.
Do you need our trading partner's implementation guide to start?
It helps, but you can start without one. Tell us who you trade with and which systems you run, and we will help obtain and review each partner's requirements. The guide, not this page, decides the exact documents, versions and rules for that partner.
Talk to an EDI/API expert about eyewear and optical product manufacturers
Share your trading partners, your ERP, a sample document or the problem that keeps recurring. A completed specification is not needed: a partner guide, a rejected document or a description of the issue is enough to start.