The two halves of certification cost
The cost of a Matter certificate has two halves: a one-time certification and testing fee paid to earn the mark, and a recurring cost paid to keep the mark valid and the product listed. The first half is visible and easy to quote. The second half — the annual programme membership, the per-product listing fee, and the recertification events that arrive two or three years later — is what first-time brands forget, and it is what actually decides whether a thin-margin sensor line stays profitable across its life.
Thinking about certification as a single number also hides a structural fact: the certifying body runs a membership and programme model. A brand must hold a membership to certify products, and each certified product carries an annual listing charge on top of the membership. The one-time test fee is the headline; the membership and listing are the subscription.
The published fee structure
The published Matter certification schedule separates three recurring charges: an annual membership or programme fee for the certifying body, a one-time per-product certification fee, and a per-product annual listing fee that recurs for as long as the product is sold. A brand that certifies hardware typically joins at the Adopter or Participant tier; the exact tier and the precise per-product amounts shift with membership level and with the schedule in force at the time, so they are always confirmed per project rather than quoted as fixed forever. What is stable is the structure itself.
For a security product line the practical reading is simple. Joining the programme is a recurring annual cost whether you ship one SKU or fifty. Each SKU you certify adds a one-time certification fee. And each certified SKU then adds an annual listing fee that you pay every year the product is on the market. A line of ten certified sensors therefore carries ten annual listing fees plus the one membership — a number that compounds quietly if the catalogue grows without discipline.
What triggers recertification
Recertification is triggered by any change that alters what the certificate actually covers: a new Major or Minor version of the Matter specification that changes cluster behaviour, a firmware change to a certified cluster, a hardware change to the connectivity module or the RF path, or a change to the device-attestation chain. None of these are arbitrary. The certificate is a claim that a specific design, in a specific firmware state, on a specific module, behaves according to the spec. Change one of those and the claim must be re-examined.
The trap is that firmware changes feel free. They are not, in certification terms. A patch that adds a cluster feature, changes a cluster's behaviour, or even moves the firmware in a way that touches a certified endpoint can require a re-test or at least a delta assessment. The factory's job is to scope that delta before the change is committed, so the brand knows whether a quiet firmware update is a free patch or a recertification event. Treating every firmware build as certification-neutral is the single most common way a security brand walks into an unexpected cost.
The cheap way to extend a family
Matter was designed so a product family does not pay full price for every variant. Certification by similarity lets a follow-on product reuse an existing certificate when its design is close enough to a certified base model, instead of running a full new programme, and there are also rapid-recertification routes for closely related changes. A second colour, a regional power variant, or a small enclosure change that does not touch the RF or the certified clusters can often ride the base certificate for a fraction of a full certification fee.
The discipline is in the word "similar." A change that alters the connectivity module, the antenna, the MCU, or any certified cluster behaviour is no longer similar and must run the fuller route. A good manufacturer scopes the delta honestly: if the change is within similarity, the brand pays the similarity fee; if it is not, pretending otherwise just pushes the cost into a failed audit or a revoked listing later. For the one-time cost buckets that precede all of this, our Matter ODM cost breakdown covers the development, tooling and unit-cost side; this note covers everything that comes after the first certificate.
Who owns the recurring duties
The manufacturer that designs and builds the product owns and supports the certification programme, because the certificate covers a specific schematic, firmware state machine, enclosure and connectivity module — not an abstract concept of the product. Shenan Yangguang designs, prototypes, validates and mass-produces Matter security hardware, and we hold and support the certification for the products we build. We do not relabel a third party's certified product and present it as ours.
In practice that means we track the listing and renewal obligations, we flag the firmware and hardware changes that would require recertification before they are committed, and we run the certificate through the right route — full, by similarity, or rapid recert — based on the real delta rather than on what is cheapest to say today. For a brand, the value is not just that the certificate exists at launch; it is that someone is watching the recurring side so the line does not quietly fall out of compliance two years in. If you are planning a multi-SKU security line and want the lifetime certification cost modelled honestly, send the planned variants and we will scope which ones share a certificate and which ones need their own.