Unlicensed but Not Unregulated: The Certification Path for 2.4 GHz BLE Products
Every year, a handful of hardware startups get to the finish line—working prototype, manufacturer lined up, crowdfunding campaign funded—and then discover they can’t legally sell their product in the United States. Not because anything is wrong with it. Because nobody on the team realized that “unlicensed spectrum” doesn’t mean “no certification required.”
The word “unlicensed” is doing tremendous damage. It creates a mental model where founders assume that because the 2.4 GHz ISM band doesn’t require a spectrum license (true), their BLE device doesn’t need FCC authorization (dangerously false). The result is a $15K–$30K surprise, a 3–6 month schedule slip, and occasionally a Kickstarter update that starts with “We regret to inform our backers…”
Here’s the reframe: “unlicensed” is like a public road. Anyone can drive on it. But you still need a street-legal car. FCC certification for a BLE device is the vehicle inspection, and the path is well-worn, manageable, and far cheaper than most founders fear, if you make the right architectural decision early.
Why the FCC Cares About Your BLE Radio
Your BLE radio deliberately generates and transmits RF energy. In FCC terminology, that makes it an intentional radiator, a device specifically designed to emit electromagnetic signals. Every intentional radiator sold, marketed, or imported into the US must receive an equipment authorization under FCC Part 15. No exceptions for startups. No exceptions for small batches. No exceptions for “it’s just Bluetooth.”
Specifically, BLE devices operating in the 2.4 GHz unlicensed ISM band fall under FCC Part 15 Subpart C, which governs intentional radiators using spread spectrum or digital modulation techniques (§15.247). The rules set limits on output power, antenna gain, spurious emissions, and occupied bandwidth. Your device must prove it stays within those limits.
But here’s what catches people: your device is also an unintentional radiator. Your microprocessor, switching power supply, display driver, and every high-speed trace on your PCB emit RF energy as a byproduct of their operation. Those unintentional emissions fall under Part 15 Subpart B, a separate set of requirements that applies to the overall device regardless of how the intentional radiator is handled.
Your BLE product therefore has two regulatory obligations: Subpart C for the radio, and Subpart B for everything else. Understanding this distinction is the key to understanding why the pre-certified module path exists and why it saves you so much.
The Two Paths: Pre-Certified Module vs. Custom RF Design
You have two fundamentally different options for FCC certification of your BLE device. One is a well-paved highway. The other is bushwhacking through the jungle with a machete and a hope.
Path A: Use a Pre-Certified BLE Module
A pre-certified module is a BLE system-on-chip packaged with an antenna (or antenna connector) that has already gone through full FCC Part 15 Subpart C testing and received its own FCC ID grant. Companies like Nordic Semiconductor, Espressif, and Silicon Labs all offer modules in pre-certified form factors. Search the FCC ID database and you’ll find the grant listing the module’s authorized operating parameters, antenna specifications, and test results.
When you integrate a pre-certified module into your product following the grant’s conditions, the intentional radiator portion of your compliance obligation is already satisfied. You’re building on the module manufacturer’s existing authorization. You don’t need your own FCC ID for the radio.
You do still need to handle Subpart B for your host device (more on that shortly), but that’s a dramatically smaller, cheaper, and faster obligation.
Path B: Design Your Own RF Circuitry
If you’re designing your own antenna, building your own matching network, or using a bare-die BLE SoC without pre-certification, you own the full Subpart C certification burden. You’ll need to engage an FCC-accredited test lab, run the complete intentional radiator test suite, potentially iterate on your RF design when something fails, and file your application through a Telecommunication Certification Body (TCB) to obtain your own FCC ID.
This is the path where startups bleed money and time.
Here’s how the two paths compare:
┌─────────────────────┬──────────────────────┬──────────────────────┐
│ │ Pre-Certified Module │ Custom RF Design │
├─────────────────────┼──────────────────────┼──────────────────────┤
│ Intentional │ Covered by module's │ Full FCC ID │
│ Radiator (Subpart C)│ existing FCC grant │ certification needed │
├─────────────────────┼──────────────────────┼──────────────────────┤
│ Unintentional │ SDoC required for │ SDoC required for │
│ Emissions (Sub. B) │ your host device │ your host device │
├─────────────────────┼──────────────────────┼──────────────────────┤
│ Typical Cost │ $3K–$8K total │ $15K–$30K+ │
├─────────────────────┼──────────────────────┼──────────────────────┤
│ Typical Timeline │ 2–4 weeks │ 3–6+ months │
├─────────────────────┼──────────────────────┼──────────────────────┤
│ Failure/Redesign │ Low (module is │ High (antenna tuning,│
│ Risk │ already proven) │ emissions, harmonics)│
└─────────────────────┴──────────────────────┴──────────────────────┘And here’s the decision logic:
┌─────────────────────────┐
│ Does your design use a │
│ pre-certified BLE module?│
└────────────┬────────────┘
┌─────┴─────┐
YES NO
│ │
▼ ▼
┌─────────────┐ ┌──────────────────┐
│ Module's FCC │ │ Custom RF design? │
│ grant covers │ │ Bare die / own │
│ intentional │ │ antenna? │
│ radiator │ └────────┬─────────┘
└──────┬──────┘ │
│ ▼
│ ┌──────────────────┐
│ │ You need FULL FCC │
│ │ ID Certification │
│ │ (Subpart C + B) │
│ │ $15K–$30K+ │
│ │ 3–6+ months │
│ └──────────────────┘
▼
┌──────────────────┐
│ You still need │
│ SDoC for host │
│ device (Sub. B) │
│ $2K–$5K │
│ 2–4 weeks │
└──────────────────┘The choice should be obvious for most startups. Use a pre-certified module unless you have a compelling technical reason not to (extreme size constraints, unusual frequency requirements, or volume economics that justify the investment at 100K+ units).
The Real Cost of Going Custom
Let’s be explicit about what the custom RF path actually looks like, because the table above compresses a lot of pain into a few cells.
Test lab fees: A full Part 15 Subpart C intentional radiator test suite for a 2.4 GHz BLE device runs $10K–$20K. That’s for one round. If your device fails, and first-pass failure rates on custom RF designs are common enough to plan for, you’re paying for redesign, new board spins, and re-testing. Each cycle adds $5K–$15K and 4–8 weeks.
Lab availability: Good accredited test labs are booked weeks out. You don’t just walk in and get tested Tuesday. Scheduling alone adds lead time, and a failed test puts you back in the queue.
Engineering cost: RF design is a specialty. If you don’t have an experienced RF engineer on your team (most early-stage startups don’t), you’re hiring a consultant at $200–$400/hr. Antenna matching, impedance tuning, harmonic suppression, and layout optimization for emissions compliance are not tasks you hand to a general-purpose EE and hope for the best.
Opportunity cost: This is the silent killer. Every month your certification slips is a month your competitors are shipping, your crowdfunding backers are getting anxious, and your runway is burning. A 4-month delay in FCC testing has ended more than a few hardware startups, not because the product was bad, but because the cash ran out waiting.
Contrast this with the pre-certified module path: you’re testing for unintentional emissions only (Subpart B), which means a simpler test suite, lower fees, and a much lower failure rate if you’ve followed basic EMC design practices.
What You Still Owe with a Pre-Certified Module
Don’t mistake “easier” for “free.” Using a pre-certified FCC ID BLE module reduces your burden significantly, but it doesn’t eliminate it. Here’s what you’re still responsible for.
Follow the module grant conditions exactly. The module’s FCC grant specifies the approved antenna type and gain, ground plane size requirements, and minimum separation distances from the user’s body. If the grant says a 2 dBi PCB antenna with a minimum 30mm × 30mm ground plane, that’s what you use. These conditions are listed in the grant document. Download it from the FCC ID search tool and read it before you finalize your PCB layout. Not after.
Subpart B compliance for your host device. Your PCB, power supply, display, and all the non-radio circuitry still emit unintentional RF energy. You need to demonstrate compliance through a Supplier’s Declaration of Conformity (SDoC), which requires testing at an accredited or recognized lab. Budget $2K–$5K and 2–3 weeks. This is where good EMC design practices during PCB layout (solid ground planes, proper decoupling, controlled trace routing) pay for themselves.
Labeling requirements. The FCC ID of the module must be visible on your product. If the module is internal (it almost always is), you must include it on an exterior label, provide it through an electronic display (e-label), or reference it in the user manual with specific language. You also need the standard Part 15 compliance statement: “This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.”
Do not modify the RF path. If you change the antenna, add shielding that affects the radiation pattern, alter the matching network, or do anything that modifies the RF characteristics beyond what the grant authorizes, you’ve potentially invalidated the module’s certification. At that point, you’re back on the custom path, with all its costs and timelines.
Your Seven-Step Path to BLE Product Compliance
- Choose a pre-certified BLE module early in your design, before you commit to a form factor or PCB layout.
- Download and read the module’s FCC grant from the FCC ID database. Follow its integration conditions exactly.
- Design your PCB with EMC best practices: continuous ground planes, proper decoupling capacitors, short high-speed traces, and separation between noisy and sensitive circuits.
- Engage a test lab for a Subpart B pre-scan before finalizing your layout. A pre-scan costs a fraction of formal testing and catches problems early.
- Run formal Subpart B testing and file your SDoC. Keep the test report on file; you’re required to produce it if the FCC asks.
- Apply correct FCC labeling to your product per the module grant’s requirements.
- Ship.
Smart Decisions at the Prototype Stage Save Months at Production
The certification path for a BLE device is not the mystery the regulatory language makes it seem. “Unlicensed” describes the spectrum, not your product. Every intentional radiator needs FCC authorization, but that authorization doesn’t have to be yours if you build on a pre-certified module.
The founders who get hurt are the ones who either didn’t know certification was required or made RF architecture decisions without considering the regulatory consequences. By choosing a pre-certified module, following its grant conditions, and budgeting for straightforward Subpart B testing, you’re looking at $3K–$8K and a few weeks, not $30K and half a year.
Make the architectural decision now. Your future self, your launch timeline, and your backers will thank you.
Hubble Network connects Bluetooth devices directly to satellites—no gateways, no terrestrial infrastructure. Learn how it works →