Bluetooth SIG Fees

Hi,

We've been working on an IoT device that uses an nRF52840 in a pre-approved module from Moko. We are getting ready for a commercial launch in 2026, but I am very confused about the Bluetooth SIG fees we need to pay.

I am currently attending CES in Las Vegas and stopped by your booth. The very helpful person I talked to suggested I post here and ask for specific step by step guidance and links to make sure I was following the right path.

Background Information:

  1. We are a startup with revenue below $1M USD/yr.
  2. We are using a pre-approved module with a Nordic nRF52840.
  3. We have not modified the module hardware.
  4. We are using the standard Nordic softdevice.
  5. We joined Bluetooth SIG as an Adopter (the free membership tier).

My understanding is that we do not need to pay the full "Product qualification fee", which is currently $11,040/yr. What we do need to pay is a "Product Listing Fee". However, I can find no reference to this fee anywhere on the Bluetooth SIG site. 

I've searched here and elsewhere and found very conflicting opinions. There is mention of an innovators program that reduces the listing fee to $2500 if your company qualifies (ours would appear to) but the links to the Bluetooth SIG site for that program all show "not found".

I know this has been asked here in the past, but the links in the previous answers are all dead and I could not find any recent answers.

What I need:

  1. Confirmation of what process I should follow with Bluetooth SIG.
  2. Current cost of that process.
  3. Valid links to make sure I am following the correct path.
  4. Clarification for multiple products. Can we submit multiple products under a single application if they all use the exact same Bluetooth component?

Thank you for your help.

Parents
  • Hello Nicholas,

    https://www.bluetooth.com/fee-schedule/

    https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/bt/bt_qualification/index.html

    You would be an adopter and to qualify a new product the fee for adopters is 11040USD (to be updated 1st of March 2026. That is normally the case.

    If you have a module with certificated QDID and not change any of the stack, implementation or SW and HW you could in theory reuse the module manufacturer QDID if they allow it. Although, this is not common as normally there will be a change done to some aspect. So the product qualification fee is the normal route for the case such as yours. 

    Best regards

    Asbjørn

  • Respectfully, this is the exact opposite of what I was told by the staff member at your booth.

    I reviewed the Nordic link you posted, and it says:

    "The nRF Connect SDK contains qualified portions of various Bluetooth features (for example, SoftDevice Controller versions). If your product uses a qualified Bluetooth stack provided as part of the nRF Connect SDK, you can inherit this qualification from Nordic Semiconductor, provided that you do not introduce any changes to the stack." 

    This is precisely our use case. We are using the nRF Connect SDK and the Nordic soft controller. We have not introduced any changes to that stack.

    Does this not mean that we can "inherit this qualification from Nordic Semiconductor"?

    Also, we are using a pre-approved module that we do not physically alter in any way. We simply attach the complete module to our PCB as is.

    I cannot emphasize enough how important this issue is to us. The full qualification fee is a significant investment for a company our size and the Bluetooth SIG has been unhelpful in clarifying the nuances of their position.

  • Hello Nicholas,
    I can understand your frustrations as we would like this to be clear as well and for some of our customers this is an issue and concern just as it is for you right now. 
    Changes in this conext does also involve implementation of FW running on the device. So you can have qualified HW, qualified stack and using nRF Connect SDK, but unless the module manufacturer has qualified with the profile you are using and you have no access to changing the FW on it, it will come down to you have done a change to the design and most likely the fee will still apply. It's the business model of Bluetooth SIG and their members. It's ok for most, it's frustrating for a few such as yourself.
    We can change this from our point of view. What information have you gotten from Bluetooth SIG on this matter? 
    Best regards
    Asbjørn
Reply
  • Hello Nicholas,
    I can understand your frustrations as we would like this to be clear as well and for some of our customers this is an issue and concern just as it is for you right now. 
    Changes in this conext does also involve implementation of FW running on the device. So you can have qualified HW, qualified stack and using nRF Connect SDK, but unless the module manufacturer has qualified with the profile you are using and you have no access to changing the FW on it, it will come down to you have done a change to the design and most likely the fee will still apply. It's the business model of Bluetooth SIG and their members. It's ok for most, it's frustrating for a few such as yourself.
    We can change this from our point of view. What information have you gotten from Bluetooth SIG on this matter? 
    Best regards
    Asbjørn
Children
No Data
Related