MatterODM by Shenan Yangguang MatterODM by Shenan YangguangAll four end with the same thing: a Certificate of Compliance, a Certification Declaration, the right to use the Matter logo, and an entry in the Distributed Compliance Ledger (DCL). What differs is how much testing the product needs and who is eligible to use the route.
| Route | What it is for | Testing required | Who qualifies |
|---|---|---|---|
| Full certification by testing | A new design, or any product that is not derived from something already certified | Full specification test at an Authorized Test Lab (ATL) or a Specification Validation Event (SVE) | Anyone with Adopter membership or above |
| Certification by Similarity (CbS) | A product derived from an already-certified product, where the Matter-relevant implementation is unchanged and only unrelated parts differ | None, once CSA confirms the product qualifies | Derived products; the CSA certification team decides applicability |
| Certification Transfer Program (CTP) | Re-badging — putting an already-certified product into another brand's product, with no hardware and no software change | None | The transferring party must be a CSA Participant or Promoter member; the receiving brand works through that membership |
| Product Family / Portfolio certification | Several variants of the same platform — regional plug types, cosmetic variants, or a range sharing the same firmware with different feature subsets | Only the parent product is fully tested; the family or portfolio members are certified on the strength of it | Variants that share a parent and do not change conformance. A portfolio route requires a genuine, deliverable parent with the fullest feature set |
Eight steps from membership to a ledger entry. Steps 1–4 are prerequisites that most schedules underestimate.
| Step | What happens | Notes from our own projects |
|---|---|---|
| 1 | Become a CSA member | Adopter level or above is required to develop, test and certify. Associate level cannot submit a product for testing. |
| 2 | Request a Vendor ID (VID) and choose Product IDs (PID) | The VID is assigned by CSA; the PID is your own 16-bit identifier. Every distinct product needs its own PID and its own certification. |
| 3 | Finalise the product and select the network transport | Thread, Wi-Fi, Ethernet or Bluetooth-for-commissioning. This choice cascades into step 4. |
| 4 | Obtain transport certification from the relevant standards body | Thread through the Thread Group, Wi-Fi through the Wi-Fi Alliance, Bluetooth through the Bluetooth SIG, Ethernet via PMA attestation. Inheritance from a certified module is often possible and removes weeks from the schedule — checking this early is one of the cheapest schedule wins available. |
| 5 | Product testing — or skip it | If the product qualifies for CbS or CTP, you go straight to step 6. Otherwise an ATL runs the specification tests. |
| 6 | Submit the certification application | Through the CSA Certification Web Tool, with the documents listed in the next section. |
| 7 | CSA reviews the application | This is where an incomplete or inconsistent document set costs you a full cycle. |
| 8 | Approval and publication | Certificate of Compliance, CSA website listing, certified logos, Certification Declaration, and the DCL record that lets devices commission into ecosystems. |
Four documents are requested at application. Each one depends on decisions made much earlier in the project — which is why we produce them during development, not the week before submission.
| Document | What it has to say |
|---|---|
| Declaration of Conformity (DoC) | Your formal declaration that the product conforms to the specification. |
| PICS Protocol Implementation Conformance Statement | The declared feature set: which clusters, attributes and commands the product supports. This is the single most consequential document in the pack. Under-declare and the product is under-tested; over-declare and you commit to behaviour you have not implemented. |
| Network Transport Attestation | Proof of the transport certification obtained in step 4, or of inheritance from an already-certified component. |
| Security Attestation | Evidence that the security requirements are met, including the device attestation credentials used during commissioning. |
The moment a product does two things — a sensor that also reports temperature, a plug that also monitors energy, a panel that combines a switch and a sensor — the endpoint structure becomes a certification decision rather than a firmware detail.
| Concept | What it means for certification |
|---|---|
| Composed device | One Matter node presenting more than one functional device type, each on its own endpoint, with the root node at endpoint 0. Tested as a whole. |
| Endpoint and cluster allocation | Decides the test surface. Allocating the same function across two endpoints instead of one can change which test cases apply and how many. |
| Bridge / aggregator | A different construction: a Matter node that exposes non-Matter devices to the ecosystem through bridged endpoints. Bridges have their own requirements and are not simply "a device with extra endpoints". |
We do not publish a single headline price for Matter certification, because there is no honest single number — a similarity-based re-badge and a clean-sheet multi-endpoint device are not the same purchase. What we can give you is the composition, so you can see which lever you are pulling.
| Cost component | Driven by | How to control it |
|---|---|---|
| CSA membership | Membership tier | If you have no other Matter programme, running the certification under an existing membership is usually cheaper than joining for one product. |
| Certification application fee | Membership tier and route | Similarity and transfer routes carry lower application fees than full certification. |
| Test lab fee | How much of the specification the product exercises | The dominant variable. Controlled by an accurate PICS and a clean pre-compliance run. |
| Transport certification | Thread, Wi-Fi, Bluetooth | Check inheritance from the certified module before assuming it has to be tested again. |
| Pre-compliance engineering | How mature the firmware is on first submission | Cheap insurance. A dry run against the test harness costs a fraction of a failed lab cycle. |
| Re-test | Whether the first submission passes | Only eliminated by doing the previous line properly. |
We keep an internal checklist of the items that have actually caused a failed or delayed submission in our own projects. It covers membership and identification, the data model and PICS, transport certification inheritance, the security and attestation items, sample preparation and the document set.
The checklist we run before every submission. Built from our own failures, not from a specification summary. Request it and we will send the current version by email.
Tell us the product type and whether anything similar is already certified. We will tell you which routes are realistically available to you and what each one implies for cost and schedule.
The cost has five parts: CSA membership, the certification application fee, the test lab fee, transport certification, and pre-compliance engineering. The lab fee dominates and depends on how much of the specification your product exercises. A similarity-based route removes the lab fee almost entirely — but only if the product is genuinely derived from something already certified.
Application and review is not the long pole. The schedule is dominated by three things: whether transport certification can be inherited, how clean the pre-compliance run is, and lab availability. A well-prepared product with inherited transport certification moves through in weeks; a product that fails its first submission can lose a full cycle to lab re-booking.
Certification by Similarity (CbS) certifies a product derived from an already-certified product, typically with no additional testing. The Certification Transfer Program (CTP) is for re-badging: one member's certified product is carried into another brand's product, with no hardware or software change. CbS is about the product being similar; CTP is about a commercial transfer of an existing certificate.
To certify a product you need at least Adopter membership. Associate membership is cheaper and permits participation in the Certification Transfer Program, but not product testing. If you work with us, the certification can run under a membership that already exists, which removes both the fee and the setup time.
Sometimes — that is what CTP is for. But the transfer has to be a real arrangement between CSA members at the right tier, and it only covers a product that is unchanged in both hardware and software. If you need any change, the certificate does not transfer and you are back to a testing route.
A composed device is a single Matter node that presents more than one functional device type on separate endpoints. You need one when your product does more than one thing and you want it to appear as one device to the ecosystem rather than several.
The transport must be certified before Matter certification completes. Often this can be inherited from a certified module or certified component library, which is both cheaper and faster than testing the transport again. If your design uses a host/RCP architecture, that inheritance may not be available — worth checking before the design is frozen.
A Declaration of Conformity, the PICS, a Network Transport Attestation and a Security Attestation. The PICS is the one that most often causes trouble, because it defines the test surface.
You fix the failure and resubmit, which usually means paying for another lab slot and waiting for availability. Most failures we see are behavioural or cluster-configuration issues that a pre-compliance dry run would have caught.
Not always. There is a rapid re-certification route for products updated because of SDK or specification changes. Whether it applies depends on what changed and how it maps to the original declaration — if the cluster behaviour changed, the PICS changes with it.
The Distributed Compliance Ledger. Once a product is certified, its compliance record is published there, and that record is what allows the device to be recognised as certified when it is commissioned into an ecosystem. A certificate without a ledger entry is not the end state — the ledger entry is.
Send the product type and whether anything similar has already been certified. We will tell you which routes are realistically open and what each one costs you in time and money.