FCC modules in a hardware prototype: do I need full certification?
You may not need a new FCC certification for the radio in your hardware prototype if you use a pre-certified module within its grant conditions. You still need to follow the integration instructions, check finished-product emissions, handle any required authorization for digital circuitry, and label the product.
Not legal or regulatory advice. FCC rules depend on your exact device. Confirm your plan with an FCC-recognized test lab or a Telecommunication Certification Body (TCB) before you sell anything.
Is my device even regulated by the FCC?
The FCC's RF device page starts broad: "Almost all electronic-electrical products (devices) are capable of emitting radio frequency energy." Most, but not all, of those products must be tested to show they comply. As a general rule, a product that by design contains circuitry operating in the radio frequency spectrum has to go through an equipment authorization procedure, and an RF device "must be approved using the appropriate equipment authorization procedure before it can be marketed, imported, or used in the United States."
The same page sorts devices into categories. Three matter for most small hardware projects:
- Incidental radiators. Devices not designed to intentionally use or emit RF energy, such as AC and DC motors, mechanical light switches and basic power tools without digital logic. These need no equipment authorization, but if one causes harmful interference, the user must stop operating it and fix the problem.
- Unintentional radiators (Part 15, mostly Subpart B). Anything that uses digital logic or RF signals internally but is not meant to emit RF energy wirelessly. The FCC notes that most electronic products today fall here. Some digital-only products may be exempt under Section 15.103.
- Intentional radiators. Devices that deliberately generate and emit RF energy, such as Wi-Fi and Bluetooth radios.
A product with a microcontroller and a radio is both an unintentional and an intentional radiator.
SDoC or Certification: which procedure applies?
The FCC has two approval procedures: Supplier's Declaration of Conformity (SDoC) and Certification. Which one you need is set by the rule part that applies to each function of your device, and a single product can need both.
- SDoC still requires testing, but the lab doesn't have to be FCC-recognized and accredited. The responsible party keeps the compliance records.
- Certification requires testing at an FCC-recognized accredited lab. The responsible party gets an FCC Registration Number (FRN) and a Grantee Code, then files with a TCB, which reviews the application and issues the grant.
The FCC also warns that design changes to an approved product may need further approval (see KDB 178919 and the permissive change rules in Section 2.1043).
What a pre-certified module actually covers
A pre-certified (modular) transmitter is a radio that its maker has already taken through FCC Certification. The FCC's guidance for the people who build products around those modules is KDB Publication 996369 D04, Module Integration Guide v02 (October 2020). Its introduction says leveraging a certified module "has the advantage of reducing subsequent FCC filing requirements," but that host product manufacturers remain responsible for:
- following the module's integration instructions;
- performing a limited set of transmitter verification tests on the finished product;
- all other authorization and testing the module grant does not cover, such as the Part 15 Subpart B rules for your digital circuitry.
The guide's general guidance strongly recommends that host makers address six items, summarised here:
- Account for every applicable FCC requirement, digital circuitry and transmitters alike, and document how the product complies.
- Address every item in the module's integration instructions, including the conditions of a limited module grant.
- Confirm the RF exposure instructions are followed (more on this below).
- Obtain the equipment authorization for the host's unintentional radiator functions (Part 15 Subpart B), plus anything needed for transmitters that are not certified modules.
- Test the finished product with its transmitter(s) running. The guide says this can be a spot check of emissions with all transmitters operating together; a formal filing of the results is not required.
- Label the product correctly (KDB Publication 784748).
The guide is explicit on this point: host manufacturers "should not assume that because the modular transmitter is certified that they do not have any responsibility for final product compliance."
Modular approval vs limited modular approval
Section 15.212 sets out what a module needs for modular approval, including its own shielding, buffered data inputs, its own power supply regulation, compliant antenna arrangements and its own FCC ID label. The same rule also allows a limited modular approval for modules that don't meet every requirement, or whose RF exposure compliance was only shown for particular product configurations. In that case the module's grantee has to state how it will keep control of the end products the module goes into. If the module you're considering is a limited module, its integration instructions carry even more weight, and KDB 996369 D04 asks host makers to address the conditions of a limited module grant explicitly.
Is a "fully certified MCU module" actually fully certified?
Words such as "pre-certified", "fully certified" or "fully certified MCU module" are datasheet wording, not terms defined in Section 15.212. Whatever the label says, the thing to check is the grant behind the module's FCC ID: FCC grants are public and searchable by FCC ID, and the integration guide notes that module test reports "are publicly available on the FCC website." An FCC grant is a US equipment authorization, so if you also plan to sell elsewhere, check the module's approvals for each of those markets separately. We walk through FCC grant review.
Which FCC KDB publications matter for modules?
The FCC publishes much of its guidance as numbered KDB publications. The ones this guide and our related FCC guides draw on are:
- KDB 996369, the guidance for modular transmitters. Its publication page (dated 11/15/2024) lists attachments D01 to D05; D04 is the Module Integration Guide for host product makers.
- KDB 784748, the FCC's labeling guidance, which the integration guide points to for labeling the finished product.
- KDB 178919, which the FCC points to, along with the permissive change rules in Section 2.1043, when the design of an approved product changes.
- KDB 447498, which the integration guide points to for RF exposure when more than one transmitter operates at the same time.
- KDB 726920, on confidentiality of the exhibits filed with a grant, which matters when you look for a module's documents.
Treat this list as a reading map, not a compliance checklist: a lab or TCB will tell you which guidance applies to your product.
Radio module integration on your own board
The radio module integration work mostly lands on your PCB and enclosure. Follow the module's integration instructions for antenna placement and layout, keep its antenna and distance conditions in view, and plan the finished-product check that KDB 996369 D04 describes: a spot check of emissions with all transmitters operating together, for which the guide says a formal filing of the results is not required. Add the module's layout rules to the PCB review you run before ordering boards, next to footprint and design rule checks.
Why antenna placement and distance matter
A module's grant reflects how it was tested. The integration guide gives the example of a module whose instructions require at least 20 cm between the antenna and nearby people: the host maker must confirm the product's real use conditions meet that distance. Antenna gain is another limit: for a module certified on conducted output power, the guide says a gain change is possible through a Class II permissive change with the module grantee, or by filing a change in FCC ID. For a module certified on radiated power or field strength, a higher-gain antenna may not be possible without lowering the transmitter's output power.
If your design can't stay inside those conditions, you are choosing between the module's grant and more certification work of your own. We compare modular approval vs full certification in a separate guide.
This is also why radio problems tend to surface during the works-like prototype stage, when the radio, power, enclosure and firmware first run together.
What to write down before you talk to a lab
You don't need to solve compliance on day one, but collect the facts a lab will ask for, and log anything unconfirmed as unverified risks in your feasibility notes:
- Target markets (the FCC covers the US only).
- Every function: digital logic, each radio type, chargers or power supplies.
- The exact module part number and its FCC ID, plus a link to its integration instructions. If you haven't picked one yet, see pre-certified module selection and look its grant up yourself.
- Antenna type and position, and how close the device sits to people in normal use.
- Enclosure material, especially metal near the antenna.
- Which design details are frozen and which may still change.
The same list belongs in the manufacturer pre-contact checklist, because factories will ask what compliance work is already done.
Synthetic example, made up for illustration: a desk sensor with a pre-certified BLE module would, under the guidance above, still involve Subpart B authorization for its digital circuitry, a check of the module's antenna and distance conditions, verification testing of the finished unit, and labeling. Only a lab can confirm what applies to a real design.
FAQ
Do all electronics need FCC certification?
Not all need Certification, but almost all are in scope. Devices without digital logic may be incidental radiators that need no authorization. Digital circuitry is commonly authorized under SDoC (the FCC's module guide uses this as an example), and products with transmitters such as Wi-Fi or Bluetooth radios typically involve Certification. Some digital-only devices may be exempt under Section 15.103.
Does a pre-certified Wi-Fi or Bluetooth module mean I don't need FCC approval?
No. According to KDB 996369 D04 v02, the module reduces filing requirements for the radio, but you still handle your product's digital circuitry authorization, follow the integration instructions, verify emissions of the finished product, and label it.
What does "pre-certified" mean?
It means the module itself already holds an FCC grant of Certification, obtained by its manufacturer, with conditions described in its integration instructions.
What if my design can't meet the module's antenna or distance conditions?
The FCC guide lists options: a Class II permissive change by the module grantee, a Change in FCC ID followed by a permissive change, or your own new FCC ID.
Does ThingWeave certify my device?
No. ThingWeave doesn't certify designs or give regulatory advice. It helps you keep requirements, sources and open questions in one project so you can brief a test lab clearly.
Start your first project
ThingWeave is a pilot workspace where you and your AI agent keep requirements, sources, decisions and open questions for a hardware idea in one place. Record your module choice, its FCC ID and your antenna questions now, and they'll be ready when you talk to a lab.
Sources
- FCC, Equipment Authorization – RF Device: https://www.fcc.gov/oet/ea/rfdevice
- FCC, Equipment Authorization (approval procedures and steps): https://www.fcc.gov/engineering-technology/laboratory-division/general/equipment-authorization
- FCC KDB Publication 996369 (publication page, dated 11/15/2024): https://apps.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm?id=44637&switch=P
- 47 CFR § 15.212, Modular transmitters (eCFR): https://www.ecfr.gov/current/title-47/chapter-I/subchapter-A/part-15/subpart-C/subject-group-ECFR2f2e5828339709e/section-15.212
- FCC, 996369 D04 Module Integration Guide v02 (October 13, 2020): https://apps.fcc.gov/kdb/GetAttachment.html?desc=996369+D04+Module+Integration+Guide+V02&id=bNCiEdkFEKnHsZF9GHCNdg%3D%3D&tracking_number=44637
Sources 1–3 and 5 accessed October 19, 2026; source 4 accessed October 21, 2026.