The timeframe for BQB certification depends entirely on whether you're going through full qualification or EPL simplified listing. The difference between these two paths isn't incremental — it's an order of magnitude. This article breaks down realistic timelines for each path, what each stage takes, what bottlenecks to expect, and how to plan your schedule properly.
Important baseline: The currently effective global specification is QPRDv2. QPRDv3 is still in draft and has not been officially released — do not plan your filing materials based on an unenacted draft. The industry's former designation QDID is now officially DID (Design ID) under SIG's current naming. The legacy Launch Studio platform has been fully decommissioned. The current Qualification Workspace online system has abolished the entire RN (Receipt Number) purchasing mechanism — no entry tickets to buy, no expiration dates to worry about. Once hardware is finalized and testing is complete, you directly open a DID submission.
EPL Simplified Listing: 1 to 2 Weeks to Certification
If you're using a Bluetooth module that already holds BQB certification on the market, your end product doesn't need bottom-up Bluetooth performance testing. You reference the module's certification record for listing — and this path is by far the fastest.
Here's the specific timeline:
·Documentation preparation: 1-2 days after confirming the module's DID is in valid status and you have the complete reuse authorization documents from the module vendor. You need product information, Profile list, product photos.
·Qualification Workspace online filing: Half a day to one full day.
·SIG review: Standard EPL review takes 3-7 business days. With complete documentation and no defects, you can get your DID in as fast as one week. During peak review periods or when cross-enterprise references are missing authorization documents, the maximum is two weeks.
EPL is fast because it skips the entire lab testing phase. The Bluetooth underlying compliance is already covered by the module — your end product just needs to prove it's an integration of a compliant module. Naturally, the filing process is short.
But there are prerequisites that, if not confirmed, can actually slow you down:
·The module's certification record must be in valid status. If the module vendor's certification has expired or documentation is incomplete, you can't directly reference it.
·For cross-enterprise references using third-party purchased modules for EPL filing, you must provide the module vendor's stamped authorization reuse document and the module's complete valid Component Listing. Missing authorization documents will get you rejected by SIG outright, and supplementing materials adds another few days to two weeks of back-and-forth. Same-enterprise self-owned module reuse review is considerably more relaxed.
Full Qualification: Months, Not Weeks
For self-developed Bluetooth solutions or uncertified modules, full qualification is the only option — and the timeline is substantially longer. Once samples are in hand, the time distribution across stages looks like this:
Lab Testing Time
·Single-mode BLE or single-mode BR/EDR, no LE Audio, no test failures: 2-4 weeks of pure lab testing.
·Dual-mode BR+BLE with LE Audio (LC3, BIS, Auracast dedicated): 4-8 weeks of pure testing.
·With Channel Sounding centimeter-level ranging: Add another 2-4 weeks of dedicated testing.
Queue Time
Lab peak-season scheduling typically adds 1-3 weeks of waiting. If testing reveals issues requiring整改 rework, each rework round adds 1-3 weeks. So realistically, from sample delivery to complete test reports: smooth sailing is 1-2 months; multiple rework rounds can stretch to 3-4 months.
SIG Review After Testing
Once all tests pass, you submit the complete certification application and documentation on Qualification Workspace. SIG's official review runs 1-4 weeks under normal conditions. During peak periods around specification version updates, review can stretch to 4-6 weeks.
Bottom line for full qualification: From project kick-off to DID in hand, 2-4 months is the normal range. If multiple rework rounds are needed, 4+ months is realistic.
What Actually Slows Projects Down
1. No Test Interface on Sample Units
Mass-production sealed units without RF engineering test mode access can't undergo RF testing at all. You'd have to go back and build new engineering samples — 2-4 weeks lost. Always reserve test interface access during the sample phase.
2. Missing Profile Declarations
Omitting a Profile during filing means supplementing materials and re-running the process. Know which Profiles your hardware supports from day one — don't start figuring it out when you're filling out the application. QPRDv2 rules require that hardware-supported Profiles and protocol features must be declared truthfully. You can't check "not supported" to dodge testing.
3. Test Failures and Rework
This is common in full qualification. First-round RF test issues mean going back to adjust antenna matching or swap components, then resubmitting for round two. How long rework takes depends on problem complexity — sometimes one round fixes it, sometimes multiple rounds. Pre-testing before formal submission reduces rework rounds.
4. SIG Review Peak Periods
SIG's global review team handles certification applications from all countries. Certain periods see concentrated application volumes, and review timelines stretch by several weeks.
5. Using Outdated Process Knowledge
QPRDv2's current filing system has only had UI display logic optimizations. End Product, Component, and Subsystem product classification rules have not been cancelled — don't be misled by QPRDv3 draft rumors. If you plan based on the wrong classification framework, your materials won't match, and resubmitting wastes significant time.
Timeline Differences by Product Type
·Bluetooth audio products (speakers, earbuds): If only doing traditional A2DP and HFP, test items are relatively standard — timeline follows single-mode BR norms. With LE Audio support, plan for 4-8 weeks of dual-mode + LE Audio testing.
·Bluetooth data products (IoT modules, sensors): BLE-only with simple functionality, test scope is manageable — 2-4 weeks for pure testing, notably faster than dual-mode audio products.
·Automotive Bluetooth products: A2DP + HFP + AVRCP + SPP means more Profiles, more test items, and longer timelines than simple BLE products.
Multi-SKU Family Certification
Products sharing the same hardware family (identical Bluetooth chip, RF matching, and underlying protocol stack firmware) only need the primary model to complete full testing. Derivative models only file incremental differences without re-running lab tests — significantly shortening certification for subsequent models. But the base model's full timeline doesn't change. The time savings kick in from the second model onward.
Need help planning your BQB certification timeline? Contact BlueAsia Testing & Certification — Consultant: 13534225140 (Benson)
相关新闻
