Some people think only Bluetooth earbuds and speakers need BQB certification. Others assume using a certified module means you're off the hook entirely. Still others figure domestic sales don't require it. The market's understanding of BQB certification's product scope has significant gaps.
This article breaks down the determination logic, filing classification, certification paths, and exemption boundaries from scratch. All content is based on the currently effective QPRDv2 rules and Qualification Workspace online system operations as of 2026.
Determining Whether Your Product Needs BQB: Two Conditions, But Priority Matters
BQB certification's mandatory obligation doesn't depend on where you sell, what chip brand you use, or your Bluetooth type. It comes down to two conditions — and their triggering priority differs.
Higher Priority: Has Your Product Used the Bluetooth Trademark Anywhere?
"Anywhere" includes product housing silkscreen, packaging box, instruction manual, product listing page, system settings interface, or app connection screen. If you've used the Bluetooth word mark or logo anywhere, regardless of whether your hardware actually contains a Bluetooth chip or whether Bluetooth functionality is actually enabled, the BQB certification obligation is triggered.
SIG enforces this through the trademark licensing system. The logic is direct: you're publicly representing that your product conforms to Bluetooth technical standards, and SIG requires you to produce certification records as proof.
Lower Priority: Does Your Product Hardware Use Bluetooth?
If your hardware genuinely incorporates a Bluetooth RF chip and uses Bluetooth-defined wireless communication protocols in the 2.4 GHz band, but you never use any Bluetooth trademark anywhere — no marking, no mention in manuals, no public claim of Bluetooth functionality — under QPRDv2's current rules, there is no mandatory BQB obligation.
Note the logical priority: as soon as you use the Bluetooth trademark, BQB is unavoidable regardless of hardware. Many people intuitively think "has Bluetooth hardware, therefore must certify" — the actual rule works the other way around. Trademark is the primary trigger condition.
BLE (Bluetooth Low Energy) and Classic Bluetooth have zero difference in determining the certification obligation. There's no such thing as "BLE can be exempted" or "low power means you can skip it." The exemption criterion is trademark usage, not Bluetooth type.
Products sold domestically in China versus export products have no difference in BQB obligation — certification is globally unified. Domestic products additionally require SRRC (State Radio Regulation Center) type approval on top of BQB, and the two systems don't substitute for each other. Having SRRC without BQB still leaves trademark infringement risk on the table.
Current Filing Classification: No Longer by "End Product / Component / Subsystem"
There's an industry information gap that needs correcting first.
Many BQB certification resources, including market articles from several years ago, describe SIG dividing Bluetooth products into three types: End Product, Component, and Subsystem. This classification was indeed SIG's official framework during the legacy Launch Studio platform era.
But from July 2024 onward, through to the current 2026 fully operational Qualification Workspace online system, SIG has retired this legacy product type classification. Current filing no longer asks you to check "I'm an end product" or "I'm a component" — instead, classification is by core configuration layer: BR/EDR Core Layer (Classic Bluetooth), LE Core Layer (Low Energy Bluetooth), or a combination of both for dual-mode. Which configuration path your product takes in the system is determined by actually implemented Bluetooth capabilities, not by the "are you an end product or component" label.
Are the old classification concepts completely useless? In practical business communication, terms like "module certification" and "end-product certification" are still used because they describe certification chain roles — whether you're a module supplier or an end-product manufacturer — rather than certification types themselves. We'll continue using terms like end product and module below, but understand they're business roles, not system filing categories.
The practical question for end-product manufacturers is: I'm building a complete product and need to make it BQB-compliant. What paths are available?
Two Certification Paths for End Products: Boundary Conditions Explained
Path 1: EPL (End Product Listing Using Existing Design)
You purchase a Bluetooth module that already holds BQB certification, reference the module's certification record, and list your end product. No lab testing needed. With complete documentation, review takes a few business days — from project start to DID number in 1-2 weeks.
But EPL isn't an unconditional "buy a certified module and you're automatically done." There's a critical boundary condition: your end product's actually enabled Bluetooth feature configuration must completely match the module's native certified ICS configuration.
Conversely, if the module was only certified for BLE single-mode and your end product only enables BLE — feature configuration is identical — that's the ideal EPL scenario. "Feature configuration matches" doesn't mean "looks roughly similar" — it means ICS item-by-item consistency.
Path 2: Full Qualification
Your Bluetooth solution is designed from chip selection to antenna matching circuit from scratch, or you're using a chip with no existing BQB certification record. You must go through the full test flow — RF conformance, PTS protocol stack consistency, and Profile scenario verification — all three rounds must pass. After testing, submit the complete report package for review.
Baseline timeline for full qualification: a typical dual-mode consumer electronics product doing only traditional A2DP, HFP, and SPP without LE Audio or Channel Sounding, from lab project opening to DID receipt, two months is the normal pace. If protocol stack rework is needed during testing, three to four months is common.
Add LE Audio functionality (LC3, BIS, Auracast), and the baseline timeline jumps by 4-6 weeks. Add Channel Sounding ranging, and it goes up another 4-6 weeks. More features mean longer timelines — this variable cannot be ignored during project scheduling.
Product Category Guide: Certification Considerations by Type
Rather than organizing by the old product classification framework, let's go by actual shipping product categories. One additional note: IOP (Interoperability) testing is not a SIG mandatory audit item, not part of BQB certification's formal pass/fail criteria, and doesn't generate an official audit report.
Consumer Audio
Bluetooth TWS earbuds, over-ear headphones, neckband styles, Bluetooth speakers, Bluetooth soundbars, Bluetooth transmitters and receivers. This category has the largest shipping volumes and the most brands — SIG's surveillance coverage is highest here. Don't cut compliance corners. Products with LE Audio (LC3 codec, Auracast) face a full additional test suite beyond traditional A2DP.
Wearables
Smartwatches, fitness bands, smart glasses with Bluetooth connectivity. Most are BLE single-mode solutions with a relatively narrow test scope, but GATT-layer Profile interaction logic is complex — notifications, read, write, indicate operations make GATT the highest-fault module in protocol stack consistency testing.
Smart Home and IoT
Smart locks, smart bulbs, smart plugs, smart sensors, Bluetooth Mesh lighting control devices. This category is predominantly BLE with a certification path similar to wearables. SIG surveillance rates for high-volume IoT categories are increasing year over year.
Automotive
In-vehicle infotainment systems (head units), OBD Bluetooth adapters, Bluetooth digital car keys, in-vehicle Bluetooth hands-free systems. Common misconception to correct: many head units simultaneously pursue BQB and Android Auto certification, but Google's Android Auto 2.0 certification does not make BQB DID a mandatory prerequisite — it only requires Bluetooth interaction functionality to conform to Bluetooth specifications with complete test data.
Not having BQB doesn't mean you "absolutely cannot start AA testing." The certifications that do make BQB a mandatory prerequisite are Huawei HiCar and some OEM in-vehicle connectivity specifications — don't generalize this condition to all automotive certification scenarios. That said, from a practical standpoint, doing BQB first makes Bluetooth compliance data readily available for other certifications and smooths the overall process.
Computer Peripherals
Bluetooth keyboards, mice, touchpads, game controllers. Most use BLE HID Profile with concentrated test items and a mature certification path.
Health and Medical
Bluetooth blood pressure monitors, glucometers, body composition scales, heart rate straps, Bluetooth-enabled hearing aids. Medical products need BQB certification plus medical device registration certification. The two systems' test data and report formats don't fully align — tell the lab about medical registration requirements before starting certification to avoid going back for supplemental data.
Multi-Radio Composite Products
Products simultaneously featuring Wi-Fi, NFC, and other wireless functions. BQB certification only covers the Bluetooth portion — having Wi-Fi doesn't mean additional Bluetooth testing. However, BQB's Bluetooth RF reports can only be partially referenced for FCC, CE-RED, SRRC, and other RF compliance certifications. Basic RF indicators may be reusable, but complete test exemptions are unlikely because different regulations have different test equipment, limit requirements, and spurious frequency band coverage.
Family Listing: Hard Conditions for Multiple SKUs Sharing One DID
Can related products be grouped under one Family and share a single DID? SIG allows it, but with hard prerequisites.
The Bluetooth chip model, RF matching circuit, and underlying protocol stack firmware must be completely identical. Under this condition, differences in housing material, color, screen size, storage capacity, and passive components don't trigger independent certification — they can be grouped under the same Family.
But there's a commonly overlooked constraint: even if the chip, RF, and protocol stack are all unchanged, adding or removing Profile functionality means you can't fold into the existing Family. For example, if the original only did A2DP and SPP and the new model adds HFP, or if new features like LE Audio or Channel Sounding are added, these can't be grouped under the original Family — additional differential test items are required.
This mechanism saves real money for brand owners with many SKUs but a unified Bluetooth solution. Ten-plus SKUs per year with only one Bluetooth core design and no Profile configuration changes? You pay testing fees once and DID application fees once.
Not sure if your product needs BQB certification? Contact BlueAsia Testing & Certification — Consultant: 13534225140 (Benson)
相关新闻
