Some manufacturers complete BQB certification in just over a month – while others, with unclear solutions and insufficient documentation, face delays of over half a year with remediation. Timeline depends not just on lab test days – every stage from solution selection to scheduling affects overall progress.
1.1 SIG membership and product registration
First, register as an Adopter member on the Bluetooth SIG website – this basic tier is free and sufficient for most head-unit and consumer-electronics manufacturers. After registration, create a product listing in the system – model number, Bluetooth version, and supported Profile functions.
This can be done in half a day. Common blockers: company registration name mismatch with the business licence – causing review rejections and wasted time.
1.2 Chip/module DN validity verification
During hardware selection, confirm whether the Bluetooth chip or purchased module has a valid DN (Design Number) – this determines whether you need a full test suite or can proceed with module-derived listing. Request the full DN documentation from the supplier and verify its status in the SIG public system. Important: if the module manufacturer's membership expires, you may not be able to continue using its DN for derivation – identify this risk early.
1.3 Define test scope and test plan
With the BQTF lab, confirm the test scope – basic Bluetooth 5.3 dual-mode, 5.4's new PAwR, LE Audio support – different feature sets mean different test cases. The lab provides a test plan for confirmation – typically 3–5 working days.
2. Lab Testing Phase
First, distinguish two main paths – often confused: self-developed new hardware with no certified module DN → full testing for a new DN; off-the-shelf certified module used without changing RF or Bluetooth firmware → QDL module-derived listing.
2.1 Full testing for new solutions – duration
Without an existing module DN, samples are sent to a BQTF lab for full RF and protocol conformance testing. Basic BR/EDR+BLE 5.3 dual-mode devices: 2–3 weeks lab occupation; adding full LE Audio: another 1–2 weeks.
Important clarification: -40°C to 85°C wide-temperature RF testing is not SIG BQB mandatory – it is an OEM DVT specification for automotive. Do not treat it as a BQB required test – it adds unnecessary budget and timeline. With no major remediation, full testing typically takes 4–6 weeks.
2.2 Module DN derivation listing – duration
Using a certified module as-is – without changing RF circuitry, antenna, or Bluetooth firmware – QDL derivation listing applies. Standard scenarios do not require full lab RF/protocol testing – only module authorisation documentation submission. If you modify any Bluetooth-related parameters of the module, difference-item retesting is required – test workload is roughly 20–30% of a full project – 3–5 working days if smooth.
- Verify derivation conditions in advance
From 2026, SIG has tightened derivation review. Do not assume that small firmware changes still qualify. Pure UI/business-logic changes can be filed with a declaration. Changes to the protocol stack, RF transmit parameters, or new Profile additions – high probability of losing derivation eligibility – requiring retesting or even full retesting. Obtain the module's full technical documentation and verify every item before starting.
2.3 Remediation timeline after test failures
If first-round tests show spurious emissions, adjacent-channel power, or sensitivity failures – hardware rework is required – antenna matching, transmit power adjustments, or RF PA replacement. Remediation speed depends entirely on the hardware team's responsiveness – a smooth fix takes one week; multiple rounds of debugging can easily take a month. Arrange pre-testing before formal submission to significantly reduce rework risk.
3. Report Compilation and SIG Online Listing Review
3.1 Lab issues formal report
After all tests pass, the BQTF lab compiles the full test report – typically 3–5 working days; more complex devices with multiple protocols may take up to 7 days. For standard module derivation, a full test report is not required – the key document is the module authorisation file.
3.2 SIG system submission – two fee categories
Upload documentation to the SIG system and initiate the qualification application. Two fees are often confused: Adopter full new DN qualification – USD 12,000 (effective from March 2026); QDL module derivation listing – this high fee does not apply. Distinguish clearly when requesting quotes and budgeting.
SIG's official review timeline: 10 working days – with complete documents, ~1 week; during system maintenance or backlog, up to 3 weeks. SIG offers a paid Fast Track expedite channel – rarely used for standard projects – do not assume it does not exist.
3.3 Listing completed upon approval
After review, the product is entered into the SIG public database and assigned a DN – completing the process – the product can legally use Bluetooth trademarks and logos.
4. Key Factors Affecting Overall BQB Timeline
4.1 Lab scheduling
Global BQTF labs are limited – peak seasons (early year and mid-year) are busy – book 2–3 weeks in advance to secure a slot. Last-minute insertion not only costs extra but also does not guarantee a fixed delivery date.
4.2 Sample maturity
Submit samples in final production state – firmware version, antenna solution, and RF parameters all locked. Submitting engineering samples – if later changes affect Bluetooth software/hardware – will require reassessment and additional timeline.
4.3 Multi-protocol feature overlap
Devices supporting BR/EDR, BLE, and LE Audio simultaneously have significantly more test cases – longer equipment occupation. Lock product features early – do not add major modules like LE Audio after samples are already at the lab.
5. Three Typical Scenario Timelines
5.1 Fastest path – QDL module derivation listing
All module documentation complete – no Bluetooth-related changes – no lab retesting. Documentation + SIG review: 3–4 weeks total.
5.2 Standard path – new full test, Bluetooth 5.3 dual-mode, no remediation
Lab testing 4–6 weeks + SIG review 2 weeks: 6–8 weeks total.
5.3 Slowest path – new full test + LE Audio + remediation + peak-season scheduling
Multiple hardware remediation rounds + lab peak season: 12–16 weeks total.
Summary: before starting a project, prioritise three things – module DN validity, clear test scope, and sample hardware/software finalisation. Any change in any of these will cause cascading delays.
For BQB certification timelines, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.
相关新闻
