Key takeaways
- A pre-certified BLE module carries its FCC/IC modular approval onto your product — the single biggest cost lever.
- A custom RF design must pass full intentional-radiator testing in every market you ship to.
- Budget per region: FCC (US), ISED/IC (Canada), CE/RED (EU) — each has its own fees and rules.
- Even with a module, you still pass unintentional-radiator emissions tests on the finished product.
- Antenna choice and label/host-marking rules decide whether modular approval actually applies.
The one decision that drives the bill
BLE certification cost is dominated by a single architectural choice: pre-certified module versus custom radio. A module that already holds FCC and ISED/IC grants lets you inherit that approval (modular or limited-modular), provided you respect its integration conditions — approved antenna, trace layout, and host labeling. A custom RF front end forfeits that inheritance: you become the grantee and must fund full intentional-radiator testing yourself.
For most North-America-primary products shipping globally, the module path is the pragmatic default. Reserve custom RF for cases where size, cost-at-scale, or performance genuinely demand it.
Cost by path and region
| Item | Pre-certified module | Custom RF design |
|---|---|---|
| FCC (US) intentional radiator | Inherited (≈US$0 radio test) | Full test: ~US$15k–40k |
| ISED/IC (Canada) intentional radiator | Inherited | Often shares FCC test data; filing + delta |
| CE / RED (EU) intentional radiator | Largely inherited (verify EU notified-body status) | Full RED radio + EMC: ~€10k–30k |
| Unintentional radiator (finished product) | Required either way: ~US$3k–10k | Required: ~US$3k–10k |
| Typical all-in (US + Canada) | ~US$5k–15k | ~US$25k–75k+ |
| Lab time | Days to a few weeks | Weeks to months |
Figures are planning-grade ranges; actual quotes depend on your test lab, product complexity and number of radios.
What you still pay even with a module
Modular approval covers the radio, not the whole product. You still owe:
- Unintentional-radiator testing (FCC Part 15B / ICES-003) on the finished device — clocks and digital circuitry emit regardless of the radio.
- Integration compliance: using the module’s approved antenna and layout, and applying the correct host label (the “Contains FCC ID / IC” marking).
- Documentation: a clean test report and declaration the EMS and regulators can audit.
Skip these and a “pre-certified” radio still leaves you non-compliant. A common surprise: a switching power supply or a fast digital bus pushes the finished product over the Part 15B limit even though the radio passed cleanly. Plan a pre-scan at the design stage so you find that margin in the lab on your schedule, not in a failed compliance run on the certifier’s.
The three markets, briefly
FCC (United States)
Intentional radiators fall under Part 15.247 / 15.249 for BLE; modular grants are inheritable when integration rules are met. This is usually your reference test from which other regions reuse data.
ISED / IC (Canada)
Canada’s RSS standards align closely with FCC, so the same module and much of the same test data carry over with a separate filing and IC number. Doing US and Canada together is the cheapest combination.
CE / RED (European Union)
The EU’s Radio Equipment Directive adds its own radio, EMC and safety requirements. Module inheritance helps but verify the module holds valid EU coverage before assuming it.
Plan certification into the schedule, not after it
Certification is not a final formality — antenna placement, module choice and label area are design decisions made during hardware development. Pick a module with broad regional grants early, design to its integration conditions, and you convert a five-figure risk into a predictable, scheduled line item. For the design-side groundwork, pair this with your DFM checklist so RF clearances and label area are reserved before layout closes.
Where Fundamentum fits
Certification gets the product to market; Fundamentum, our Canadian IoT platform, keeps the fleet governed afterward — device identity and fleet provisioning at first power-on, then governed OTA and an audit trail once units are in the field, inside a SOC 2 Type II perimeter. It interfaces with AWS, Azure or Google Cloud only if your architecture requires it. See the platform →
Frequently asked questions
Does a pre-certified module eliminate certification cost entirely?
No — it eliminates the expensive part: the intentional-radiator (radio) testing. You still pay for unintentional-radiator emissions testing on the finished product (FCC Part 15B / ICES-003) and must follow the module’s integration and labeling rules. The savings are large but not total.
Can I reuse FCC test data for Canada?
Largely, yes. Canada’s ISED/IC RSS standards align closely with the FCC, so the same module and much of the same test data carry over with a separate filing and IC number. Certifying the US and Canada together is the most cost-efficient combination.
How much does custom RF certification add?
A custom radio means full intentional-radiator testing in each market — roughly US$15k–40k for FCC alone, plus CE/RED for the EU, often pushing an all-in US+Canada figure to US$25k–75k or more. You also become the grantee, taking on the regulatory responsibility a module would have carried.
When is a custom RF design worth it despite the cost?
When module size, performance, or per-unit cost at high volume genuinely require it. For most North-America-primary products shipping globally, a pre-certified module is the pragmatic default; reserve custom RF for cases where the constraints leave no alternative.
When should I plan certification in the project?
From the start. Antenna placement, module choice and host-label area are design decisions made during layout. Pick a module with broad regional grants early and design to its integration conditions, and certification becomes a predictable scheduled line item instead of a late five-figure risk.
Related reading
Talk to an IoT engineer — free
Book a FREE 30-minute consultation with our team. No slides, no obligation — a working session on your connectivity, platform or compliance questions.
