The question usually arrives in the middle of a sourcing decision. Your module vendor offers two parts: one that already carries an FCC ID, and a cheaper uncertified alternative. Or two quotations for the same product come back looking nothing alike - one is mostly radio testing, the other is a much longer list - and nobody in the meeting can explain the difference. Behind both sits one of the most common misunderstandings in electronics compliance: what a pre-certified module actually gives you.
The honest answer is that the module route is usually cheaper and faster, but only when three specific conditions hold. When they do not, the pre-certified module saves nothing, because the expensive part of the test programme was never the radio in the first place. This article sets out what a module approval covers, what it never covers, and how to work out which combination costs less for your product.
What a module approval actually is
In the FCC system, a radio module can be certified on its own as a single modular transmitter. That status is conditional on the module being a genuinely self-contained part: its RF circuitry is shielded, its data and control inputs are buffered, its power regulation sits on the module itself, its antenna follows the antenna rules, and it was tested installed in a host device. The module receives its own FCC ID. When you integrate it into a product, the product references it on the label - typically a "Contains FCC ID" statement, or an electronic label where the product has a display and the labelling rules permit it.
What that grant covers is the radio as tested: the transmitter's conducted and radiated emissions, output power, occupied bandwidth and unwanted emissions, for the antenna type and gain and the operating modes it was certified with. That is the entire scope. Everything else in your product sits outside the grant, and that is where most of the confusion - and most of the cost surprises - live.
| Item | Covered by the module grant? |
|---|---|
| Radio emissions, output power and unwanted emissions - as tested with the certified antenna and modes | Yes, as tested |
| A different antenna type, or a higher-gain antenna | No - permissive change filing or new certification |
| Unintentional emissions from the host circuitry (converters, displays, clocks, cables) | No - required regardless of the module |
| Immunity and ESD performance | No |
| Safety of the finished product | No |
| RF exposure - the separation distance evaluated in the grant | Conditionally - your enclosure must maintain it |
| DoC, technical documentation and the product label | Never - always the finished product's responsibility |
Three rows in that table cause nearly all of the trouble in real projects, so they are worth a closer look.
The three conditions that make the module route cheaper
1. The grant conditions match your integration
The most fragile assumption is the antenna. A module grant covers the antenna it was certified with. Swapping in the same antenna type with equal or lower gain is generally acceptable. Moving to a different antenna type, or anything with more gain, generally requires a Class II permissive change filing - with a new FCC ID where the antenna type changes - or certification of the new configuration outright. Some modules are listed with antenna conditions that forbid substitution altogether. The grant listing and the module's installation manual state all of this explicitly; most integrators never read either until a problem appears.
The same applies to radio modes. A module certified for 2.4 GHz Wi-Fi does not automatically bring Bluetooth or 5 GHz modes under its approval if those modes were not part of the tested configuration. Your product is what goes on the market, and every transmitter mode inside it has to be accounted for.
2. It is a single modular approval, not a limited one
FCC rules distinguish a single modular approval - valid in any compliant host - from a limited modular approval, which is granted only for specific host configurations defined by the module manufacturer, usually its own reference design. Both get an FCC ID, and both look identical in a datasheet. If your module turns out to be limited and your host is not one of the listed configurations, the approval work you assumed you were buying does not transfer, and the shortfall appears as additional testing on your side. Ask which type of approval the module holds before you compare module prices.
3. The work that remains is small
Even with a perfect module grant, the finished product still needs its own compliance work: unintentional-radiator EMC testing of the host - in the United States, Part 15 Subpart B via SDoC, which is not optional and which the module does nothing for - plus immunity and safety where the destination market requires them, and the paperwork: declaration, technical documentation, labels. For a simple host that remaining list is short. For a product with switching power supplies, a display, a motor or long cables, that remaining list is where most of the testing budget goes, and no module choice changes it. If you are unsure where your product sits in the FCC framework at all, start with whether your product needs FCC certification and which route applies.
Where the money actually goes
Put the two routes side by side and the comparison becomes clearer. The module route trades a recurring per-unit premium for skipping the radio transmitter testing. The finished-product route pays for that testing once and uses the cheaper component forever.
| Pre-certified module route | Certify the finished product as the transmitter | |
|---|---|---|
| Component cost | Premium per unit, for the life of the product | None - use the cheaper part |
| Radio transmitter testing | Skipped, if the grant conditions match | Required - the product gets its own FCC ID |
| Host EMC (unintentional emissions) | Required | Required |
| Immunity and safety | Required | Required |
| Paperwork (DoC, technical file, labels) | Required, referencing the module grant | Required, in your own name |
| Main risk | Coverage gaps discovered late | Higher upfront test cost |
Notice how many rows are identical. That is the point: the two routes differ in exactly one line - who pays for the radio testing - and in the risk profile of that difference. Everything else is common to both, which is why the two quotations you are holding should be compared line by line on scope, not on total. What belongs in a quotation, and which extra items appear when scope is vague, is covered in what a testing quotation should actually include.
Four situations we see over and over
The antenna swap for better range. A team integrates a pre-certified module with its PCB antenna, then a later hardware revision replaces it with an external whip antenna to improve range. The module's FCC ID no longer covers the configuration - the antenna type changed and the gain went up. The fix is a permissive change filing or certification of the new configuration, and it lands late, weeks before a shipment date, because nobody flagged the antenna change as a compliance event when it was made.
The "certified" module that was limited. A customer selects a module on price and integration convenience, builds a host that differs from the vendor's reference design, and only at the test booking does the grant's fine print surface: the approval was limited to the vendor's own host configurations. The testing the customer thought they had avoided is back on their programme, plus the schedule slip.
The module covered one mode. A product carries a module with a 2.4 GHz Wi-Fi grant, but the firmware also runs Bluetooth and a 5 GHz mode. The pre-certification covered a fraction of the radio configuration; the remaining modes needed testing anyway. The module route was still viable, but the savings the team had counted on mostly evaporated, because the quotation assumed one mode and the product had three.
The host was the expensive part all along. A compact device with a switching power supply and a small display fails its radiated emissions test in the 30-300 MHz range - noise from the converter, not from the radio. The module grant is irrelevant here; this failure would have happened with any module choice. What matters is that the budget was allocated as if the radio were the whole programme, so the EMC work on the host had been squeezed to fit.
So is the module route cheaper?
For most products the real decision is not "module versus finished product" - it is "module approval plus host testing" versus "full product certification as one unit". The module grant almost never eliminates testing; it removes the radio transmitter testing from your programme and leaves the rest. Whether that trade is worth it comes down to three checks:
- Read the grant conditions before quoting. FCC ID, approval type (single or limited), certified antenna and gain, and the full list of certified modes. Ten minutes of reading prevents the most expensive class of surprises.
- Count what remains. Host EMC, immunity, safety, RF exposure separation, paperwork. For a simple host - say a dongle that is essentially module, antenna and battery - the remaining list is short and the module route usually wins. The finished product is close to being the transmitter anyway.
- Multiply the module premium by expected volume. The module route converts a one-off test cost into a per-unit cost for the life of the product. At low volumes the trade usually favours the module; at high volumes the one-off certification often pays for itself quickly.
One more warning: copying a module's reference design onto your own PCB does not inherit anything. The modular approval attaches to the self-contained part, not to the circuit topology. If the radio circuitry moves onto your board, you are certifying your design from scratch.
How we scope module versus finished product work
At SZC we start this comparison from the module's FCC ID and its grant conditions, the intended antenna and its gain, and the full list of radio modes in the product - not from a one-line product description. We check whether the grant is single or limited, whether the antenna and modes match the tested configuration, and then price what remains: host EMC, immunity, safety and the documentation set. Both routes are quoted side by side, with the coverage gaps in the module route stated explicitly rather than discovered during testing.
The EMC, radio and safety testing services cover the host and the radio under one scope, so the module verification and the host testing are scheduled together instead of surfacing sequentially. For wireless products specifically, the scope and typical test programmes are described on the wireless device certification page. Where a client arrives with two quotations from different suppliers, we first reconcile the scopes line by line, because in our experience most "price differences" are actually scope differences wearing a cheaper number.
If you are holding two quotations that do not reconcile, or a vendor is telling you a module "is already certified", send the module's FCC ID, the intended antenna and its gain, the full list of radio modes, and a short description of the host product. We will check the grant conditions, tell you exactly what carries over and what does not, and price the remaining scope - which sometimes means telling you the module route saves less than the datasheet suggests.