Direct answer
Use OEM when adapting an established platform and ODM when development changes the product architecture or industrial design. In both cases, define acceptance criteria, approve an identified sample and control every production change.
Information required before model matching
| Area | Buyer input | Supplier response |
|---|---|---|
| Application | Use environment, audience, channel and market | Applicable platforms and limitations |
| Functions | Acoustic, wireless, controls, power and accessories | Implemented scope, gaps and test plan |
| Customization | Industrial design, colors, logo, firmware, packaging | Feasibility, tooling, MOQ and change impact |
| Evidence | Required tests and destination-market documents | Available, pending and not-applicable records |
| Commercial | Quantity, schedule, delivery and quality requirements | Written quotation and production plan |
Development gates
01
Requirement freeze
Record the target, assumptions and open questions.
02
Engineering review
Confirm architecture, risks, tooling and verification.
03
Sample approval
Test the identified revision and record deviations.
04
Production release
Approve specification, artwork, documents and quality plan.
Change control
Any change to driver, enclosure, battery, radio module, firmware, adapter, material, supplier, label or packaging can affect performance, compliance and approved appearance. Record the change, reason, affected evidence and re-approval decision.
Evidence boundary: This page provides a decision framework, not a statement that a selected product has passed a test or holds a certificate. Confirm model-specific specifications, reports, samples and commercial terms in current written documents.