From March 2026, Bluetooth SIG introduced new fee structures – many only heard the headline "8.7% increase" – but the details are far more nuanced. As early as October 2025, the industry formally switched to QPRD v3. There's a common misconception: not all new certification projects require hardware upgrades to Bluetooth 5.4. The review logic follows the functions actually enabled by the product – it does not simply check the hardware version. In 2026, LE Audio testing requirements for audio devices have tightened – Auracast broadcast audio follows the same principle.

The core point: testing follows marketing claims. Even if the chip supports the feature natively – if you don't claim it publicly – you don't have to run the corresponding tests. Once packaging or listings claim support – the full test suite is required. Many projects fail at certification because chip selection and product marketing weren't aligned with compliance requirements from the start.

The long‑used Launch Studio platform has been fully decommissioned – all certification operations have moved to the new Qualification Workspace system. The old QDID numbering has been replaced by DN (Design Number) – historical records have been migrated. The RN mechanism remains – to submit a DN application in the new system, you still need to purchase an RN first.

1. Membership Tier Selection – Align with Volume

1.1 Adopter vs. Associate – the trade‑off

·Adopter: no annual fee – but per‑model DN filing fees are higher.

·Associate: annual fee – but per‑model DN fees are significantly lower.

·2026: new mid‑tier – Contributing Adopter – adds flexibility.

Practical reference:

·2–3 new models/year → Adopter – avoid ongoing annual fees.

·5+ models/year → Associate – more cost‑effective long‑term.

The per‑model cost difference between the two is nearly double – estimating in advance helps control compliance budgets.

Many ODM clients produce multiple variants based on the same hardware platform – with slight configuration tweaks for different appearances and functions. Note: each independently sold model requires its own DN. Comparing costs: Adopter for five models – total cost significantly higher than Associate annual fee + per‑model fees. Don't wait until mid‑project to change membership status.

1.2 RN – don't forget the expiry

·Adopter: RN validity 6 months – expires automatically – fees non‑refundable.

·Associate: RN validity 12 months.

RNs are only used for DN qualification submissions – not suitable for bulk purchase long‑term storage.

Validity starts from the payment date – not the later submission date – factor this into project scheduling. Individual RN costs aren't high – but multiple expiries within a year add up. In the past, many companies pre‑purchased RNs – now, for Adopter clients, hoarding is risky – if projects are delayed, expired RNs must be repurchased.

  2. LE Audio – Don't Be Misled

2.1The core criterion – follow public claims

The common claim "LE Audio is fully mandatory from 2026" is not accurate. The current TCRL specification clearly states – reviewers check public product claims. If marketing materials, listings, or packaging claim support for LC3 encoding, CIS low‑latency links, or Auracast broadcast audio – full BAP, CAP, and LC3 tests are required.

Key logic: reviewers look at public market materials – not chip‑level parameters. Even if the chip natively supports LE Audio – if you don't claim it anywhere – no testing is required. Many manufacturers have been caught – packaging or listings claimed LE Audio – but the submission didn't include the tests – forcing material changes and supplementary testing – wasting time and money.

2.2Which categories don't trigger LE Audio tests?

Keyboards, remote controls, and similar peripherals – using classic Bluetooth for voice – without LE Audio functionality – even if voice is over BLE or classic Bluetooth – as long as LE Audio isn't claimed – no LE Audio testing is required. Don't add unnecessary tests based on oversimplified online articles.

2.3Audio terminals – specific rules

For headphones, speakers, in‑vehicle audio – only if they explicitly claim LE Audio support – do they need full LE Audio testing. Test focus: audio latency, transmission loss, multi‑device sync stability. If the product continues using traditional A2DP/HFP audio – and doesn't claim LE Audio – the rule does not apply.

Auracast broadcast audio is a major LE Audio application. If marketing material claims Auracast support – full BAP broadcast profile and CAP general audio profile tests are required – covering broadcast sync, multi‑device access, and broadcast latency. For public audio broadcast scenarios (stations, shopping malls) – reserve sufficient testing lead time.

  3. Bluetooth 5.4 – Clarifying Common Misconceptions

3.1October 2025 – new review standards

Many assume all new submissions must use Bluetooth 5.4 hardware. The actual rule: new projects follow QPRD v3 – reviewing actually enabled features – including low‑power optimisation, channel switching, and interference resistance.

Compared to Bluetooth 5.3, the new standard improves receiver sensitivity and power consumption. Companies still using Bluetooth 5.0 or 5.3 chips should note – simply upgrading firmware is generally insufficient – chip‑level support is required. Confirm chip capabilities during selection – avoid discovering mismatches after samples are built.

3.2AoA/AoD positioning – test points

For devices with AoA (Angle of Arrival) or AoD (Angle of Departure) direction‑finding – certification focuses on positioning stability and interference resistance.

Clarification: positioning accuracy figures like 5cm or 8cm are marketing parameters from solution vendors – not SIG mandatory acceptance metrics. For IoT positioning devices – follow the ICS function list – don't be limited by online precision standards.

  4. Four Certification Paths – Choose by Solution

4.1Full Certification

·Self‑selected chips, self‑designed RF – or new modules without BQB filing.

·RF conformance, protocol conformance, and interoperability all tested.

·Lab test cycle: 4–6 weeks – higher investment.

4.2EPL – simplified listing

·Products using certified commercial modules (Nordic, Telink, Espressif, etc.) – with no hardware modifications to the module.

·No RF/protocol retesting – reference the module's DN – submit documentation.

·Cycle: 1–2 weeks.

Common trap: for downstream EPL referencing, the module's DN must be classified as Component type. If the module DN is End‑Product type – EPL applications are rejected. Confirm DN classification with the supplier at the time of module purchase.

4.3Component certification

·For chip and module suppliers – Full Certification to obtain a Component DN.

·Downstream terminal manufacturers – using the same chip/module with hardware unchanged – can reference this DN for EPL listing.

4.4Upgrade certification

·For minor firmware iterations or small hardware changes – within SIG's defined change scope.

·Cycle: 1–2 weeks – lower cost than Full Certification.

·Larger changes cannot use this path – require Full Certification.

  5. Test Timeline and Common Rejections

5.1Timeline reference

·Full Certification: 4–6 weeks.

·EPL: 1–2 weeks.

These are lab testing man‑hours only – plus document preparation, RN purchase, and SIG review – total timeline: +1–2 weeks.

Year‑end is peak submission season – lab capacity is tight – book in advance. Last‑minute submissions often face long queues.

Before sample shipment: confirm firmware version, RF parameters, and application documents all match. If the lab finds version mismatches mid‑test – the entire process restarts. Include with samples: sample count, firmware version, and claimed feature list – helping the lab verify and reducing back‑and‑forth.

5.2Most common rejection reasons

·Claimed features not matching selected test items – packaging/listing claim LE Audio – submission lacks tests – revision required.

·Product model format inconsistent with DN filing – system verification fails.

Submit complete documents in one go – avoid month‑end peak submission periods – processing efficiency drops significantly.

5.3Early planning advice

At the project definition stage, decide the certification path. For purchased certified modules – obtain the Component DN from the supplier immediately. For self‑developed RF – book Full Certification test slots early. Purchase RNs as needed – don't hoard.

Before marking LE Audio claims – verify chip‑level support for LC3 encoding and Auracast stacks. If the chip lacks capability – don't add claims – once claimed, full testing is required – and failure blocks certification. Bluetooth 5.4 features and LE Audio capabilities should be confirmed at the chip‑selection stage.

For 2026 BQB certification, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.