MatterODM by Shenan YangguangProduct line, not product list
A product line is a family of related SKUs that share a platform — enclosure, connectivity module, firmware base and certification footprint — while varying in function, finish or market; treating it as a mere list of unrelated items is what makes a new brand expensive to run. The line is an asset that compounds: the second SKU is cheap because the first one paid for the platform. A list of unrelated gadgets gives you none of that compounding and all of the overhead.
A shared hardware platform is the set of common mechanical, radio and firmware building blocks reused across several SKUs — one enclosure family, one standard CSA-certified connectivity module, one battery architecture, one firmware base — so each new variant costs far less to develop than a from-scratch design. Shenan Yangguang designs and owns this platform for the Matter security hardware we produce. We do not relabel a third party's finished devices; we build the schematic, the enclosure, the firmware and the certification programme, which is what makes a coherent line possible rather than a pile of incompatible SKUs.
How many SKUs to start with
A disciplined starting set is usually a small core — a door/window contact, a PIR motion sensor, and sometimes a combined contact-plus-PIR or a local alarm hub — enough to form a real intrusion-detection story without spreading certification and inventory thin. The exact count depends on the channel and the markets, but the principle holds: launch where the alarm logic is complete, then expand. A contact that opens a local siren through a binding, plus a PIR that does the same, is a security story. A lone sensor on a shelf is a component.
Each SKU carries certification cost, inventory, support and its own shelf of failure modes, so launching many at once spreads a new brand thin and hides which product actually sells; starting narrow proves the alarm logic end to end and earns the right to expand. The platform investment pays back exactly when the brand adds the next variant on top of what already works.
Standardize what the customer never sees
The platform discipline is mostly invisible: standardize the enclosure mounting, the battery type, the standard CSA-certified connectivity module and the firmware base so that what differs between SKUs is function and finish, not the underlying engineering. When the battery is the same across the line, the support team learns one replacement cycle; when the module is the same, one certification footprint covers the radio for the whole family; when the firmware base is shared, a fix propagates instead of being reinvented. This is factory engineering, and it is the difference between a line that scales and one that fragments.
Finish and region are the cheap variables
Once the platform is fixed, the variables that are genuinely cheap to change are finish and region — a white or black enclosure, a branded label, a market-specific plug or radio band — while the expensive variables (the schematic, the module, the firmware, the certification) stay constant across the whole family. This is why a brand can offer colour choices or serve both the EU and US from one engineering base without re-opening the design: the regulatory differences for a battery sensor are mostly in marking, documentation and the radio band, not in the core hardware. A factory that owns the platform plans for these regional variants up front, so adding a market is a paperwork and configuration task, not a new development programme.
Composed-device expansion
Composed-device expansion is the strategy of putting several Matter device types into one enclosure and certifying the whole unit once, rather than shipping and certifying each function as a separate product — turning two or three SKUs' worth of certification into a single programme. A combined contact-and-PIR, or a hub that also acts as a Thread border router, becomes one certification effort instead of two or three. The saving is in development, tooling and certification, and it is only clean to do when the underlying platform was designed for it from the start.
This expansion only pays off on a platform built for it: the enclosure must have the space and the antenna budget, the module must have the headroom, and the firmware base must already support multiple endpoints, or "composed" becomes a costly retrofit. We plan the platform so composed devices slot in as a natural next step — the hardware is already there, and the certification programme is scoped to add device types rather than restart. A brand evaluating a factory should ask directly whether the platform was designed for composed devices or bolted together afterward.
Where the factory's ownership lies
The manufacturer that builds the line owns the shared platform and the certification footprint, because both come from the schematic, the firmware and the test programme it controls — and a brand cannot reshape a platform it does not own. This is the heart of the factory-versus-relabeller distinction. A brand that relabels a third party's finished product inherits that third party's platform, its SKU limits and its certification shape, and can only re-skin what it is given.
Shenan Yangguang designs and owns the shared platform for the Matter security hardware we produce — enclosure, standard CSA-certified module, battery architecture and firmware base — and we plan the certification programme so new variants and composed devices slot in without re-qualifying from zero. That ownership is what lets a brand start with two SKUs this quarter and add a composed device next quarter without reopening the whole engineering file. If you are planning a Matter security line, send us your intended functions and target markets; we will propose the platform and the SKU sequence that gets you to market fast and expands cheaply.