<?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>Is this the correct process for registering a product with Bluetooth SIG using a module with nrf52832?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/97981/is-this-the-correct-process-for-registering-a-product-with-bluetooth-sig-using-a-module-with-nrf52832</link><description>Hi. We are looking to productize using a module without OS with nrf52832. The Product Type of this module is Component (Tested). 
 The ncs1.6.1 is installed in this module, but the QDID to be used when submitting an EPL application to the Bluetooth SIG</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 29 Mar 2023 04:51:45 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/97981/is-this-the-correct-process-for-registering-a-product-with-bluetooth-sig-using-a-module-with-nrf52832" /><item><title>RE: Is this the correct process for registering a product with Bluetooth SIG using a module with nrf52832?</title><link>https://devzone.nordicsemi.com/thread/417996?ContentTypeID=1</link><pubDate>Wed, 29 Mar 2023 04:51:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d1804fc2-c5d9-4b69-ae59-76837a5331be</guid><dc:creator>beginner-jp</dc:creator><description>&lt;p&gt;&lt;span&gt;Dear tesc,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Thank you for your response.&lt;br /&gt;I am relieved to hear that it is correct.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Is this the correct process for registering a product with Bluetooth SIG using a module with nrf52832?</title><link>https://devzone.nordicsemi.com/thread/417060?ContentTypeID=1</link><pubDate>Thu, 23 Mar 2023 12:45:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bc3d1b16-aa24-46de-9765-e26842789012</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;This sounds like the correct process, yes. Please see &lt;a href="https://www.bluetooth.com/develop-with-bluetooth/qualification-listing/qualification-process-with-no-required-testing/"&gt;Qualification Process with No Required Testing&lt;/a&gt;, from Bluetooth SIG, for more information about the qualification process when combining existing designs.&lt;/p&gt;
&lt;p&gt;Please also note that you may need other qualifications/certifications in addition to the Bluetooth qualification, such as FCC, CE, MIC, etc., depending on the jurisdictions where your product will be sold and/or used.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>