Bluetooth SIG qualification: process, fees and DN
Bluetooth SIG qualification is not a law. It is the Bluetooth Qualification Process defined by the Bluetooth SIG in its Qualification Program Reference Document (QPRD), now at version 5 of 21 April 2026, and it is what lets a member ship a product under the Bluetooth patent/copyright licence and trademark licence. It sits beside radio law, never in place of it: RED in the European Union, FCC Part 15 in the United States. The process changed in July 2024 (Design Numbers, Qualification Workspace) and the fees changed in March 2026, so most guides still describe a programme that no longer exists. This page follows the current texts.
What qualification is, and what it is not
Section titled “What qualification is, and what it is not”The SIG overview page states it plainly: all Bluetooth products must be qualified, and the process helps members comply with the Bluetooth Patent & Copyright License Agreement and the Bluetooth Trademark License Agreement. The QPRD itself is the document those agreements point to: it holds the "Compliance Requirements" referred to in section 1(i) of the patent/copyright licence.
Four rules from the QPRD and the SIG overview page shape everything else:
- Your own account. The member must submit under a user account belonging to that member. "A supplier or other Member cannot complete the Bluetooth Qualification Process for any other company's Product" (QPRD section 2).
- Before sale. Qualification must be complete on or before the date the product is first sold or distributed.
- Names must match. The product name and model number entered must match those used to market, distribute and sell the product (QPRD 3.1).
- One Design per Product. A "Product" in QPRD terms includes only one Design, is sold as a single item, and is marketed under a name or trademark identifying the member.
The SIG is not a public authority and qualification grants no right to place a radio on a market. Equally, a RED or FCC file grants no right to use the Bluetooth licences.
| Aspect | Bluetooth Qualification Process | Radio certification (RED / FCC) |
|---|---|---|
| Nature | Contract with a private standards body | Public law |
| Rulebook | QPRD v5 + Bluetooth Specifications | Directive 2014/53/EU, 47 CFR Part 15 |
| Who decides | Bluetooth SIG (submission review) | Manufacturer declaration or notified body (EU), TCB or FCC (US) |
| Subject matter | Conformance to the Bluetooth Specifications, interoperability | Spectrum use, EMC, safety, health, cybersecurity |
| Sanction | Enforcement fees, membership suspension, border seizure reported by the SIG | Market surveillance measures, fines |
| Identifiers | Design Number (DN), legacy QDID and DID | RED declaration of conformity, FCC ID |
See the RED pillar and the FCC pillar for the radio regimes themselves.
What changed on 1 July 2024
Section titled “What changed on 1 July 2024”The SIG quick start guide defines the QDID as "this legacy term is a unique identifier referencing a qualified design prior to 1 July 2024". From that date the process runs in a tool called Qualification Workspace and new Designs receive a Design Number (DN). QPRD v3 was approved on 11 June 2024, three weeks before the switch; v4 followed on 21 July 2025 and v5 on 21 April 2026. The QPRD abstract states that it supersedes the compliance requirements in Volume 0, Part B, section 3 of Core 5.4 and earlier, QPRD 2.3 and the Declaration Process Document 1.0.
| Old term (before July 2024) | Current term (QPRD v3 to v5) | What the text says |
|---|---|---|
| QDID (Qualified Design ID) | Design Number (DN) | A DN is issued for each unique Design the first time a Product using it completes the process. Old QDIDs can still be referenced. |
| Declaration ID (DID) | Qualified Product in the Qualified Product database | A DID can still be referenced under option 1 (single existing Design). |
| End Product Listing (EPL) | Option 1: use a single existing Design | No ICS change, no test plan. |
| Launch Studio | Qualification Workspace | The tool picks the option from the design details entered. |
| Listing fee / declaration fee | Product Qualification Fee (administrative fee, Receipt Number) | Charged for the first product submission that includes a specific Design. |
The three ways to specify the Design
Section titled “The three ways to specify the Design”The QPRD (section 3.2) gives three options. The quick start guide notes that members do not choose: Qualification Workspace selects the option from the design details entered.
| QPRD option | When it applies | ICS Form | Testing | New DN? |
|---|---|---|---|---|
| 1. Single existing Design (3.2.1) | Product includes one existing Design with a DN, QDID or DID, unmodified (for example rebranding another member's qualified product) | Not allowed to change | None | No |
| 2a. Combine existing Designs (3.2.2.1) | Two or more unmodified Designs combined into a permitted combination (for example a Core-Controller Design plus a Core-Host Design giving a Core-Complete Configuration) | Inconsistencies may only be fixed by removing selections | Interoperability tests (IOPT) for some combinations | Yes |
| 2b. Any other new Design (3.2.2.2) | New layers, modified layers, subset of your own Design, or reassessment against a newer test package | Required for each new or modified layer, against the active TCRL Package | Test plan generated from the ICS Form | Yes |
Details that the older "EPL versus Full" picture misses:
- Option 1 allows changes outside the Design: industrial design, branding, packaging, colour, shape, product name, non-Bluetooth radios and features. The member remains responsible for assessing that these do not affect compliance or change the ICS Form.
- Specifications must be active or deprecated at submission time for option 1. For option 2, any layer using a withdrawn specification must be removed or moved to an active one.
- Modification without an ICS change (option 2b): the member uses good engineering practice to decide which mandatory test cases are affected, and may reuse earlier evidence for the others (QPRD 3.2.2.5).
- Development tools, test equipment and "Component (non-tested)" QDIDs, product types defined in Core 5.4 and earlier, cannot be used as an existing Design.
Who may run which tests
Section titled “Who may run which tests”QPRD Appendix A sets a test case category for every test case. The SIG test facilities page adds that results for Category A test cases "at or below the HCI layer" must come from a Bluetooth Qualification Test Facility (BQTF), unless the member is itself a Bluetooth Recognized Test Facility (BRTF) testing its own products.
| Category | Test cases | Test system | Who may perform | Test declaration | Test report |
|---|---|---|---|---|---|
| A, mandatory | RF, RFPHY, BB, LL, ISOAL, LMP and lower HCI layers | Validated only | BQTF or BRTF | Required | Required |
| A, mandatory | Other layers | Validated only | Member, BQTF/BRTF or third party | Required | Required |
| B, mandatory | All | Validated, non-validated or member-defined | Member, BQTF/BRTF or third party | Required | Required |
| C, optional (recommended) | All | Any | Member, BQTF/BRTF or third party | Required | Not required |
| D, optional (informational) | All | Any | Member, BQTF/BRTF or third party | If performed | Not required |
| X, optional (recommended) | Supplementary interoperability tests | Any | Member, BQTF/BRTF or third party | If performed | Not required |
A test report must identify the test facility, the member, the product with hardware and software versions, the Test Suite version, the test system and its version, the IXIT values used, and list each test case with its date and verdict (QPRD A.3). When a pass verdict cannot be obtained, the member either fixes the product and retests or obtains a Test Coverage Waiver (TCW). The SIG Profile Tuning Suite (PTS) and other validated test systems are listed on the SIG test tools pages.
The process step by step (QPRD section 3)
Section titled “The process step by step (QPRD section 3)”- Join the SIG at Adopter level at least, under the company that will market the product.
- Provide product details: name, description, model number, publication date, and whether other users in the same member can see the product before publication (3.1). The publication date may not be more than 180 days after submission.
- Specify the Design using option 1, 2a or 2b. Ask your module or chipset supplier for the DN or QDID; the quick start guide notes members can often get it there.
- Consistency check of the ICS Form by the SIG tool (option 2 only): complete layers, inter-layer dependencies, Core Configuration and transport compatibility.
- Test plan, testing, test declaration and reports if a test plan is generated.
- Pay the administrative fee and obtain a Receipt Number. Paying by invoice adds time; the quick start guide says invoices may take 1 to 2 weeks to process.
- Submit in Qualification Workspace and sign the declarations and attestations.
- Verification by the SIG. The QPRD states that most reviews are approved within one business day and that the SIG intends to complete more complex reviews within five business days. A rejected member may appeal in writing within 30 days.
- Keep the Compliance Folder: product and design details, test declaration, reports, logs and any TCW, retained for at least one year after the product stops being offered for sale, and shown to the SIG on request (3.4.1).
Errors in product name, model number or dates cannot simply be edited: the member qualifies a new product with corrected data, then may ask for the original to be withdrawn, and only if that product was never sold or distributed. No fee is refunded (QPRD section 4).
Membership and fees, 1 March 2026 schedule
Section titled “Membership and fees, 1 March 2026 schedule”The SIG schedule of dues and fees (effective 1 March 2026, amounts in USD) introduced a new Contributing Adopter level between Adopter and Associate.
| Item | Adopter | Contributing Adopter | Associate |
|---|---|---|---|
| Annual dues | USD 0 | USD 3,500 (small) or USD 16,500 (large) | USD 11,250 (small) or USD 52,500 (large) |
| Product qualification fee | USD 12,000 | USD 8,000 for the first qualification each membership year (33% off), then USD 12,000 | USD 6,000 for every qualification (50% off) |
| Working groups | No | Join | Join, vote, lead, chair |
| Committees | No | Not listed | Join, vote, lead, chair |
| Company Identifier | USD 1,250 | USD 1,250 | USD 0 |
| Validated Test System annual fee | USD 5,000 | USD 5,000 | USD 0 |
The SIG overview page adds the rule that matters for budgeting: the fee is charged for the first product submission that includes a specific Design, and subsequent products you submit with the same Design are not charged. Other listed fees: 16-bit UUID USD 3,750, BQTF annual recognition USD 12,000, BRTF annual recognition USD 3,000, Qualification Consultant annual exam USD 900.
Enforcement
Section titled “Enforcement”The SIG enforcement page describes audits of member websites, member reporting, a third-party service crawling online marketplaces, and customs officials who rely on the Qualified Product database: an unlisted product "may be seized at the border". An updated Enforcement Program Policy took effect on 5 August 2025. Cost recovery fees in the March 2026 schedule:
| Time to resolve | First audit failure | Each additional failure |
|---|---|---|
| Day 0 to 45 | USD 0 | USD 2,500 |
| Day 46 to suspension | USD 6,000 | USD 8,500 |
| After suspension | USD 12,000 | USD 14,500 |
The same page states that a retailer or distributor reselling a Bluetooth product without branding it or presenting it as its own does not need to qualify it.
Core Specification versions in 2026
Section titled “Core Specification versions in 2026”Since 2025 the Core Specification follows a twice-yearly release schedule, announced with Core 6.1. Version dates below are those printed in each specification; the "mandatory updates" are the Specification Updates the SIG says must be applied when claiming compliance.
| Version | Version date | Headline features (SIG overview) | Mandatory Specification Updates |
|---|---|---|---|
| 6.0 | 2024-08-27 | Channel Sounding, decision-based advertising filtering, monitoring advertisers, ISOAL enhancement, LL extended feature set, frame space update | 25800, 27096, 27195, 28108, 29015 |
| 6.1 | 2025-04-29 | Randomized RPA updates (address change timing randomised, handled by the Controller) | 27096, 27195, 28108, 29015 |
| 6.2 | 2025-11-03 | Shorter Connection Intervals (minimum 375 µs, 125 µs resolution), Channel Sounding amplitude-based attack resilience, HCI USB LE isochronous support, LE test mode enhancements | 28108, 29015 |
| 6.3 | 2026-05-05 | Channel Sounding inline PCT transfer, PHY-specific RTT accuracy, "Running Out of Bits" (larger HCI command and event masks), ACP and C/I limit relaxation for BR/EDR | 29015 |
Deprecation and withdrawal dates on the SIG specification list (dates for 5.2 and later are flagged with an asterisk there):
| Core version | Deprecation | Withdrawal |
|---|---|---|
| 5.0 (amended) | 1 Feb 2027 | 1 Feb 2032 |
| 5.1 (amended) | 1 Feb 2029 | 1 Feb 2034 |
| 5.2 (amended) | 1 Feb 2030 | 1 Feb 2035 |
| 5.3 (amended) | 1 Feb 2032 | 1 Feb 2037 |
| 5.4 (amended) | 1 Feb 2033 | 1 Feb 2038 |
| 6.0 | 1 Feb 2035 | 1 Feb 2040 |
Core 4.2 and earlier no longer appear on the list. Under QPRD option 1, an existing Design may only implement specifications that are active or deprecated at submission; a Design built on a withdrawn specification must be updated through option 2b.
How to describe Bluetooth on the product
Section titled “How to describe Bluetooth on the product”The SIG guidance "Communicating supported Bluetooth functionality" does not endorse writing the Core version as a feature claim ("Bluetooth 5.4"), because it leads to wrong assumptions about functionality. It recommends "Bluetooth®" alone, plus application names only when the matching layer is qualified:
| Communication element | Layer that must be in the qualified product |
|---|---|
| Auracast | PBP (plus the extra rules in the Brand Guide) |
| LE Audio | TMAP or HAP |
| Classic Audio | A2DP or HFP |
| ESL | ESLP |
| NLC | One of the NLC profiles (ALSNLCP, BLCNLCP, BSSNLCP, DICNLCP, ENMNLCP, HINLCP, OCSNLCP) |
If the Core version is shown, the SIG suggests the form "Qualified against Bluetooth® Core 5.4", and not in the product name. "Ready for" a future element is allowed only if the member intends to qualify it and update products already in the field.
Interaction with the RED
Section titled “Interaction with the RED”In the European Union a Bluetooth radio falls under Directive 2014/53/EU. For article 3.2 (efficient use of spectrum) the harmonised standard used for 2.4 GHz wideband transmitters, Bluetooth included, is EN 300 328. It covers RF output power, occupied channel bandwidth and the medium access rules (AFH and other adaptive mechanisms). None of this is part of SIG qualification, and SIG test reports do not substitute for it.
The other RED essential requirements also apply: article 3.1(a) health (often EN 62479 or EN 62311 for low-power devices), article 3.1(b) EMC with EN 301 489-17, and, since 1 August 2025, article 3.3(d)(e)(f) cybersecurity for internet-connected and data-processing radio equipment, with EN 18031 parts cited with restrictions. See RED tests.
Interaction with FCC Part 15.247
Section titled “Interaction with FCC Part 15.247”In the United States most Bluetooth radios are authorised under 47 CFR 15.247. The limits that matter for Bluetooth, from the eCFR text:
| Rule | Requirement |
|---|---|
| 15.247(a)(1)(iii) | Frequency hopping systems in 2400-2483.5 MHz use at least 15 channels; average occupancy per channel at most 0.4 s within 0.4 s times the number of channels |
| 15.247(b)(1) | Peak output power 1 W for hopping systems with at least 75 non-overlapping channels; 0.125 W for all other hopping systems in 2400-2483.5 MHz |
| 15.247(a)(2) | Digital modulation (DSSS and similar): minimum 6 dB bandwidth 500 kHz |
| 15.247(b)(3) | Digital modulation: 1 W, measurable as maximum conducted output power |
| 15.247(b)(4) | Limits assume antenna gain up to 6 dBi; above that the power is reduced |
Which 15.247(b)(1) power limit applies to a hopping radio therefore depends on how many channels it actually uses. Measurement methods are in the FCC KDB guidance. The resulting FCC ID is unrelated to the SIG Design Number. For a product sold on both sides of the Atlantic, see EU + US dual certification.
Claims the texts contradict
Section titled “Claims the texts contradict”| Common claim (including this page before October 2026) | What the source says |
|---|---|
| "Qualification is only a trademark licence." | The QPRD holds the Compliance Requirements of the Patent/Copyright License Agreement; qualification brings the product under both the patent and trademark licences (SIG overview and Join pages). |
| "The QDID and DID identify qualified designs and products." | QDID is a legacy term for designs qualified before 1 July 2024; new Designs get a Design Number (quick start guide, QPRD 1.1). |
| "EPL on a module QDID costs a reduced listing fee." | There is one Product Qualification Fee (USD 12,000 for an Adopter in the March 2026 schedule), charged for the first product including a given Design; later products with the same Design are free (SIG overview page). |
| "Every SKU needs its own paid listing, so variants get expensive." | Same rule: further products with the same Design are not charged. Each product is still submitted, with its own name and model number. |
| "Your module supplier's qualification covers your product." | A supplier cannot complete the process for another company's product; you submit under your own membership (QPRD section 2). |
| "Associates pay a fee scaled to revenue; Adopter is the only free-ish level." | Dues are fixed small/large amounts; a Contributing Adopter level now exists (fee schedule, 1 March 2026). |
| "BQTF testing is mandatory for LE Audio and Auracast during their introduction." | The QPRD ties BQTF/BRTF testing to Category A test cases in RF, RFPHY, BB, LL, ISOAL, LMP and lower HCI layers, not to specific profiles. |
| "Auracast needs qualified CAP, BAP and BASS profiles." | The SIG communication guide ties Auracast to the PBP layer (plus brand rules); LE Audio to TMAP or HAP. |
| "Mention Bluetooth 5.x in your documentation once listed." | The SIG does not endorse Core-version claims and says the Core version should not be included in product names. |
| "Any hardware change, such as the antenna, invalidates the qualification." | Option 1 allows changes outside the Design (industrial design, other radios, packaging); the member assesses that they do not affect the ICS Form or compliance. Antenna changes stay a RED/FCC question. |
Common pitfalls
Section titled “Common pitfalls”- Qualifying late. Qualification must be complete on or before the first sale or distribution, and customs may check the database.
- Name mismatch. A model number on the box different from the one submitted breaks QPRD 3.1, and correcting it means a new qualification.
- Assuming the module covers you. Ask the supplier for the DN or QDID, then submit under your own account and budget the fee for the first product with that Design.
- Changing the ICS Form. Adding or removing layers or ICS selections turns option 1 into option 2 and can generate a test plan.
- Old Core versions. Check deprecation dates before reusing a Design for a new product: Core 5.0 is deprecated from 1 February 2027.
- Incomplete Compliance Folder. Test logs and reports must be kept for at least a year after the product leaves sale.
Engineering support for qualification
Section titled “Engineering support for qualification”See also
Section titled “See also”- Certifying a Bluetooth Low Energy Wearable
- Wireless certification: the law vs the logo
- Zigbee + CSA: certification of the 802.15.4 mesh protocol
- Wi-Fi Alliance: interoperability + Wi-Fi brand
- Matter certification (CSA): process, DAC and DCL
- Qi, Qi2 wireless charging certification (WPC)
- UWB and FiRa Consortium certification
See also the glossary for QDID, DID, ICS, IXIT definitions, and the guides RED standards, FCC scope and EU + US dual certification for a dual programme.
Sources & references
- Qualification Program Reference Document (QPRD) v5, 2026-04-21, Bluetooth SIG www.bluetooth.com/wp-content/uploads/Files/Specification/HTML/QPRD/out/en/index-en.html
- Qualify your product, Bluetooth Qualification Process overview, Bluetooth SIG www.bluetooth.com/develop-with-bluetooth/qualify/
- Bluetooth Qualification Process quick start guide, Bluetooth SIG www.bluetooth.com/bluetooth-qualification-process-quick-start-guide/
- Schedule of dues and fees, effective 1 March 2026, Bluetooth SIG www.bluetooth.com/fee-schedule/
- Join the SIG, membership levels, Bluetooth SIG www.bluetooth.com/develop-with-bluetooth/join/
- Specifications and documents (status, deprecation and withdrawal dates), Bluetooth SIG www.bluetooth.com/specifications/specs/
- Bluetooth Core 6.0 feature overview, Bluetooth SIG www.bluetooth.com/core-specification-6-feature-overview/
- Bluetooth Core 6.1 is here (bi-annual release schedule), Bluetooth SIG www.bluetooth.com/blog/delivering-on-the-bi-annual-release-schedule-bluetooth-core-6-1-is-here/
- Bluetooth Core 6.2 feature overview, Bluetooth SIG www.bluetooth.com/bluetooth-core-6-2-feature-overview/
- Bluetooth Core 6.3 technical overview, Bluetooth SIG www.bluetooth.com/bluetooth-core-6-3-technical-overview/
- Communicating supported Bluetooth functionality, Bluetooth SIG www.bluetooth.com/communicating-supported-bluetooth-functionality/
- Bluetooth enforcement program, Bluetooth SIG www.bluetooth.com/develop-with-bluetooth/qualify/bluetooth-enforcement-program/
- Qualification test facilities (BQTF list), Bluetooth SIG www.bluetooth.com/develop-with-bluetooth/qualify/qualification-test-facilities/
- ETSI EN 300 328, wideband transmission systems in the 2.4 GHz band, ETSI www.etsi.org/deliver/etsi_en/300300_300399/300328/
- 47 CFR 15.247, operation within the bands 902-928 MHz, 2400-2483.5 MHz and 5725-5850 MHz, eCFR www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15/subpart-C/section-15.247
Frequently asked questions
- Does Bluetooth SIG qualification replace RED or FCC radio certification?
- No. The Bluetooth Qualification Process is a contractual programme of the Bluetooth SIG, tied to its patent/copyright licence and its trademark licence. It says nothing about spectrum law. A Bluetooth product placed on the EU market still needs RED compliance (EN 300 328 for article 3.2), and in the US an FCC authorisation (Part 15.247 for most Bluetooth radios). Both tracks are needed and neither replaces the other.
- Do you have to be a Bluetooth SIG member to qualify a product?
- Yes. The QPRD requires the submission to be made under a user account of the member that markets the product, and a supplier or another member cannot qualify it on your behalf. Adopter membership costs USD 0 a year. Contributing Adopter (USD 3,500 or 16,500) and Associate (USD 11,250 or 52,500) add working group access and discounts on the qualification fee.
- What replaced the QDID and the Declaration ID?
- Since 1 July 2024 the SIG issues a Design Number (DN) the first time a product using a new Design completes the process. QDID is now a legacy term for designs qualified before that date. Existing QDIDs, and Declaration IDs for the single existing Design option, can still be referenced when you qualify a product.
- What are the ICS and IXIT in a qualification file?
- The ICS is the document the SIG publishes for each specification listing its features, and the ICS Form is what the member fills in to say which features the Design implements. The IXIT is a form giving extra configuration details needed to run the tests. The SIG tool checks the ICS Form for consistency and generates the test plan from it.
- Can testing be skipped by reusing an already qualified Bluetooth module?
- Yes, if the Design is used unmodified (QPRD option 1: a single existing Design, no change to the ICS Form). No test plan is generated. You still submit the product under your own membership and pay the qualification fee for the first product that includes that Design; later products with the same Design are not charged.
- What happens when a Bluetooth product is sold without completing qualification?
- The SIG enforcement programme applies, with cost recovery fees that rise with the time taken to resolve the failure, and possible suspension of membership. The SIG also states that customs officials check its Qualified Product database and that unlisted products may be seized at the border. Non-members are placed in a compliance programme.
- Which Bluetooth Core versions can be used for a new design in 2026?
- The SIG list of specifications shows Core 5.0 to 5.4 (amended) and Core 6.0, 6.1, 6.2 and 6.3 as adopted. Core 5.0 has a deprecation date of 1 February 2027. Since 2025 the Core Specification follows a twice-yearly release schedule, so a new version appears roughly every six months.