MatterODM by Shenan Yangguang
Request a Quote
Home › Insights › Matter Certification Transfer
Certification · Transfer · Smart Home Security

Matter Certification Transfer & Certification by Similarity: Reusing a Certificate the Right Way

Published 2026-10-28 · 9 min read · By Shenan Yangguang engineering

Brands hear two promising phrases around Matter certification — "we can transfer the certificate" and "this qualifies for certification by similarity" — and both can be true, but neither is a free pass. Each route has a hard boundary, and crossing it silently turns a shortcut into a non-compliant product. Here is the honest map of when a certificate moves and when it does not.

Key takeaways

  • Certification transfer moves an existing certificate and its Vendor ID / Product ID to a new holder so fielded devices keep the same identity in the Distributed Compliance Ledger.
  • Certification by similarity extends a certificate to a near-identical product without repeating the full test suite, after the certification body reviews the engineering delta.
  • The claim breaks the moment the radio, connectivity module, device type, clusters or certified firmware behaviour change — those are exactly what the original test verified.
  • A transfer preserves the device identity ecosystems recognise, but a new Product ID should still be re-validated against target ecosystems.
  • A factory should scope the delta in writing before promising a shortcut; an unverified similarity claim is a compliance risk, not a saving.

What "certification transfer" and "certification by similarity" actually mean

Certification transfer, in the Matter context, is the process of moving an existing, valid Matter certificate — and the Vendor ID (VID) and Product ID (PID) recorded against it — from one certificate holder to another, or extending it to a closely related product, without repeating the full conformance test suite from scratch. The reason this is possible at all is that a Matter certificate is tied to a specific product identity recorded in the Distributed Compliance Ledger (DCL), the public database that controllers and ecosystems check to confirm a device is genuine and conformant. If the product's conformance-relevant identity can be preserved or lawfully moved, there is no need to re-prove what was already proven. The two routes that use this idea are ownership transfer — the certificate changes hands — and certification by similarity — the certificate reaches to cover a new but near-identical product. Both are real, both are governed by the Connectivity Standards Alliance's rules, and both are easy to over-promise.

Three situations where a certificate moves instead of starting over

Most "can we reuse the cert?" questions fall into one of three buckets. Knowing which bucket you are in decides whether you save months or waste them.

Transfer of ownership (the VID moves with the product)

A transfer of ownership happens when the legal entity that holds a Matter certificate changes — for example a brand acquires a product line, or a manufacturer's programme is handed to the brand that will sell it — and the certificate, VID and PID travel with the product so the fielded devices keep their identity in the Distributed Compliance Ledger. This is the cleanest case, because nothing about the device changes; only who holds the paper changes. The ecosystems that already recognise the device keep recognising it, and customers with the product installed are unaffected. The practical caveats are administrative: the transfer must be executed through the proper CSA process, the responsible contact and the testing laboratory of record should be informed, and any onward support obligation should be written down so the new holder actually owns the certificate, not just a screenshot of it.

Certification by similarity (a new but near-identical product)

Certification by similarity is the route offered when a new product is functionally and electrically close enough to an already-certified one that it does not need the full conformance test suite repeated; the certification body reviews the delta and, where the change is within scope, extends the certificate rather than running the whole suite again. A classic example is a second colourway, a different enclosure shape, or a regional variant of the same board: the radio is identical, the firmware behaviour is identical, the device type and clusters are identical, so the only honest question is whether the visible change could alter conformance. It usually cannot, and the body agrees. The saving here is real — weeks of test-lab queue and a meaningful slice of programme cost — but it rests entirely on the delta being confined to non-conformance-relevant parts.

When a change quietly breaks the claim

The similarity claim fails the moment a change touches the conformance-relevant parts of the product — a different radio or connectivity module, a new device type, changed clusters, or firmware that alters certified behaviour — because those are exactly the things the original test verified, and the body must re-test or refuse the extension. This is where projects go wrong. A team swaps a connectivity module for a "drop-in equivalent" from a different supplier, assumes the similarity route still applies, and discovers late that the new module changes the radio certification footprint and the attestation chain. Or they add a cluster to support a new feature and assume it is minor, when in fact any change to certified behaviour is a new certification event. We treat the module, the device type and the cluster set as the bright line: inside it, similarity; outside it, full or near-full certification. There is no middle ground a factory should bet a shipment on.

What this means for your BOM, your schedule and your risk

A reused or extended certificate protects the schedule only if the underlying hardware stays inside the certified envelope, so the BOM discipline that kept the original product certifiable is the same discipline that keeps the similarity claim alive for its derivatives. For a brand, the operational implication is that "cheap variant" engineering has to be cheap in the right places. Changing a housing material, a label, a battery holder or a cosmetic feature is usually free from a certification standpoint; changing the connectivity module, adding a sensor type that brings a new cluster, or rewriting the firmware state machine is not. We surface this at the quotation stage, because a variant that looks like a similarity case but is actually a full certification is the difference between a four-week delta review and a multi-month new programme — and between a saved cost and a surprise one.

Factory stance: we scope the delta before we promise a shortcut

Shenan Yangguang designs, prototypes, validates and mass-produces Matter security hardware; we hold and support the certification programmes for the products we build, and we do not relabel a third party's product. On transfer and similarity we are deliberately conservative: we document the engineering delta from the certified baseline, we separate conformance-relevant changes from cosmetic ones, and we tell the brand in writing which route the delta actually supports before any commitment is made. If the delta is inside the envelope, we pursue the similarity route and prepare the delta package the certification body expects. If it crosses the line, we say so early, because an unverified similarity claim that collapses at audit is a far larger cost than running the tests properly the first time. Where a VID or PID needs to move between entities, we handle the paperwork through the proper CSA process rather than leaving the brand to discover the gap after launch.

For the mechanics of how a product is first certified, see our Matter certification procedure guide; for how a change to the radio changes your obligations, our RF and radio certification view covers the module question directly.

Frequently asked

Can a Matter certificate be transferred to another company?

Yes — the ownership of a Matter certificate, together with its Vendor ID and Product ID, can be transferred from one certificate holder to another so that fielded devices keep the same identity in the Distributed Compliance Ledger; the exact mechanism and any fees are governed by the Connectivity Standards Alliance and should be confirmed per project before the transfer is relied upon.

What is certification by similarity in Matter?

Certification by similarity is the route offered when a new product is functionally and electrically close enough to an already-certified one that it does not need the full conformance test suite repeated; the certification body reviews the engineering delta and, where the change is within scope, extends the existing certificate rather than running every test again.

Does changing the enclosure count as similar enough?

Usually yes, if the internal electronics, connectivity module, device type and certified clusters are unchanged, because the conformance-relevant parts are what the original test verified; but a change to the radio, the module, a cluster or certified firmware behaviour breaks the similarity claim and triggers re-testing.

Will a transferred or similar product keep working with existing ecosystems?

The device identity recorded in the Distributed Compliance Ledger is preserved through a transfer, so controllers still recognise it as a certified product; where a new Product ID is issued, the brand should re-validate against the target ecosystems because each ecosystem maintains its own compatibility checks on top of the Matter certificate.

How should a brand decide between full certification and certification by similarity?

The decision is driven by the engineering delta from the certified baseline: a cosmetic or enclosure-only change usually qualifies for the similarity route, while any change to the radio, module, device type or certified clusters should be budgeted as a full or near-full certification; we scope the delta in writing before promising a shortcut.

Planning a variant or acquiring a certified line?

Send us the certified baseline and your proposed change. We scope the delta in writing, separate cosmetic from conformance-relevant changes, and tell you whether transfer or certification by similarity applies — before you commit.

Request a Quote