OEM vs ODM vs White Label Security Cameras: Cost, MOQ and Certification Responsibility

Sourcing guide · Updated 10 November 2026 · 8 min read

Most sourcing problems we see at the sample stage are not quality problems. They are model mismatches: a first-time importer orders full OEM with custom certification at 300 units, or a distributor with a ten-year brand expects white label to give them exclusivity. The product is fine; the commercial model does not fit the volume.

This guide breaks the three models down by the four things that actually decide the deal: who owns the tooling, who owns the certificate, how MOQ is calculated, and how long the timeline runs.

1. What each model actually means

White label

The factory already sells the product. You buy it, add your logo to the product and packaging, and resell it. The hardware, firmware and certification stay exactly as the factory defined them. Differentiation is limited to branding and the channel you sell through.

ODM (Original Design Manufacturer)

The factory designed the product and owns the platform, but you influence the configuration: battery capacity, solar panel size, Wi-Fi or 4G bands, lens options, memory, accessories, packaging, app name and UI language. You are not creating a new product, you are configuring an existing one into a version that fits your market.

OEM (Original Equipment Manufacturer)

The product is built to your specification. Enclosure, board layout, firmware behaviour and packaging follow your requirements, and in most contracts the tooling is paid for by you and belongs to you. This is the only model that gives you a product nobody else can sell.

2. Side-by-side comparison

3. Where the money actually goes

Buyers usually compare quoted unit prices. That comparison is misleading, because the three models do not carry the same fixed costs. The real comparison is total cost of ownership for the SKU, which has four layers:

The pattern is consistent: white label and ODM push fixed cost into the factory's catalogue and recover it across everyone who buys that platform. OEM pulls the fixed cost onto your balance sheet, which is why the unit price looks better at high volume and worse at low volume.

4. Certification responsibility — the part that causes recalls

This is where OEM deals fail after the container has shipped. The rule is not "the factory handles certification". The rule is: the entity placing the product on the market is the entity responsible for compliance.

Two practical consequences:

• Certification is per SKU, not per factory. A new enclosure, a different radio module or a larger battery can each require a new test report. This is one of the reasons private-label MOQ exists.
• Ask for the document, not the claim. Request the actual test report PDF, the certificate holder's legal name, and the model number printed on it. If the model number does not match what you are buying, the report does not cover your product.

5. Why MOQ exists, and how it is actually calculated

MOQ is not a negotiating tactic. It is the point at which three fixed costs stop losing money:

1. SMT changeover. Loading a line for a specific board, programming the pick-and-place machines and running first-article inspection costs the same whether you build 200 units or 2,000. Below a certain quantity that setup is not recoverable.
2. Packaging print runs. Custom boxes and manuals have their own minimum from the printer, and that minimum is usually higher than buyers expect.
3. Testing and certification per SKU. Each new configuration needs functional testing, aging testing and — where the radio or battery changed — new certification.

In practice MOQ moves with three variables: the model, the degree of customisation, and whether the configuration already exists in the factory's catalogue. A configuration that already runs on the line has a much lower entry point than a new one, and that is the cheapest way to test a market.

6. Timeline: what to expect at each stage

Projects that run late almost always lose time before production starts — in artwork approval, in firmware scope changes, or waiting for a lab slot. The production line itself is rarely the bottleneck.

7. Which model fits your situation

8. Red flags when comparing suppliers

• "We can do any MOQ." A factory that accepts 50 units of a custom SKU is either absorbing cost it will recover elsewhere, or will not deliver on time.
• No certificate holder name. If nobody can tell you which legal entity holds the test report, that report probably does not cover your product.
• Unit price with no fixed-cost breakdown. Tooling, firmware and certification should each be a separate line. A single blended number hides where the risk sits.
• No aging test in the process. Functional testing catches assembly errors. Aging testing catches the failures that show up in month three, in your customer's hands.

Frequently asked questions

Is OEM cheaper than ODM?

Per unit, at high volume, usually yes — because you stop paying for design work that is shared with other buyers. At low volume, almost never: tooling, firmware and new certification are fixed costs that only amortise across a large order.

Can I start with ODM and move to OEM later?

Yes, and it is the most common path. Start on an existing platform to validate the market, then invest in tooling and full certification once you have sell-through data. The configuration work you did in the ODM phase carries over.

Who pays for certification in an OEM project?

Normally the buyer, because in full OEM the buyer is usually the entity placing the product on the market and signing the declaration. The factory supplies samples, technical files and support through the test process.

How many units do I need before OEM makes sense?

It depends on tooling cost and how many markets you need certificates for, not on a fixed number. The right calculation is: (tooling + firmware + certification) ÷ your expected annual volume, compared against the per-unit premium of an ODM configuration.