<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bluetooth SIG Fees</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/126424/bluetooth-sig-fees</link><description>Hi, 
 We&amp;#39;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</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 16 Jan 2026 06:31:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/126424/bluetooth-sig-fees" /><item><title>RE: Bluetooth SIG Fees</title><link>https://devzone.nordicsemi.com/thread/558850?ContentTypeID=1</link><pubDate>Fri, 16 Jan 2026 06:31:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6248a999-46bb-4fe2-b876-5a6b18b2c591</guid><dc:creator>NickN</dc:creator><description>&lt;p&gt;Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth SIG Fees</title><link>https://devzone.nordicsemi.com/thread/558662?ContentTypeID=1</link><pubDate>Wed, 14 Jan 2026 06:52:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d814dd89-bffe-4dc9-87ae-15dfa98e4519</guid><dc:creator>Asbj&amp;#248;rn</dc:creator><description>[quote user="NickN"]The fee being a one-time payment and not annual is particularly helpful for us. A SIG rep once claimed otherwise. An annual $11k fee for a pre-revenue small company is tough to swallow.[/quote]
&lt;p&gt;This is a good clarification by &lt;a href="https://devzone.nordicsemi.com/members/emil-lenngren"&gt;Emil Lenngren&lt;/a&gt;&amp;nbsp;. Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth SIG Fees</title><link>https://devzone.nordicsemi.com/thread/558639?ContentTypeID=1</link><pubDate>Tue, 13 Jan 2026 20:00:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:123b433d-af47-4d13-aeba-abb9de0e7926</guid><dc:creator>Emil Lenngren</dc:creator><description>&lt;p&gt;At&amp;nbsp;&lt;a id="" href="https://www.bluetooth.com/fee-schedule/"&gt;https://www.bluetooth.com/fee-schedule/&lt;/a&gt;&amp;nbsp;it is clearly marked which fees are paid annually. The qualification fee is not one of them.&lt;/p&gt;
&lt;p&gt;It also says &amp;quot;&lt;em&gt;A Product Qualification Fee is charged for the first Product submission from a Member Company that includes a specific Design whether that Design is an existing Design (identified by a Design Number) or a new Design (that will be issued a Design Number upon completion of the Qualification process). Subsequent Product submissions from the same Member Company that include the same Design will not be charged a Product Qualification Fee. In addition, any Product submission from a Member Company that includes a subset Design (QPRD, Section 3.2.2.2.1) or a reassessed Design (QPRD, Section 3.2.2.2.2) will not be charged a Product Qualification Fee&lt;/em&gt;&lt;span&gt;.&amp;quot;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;If you are doing multiple products having the same bluetooth module and same bluetooth stack, you should simply reference the manufacturer&amp;#39;s design when you make the declaration. Then add as many products as you like using the same design. See&amp;nbsp;&lt;a id="" href="https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/QPRD/out/en/index-en.html"&gt;https://www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/QPRD/out/en/index-en.html&lt;/a&gt;&amp;nbsp;and table 3.2&amp;#39;s column &amp;quot;Use a single existing design&amp;quot;.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth SIG Fees</title><link>https://devzone.nordicsemi.com/thread/558637?ContentTypeID=1</link><pubDate>Tue, 13 Jan 2026 19:32:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ac992c9-bbfe-4687-abd3-4865d23265b0</guid><dc:creator>NickN</dc:creator><description>&lt;p&gt;Thanks Emil. That&amp;#39;s helpful. It doesn&amp;#39;t completely square with what I&amp;#39;ve been told by either the Bluetooth SIG or Nordic, but at least it makes sense.&lt;/p&gt;
&lt;p&gt;The fee being a one-time payment and not annual is particularly helpful for us. A SIG rep once claimed otherwise. An annual $11k fee for a pre-revenue small company is tough to swallow.&lt;/p&gt;
&lt;p&gt;Similarly, it&amp;#39;s very unclear to me what is considered a different device. We are developing IoT sensors and related products, so the Bluetooth functionality is just one small part of the device. We will be using the exact same Bluetooth module and antenna in multiple products. The Bluetooth stack will be identical, but the rest of the firmware and PCB will be different because the devices have different functionality (Bluetooth functionality is the same, the rest of the device features are different). I&amp;#39;ve heard &amp;quot;this would be considered the same device&amp;quot; and &amp;quot;this would be considered a new device&amp;quot; with no obvious right or wrong answer.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;And it does seem that the SIG will aggressively protect their IP if you try to launch without paying them. That part I can understand and respect, but the lack of clarity and the lack of flexibility for small companies is frustrating.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth SIG Fees</title><link>https://devzone.nordicsemi.com/thread/558576?ContentTypeID=1</link><pubDate>Tue, 13 Jan 2026 11:22:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d73c94b0-be5f-4ae7-bc65-10ba9d33ffe5</guid><dc:creator>Emil Lenngren</dc:creator><description>&lt;p&gt;I agreee that Bluetooth SIG is definitely not friendly to startups, due to the high costs related to the Bluetooth product listing fees, compared to large corporates that sell millions of units, paying the exact same (static) fee.&lt;/p&gt;
&lt;p&gt;According to &lt;a href="https://www.eevblog.com/forum/chat/bluetooth-device-registration-is-$8000/"&gt;this link&lt;/a&gt;, the Innovation Incentive Program was quietly stopped in February 2020.&lt;/p&gt;
&lt;p&gt;For your first product using a particular design, you&amp;nbsp;pay the product listing fee, currently $11,040, which is a fixed fee and not a fee that must be paid every year. If you use the same design in multiple products, you can add those additional products to your listing without paying anything extra. Typically, if you use the same Bluetooth stack (hardware and software), it counts as the same design.&lt;/p&gt;
&lt;p&gt;Whether you use a pre-approved module or software is irrelevant regarding the listings fee of your first product submission. Using such a pre-approved design only helps you in the way that you don&amp;#39;t have to perform any testing (which might otherwise incur further costs, in addition to the product listing fee). Even if you take an off-the-shelf white label product and you sell it as your own under your own name, you need to pay the fee.&lt;/p&gt;
&lt;p&gt;Note that paying the fee to Bluetooth gives you two things:&lt;/p&gt;
&lt;p&gt;1. The right to use the Bluetooth brand/trademark, including the name and logotype, for example in your marketing or on the product packaging. Bluetooth SIG claims that customs&amp;#39; authorities sometimes look in the Bluetooth SIG product database to see if such products are listed correctly.&lt;/p&gt;
&lt;p&gt;2. A license to use necessary patents for the applicable Bluetooth technology. A member company that owns a patent necessary to implement BLE might sue you in court if you have not paid the fee, if your product makes use of the technology in that patent. Since BLE is pretty old now, the patents should expire pretty soon, in the near upcoming years, at least those covering those features included in the original Bluetooth 4.0 specification.&lt;/p&gt;
&lt;p&gt;Thus, only if you don&amp;#39;t use the Bluetooth brand, and are 100% sure you are not using any technology covered by any patent, then you do not have to perform the qualification process.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth SIG Fees</title><link>https://devzone.nordicsemi.com/thread/558492?ContentTypeID=1</link><pubDate>Mon, 12 Jan 2026 11:11:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5391c0e7-86cf-4142-9d6f-7bebbd39696a</guid><dc:creator>Asbj&amp;#248;rn</dc:creator><description>&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;Hello Nicholas,&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;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.&amp;nbsp;&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;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&amp;#39;s the business model of Bluetooth SIG and their members. It&amp;#39;s ok for most, it&amp;#39;s frustrating for a few such as yourself.&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;We can change this from our point of view. What information have you gotten from Bluetooth SIG on this matter?&amp;nbsp;&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;Best regards&lt;/div&gt;
&lt;div style="color:rgba(0, 0, 0, 1);direction:ltr;font-family:Calibri, Helvetica, sans-serif;font-size:11pt;"&gt;Asbjørn&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth SIG Fees</title><link>https://devzone.nordicsemi.com/thread/558446?ContentTypeID=1</link><pubDate>Sat, 10 Jan 2026 21:53:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:efaacf4b-413d-4289-a72b-ac4cd7eb8836</guid><dc:creator>NickN</dc:creator><description>&lt;p&gt;Respectfully, this is the exact opposite of what I was told by the staff member at your booth.&lt;/p&gt;
&lt;p&gt;I reviewed the Nordic link you posted, and it says:&lt;/p&gt;
&lt;p&gt;&amp;quot;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.&amp;quot;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Does this not mean that we can &amp;quot;inherit this qualification from Nordic Semiconductor&amp;quot;?&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth SIG Fees</title><link>https://devzone.nordicsemi.com/thread/558440?ContentTypeID=1</link><pubDate>Sat, 10 Jan 2026 19:43:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ca16010e-d688-444a-b02b-93d364c65776</guid><dc:creator>Asbj&amp;#248;rn</dc:creator><description>&lt;p&gt;Hello Nicholas,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.bluetooth.com/fee-schedule/"&gt;https://www.bluetooth.com/fee-schedule/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/bt/bt_qualification/index.html"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/protocols/bt/bt_qualification/index.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;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.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;
&lt;p&gt;Asbjørn&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>