MatterODM by Shenan YangguangOEM vs ODM, without the jargon
An OEM (original equipment manufacturer) relationship traditionally means the client provides the design and the factory produces it. An ODM (original design manufacturer) relationship means the factory provides the design and the client applies its brand. In smart-home security the line is rarely that clean: most partnerships sit on a spectrum, with the factory owning more or less of the schematic, firmware, and enclosure depending on the client's own capability.
The practical question for a founder is not "OEM or ODM?" but "who owns the engineering risk?" When the factory owns schematic, firmware, and tooling, your time-to-market drops and your unit economics improve — at the cost of less design differentiation. When you own the design, you keep control but carry the NRE, the certification burden, and the debug cycle.
A useful way to frame the choice
If your edge is brand, distribution, or a specific app experience, an ODM-style partner that supplies proven hardware frees you to spend on what you own. If your edge is a novel sensor or enclosure, an OEM-style build of your design protects that moat. Many security brands start ODM and migrate specific SKUs to custom OEM as volume justifies the tooling.
What a real manufacturer owns, end to end
Shenan Yangguang is the factory, not a trading desk. The work that determines product quality lives inside our walls:
- 画板 / Schematic & PCB design — circuit and layout owned by our engineering team, not outsourced.
- 打板 / Prototyping & board bring-up — functional samples validated before any tooling money is spent.
- 研发 / Firmware & product R&D — device behavior, clusters, OTA, and app integration.
- 配合认证 / Certification cooperation — test samples, fixes, and standards documentation.
- 大面积出货 / Mass production — enclosures, SMT assembly, QC, and scale.
Owning these steps is what lets a factory tune the things customers actually feel: battery life, false-alarm rate, and how cleanly a device pairs. It is also what separates a manufacturer from a re-badger.
Connectivity is a component, not a product
A common confusion in this category: brands assume "Matter" or "the app" is something the factory is. It is not. Connectivity is integrated as a standard CSA-certified Matter connectivity module — a purchased component, exactly like an MCU, a PIR element, or a speaker. We select and integrate it; the silicon and the certification behind it come from the module supplier.
This matters for your positioning. Because the connectivity layer is a component we source and integrate, the finished device carries our design, our enclosure, and our brand program. We do not resell a third party's finished product under a private label and call it ours. The value a factory adds is everything around that module: the board, the firmware, the enclosure, the certification cooperation, and the volume.
The white-label app + cloud stack
A white-label app + cloud stack is a ready application and backend that a factory provides under your brand — your logo, your name, your store listing — without you building the software from scratch. It connects to the device firmware so end users get setup, alerts, and remote control. For a new brand this removes the hardest, slowest part of launch: standing up cloud infrastructure and a polished mobile app. You should still confirm data residency and the upgrade path, because the app is the part customers touch every day.
Certification cooperation is the real differentiator
Anyone can ship an uncertified sensor. Shipping one that interoperates with Apple Home, Google Home, Alexa, and SmartThings — and clears radio and safety rules in your target markets — is the hard part. A factory with in-house engineering can cooperate through the CSA Matter process:
- CTP (Certified Product Type) route — reuse a pre-certified base to shorten time-to-market.
- Composed-device support for multi-endpoint products (sensor + siren + light in one certified device).
- Firmware and cluster configuration aligned to the Matter specification.
- Engineering cooperation on test samples, fixes, and CSA documentation, plus pre-testing to compress the timeline.
Equally important for cross-border sales: the same factory should be able to support CE (EU), FCC (US), RoHS, and UKCA evidence — see our companion compliance guide.
How to evaluate a manufacturing partner
Five questions cut through the brochures:
- Where is the engineering? Do they own schematic/firmware, or just assembly?
- Who certifies? Can they show a real certification cooperation history, not just "we can do Matter"?
- What is sourced vs owned? Ask plainly what is a component and what is their design.
- What is the app story? White-label, your app, or a bridge to a platform you already use?
- What does scale look like? Lead times, MOQ, and whether tooling is shared or dedicated.
None of these require you to reveal your bill of materials. A confident factory answers them directly and shows you the bench, not just a catalogue.
Lead time, MOQ, and who carries the tooling
Two commercial details decide whether a partnership scales. Lead time is the gap between "approved sample" and "cartons on a boat" — it is driven by component sourcing, enclosure tooling, and certification, not by assembly alone. MOQ (minimum order quantity) sets how much working capital a launch ties up; a factory that shares tooling across a platform family can usually quote a lower MOQ than one carving a unique mold per SKU. Ask plainly who owns the tooling and what happens to it if the programme pauses — dedicated tooling is an asset on your balance sheet, shared tooling is a cost you avoid.
The factory stance, stated plainly
We are a manufacturer. We draw the boards, bring them up, write the firmware, cooperate on certification, and ship at volume. Connectivity modules and the app/cloud layer are components we integrate — the same way any OEM integrates chips. That is the honest description of how modern hardware is built, and it is the foundation a security brand can stand on without pretending the factory is something it is not.