Radio Modules vs Chipsets: The Compliance Decision You Make at Design Stage

Choosing a radio module or a chipset is a compliance decision, not just a bill-of-materials one. A pre-approved module carries approvals you can reuse; a chipset carries none. Manufacturers designing connected equipment set their whole certification scope at this point, long before procurement sees a price.  

In this article, radio expert Robert Graham sets out what a module's existing approval does and does not carry into your product, what changes when you design with a chipset, and the questions you should answer before the schematic is finalized.

 

What is the difference between a Radio Module and a Chipset? 

A radio module is a self-contained transceiver subsystem: RF silicon, matching network, shielding, its own power supply regulation, and an integrated or connected antenna, tested and approved in a standalone configuration.

A chipset is a component. It is silicon, usually supplied with a reference design, a recommended matching network and antenna layout guidance. It has no regulatory status of its own. 

The difference in regulatory treatment follows directly from that physical difference:

• A radio module can be characterized on its own and behaves predictably when dropped into a host provided the manufacturers' integration instructions have been followed to the letter, so regulators generally allow its approval to be reused for directly connected compliance tests.
• A chipset cannot be meaningfully tested on its own, because its RF performance is influenced by the board around it. Under47 CFR 15.212, the FCC only grants full modular approval where the RF circuitry is shielded, data or modulation inputs are buffered, the module has its own power supply regulation, antennas are permanently attached or use a unique connector, and the module must be tested standalone.

Those five conditions are, in effect, a description of why a module is portable between hosts and a chipset is not.

 

Radio Module vs Chipset: Three assumptions that cost manufacturers time (and money) 

Before comparing the two routes properly, it is worth addressing the three beliefs that most often derail a program.

• A pre-approved module means no radio testing. It does not. Modular approval reduces the certification burden, not necessarily the test burden. The module was approved standalone, in free space, with its own antenna and no host electronics nearby. Your product is none of those things. In our test experience, radiated measurements routinely shift once a module is installed, and both the FCC (in KDB 996369) and ETSI (in EG 203 367) recommend repeating at least output power and radiated spurious emissions in the host. For more details on radio module integration, you can read our whitepaper.
• A chipset vendor's reference design is effectively pre-approved. It is not. A reference design is electrically sound engineering advice, and following it closely will improve your chances, but regulatory approval attaches to a specific tested product. Your enclosure, ground plane, antenna placement and cable set will differ from the evaluation board in ways that matter at RF.
• The decision between radio module vs chipset can be deferred. In practice, the antenna type, its placement, the keep-out area and the RF ground plane are all fixed at PCB layout. Switching from a module to a chipset after design means a new certification program and, in the US and Canada, a new FCC ID and ISED certification number rather than a permissive change.

 

What Radio Module approvals actually give you

Radio Module compliance in Europe and UK 

A CE-marked module comes with a Declaration of Conformity (DoC) and, if you ask for them, test reports against harmonized standards such as EN 300 328 for 2.4 GHz wideband systems, EN 301 893 for 5 GHz RLAN, and EN 303 687 for 6 GHz RLAN or the relevant parts of the EN 301 489 series for EMC. That evidence is genuinely useful, and much of the conducted radio test data will remain valid. What it does not do is discharge your obligation. You sign your own DoC covering the entire product, so you need host-level EMC, a safety assessment, an RF exposure assessment and enough radio re-verification to show that integration has not degraded performance. For more, read our 10-point CE Marking checklist for pre-approved modules. 

One gap catches integrators  repeatedly in the assessments we run. The RED cybersecurity requirements under Delegated Regulation 2022/30, applicable since 1 August 2025, sit at product level, not module level. A module's DoC will almost never cover Articles 3(3)(d), (e) and (f), because the security behaviours assessed under the EN 18031 series belong to your firmware, your update mechanism and your network interfaces. Buying a certified module transfers none of that work.

 

Radio Module compliance in the US and Canada 

A module with an FCC ID or an ISED certification number lets you use its authorization / certification in your host. This, however, is provided you honour every condition on the FCC Grant of Equipment Authorization / module certificate holder integration instructions and label the host correctly, typically with a statement in the form “Contains FCC ID: XXXXX” / “Contains IC: XXXXX”. Full modular approval travels between hosts; a limited modular approval only travels into the specific host types in which the unmet conditions were shown to be satisfied, which is a distinction worth confirming before you design around a part. 

Two situations remove the benefit almost entirely.

1. If your device is handheld and/or wearable
2. If your device contains more than one transmitter

ISED requires host certification regardless of the modules' existing certification. If you need the freedom to make your own changes later, you will usually want to bring the certification into your own name through an FCC Change in ID or an ISED Multiple Listing, which is administrative rather than technical work but needs planning. For more information on the requirements to use pre-approved radio modules in the US or Canada.

 

What changes when you design with a Chipset vs a Radio Module 

The antenna becomes your responsibility 

In our experience, this is the single largest shift. With a module, if the antenna isn’t integrated onto the module PCB, the integration manual will specify the type and maximum gain of the antenna and even transmission line dimensions. With a chipset, you own the matching network, the trace or chip antenna, the ground plane and the RF power tuning. The characteristics of the antenna contribute directly to both spurious emission margin and RF exposure calculations. Poor design can exceed radio limits and push a device from a calculation-based exposure assessment into full SAR testing at the same time.

 

The full test scope applies to every variant 

A chipset-based design is a full approval in the US and Canada and a full conformity assessment in the EU and UK. Every unique combination of radios needs its own certification, and hardware changes generally require new regression test evidence. Where a radio module route lets you build five product variants on one radio approval, a chipset route can mean five separate compliance tests unless the variants are demonstrably identical at RF. For more on hardware changes and variants, watch our webinar.

 

Firmware becomes a regulated feature 

With a chipset, you control transmit power tables, channel plans, regional country codes and, where applicable, DFS behaviour for 5 GHz. Those become compliance-critical software. Changes that alter reported transmitter characteristics are Class II permissive changes at the FCC and can reach Class III where the device is approved as a software-defined radio; ISED treats firmware changes that degrade reported characteristics or add frequency bands as Class III. Your release process needs to know which firmware changes touch the certification.

 

Environmental extremes need establishing

A radio module's test report states the temperature range over which compliance was demonstrated. A chipset design has no such range until you generate one, and RF performance at temperature and supply-voltage extremes is exactly where marginal designs come apart. Recent standards have made this sharper: ETSI EN 300 220-2 V3.3.1 now ties mandatory temperature test ranges to product use category for short-range devices. For more information on the latest changes to ETSI EN 300 220-2 V3.3.1, read our whitepaper.

 

Cost, schedule and volume: The real trade-offs between Radio Modules vs Chipsets

Radio modules carry a higher unit cost and much lower non-recurring engineering. It shortens schedule, simplifies variant management and gives you a fallback position when a test result surprises you. In exchange, you accept dependence on someone else's product lifecycle. If the module goes end-of-life, or the supplier makes a permissive change you were not expecting, the consequences land in your compliance file.

Chipsets invert that. Unit cost falls, sometimes substantially at volume, but you fund the RF design, the antenna work, the pre-compliance iterations and full certification in every target market. You have control over the quality of your product when the inevitable component changes due to end-of-life, second sourcing or value engineering happen. You also own the outcome completely, with no second-party dependency on a supplier's grant. 

 

Radio Modules vs Chipsets: 7 questions to answer before design is complete 

1. Your full market list, including markets planned for later phases, since retrofitting a region often costs more than designing for it.
2. Whether the module you are considering holds full or limited modular approval, and for which host types.
3. Every condition on the module's Grant of Equipment Authorization and/or integration manual, particularly co-location, separation distance and permitted antennas.
4. Whether the module's RF exposure authorization (fixed, mobile or portable) matches how your product will actually be used.
5. Which party will hold the certification in its own name, and whether a Change in ID or Multiple Listing is needed.
6. How many hardware variants the platform will support, and whether they are genuinely identical at RF.
7. Who owns cybersecurity conformity, given that it will not come from the module.

 

When a hybrid approach works 

The two routes are not mutually exclusive across a portfolio. A common and sensible pattern is to launch on an approved module to reach market quickly and prove demand, then move to a chipset design for the high-volume follow-on once the RF competence and antenna data exist in-house. The intermediate option, a module with a host-mounted antenna, deserves a note of caution: it is popular with cellular designs, but the moment the RF chain extends onto your PCB you have modified the approved configuration, and verification testing of that trace and connector becomes necessary.

 

Conclusion: The decision between Radio Modules vs Chipset, treat it as a compliance decision

Whichever way the decision goes, the useful discipline is to treat it as a compliance decision with a procurement consequence rather than the reverse. The component cost difference is visible on a spreadsheet from day one. The certification cost difference only becomes visible when you count the number of compliance programs, variants and markets, which is precisely why it is so often underestimated.

 

Radio module vs chipset: Frequently asked questions

Is a radio module or a chipset cheaper?

It depends on volume. A radio module has a higher unit cost but lower engineering and certification cost, so it wins at low volume. A chipset has a lower unit cost that pays off at scale, but you fund the RF design, antenna work and full certification in every market.

Do you need to retest a pre-approved radio module after integrating it?

Usually, yes. Modular approval cuts the certification burden, not the test burden. Both FCC KDB 996369 and ETSI EG 203 367 recommend repeating measurements of at least output power and radiated spurious emissions once the module is in your host, because radiated performance varies with real hardware.

What is FCC modular approval?

It is an authorization that lets a self-contained transmitter be reused across host products without re-certifying the radio each time. Under 47 CFR 15.212, the module must be shielded, have buffered inputs, have its own power regulation, use a permanently attached or unique-connector antenna, and be tested standalone.

Can you switch from a radio module to a chipset later in the design?

Not cheaply. The antenna, its placement, the keep-out area and the RF ground plane are all fixed in the PCB layout. Switching after design means a new certification program and, in the US and Canada, a new FCC ID and ISED certification number rather than a permissive change.

Does a certified radio module cover the RED cybersecurity requirements?

No. RED Articles 3.3(d), (e) and (f), assessed through the EN 18031 series and applicable since 1 August 2025, sit at product level. They cover your firmware, update mechanism and network interfaces, so a module's Declaration of Conformity almost never covers them.

 

Footnotes

1. FCC, 47 CFR 15.212, modular transmitter requirements. Electronic Code of Federal Regulations (eCFR).