MatterODM by Shenan Yangguang
Request a Quote
Home › Insights › Matter Certification Testing
Matter · Certification · Testing

Matter Certification Testing: PICS, the Test Plan, ATL Selection and What Usually Fails

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

Most Matter certification delays are not caused by the test lab. They are caused by what reaches the lab: an incomplete feature declaration, firmware that does not match the claim, or attestation that was never set up. Here is the testing process as a factory runs it, and the failure modes worth planning around before you book the slot.

Key takeaways

  • The PICS defines the test scope — the lab only exercises the features you declare, so an honest, complete PICS is the first control on schedule and cost.
  • Testing runs through a CSA-recognized Authorized Test Lab; the decision is which one, not whether to use one.
  • Most failures are preparation problems: cluster-behaviour gaps, commissioning errors and attestation mistakes, not the lab's clock.
  • A factory-side pre-test closes those gaps on the bench, where a re-run is free, instead of at the ATL, where it costs a second pass.
  • Certification is a process owned jointly by the brand and the manufacturer; the brand holds the certificate, the factory owns the evidence.

Certification testing is where timelines slip

Matter certification testing is the phase in which an Authorized Test Lab executes a defined set of conformance and interoperability cases against a product sample to produce the evidence a certificate requires. The phase itself is bounded; the slips come from everything feeding into it. A brand that scopes certification late, or hands the lab firmware that does not match the feature declaration, can lose weeks that had nothing to do with the test equipment. We therefore treat testing as the output of a preparation chain, not a standalone event.

Step one: building the PICS

A PICS (Protocol Implementation Conformance Statement) is the document in which a manufacturer declares which Matter features and optional behaviours its product implements, and it defines the scope of certification testing because the test lab only exercises the features the PICS claims. This single document sets both cost and schedule: a larger, optional-rich PICS means more test cases and more chances to fail one. The honest move is to declare exactly what the product does, no more, and to make sure the firmware actually delivers it.

PICS drives cost and schedule

The PICS drives cost and schedule because every declared feature becomes a set of test cases the lab must run and the brand must pay for and pass, so over-claiming optional behaviour adds both expense and risk without adding product value. We build the PICS from the device's actual cluster set — for a contact sensor that is the ContactSensor cluster and its mandatory attributes, for a PIR the OccupancySensing cluster, and so on — and we review it against the firmware before submission. A PICS that promises a behaviour the code does not implement is the most expensive typo in the programme, because you only find out at the lab.

Step two: the test plan from the ATL

The Matter test plan is the concrete list of test cases derived from the product's PICS that the ATL executes, covering conformance, interoperability and, for security-relevant devices, the cluster behaviour thatControllers rely on. The lab turns the PICS into a plan and confirms the sample configuration, the commissioning method and the controllers it will pair against. For a security sensor, the plan is not just "does it join the network" — it covers the state reports a controller expects, the attribute reads, and the failure signalling. We review the plan with the brand so there are no surprises about what "pass" means for a door or motion event.

Step three: choosing an ATL

An ATL (Authorized Test Lab) is a CSA-recognized laboratory authorized to run Matter conformance and interoperability tests and to issue the results that support a certification, so the choice is between recognized labs, not whether to use one. All recognized labs run the same specification, but they differ in lead time, sample handling, regional location and how they communicate during the run.

What to check in an ATL

The practical checks when selecting an ATL are current recognition for the device category, available slot lead time, clarity on sample quantity and shipping, and a working style that reports failing cases early rather than only at the end. We have found that the cheapest line item is rarely the cheapest outcome; a lab that surfaces a failing case in week one lets you fix it before the clock runs out, while a lab that batches everything to the final report can turn a small gap into a full re-run. The brand holds the commercial relationship with the lab in most programmes, and we support it with the technical submission package.

What usually fails

The failures that actually occur in Matter security-device testing are overwhelmingly preparation problems — cluster-behaviour gaps, commissioning and attestation errors — rather than the lab discovering a fault in compliant hardware. Knowing the usual suspects lets a factory pre-empt them.

The cluster-behaviour traps

A cluster-behaviour trap is when the PICS claims a feature the firmware only partially implements — for example reporting an occupancy state but not the expected attribute, or a contact that joins but does not emit the open/closed transition a controller waits for — and the lab's case fails on that gap. These are invisible until paired against a strict controller, which is exactly what the ATL provides. Our counter is an internal pre-test against reference controllers and the official test harness before the sample ships, so the gap is closed on the bench where a re-run costs nothing.

The attestation and commissioning traps

An attestation or commissioning trap is a malformed setup code, a missing or incorrectly provisioned Device Attestation Certificate, or a commissioning flow that works on one app but not another — all of which block the very first step of testing. Device attestation is a line discipline we treat seriously: the DAC, the PAI/PAA chain and the DCL entry must line up before the device leaves the factory, not patched after a failure. Our article on Matter device attestation goes deeper on why provisioning is a manufacturing control, not a software afterthought.

How a factory shortens the loop

A factory shortens the certification loop by running an internal pre-test that mirrors the ATL's cases, fixing cluster and attestation gaps on the bench, and submitting a stable sample with a complete, accurate PICS — so the lab's run is confirmation, not discovery. We integrate a standard CSA-certified Matter connectivity module as the radio component, which removes one whole class of radio-layer surprises, and we keep the application-cluster implementation and the attestation provisioning as our own controlled process. The brand still owns the certificate and the relationship with the lab; we own the evidence that gets it granted. The broader routes and budget picture are covered in our pieces on certification paths for alarm sensors and certification cost and timeline.

Factory stance

Shenan Yangguang designs, prototypes, validates and mass-produces the Matter security hardware and runs the pre-certification work; we do not relabel a third party's certified product. Our job on testing is to hand the ATL a sample that passes the first time it reasonably can: an honest PICS, firmware that matches it, and attestation provisioned on the line. Where a feature is still maturing and we are unsure it will pass, we say so and scope it out of the first certificate rather than risking a failure on a claim we cannot yet stand behind.

Frequently asked

What is a PICS in Matter certification?

A PICS (Protocol Implementation Conformance Statement) is the document in which a manufacturer declares which Matter features and optional behaviours its product implements, and it defines the scope of certification testing because the test lab only exercises the features the PICS claims.

What does an Authorized Test Lab (ATL) do, and do I have to use one?

An ATL is a CSA-recognized laboratory authorized to run Matter conformance and interoperability tests and to issue the results that support a certification. Certification normally requires testing through such a recognized lab, so the ATL is not optional for a full certificate; the choice is which recognized lab you use.

How long does Matter certification testing take?

The testing window itself is typically a few weeks once a stable sample and a complete PICS reach the lab, but the real schedule is set by preparation and rework. Most delays come from incomplete PICS, firmware that fails cluster behaviour, or attestation setup problems before the lab ever starts, not from the lab's clock.

What is the most common reason a Matter security device fails testing?

The most common reasons are cluster-behaviour gaps — the device claims a feature in the PICS but does not implement it correctly — and commissioning or attestation problems such as a malformed setup code or Device Attestation Certificate. These are preparation issues, which is why a factory runs an internal pre-test before the sample leaves the bench.

Can a product be fixed and re-tested if it fails?

Yes. A failure is not the end of the programme: the lab reports the failing cases, the firmware or configuration is corrected, and the affected tests are re-run. The cost is schedule and a second test pass, which is why closing gaps in a pre-test is cheaper than discovering them at the ATL.

Want a certification run that passes the first time it reasonably can?

Send the target device type and cluster set. We build the PICS from the real firmware, pre-test against reference controllers, and hand the ATL a stable sample.

Request a Quote