OEM vs ODM vs Grey-Label
Suppliers use “OEM” and “ODM” loosely, and buyers pay for it — in tooling they did not need, in minimums they could not move, or in a firmware licence they never asked about. The useful way to think about it is a ladder of control: at each rung you get more of a product that is yours, and you take on more cost, lead time and risk. This page sets out the three rungs that matter for smart watches, fitness bands and AI glasses, what changes at each one, and a plain framework for picking one on your first order.
The three models, defined plainly
Grey-label is our finished hardware with your logo and perhaps your box. The design, firmware and app are stock; you are buying distribution, not development.
OEM puts your brand on our design: your logo, boot splash, packaging, strap choice and a configured firmware and white-label app. The product concept and tooling are still ours.
ODM is a product developed to your specification. It starts with requirements and can extend to custom industrial design, a new case, different sensors and your own app architecture. This is where tooling and longer timelines enter.
What changes at each level of customisation
Customisation is not one switch; it is a stack of independent dials, each with its own cost and minimum. Turning them up moves you along the ladder:
- Logo — laser or print on the case and strap. Cosmetic, quick, cheap to change.
- Packaging — retail box, insert and film. A printed batch, so it commits you earlier.
- Firmware configuration — boot image, default languages, feature set, health targets.
- App white-label — your brand, colours and languages on the companion app, and a data region choice.
- Hardware and tooling — a new case or bezel, different sensors, custom shape. This is the ODM step, and the only one that needs a mould.
The first four are genuinely OEM territory. Only the fifth is a design project. Many buyers reach for the fifth because it looks differentiated, when the first four already carry their brand at a fraction of the risk.
Side by side
| Aspect | Grey-label | OEM | ODM |
|---|---|---|---|
| What is yours | Logo and box | Brand, packaging, firmware config, app skin | Industrial design, spec, app architecture |
| New tooling | None | Usually none (open tooling) | Yes — you fund and, once paid, own the mould |
| Firmware / app IP | Factory stock build | Factory base + your licence | Negotiated up front |
| Unit price | Lowest | Mid | Highest, plus NRE |
| Lead-time risk | Lowest | Low–mid | Highest — tooling and revisions |
| Indicative MOQ | 500 units | 500 logo / 1,000 packaging | 2,000 for firmware or app white-label; higher for full tooling |
For the record, the tiers we quote are: standard models 500 units, logo printing 500, custom packaging 1,000, and firmware or app white-label 2,000. They reflect physical constraints — a print run or an engineering build — which is why they climb even though none of them is “ODM” yet. The MOQ and lead-times guide explains the reasoning behind each number.
IP ownership of firmware and the app
This is the part most first-time buyers skip and most often regret. The default position is that the factory owns the base firmware and grants you a licence to run and brand it. A white-label app is yours to brand — names, colours, languages and a chosen data-hosting region — but the underlying stack is usually still the factory's, licensed to you. That is fine and normal, provided it is written down. What you want agreed before you pay: whether custom source is yours or licensed, whether the tooling can be moved to another supplier if you ever leave, and what happens to firmware updates and support after launch. For an ODM project, add ownership of the industrial design files and the custom app. Our terms are consistent with the supplier-vetting checklist; get the same three lines in the order before a deposit moves.
What to ask your supplier: “For this configuration, exactly what do I own outright, and what am I licensing? Put the firmware, the app and the tooling in three separate sentences.”
A framework for choosing
- Proving demand? Grey-label. Lowest cost and risk, fastest to market, 500 units.
- Building a brand line? OEM. Your logo, packaging, boot image and white-label app on proven hardware — the sweet spot for most distributors.
- Selling steadily and need real differentiation? Then ODM, and only then accept the tooling cost and longer, higher-MOQ schedule.
- Mix deliberately. Grey-label to test, OEM to grow, ODM to defend a position. Each rung is reversible up to the point you cut a tool.
FAQ
- What is the difference between OEM, ODM and grey-label?
- Grey-label is our existing hardware with your logo on it. OEM is your brand, packaging and firmware configuration applied to our design. ODM is a product designed around your specification, which can mean custom industrial design and tooling. Each step adds control, cost and risk.
- Who owns the firmware and the app?
- Typically the factory owns the base firmware and grants you a licence to use and brand it; a white-label app carries your brand, colours and language, and the scope of what you own versus what is licensed is written into the agreement. For an ODM build, ownership of custom design files and the app is negotiated up front. Never assume — put it in the order terms.
- Do I need custom tooling to look like my own brand?
- No. Most brands start with OEM at 500 to 1,000 units — your logo, boot image, packaging and app skin on proven hardware — and only move to custom tooling once a product line is selling steadily.
- Which model should a first order use?
- Almost always grey-label or OEM. They carry the lowest unit price, the shortest lead time and the least tooling risk, which is what you want while you are still proving demand. Reserve ODM for a range you have already validated.