[Home](/)/[Resources](/resources)/Bluetooth SIG Qualification United StatesBluetoothCertificationFCC # Bluetooth SIG Qualification: QDID, Declarations, and the Listing Process Explained Bluetooth qualification is misunderstood by most hardware teams — it is not an FCC requirement, but it is an IP licensing obligation, a trademark prerequisite, and a commercial necessity for any product carrying the Bluetooth brand. Understanding QDIDs, declaration types, BQTF requirements, and module inheritance paths determines whether your Bluetooth product launches on time or stalls in qualification. Copy Link[Share on WhatsApp](https://wa.me/?text=https%3A%2F%2Fkrono-labs.com%2Fguides%2Fus-bluetooth-qualification) At a glance SIG membership cost ~$8,000/year (Adopter tier) Declaration types End Product, Component, Design QDID inheritance From chip/module vendor's qualification Trademark requirement Membership + qualified product listing ## Core Bluetooth SIG qualification concepts ### Bluetooth SIG Membership Tiers and What They Permit Bluetooth SIG has two main commercial tiers. Associate members pay higher fees and participate in specification development. Adopter members (approximately $8,000/year as of 2024 — verify current rates with Bluetooth SIG) can use the Bluetooth specifications royalty-free, submit qualification declarations, and license Bluetooth trademarks. Non-members have no right to implement Bluetooth specifications, qualify products, or use Bluetooth trademarks — selling a Bluetooth product without SIG membership exposes the company to IP infringement claims and trademark disputes. There is no compliant path to selling a branded Bluetooth product without becoming at least an Adopter member or using a fully qualified module whose supplier's membership covers downstream use (it does not — each company must be a member). ### The Bluetooth Qualification Program (BQP): What 'Qualified' Means Bluetooth qualification under the BQP means that a product has demonstrated conformance to Bluetooth specifications through testing against the TCRL (Test Case Reference List) and that the implementing company has submitted a Declaration through Bluetooth SIG's Launch Studio portal. Qualification is not the same as FCC authorization — it is an industry IP and conformance program, not a regulatory program. The TCRL defines mandatory and conditional test cases per specification version (currently 5.3 and 5.4 for core) and per profile (A2DP, HFP, GATT, etc.). The applicable TCRL version at the time of Declaration submission determines which test cases must be passed. ### Declaration Types: End Product, Component, and Design There are three Declaration types in Launch Studio. An End Product Declaration covers a finished product that will carry the Bluetooth brand and be listed in the Bluetooth SIG product database. A Component Declaration covers a subsystem (e.g., a Bluetooth chip or module) that will be integrated into other products — this creates a QDID that downstream manufacturers can reference. A Design Declaration covers an implementation (e.g., a Bluetooth stack) intended for integration. Most hardware manufacturers shipping finished goods will submit End Product Declarations, often inheriting from a Component QDID provided by their Bluetooth chip or module vendor. ### QDID: Qualified Design ID and Inheritance A QDID (Qualified Design ID) is the identifier assigned to a successful qualification submission. When a chip or module vendor qualifies their Bluetooth implementation and receives a QDID, downstream product manufacturers can inherit that QDID in their own End Product Declaration — provided the product uses the qualified design without changes to the layers covered by the QDID. Inheritance does not eliminate the need for an End Product Declaration; it means you reference the existing QDID rather than conducting new BQTF testing for the covered layers. If your product adds Bluetooth profiles not covered by the inherited QDID, those additional profiles require either new testing or a separate Component Declaration. ### BQTF Testing: When It Is Required vs. Self-Testing A BQTF (Bluetooth Qualified Test Facility) is a test lab authorized by Bluetooth SIG to conduct qualification testing. Not all test cases require BQTF involvement — the TCRL distinguishes between test cases that can be self-tested (using the PTS — Profile Tuning Suite — software provided by Bluetooth SIG) and those that require a BQTF. RF-level physical layer tests and certain protocol conformance tests require BQTF. Profile-level and application-level tests are often self-testable via PTS. The split is specified per test case in the TCRL — review it before assuming you can self-test, as incorrect self-testing claims are a qualification audit risk. ### Bluetooth Trademark License and Product Database Listing The Bluetooth word mark and Bluetooth logo are registered trademarks of Bluetooth SIG. Using either on product packaging, in product names, or in marketing materials requires executing Bluetooth SIG's trademark license — which is available to Adopter and Associate members as part of membership. The trademark license governs logo size, placement, color, and context. Beyond trademark licensing, Bluetooth SIG requires that qualified products be listed in the publicly searchable Bluetooth product database at bluetooth.com. The listing is a qualification program condition — an unregistered product that uses Bluetooth trademarks violates both the trademark license and program rules. ## Bluetooth qualification process step by step 01 Join Bluetooth SIG as an Adopter member. Membership requires agreeing to the Bluetooth SIG Membership Agreement, which includes the IP license (royalty-free right to implement Bluetooth specifications) and the trademark license. Current Adopter membership is approximately $8,000/year — confirm current fees at bluetooth.com/develop/join/. 02 Identify which Bluetooth core specification version (5.3, 5.4) and which profiles/services your product implements (e.g., A2DP for audio streaming, HFP for hands-free, GATT for BLE data). Each profile has its own TCRL defining mandatory test cases. Pull the current TCRL from bluetooth.com/specifications/assigned-numbers/ and map it against your implementation. 03 Obtain an ICS (Implementation Conformance Statement) for each profile. The ICS is a checklist of which profile features your implementation supports, which are mandatory, and which are optional. The ICS drives which test cases apply. Complete the ICS before engaging a BQTF — incomplete or inaccurate ICS submissions are the most common cause of qualification delays. 04 Determine whether your product can inherit an existing QDID from your Bluetooth chip or module vendor. Contact the vendor for their QDID and confirm the scope of layers covered. If inheritance covers your use case, you will reference the vendor's QDID in your End Product Declaration and only need to self-test or BQTF-test any additional profiles not covered by the inherited QDID. 05 Engage a BQTF for any test cases that require it under the applicable TCRL. Download Bluetooth SIG's PTS (Profile Tuning Suite) for self-testable cases and run all applicable test cases against your implementation. Document pass/fail results — you will attest to test completion in Launch Studio when submitting your Declaration. 06 Submit your Declaration in Bluetooth SIG's Launch Studio portal. Select the appropriate declaration type (End Product, Component, or Design), attach or reference your ICS, reference inherited QDIDs if applicable, enter BQTF test results if required, and pay the declaration fee. Upon approval, your QDID is issued and your product appears in the Bluetooth product database. 07 License and apply Bluetooth trademarks per the trademark usage guidelines. Bluetooth word mark and logo usage must comply with the Bluetooth Brand Guidelines — download the current version from bluetooth.com. Incorrect logo usage (wrong color, insufficient clear space, unapproved context) can trigger trademark notices from Bluetooth SIG. ## Frequently asked questions ### Is Bluetooth SIG qualification legally required to sell a Bluetooth product? Bluetooth SIG qualification is not legally mandated by US federal law — the FCC requirement for Bluetooth devices is equipment authorization under 47 CFR Part 15 (intentional radiator rules), which is entirely separate. However, Bluetooth SIG qualification is contractually required by the Bluetooth SIG Membership Agreement for any company that implements Bluetooth specifications. Since implementing Bluetooth without an IP license from Bluetooth SIG exposes the company to patent infringement claims from the members who contributed to the specification, qualification is effectively mandatory for any company that wants to sell Bluetooth products without IP liability exposure. Additionally, the right to use the Bluetooth word mark and logo — without which consumer marketing is severely constrained — requires an active membership and a qualified product. ### What's a QDID and how do I get one without doing all the testing myself? A QDID (Qualified Design ID) is the identifier assigned when a Bluetooth implementation is successfully qualified through a Declaration submission in Launch Studio. You get a QDID by submitting a Declaration (End Product, Component, or Design) and completing the required testing. The path to minimizing your testing burden is inheriting from your chip or module vendor's existing QDID. If your Bluetooth chip vendor (e.g., Nordic, Silicon Labs, Qualcomm, Mediatek) has already qualified their implementation and obtained a QDID, you can reference their QDID in your End Product Declaration for the layers they have covered. You still need to submit your own End Product Declaration and test any additional profiles your product implements that are not covered by the inherited QDID — but the core physical layer and controller tests that require BQTF are typically already covered. ### What's the difference between a Component Declaration and an End Product Declaration? A Component Declaration is submitted by a manufacturer of a Bluetooth subsystem — a chip, module, or stack — that will be integrated into other products. The resulting QDID can be inherited by downstream product manufacturers in their own End Product Declarations, covering the layers implemented by the component. An End Product Declaration is submitted for a finished product that will be sold to end users and listed in the Bluetooth product database. An End Product Declaration may inherit from one or more Component QDIDs for layers covered by those components, and self-tests or BQTF-tests any additional layers or profiles not covered. A Design Declaration covers a Bluetooth implementation (typically a software stack) intended for integration — similar to Component but for software-only implementations. Most hardware companies shipping finished goods need an End Product Declaration; they may also need a Component Declaration if they build a module that other companies will integrate. ### Can I use a pre-qualified Bluetooth module and skip SIG membership? No. Using a pre-qualified Bluetooth module does not eliminate the need for Bluetooth SIG membership. The module vendor's QDID covers the module's implementation — it does not transfer IP license rights or trademark rights to you as the end product manufacturer. You must be an Adopter or Associate member of Bluetooth SIG to: (1) implement Bluetooth specifications under the royalty-free IP license, (2) submit an End Product Declaration referencing the module's QDID, and (3) use Bluetooth trademarks on your product. The module vendor's qualification reduces your testing burden by providing a QDID you can inherit, but it does not substitute for your own membership and Declaration submission. There is no compliant shortcut around membership for a company selling a branded Bluetooth product. **Disclaimer:** Educational resource only. Regulatory requirements change frequently. Consult a licensed US customs broker, trade attorney, or compliance specialist before making decisions. 🇺🇸 US roadmap for radio equipment Every standard, document, and test that applies — free, no account required. See your free roadmap Learn this properly In-depth course that teaches the full process, not just this one answer. [Start the course — $149](/courses/02-fcc-authorization-for-hardware-startups)[Prefer to read? Get the book — $24.99](/books/02-fcc-authorization-for-hardware-startups) Related guides * [Wi-Fi Alliance CertificationWi-Fi Alliance certification programmes explained: WPA3, Wi-Fi 6E and Wi-Fi 7, the Authorized Test Laboratory system, how 6 GHz certification interacts with FCC Part 15, member vs non-member paths, and recertification triggers.](/guides/us-wi-fi-certification) * [FCC Equipment AuthorizationComplete guide to FCC equipment authorization for electronic devices.](/guides/fcc-equipment-authorization) * [EN 300 328: WiFi and BluetoothEN 300 328 is the primary harmonised standard for 2.4 GHz wideband radio equipment.](/guides/en-300-328-wifi-bluetooth) * [OTA Testing for Wireless DevicesOver-the-air (OTA) testing measures the actual radiated performance of a wireless product in a controlled environment, accounti…](/guides/ota-testing-wireless) * [FCC Part 15 Class A vs Class BFCC Part 15 Class A vs Class B explained: how to classify your digital device, emission limits, residential vs commercial use, …](/guides/fcc-part-15-class-a-vs-b)