Developer Konsole
Vielen Dank für deinen Besuch. Diese Seite ist nur in Englisch verfügbar.

Provisionee Certification Guide

This guide explains the Frustration-Free Setup certification process, which requires you run test based on the test plan and submit certification request. Amazon will verify your certification test result to approve or reject your request. The certification process does not replace your feature, security, or performance testing.

Device Details

Compliance with the FFS specification and implementation helps ensure a consistent and secure experience for our customers. Amazon requires that FFS-compatible devices are validated and certified. Exceptions to specific requirements may be possible, so ask your PoC for potential options.

  • If your integration requires an SDK, Amazon ensures that you have correctly implemented the full TLS security flow within the SDK by testing it against our Device Setup Service (DSS) and looking at the resulting connection details. Security is paramount and this is non-negotiable.
  • Amazon ensures that your device only requests network credentials for SSIDs that it detects in the immediate vicinity. Requests for other SSIDs are not permitted.
  • Amazon ensures that your implementation successfully provisions your device in 95% of testing attempts.
  • Depending on your implementation, Amazon ensures that your mobile application supports Login with Amazon, including the FFS scope. Amazon ensures that all messaging to the customer for permission regarding FFS, and the explanation of why the customer needs to grant permission is clear. Amazon also ensures that your application does not obfuscate the Login with Amazon flow.
  • Amazon ensures that, in the event that the FFS set up flow fails, your device's existing non-FFS set up flow starts up and attempts to set up the device for the customer.

Packaging Details

Amazon verifies that the device's packaging includes the required outer barcode mentioned in the manufacturing document with proper contrast. This verification ensures accurate barcode scanning during the order fulfillment process, which is necessary to properly pre-associate your device with the Amazon customer.

Timeline

Amazon reviews your certification test result after you have completed it and submitted certification request through the developer portal no later than 7 days following your test. Please allow one week to verify the test result and approve or reject your certification request accordingly.

Certification Steps

  1. Download the appropriate protocol and version specific of test plan from the tables below
  2. Prepare and test your device based on the test plan. Please use the latest test plan and include the information below in your test report
    1. Test device barcodes' images and dimensions
    2. Amazon customer ID (from link)
    3. Number of tests executed
    4. Test start time and end time (in UTC time zone)
  3. Log into the developer portal and request certification with detailed test report no later than 7 days following your test

Amazon notifies your company's primary contact when your device passes certification. You can follow the guide to configure the device's ASIN(s) for FFS. Your device remains certified as long as your device remains in compliance with the certification standards set at the time of testing. If your device falls out of compliance, per program requirements, Amazon may disable your device from communicating with our FFS backend service. If Amazon rejects your certification request after review, Amazon provides a list of failures. You can resubmit your certification request after you have addressed the failures and rerun the test.

Derivative Certification

After a device passes certification, you can certify it in other marketplaces, or you can certify a similar device in the same marketplace. This is referred to as Derivative Certification and requires less effort than a first-time certification. Derivative Certification also applies to those products based on certified reference designs provided by solution providers.

Not all devices qualify for a derivative certification. If your new device has a different model from a certified one considering hardware/chipset, major FW/SW version, and/or FFS protocol, it will NOT be treated as derivative; please use standard or simplified test plan and test your device with all required test cases.

  • Definition
    • Marketplace Derivative: Amazon Device Setup Service (DSS) operates in three stack regions: North America (NA), Europe (EU), and Far East (FE). If a product passes certification in one marketplace within a region, it is automatically certified in all other marketplaces in that same region. Marketplace derivative certifications are required for products to be sold in non-certified regions. For example: You executed the certification test for your smart plug using your Amazon UK account, requested certification in the EU region and received approval. However, if you want to launch this smart plug in Japan, you will need to conduct a derivative certification test with your Amazon Japan account and submit a certification request in the FE region. Marketplace list in each region:
      • NA: US, CA, MX, BR, PL, SA, SE
      • EU: UK, DE, FR, IT, ES, NL, IN
      • FE: JP, AU
    • Product Derivative: If your device has the same chipset, firmware, and protocol as a certified one and the main difference is either the form factor or added functionalities which are not related to networking like extended color, temperature, sensors, etc.
  • Derivative process
    • Please use derivative test plan for both type of derivatives.
    • For Product Derivative, please onboard a new Product and use the APID of the originally certified product as "Reference APID".

Test Plans

The tables below list different versions of certification test plans for each FFS protocol. Please download the appropriate test plan for the protocol your device implements. While performing test, please run each test case and enter the actual test result as instructed.

Standard Test Plans

Applied to those standard products and IoT Solution provider's base devices. Each test plan includes all required test scenarios and 50 iterations provisioning test.

Test Plan Name Version Protocol Link
WSS over Wi-Fi Provisionee (standard) 1.2 Wi-Fi Download
WSS over BLE Provisionee (standard) 1.1 Wi-Fi + BLE Download
MSS for Wi-Fi Provisionee (standard) 1.1 Wi-Fi + BLE Download
MSS for Thread Provisionee (standard) 1.1 Thread + BLE Download

Simplified Test Plans

Applied to those BSS/ZSS standard products, WSSoWiFi and Matter products based on some certified reference design (like ACK products), and IoT Solution provider's sample devices. Each test plan includes simplified test scenarios and 20 iterations provisioning test.

Test Plan Name Version Protocol Link
WSS over Wi-Fi Provisionee (Simplified) 1.2 Wi-Fi Download
WSS over BLE Provisionee (ACK and ACK SDK) 1.2 Wi-Fi + BLE Download
ZSS Provisionee 1.2 Zigbee Download
BSS Provisionee 1.2 Bluetooth Mesh Download
MSS for Wi-Fi Provisionee (Simplified) 1.1 Wi-Fi + BLE Download
MSS for Thread Provisionee (Simplified) 1.1 Thread + BLE Download

Derivative Test Plans

Applied to those derivative including OEM's products based on IoT SP's certified samples. Each test plan includes barcodes test and just 1 iteration of provisioning test.

Test Plan Name Version Protocol Link
WSS over Wi-Fi Provisionee (derivatives) 1.0 Wi-Fi Download
WSS over BLE Provisionee (derivatives) 1.0 Wi-Fi + BLE Download
ZSS Provisionee (derivatives) 1.0 Zigbee Download
BSS Provisionee (derivatives) 1.0 Bluetooth Mesh Download
MSS for Wi-Fi Provisionee (derivatives) 1.0 Wi-Fi + BLE Download
MSS for Thread Provisionee (derivatives) 1.0 Thread + BLE Download

Certification Tool

For partners implementing the BSS, ZSS or MSS protocols, Amazon has open sourced a set of Python based automation scripts to control the Alexa App and help facilitate automated performance testing. These scripts help execute the certification tests and shorten the product certification time. Support for other protocols will be made available in future updates.

Please view GitHub for the details.


Last updated: Oct 18, 2024