Start an OEM lighting project with a controlled specification
The safest OEM path is to freeze requirements in stages: commercial and market scope, technical feasibility, engineering sample, compliance evidence, golden sample, packaging, production controls, and shipment release.
Published · Last reviewed
Short answer
Begin with one revision-controlled product brief and an explicit responsibility matrix. Distinguish must-have requirements from preferences. Confirm destination-market obligations before engineering is frozen. Approve samples against measurable criteria, record every change, and define what evidence releases production and shipment. Price, minimum quantity, tooling, schedule, warranty, ownership, and compliance are negotiated project facts, never assumptions.
1. Build a decision-ready brief
Identify the buyer, brand, destination markets, sales channels, use environment, intended users, installation method, target launch window, forecast assumptions, packaging languages, and required product variants. Add drawings, reference products, and a list of features, but explain the reason behind each feature. A supplier can propose safer alternatives when it understands the function rather than being forced to imitate an unexplained detail.
The technical schedule should cover supply voltage and frequency, power architecture, dimensions and tolerances, materials and finish, mounting, optics, lumen and intensity targets where applicable, CCT and color quality, controls, environmental conditions, serviceability, labels, packaging, and documentation. Mark every unconfirmed item as open; silence is not approval.
2. Use stage gates
| Gate | Required decision or evidence |
| Scope | Approved brief, volumes as planning assumptions, destination markets, responsibilities, confidentiality, and commercial discussion boundaries. |
| Feasibility | Marked-up requirements, exceptions, architecture, preliminary bill of materials, risk list, tooling concept, and proposed verification plan. |
| Engineering sample | Fit, function, thermal behavior, optics, controls, installation, appearance, and identified deviations tested against the current revision. |
| Compliance plan | Applicable standards and regulations, responsible party, laboratory or evidence route, sample configuration, labels, technical file, and change impact. |
| Golden sample | Signed physical sample or controlled record, drawings, specifications, finish, firmware where relevant, packaging, labels, and approved deviations. |
| Production release | Final bill of materials, work instructions, inspection criteria, test fixtures, approved suppliers, traceability plan, and change-control authority. |
| Shipment release | Agreed inspection and test records, quantity and packaging checks, document set, exceptions disposition, and shipping authorization. |
3. Make samples answer questions
Do not request “a sample” without stating its purpose. An appearance sample may not be electrically representative. A rapid prototype may not use production tooling. A compliance sample must match the configuration submitted for evaluation. A golden sample should represent the approved production target and be linked to controlled drawings and a specification revision.
Create a sample report with photos, model and revision, components, test conditions, measured results, observations, deviations, actions, and approval status. Test installation, connectors, aiming, dimming, noise, visible color, finish, labels, packaging fit, and service access as applicable. If a sample changes, record what changed and whether previous evidence remains valid.
4. Plan compliance before tooling
Market access depends on product type, electrical architecture, installation, destination, claims, radio functions, materials, and who places the product on the market. Ask a qualified compliance professional to define the applicable requirements and evidence. A certificate for a different model, component, factory, standard, or configuration may not support the proposed product.
Keep the compliance matrix tied to exact models and revisions. Record critical components and approved alternatives. Changes to drivers, LEDs, optics, plastics, wiring, connectors, firmware, labels, or construction may require review or retesting. Compliance evidence is part of configuration control, not a document collected at the end.
OEM project checklist
- One owner controls the brief, decision log, and current revision.
- Destination markets, use conditions, installation, and regulatory responsibilities are explicit.
- Must-have requirements, preferences, assumptions, and open points are separated.
- Quotation identifies inclusions, exclusions, tooling, samples, payment, logistics, and validity.
- Sample purpose, configuration, tests, acceptance criteria, and approval authority are written.
- Golden sample, drawings, bill of materials, labels, packaging, and approved deviations agree.
- Production and shipment release evidence is defined before the order proceeds.
- Every engineering or sourcing change receives documented impact review and approval.
Send a useful first inquiry
Attach the brief, drawings, target market, estimated quantities as non-binding planning information, variant matrix, required launch timing, and known compliance route. Ask for questions, exceptions, proposed milestones, sample scope, and a written quotation. Review the AOCEN product range for possible base platforms, use the catalog library to identify relevant families, and contact AOCEN with the controlled brief. No certification, price, minimum quantity, lead time, warranty, or project outcome is represented by this general workflow.
Strengthen the approval chain
Screen evidence and production fit with the lighting manufacturer evaluation guide, build a comparable request with the wholesale RFQ checklist, and record the approved configuration through the luminaire sample inspection guide.
Source-safe project rule
Only place a claim in a specification, label, sales sheet, or structured record when the supporting source is identified and applies to the exact configuration. Mark proposed values as targets, supplier statements as pending verification, and approved evidence by revision and date. This keeps technical, commercial, and compliance decisions auditable.
