FCC Module Certification: Full vs Limited Modular Approval Under 15.212

TL;DR -- Modular certification under 47 CFR 15.212 lets an RF transmitter module get its own FCC ID, so every host product that integrates it can skip intentional radiator testing. Full modular approval requires meeting all 8 conditions in Section 15.212(a). If you can't meet them all, limited modular approval under 15.212(b) is available but comes with grant restrictions that bind every host integrator. Most hardware teams should use an already-certified module rather than certifying their own -- unless they're a module vendor or have unusual RF requirements.

What modular certification actually is

Section 15.212 of the FCC rules creates a mechanism for certifying RF transmitter modules independently from the products they end up in. The module gets its own FCC ID. Any host product that incorporates it can reference that FCC ID instead of going through full intentional radiator testing.

Every pre-certified WiFi, Bluetooth, Zigbee, LoRa, and Thread module on the market exists because of this rule. When Espressif certifies the ESP32-WROOM-32E or Nordic certifies the nRF52840, they're going through the 15.212 process. Thousands of downstream products then ship using that single grant.

Without modular certification, every product with a radio would need its own intentional radiator testing -- $8,000 to $20,000+ per product. With it, host manufacturers pay $2,500 to $5,500 for host-level EMC testing and move on.

The 8 requirements for full modular approval

Under 15.212(a), a module qualifies for full (unrestricted) modular approval when it satisfies all eight conditions. Meeting all eight means the module can be installed in any host without additional RF testing on the host side (beyond standard Part 15B unintentional emissions).

The point of all eight: the module must behave the same way regardless of what host it ends up in. If RF performance depends on the host's shielding, power supply, or antenna, it's not really a standalone module, and granting unrestricted use would be a compliance fiction.

Full vs limited vs split modular approval

Not every module can meet all eight requirements. Section 15.212 provides three tiers:

flowchart TD
    A["RF Module"] --> B{"Meets all 8\nrequirements?"}
    B -->|Yes| C["Full Modular Approval\n15.212(a)\nNo host restrictions"]
    B -->|No| D{"Single PCB\nor split?"}
    D -->|"Single PCB"| E["Limited Modular Approval\n15.212(b)\nGrant restrictions apply"]
    D -->|"Separate boards\nconnected by cable"| F["Split Modular Approval\nKDB 996369 D05\nPAG always required"]
    style C fill:#1e3a5f,color:#fff
    style E fill:#1e3a5f,color:#fff
    style F fill:#1e3a5f,color:#fff

Full modular approval -- 15.212(a)

The module meets all eight conditions and can be installed in any host product. The host manufacturer needs only Part 15B unintentional emissions testing and an RF exposure evaluation (if the antenna placement differs from the module's original grant). This is the path most commercial module vendors target because it maximizes the addressable market for their module.

Limited modular approval -- 15.212(b)

When a module fails one or more of the eight requirements, it can still be certified -- but the grant comes with restrictions. These restrictions are listed in the grant notes and are legally binding on every host integrator.

Common reasons a module gets limited approval:

• Standard antenna connector (SMA, U.FL, MMCX) instead of a proprietary one or permanently attached antenna -- violates requirement #4
• No RF shielding on the module itself -- violates requirement #1
• Relies on host power regulation instead of on-board regulation -- violates requirement #3

The grant notes will specify conditions like: must use a specific antenna type, maximum cable length, minimum ground plane size, or specific host enclosure materials. Five specific limited conditions trigger a requirement for Pre-Approval Guidance (PAG) via KDB 388624 (the "MODLIM" item), where the applicant must get TCB concurrence before filing.

The practical impact for host integrators: if you're using a module with limited modular approval, read the grant notes carefully. Violating any listed restriction means the module's grant doesn't cover your configuration, and you may need additional RF testing or a separate certification.

Split modular approval -- KDB 996369 D05

A split module has its radio components physically separated across two or more boards -- for example, the baseband processor on one board and the RF front-end on another, connected by a coaxial cable. This is common in automotive and industrial applications where space constraints make a single-board module impractical.

Split modules always require PAG. The certification process is more involved because the cable between boards introduces variables (length, shielding, connector type) that affect RF performance. Expect longer review timelines and more scrutiny from the TCB.

Certify your own module or use a pre-certified one?

flowchart TD
    A["Your Product\nNeeds a Radio"] --> B{"Are you a\nmodule vendor?"}
    B -->|Yes| C["Certify your module\nunder 15.212"]
    B -->|No| D{"Does an existing\npre-certified module\nmeet your requirements?"}
    D -->|Yes| E["Use the pre-certified module\nHost-level testing only\n$2,500 – $5,500"]
    D -->|No| F{"Volume above\n50K–100K units?"}
    F -->|Yes| G["Consider chip-down design\nFull certification\n$8,000 – $20,000+"]
    F -->|No| H["Find a different module\nor accept limited approval\nrestrictions"]
    style C fill:#1e3a5f,color:#fff
    style E fill:#1e3a5f,color:#fff
    style G fill:#1e3a5f,color:#fff
    style H fill:#1e3a5f,color:#fff

Use a pre-certified module when...

• You're building an end product, not a module platform
• An existing module covers your frequency bands and power levels
• Your production volume is under 50,000 to 100,000 units
• You want to reach market in 3 to 6 weeks instead of 6 to 16 weeks
• Your team doesn't have deep RF design expertise

For most IoT and consumer electronics products, this is the right call. The per-unit BOM premium of a module ($2 to $5 over chip-down) is more than offset by certification savings and reduced engineering risk at typical startup volumes.

For details on what host-level testing you still need when using a pre-certified module, see our Pre-Certified Modules and Host Testing guide.

Certify your own module when...

• You are a module vendor selling to other manufacturers
• You have a proprietary RF design that no existing module covers (unusual frequency, custom protocol, specific power profile)
• Your volume justifies the $8,000 to $20,000+ certification cost amortized across customers or units
• You need full control over the grant conditions

If you're certifying your own module, target full modular approval (all 8 requirements) whenever possible. Limited approval shrinks your addressable market because it forces restrictions on every host integrator.

Chip-down design (no module at all)

If you're soldering an RF transceiver IC directly to your product's main PCB -- an ESP32-S3 chip instead of the ESP32-S3-WROOM module, for instance -- you are not using a module. There is no modular certification to reference. You need full intentional radiator certification for your product.

This path makes financial sense above 50,000 to 100,000 units, where the per-unit BOM savings ($2 to $5) start to exceed the upfront certification cost. Below that, modules almost always win. Our FCC certification cost breakdown covers the full math.

The certification process for a module

If you've decided to certify your own module, here's what the process looks like end to end:

1. Design to meet the 8 requirements. Build in RF shielding, buffered inputs, on-board power regulation, and either a permanently attached antenna or proprietary connector. Cutting corners here pushes you into limited approval territory.

2. Pre-compliance testing. Validate emissions, spurious levels, and RF exposure before booking formal lab time. This step saves $5,000 to $30,000 in re-test costs. See our EMC pre-compliance testing guide.

3. Formal testing at an accredited lab. The lab tests the module as a stand-alone unit (requirement #5) across all applicable rule parts. For a 2.4 GHz WiFi/BT module, this means Part 15C Section 15.247 testing plus spurious emissions, band edge compliance, and RF exposure evaluation.

4. Documentation package. Internal and external photos of the module, block diagram, operational description, antenna specifications, user integration guide, and label artwork. The integration guide matters more for modules than for most other filings -- it tells host manufacturers how to install the module without violating grant conditions.

5. TCB review and filing. Submit the complete package to a TCB. For full modular approval, the review goes smoothly if your test data is clean and documentation is complete. For limited approval, expect questions about the specific restrictions and possibly a PAG requirement.

6. Grant issuance. The TCB issues an FCC grant with your module's FCC ID. For limited approval, the grant notes will list all restrictions.

Timelines assume no major failures. A first-pass test failure adds 4 to 12 weeks for diagnosis, redesign, and re-test -- which is why skipping pre-compliance is a false economy.

Common pitfalls in modular certification

Assuming "limited" means "lesser." Limited modular approval is not a lower standard of compliance. The module still passes all the same RF tests. "Limited" means the module's compliance depends on specific host conditions, and those conditions become legally binding restrictions on every downstream integrator. If you're a module vendor, limited approval directly reduces how many customers can use your product without additional testing.

Using a standard antenna connector and expecting full approval. Requirement #4 is one of the most frequently missed. If your module uses U.FL or SMA, you won't get full modular approval unless you use a proprietary adapter or coupler. Many module vendors design custom connector interfaces specifically to satisfy this requirement.

Neglecting the integration guide. The FCC expects modules -- especially those with limited approval -- to ship with clear integration instructions. Vague guidance like "follow good RF practices" invites TCB questions and delays. Specify exact antenna types, cable lengths, ground plane requirements, and installation orientations.

Forgetting RF exposure at the module level. Requirement #8 means the module itself must have an RF exposure evaluation, not just the eventual host product. For portable devices (within 20 cm of the body), this means SAR testing or a compliant exclusion analysis per KDB 447498. Getting this wrong at the module level creates problems for every host product downstream.

Ignoring the "Contains FCC ID" labeling chain. When the module's FCC ID label isn't visible on the assembled host product, the host must display "Contains FCC ID: XXXXX-YYYYYY" on its exterior label. Module vendors should make this clear in their integration documentation. See our FCC label requirements guide for the full labeling rules.

Not tracking grant condition changes. If the FCC updates the KDB guidance for modular certification (and it does -- KDB 996369 has been revised multiple times), existing grants may need to be reviewed. The October 2025 Secure Equipment Act restrictions, for example, now prohibit modular transmitter authorization for covered equipment from companies like Huawei and ZTE.

How modular certification relates to host testing

Module certification covers the intentional radiator side: proving the radio meets FCC limits. Host testing covers everything else: proving the finished product doesn't create new compliance problems.

Our Pre-Certified Modules and Host Testing guide covers the host side in detail: what Part 15B tests you need, when RF exposure re-evaluation is required, and when a pre-certified module doesn't actually save you from full certification.

The short version: even with a fully certified module, the host always needs Part 15B unintentional emissions testing. And if you change the antenna configuration, operate the module differently than its grant allows, or add additional transmitters, you may need further RF testing on the integrated product.

Key regulatory references

• 47 CFR 15.212 -- the regulation itself, defining modular transmitter requirements
• KDB 996369 D01 -- general modular certification guidance
• KDB 996369 D04 -- host device integration requirements
• KDB 996369 D05 -- split module guidance
• KDB 388624 -- Pre-Approval Guidance (PAG) for limited modular conditions
• KDB 447498 -- RF exposure evaluation procedures

Related guides

• Pre-Certified Modules and Host Testing -- what host-level testing you still need with a pre-certified module
• FCC Certification Cost Breakdown -- full cost comparison by device type and certification path
• FCC Part 15 Guide -- how Part 15 classifies your device and determines your authorization path
• FCC Certification Hub -- the complete FCC certification process from start to finish
• FCC Testing Timeline -- phase-by-phase timeline from pre-compliance through grant issuance