The most frustrating part of BQB certification isn't usually the testing — it's the documentation. There's a lot of it, the product information is highly detailed, and missing one document or filling something incorrectly means your review gets bounced back for补充, costing you weeks of back-and-forth.
Basic Documents Required for All BQB Applications
Regardless of whether you're going through EPL or full qualification, certain foundational documents are non-negotiable.
1. Company Business License and SIG Membership Information
Certification must be submitted through your own company's SIG membership account — you cannot use an agent's or supplier's account. Before applying, confirm that your membership account is active, annual dues are paid, and account information (company name, address, contact person) matches exactly with what's on your submission documents. Associate membership is the standard configuration for the vast majority of Chinese manufacturers — there's no such thing as a "zero-fee basic membership."
2. Product Information Document
Your product model name must match the final commercial product model — internal development codenames should not be used. The Bluetooth functionality description needs to be clear: is it Classic Bluetooth (BR/EDR), Bluetooth Low Energy (BLE), or dual-mode? And for each mode, which specific Bluetooth Profiles are implemented? A2DP stereo audio distribution, HFP hands-free calling, AVRCP audio/video remote control, SPP serial port emulation — these common automotive and audio Profiles need to be listed item by item from start to finish.
3. Product Appearance Photos
Nothing elaborate — just a few clear photos showing the product's overall form factor. SIG reviewers use these to confirm the product is indeed a complete Bluetooth end device, not a bare module or half-finished assembly.
Additional Documents for the EPL Path
EPL doesn't require lab testing, so the documentation burden is much lighter. But a few items are essential:
Module vendor's certification record. Specifically, the module's DID (formerly QDID), plus confirmation that the module's certification is currently valid — not revoked or expired. The module vendor typically provides a certification declaration document specifying which model the DID corresponds to, the certification status, and authorization for your end product to reference their certification record.
Full Qualification Document Checklist
Self-developed Bluetooth solutions going through full qualification require substantially more documentation. Here's the breakdown by category:
1. Product Technical Specifications
Detailed hardware architecture description: main chip model, Bluetooth chip model, antenna type (PCB antenna, ceramic antenna, or external antenna) with gain parameters, power supply method, Bluetooth protocol stack version information. This is a technical document for certification engineers — not a marketing product brochure. Data must be accurate and parameters must be complete.
2. Schematics and PCB Layouts
Certification labs and SIG reviewers only need the Bluetooth RF and protocol communication-related sections — specifically the schematic and PCB layout around the Bluetooth chip's RF trace area. You do not need to submit the complete full-board PCB layout, and peripheral circuitry unrelated to Bluetooth definitely shouldn't be included. RF trace impedance control and matching circuit details that affect RF performance must be visible on the schematic.
3. BOM (Bill of Materials)
Only list the core components in the Bluetooth RF chain: Bluetooth chip, crystal oscillator, filters, antenna matching components — specify model, specifications, and manufacturer for these key items. There's no need to pad the list with unrelated resistors, capacitors, housing materials, and accessories. The declared BOM must match actual production materials. If SIG's spot check reveals discrepancies, you've got a real problem.
4. Antenna Specifications
The antenna is central to Bluetooth RF performance. Antenna type, gain data, radiation pattern (if available) — the lab needs this information for RF testing. For external antennas, specify the connector type and cable specifications as well.
5. Bluetooth Profile Implementation List
Which Profiles the product implements, version number for each Profile, and corresponding ICS declarations. Critical note: under the current QPRDv2 framework, ICS entries must truthfully indicate hardware-native supported and unsupported protocols and Profile features. You cannot deliberately conceal integrated features by checking "not supported" to avoid testing.
6. Software Version Information
Firmware version number or software version number, protocol stack version and source (self-developed or third-party). This information is used during review to verify compatibility considerations between phone-side and device-side protocol stacks.
Test Report Documents
Important distinction: RF conformance, protocol consistency, and Profile scenario reports are only required for full qualification — all issued by SIG-authorized BQTF labs. The EPL path does not involve lab testing and requires no test report or antenna test data uploads.
1. RF Conformance Test Report
Includes test data and pass/fail conclusions for transmit power, frequency error, modulation characteristics, receiver sensitivity, spurious emissions, and other RF parameters.
2. Protocol Stack Consistency Test Report
Verifies the Bluetooth protocol stack implementation conforms to the corresponding SIG Core specification requirements.
3. Profile Scenario Test Report
Verifies application-layer Profiles like A2DP and HFP function correctly per specification in actual use scenarios.
If your product implements LE Audio — regardless of whether the underlying Bluetooth version is 5.2, 5.3, or 5.4 — you also need to submit dedicated test reports for LC3 codec, BIS broadcast sync stream, and Auracast modules. Traditional A2DP/HFP-only Bluetooth designs do not need to prepare LE Audio reports.
Channel Sounding ranging functionality currently only requires additional testing and reports for Core 6.0 devices with ranging capability enabled. Ordinary Bluetooth devices don't need this. BQTF labs are opening commercial testing for this throughout 2026 — plan accordingly if you have ranging requirements.
Declaration of Compliance Documents
The Declaration of Compliance (DoC) is a formal statement document that SIG requires, in which your company formally declares the product conforms to Bluetooth SIG technical specifications and regulatory requirements. The Qualification Workspace platform has a standardized DoC template built in — fill it out and export directly. No need to create your own format.
The declaration requires product identification information, referenced Bluetooth Core specification version, test report numbers (EPL path doesn't require this field), and company authorized signatory information. The declaration must be signed by a formally authorized company representative with an official corporate seal — upload the scanned copy. Having a random colleague sign, or the signer lacking formal authorization, will result in the declaration's validity being questioned during review.
Sample Submission Requirements
Full qualification requires submitting at least 2 engineering sample units to a BQTF lab. These aren't just two production units grabbed off the line.
At least one unit must support entering RF test mode (engineering mode) with an interface allowing test instruments to directly control the Bluetooth chip's transmit and receive parameters. Production-sealed units without test interfaces can't be tested — you'd have to produce new samples, adding delays of two weeks to a month.
Samples must match the final production product's Bluetooth design exactly. You can't use one design for testing and a different one for production. If BOM components, PCB Bluetooth RF area design, or firmware versions change later, this may trigger re-evaluation and re-testing.
Preparing BQB certification documents? Contact BlueAsia Testing & Certification — Consultant: 13534225140 (Benson)
Related News
