OEM, ODM, SKD and CKD: choosing a meter supply model
These terms are starting points for a commercial discussion, not a complete scope of work. For meter procurement, the most useful distinction is what you receive, what your team does locally and who is responsible for proving conformity.
Reviewed 11 October 2026 · AFMETER
OEM / private-label supply
Usually starts from a defined product platform and an agreed branding or build specification. Clarify artwork, packaging, firmware settings, ownership of design files, sample approval and any effect on product approvals. Do not assume every supplier uses OEM in the same way.
ODM / development scope
Often involves adapting a supplier’s design or developing a product against a market brief. Document engineering deliverables, development charges, tooling ownership, integration work and acceptance milestones. Distinguish a cosmetic change from a new electrical, mechanical or software design.
SKD / partial local assembly
Semi-knocked-down supply can use pre-assembled modules with selected operations performed locally. Define the exact subassemblies, local assembly sequence, firmware/key handling and final tests. The abbreviation alone does not determine local-content eligibility.
CKD / a wider assembly scope
Completely-knocked-down supply generally transfers a wider set of assembly operations. Review equipment, calibration, work instructions, operator training, traceability and batch release. Agree the BOM boundary in writing; CKD scope can still differ significantly between proposals.
Questions that make offers comparable
- What exactly is supplied, and which tasks remain with our team?
- Who owns the tooling, firmware, keys and technical documentation?
- Which approvals cover the final assembled product in our market?
- What are the sample criteria, MOQ, lead-time assumptions and recurring costs?