From RFQ to Mass Production: How a Matter Security ODM Runs a New-Product Program

What an ODM new-product program actually is

An NPI (New Product Introduction) program is the managed sequence of stages that turns a brand's requirement into a shippable, certified product, and in an ODM context the manufacturer owns the engineering milestones while the brand owns the product definition and the market it sells into. The value of a disciplined program is not the paperwork; it is that the brand's decisions happen at the right gate instead of after tooling has been paid for. We run a fixed set of stages so that cost, certification and manufacturability are settled in order, and so a surprise in one stage does not quietly become a recall in another.

Stage 1 — Feasibility and RFQ reply

Feasibility is the gate where the factory tells the brand, honestly, whether the requested product can be built to spec, to budget and to the required certifications within the expected timeline. A useful RFQ states the product type and the exact sensors or functions needed, the target markets with their marks (CE, FCC, UKCA, RoHS and so on), the expected volume and a realistic timeline, plus any hard constraints such as battery life or enclosure rating. The more precise the brief, the more accurate our feasibility reply and the quote — and the fewer surprises appear during certification. Where a requirement conflicts with a regulation or a physics limit, this is the cheapest moment to hear it.

Stage 2 — Design: schematic, firmware and the connectivity module

The design stage turns the agreed specification into a schematic, a firmware plan and a mechanical enclosure, and for a Matter device it centres on integrating a standard CSA-certified Matter connectivity module rather than building the radio from scratch. We design the sensor around the module's flash, RAM and RF behaviour, because those constraints ripple into everything else — the lens, the battery budget, the enclosure. The brand's job here is to lock the feature list, because every late feature addition after this point is a re-spin, not a tweak. We treat the design freeze as a real event, not a suggestion.

Why the module choice is a design decision, not a purchase

The connectivity module sets the radio, the firmware headroom, the certification path and the per-unit cost at once, so choosing it is one of the earliest and most consequential design decisions in the program. We integrate modules that already carry CSA certification, which shortens the brand's path to a certificate, but the module still has to be positioned, shielded and tuned inside our enclosure. The wireless link is only as good as the board and the housing around it — a point we cover in the RF design notes and the low-power design notes.

Stage 3 — EVT: does the concept work?

EVT (Engineering Validation Test) is the stage that proves the design works as a concept, using a small number of hand-built or prototype units to confirm the circuit, the firmware and the basic detection behaviour. This is where we find the obvious problems — a lens with the wrong coverage, a battery that cannot sustain the duty cycle, a board that fails our first RF check. EVT is deliberately rough; its job is to fail cheaply and early. A brand should expect functional prototypes here, not production-quality ones.

Stage 4 — DVT: is the design correct and certifiable?

DVT (Design Validation Test) proves the design is correct and certifiable, using a small batch built to near-final process to confirm performance, environmental behaviour and the test evidence certification will require. This is the stage where the test plan for Matter certification is executed or rehearsed, where the PICS document is finalised and where the device either demonstrates the cluster behaviour it claims or exposes a gap. We run our own validation — EMC pre-scan, environmental and life testing — so that the formal certification pass is a confirmation, not a gamble. A brand that skips DVT to save time usually pays for it at certification.

Stage 5 — Certification: the shared obligation

Matter certification is a shared responsibility in which the factory builds the device to spec, runs the test plan and integrates a certified module, while the brand is normally the certificate holder and the legal entity that places the product on the market. The exact split — who pays, who holds the certificate, who keeps the test records — should be written down before the program starts, because it decides who carries the obligation if a question arises later. Certification is also the stage most often underestimated in a timeline, which is why we plan it from the feasibility gate rather than adding it at the end. The route chosen (full certification, family, similarity or transfer) changes both lead time and cost, and we advise the brand on that choice with the product's volume in mind.

Stage 6 — Tooling and PVT: can we build it at volume?

PVT (Production Validation Test) proves the factory can build the product consistently at volume, using tools, fixtures and the real production line to confirm that what passed DVT can be repeated thousands of times. Tooling — the molds and jigs — is committed here, which is why the design must be frozen first; changing a dimension after this point means new tooling. We qualify the line, calibrate the test stations and confirm the yield, because a beautiful prototype that cannot be built repeatably is not a product. The brand's role is to approve the pilot run and the agreed acceptance criteria before the ramp.

Stage 7 — Ramp and mass production

Mass production is the steady-state stage where units are built, tested and shipped against the agreed quality plan, and where the factory's line discipline — traceability, calibration, incoming inspection — keeps every unit like the certified one. We integrate a standard CSA-certified Matter connectivity module and provision device attestation on the line, then ship against the compliance marks the brand's markets require. The program does not really end at first shipment; the post-shipment duties — firmware updates, field support, lifecycle — are a separate commitment we cover in our notes on the ODM support duty.

Factory stance: we own the build, you own the brand

Shenan Yangguang designs, prototypes, validates and mass-produces these sensors; we are the factory, not a relabeller of someone else's product. That means the engineering milestones above are ours to deliver, and the brand's decisions — definition, markets, certificate holding, volume — are respected as the brand's own. We are deliberate about writing down the certification and IP split before a program starts, because a vague split is the most common source of friction later. Where a timeline or a regulation is uncertain, we say so at the feasibility gate rather than promising a date we cannot keep. A good ODM program is less about speed and more about the right decision landing at the right gate — and that is the discipline we sell alongside the hardware.

For the compliance marks themselves, see our CE/FCC/RoHS/UKCA checklist and the deeper Matter certification paths note, and for what happens after shipment read the factory validation and ODM support notes.