Zigbee Alliance Product Certification


Silicon Labs provides a Zigbee Alliance Certified stack, but the Zigbee Alliance also provides a path for product certification as a Zigbee Compliant Platform or Zigbee Certified Product.


We're sharing details here of the Zigbee certification process provided by the Zigbee Alliance for your information and convenience. The Zigbee Alliance my change these details at any time. If you have questions about Zigbee certification or the certification process, we recommend contacting the Zigbee Alliance directly at certification@zigbee.org


Certification: Getting Started

Steps to Certification

The first step of the certification process is to submit your product to an authorized test service provider. A list of authorized providers can be found on the Zigbee Alliance website here.The provider will send a test report directly to us when testing is complete – no need to forward it yourself.
The second step in the process is to submit an application online via the Zigbee Alliance Certification Web Tool.
If you don’t already have a Zigbee Alliance user account (separate from your Workspace account), you can sign up as a new user by clicking the “Sign Up” link. When requesting a new account, be sure to sign up with a company e-mail address (not Gmail, Yahoo, 163.com, or other free e-mail domains).
For detailed instructions on creating and submitting an application in the Certification Tool, a user information guide is available here.

After you complete and submit your application, the Zigbee Alliance will review it and send you either an approval notice or feedback via e-mail.


Tips and Pointers


Have all documents ready:

  • To ensure prompt processing of your application, remember to upload all required documents before clicking the “Submit” button.
  • All applications should include completed Declaration of Conformity (DoC) and Protocol Implementation Conformance Statement (PICS) documents

Ensure consistency across all documents submitted:

  • A common mistake we see is inconsistent information across the web application, DoC, PICS, and test report – save on processing time by double-checking these entries!
  • Ensure that all hardware/software version fields match the versions declared in the test report.
  • Make sure that the compliant platform declared in the application is consistent with the DoC and test report (or the original certified application, for Certification by Similarity requests).

Tips for completing the DoC:

  • The latest DoC template can be found on Workspace here.
  • Remember to have both signature blocks (applicant and test house) signed and dated.

Tips for completing the PICS:

  • Each Zigbee standard has its own PICS document, available with its respective specification document package in the Zigbee Alliance Member’s Area (Workspace).
  • Instructions for completing PICS documents are found at the beginning of each document template.
  • For Zigbee (3.0) applications, multiple PICS documents are required (base device behavior + individual cluster PICS) – these may be uploaded to the Certification Tool in a single ZIP archive.
  • Make sure that all mandatory PICS items are supported!

Tips for the Zigbee Test Tool (in-house pre-testing):

  • Tips for PICS and ZTT (right panel: PICS):
    • Before starting, clear the previous loaded ZTT PICS (right panel: Clear).
    • In order to generate a PICS file, the ZTT Tool format uses the PICS GUI (right panel: PICS).
    • Do not forget to save from time to time (right panel: Save).
    • If you need to share the PICS with a third party (right panel: Export PICS).
    • If somebody made the test plan for you (right panel: load PICS).
    • Finally, a list of test cases is almost ready for your device, let’s build the test plan (right panel: Build Test List).
    • Tips for PIXIT: There are plenty of options in this panel (right panel: PIXIT).
  • Tips for if the unit is not joining the Network:
    • Under “Common” expander be sure that the “Channel” has the proper value (this is applicable when the ZTT is forming the NWK)
    • Under “Common” expander be sure that the NWK PANID has the correct value.
    • Under “Common” expander be sure that the DUT MAC has the correct value.
  • Tips if the DUT is not responding application unicast messages:
    • Under “Common” expander be sure that the “DUT End Point” has the correct value.
  • Tips for if you want to test a cluster or a custom test case:
    •  When the DUT is a ZC, start the DUT and run the test case “Test Cases: BDB->CS-NFS-TC-05B” (you can stop the ZTT just after the ZTT has joined the DUT NWK).
    • When the DUT is a ZR/ZED, start the DUT and run the test case “Test Cases: BDB->CS-NFS-TC-06”.
    • Now the ZTT is in the DUT NWK and you can run your custom test case.


Certification Reference Material from the Zigbee Alliance


  • ZigBee and Thread
  • Thread SDK
  • Knowledge Base Articles