Editorial owner: MCL Solar Knowledge Center
Review scope: Commercial and technical decision framework for solar street light OEM and ODM projects. Final responsibilities must be defined in the quotation, technical agreement, PI or sales contract.
Key conclusion
OEM and ODM are not quality rankings. They describe different allocations of design ownership, customization work, validation responsibility, tooling, documentation and change control. The better model is the one that matches the buyer’s product definition, order volume, intellectual-property requirements, engineering resources and launch schedule.
A logo change on an existing solar street light is not the same project as a new optical system, battery pack, housing or controller platform. Before requesting a quotation, define which elements may change and who approves the resulting design.
Working definitions for a solar street light project
| Model | Typical starting point | Typical buyer responsibility | Typical manufacturer responsibility |
|---|---|---|---|
| OEM | A buyer-owned or buyer-specified product definition. | Product requirements, protected design inputs, approvals, market compliance and change authorization. | Manufacturing review, process planning, sourcing, production, testing and agreed engineering support. |
| ODM | An existing manufacturer platform adapted for the buyer. | Application requirements, branding, target market, approval criteria and commercial forecast. | Base design, configurable options, validation evidence, production and controlled customization. |
Actual contracts may use the terms differently. The project documents should define responsibilities instead of relying on the label alone.
Choose the model by customization depth
Level 1: branding and packaging
- logo or nameplate;
- carton artwork, labels and manuals;
- approved color or surface marking;
- market-specific accessories.
This is usually closest to an ODM/private-label project because the technical platform remains unchanged.
Level 2: configuration customization
- LED power and programmed dimming profile;
- panel and battery capacity within an approved platform;
- controller settings and optional sensor;
- optical distribution, arm, bracket or pole interface;
- connector, cable and packaging configuration.
This still may use an ODM platform, but every changed combination should be checked for electrical, thermal, optical, mechanical and warranty impact.
Level 3: product or platform development
- new housing, tooling or structural design;
- new PCB, controller firmware or communication architecture;
- new battery pack, BMS or enclosure;
- new lens, optical chamber or photometric target;
- new certifications or market-specific approval program.
This requires a formal development plan regardless of whether the parties call it OEM or ODM.
Decision matrix
| Question | OEM may fit when… | ODM may fit when… |
|---|---|---|
| Who owns the product definition? | The buyer supplies controlled drawings, specifications or protected design inputs. | The manufacturer supplies an existing validated platform. |
| How quickly must the product launch? | The buyer already has mature, production-ready documentation. | An existing platform can meet the project with limited controlled changes. |
| How much engineering change is required? | The buyer needs a differentiated platform and accepts development work. | Configuration, branding and packaging changes are sufficient. |
| Who controls design changes? | The buyer requires formal approval of every controlled design revision. | The manufacturer maintains the base platform and notifies the buyer of defined changes. |
| What evidence is required? | New validation may be needed for the buyer’s design. | Existing reports may be usable only if they match the selected model and configuration. |
Documents to agree before sample production
- Product requirement specification and intended application.
- Controlled BOM or approved component list.
- Electrical configuration and energy-balance calculation.
- Mechanical drawings, finishes, labels and packaging artwork.
- Photometric file and DIALux scope where applicable.
- Environmental, ingress, impact, corrosion and structural requirements.
- Sample validation plan and acceptance criteria.
- Certification responsibility and exact model scope.
- Change-control and substitute-component approval process.
- Ownership and permitted use of drawings, tooling, firmware and branding.
Tooling and development cost
Tooling cost should be separated from unit price. The agreement should identify who owns each tool, where it is stored, who pays for maintenance, whether it can be used for other customers, and what happens at the end of the program.
Development charges may cover mechanical design, prototype machining, PCB work, firmware, photometric samples, test fixtures, certification samples and engineering validation. A low quoted tooling fee does not prove that the required validation is included.
MOQ and forecast
Minimum order quantity is influenced by custom components, cell and panel procurement, surface finish, printed packaging, production setup and supplier batch sizes. Buyers should provide an initial order, annual forecast and expected order frequency. Manufacturers should distinguish a commercial MOQ from a technical minimum needed to control the custom process.
Quality and change control
A sample approval is not enough if production components can change without notice. Define:
- which components are controlled by manufacturer and model;
- what substitutions require written approval;
- how battery cells and electronic components are traceable;
- which incoming, in-process and final tests are recorded;
- how nonconforming material and corrective action are handled;
- how firmware and controller settings are version controlled.
Warranty responsibilities
MCL Solar’s standard complete-system warranty is 5 years. Extended warranty is available only when specified in the PI or sales contract. For an OEM or ODM program, the agreement should also define whether custom buyer-specified components, third-party communication devices, poles, installation work or software services have different responsibility boundaries.
Questions to ask a prospective partner
- Which elements are existing and validated, and which must be newly developed?
- Which reports apply to the exact proposed configuration?
- Who owns tooling, drawings, firmware and branding files?
- What is the sample and pilot approval process?
- How are component substitutions controlled?
- What production and battery traceability records are retained?
- Which changes affect certification or test scope?
- What are the MOQ, lead time and forecast assumptions?
- What does the warranty cover, and what is excluded?
- How will field feedback and corrective actions be managed?