Can a CE-marked Wi-Fi product be sold in the United States on its EU test reports?

No. The product needs its own FCC authorization, usually Certification by a TCB (15.201(b)), against US limits: in the 2.4 GHz band, 1 W peak conducted output with antennas up to 6 dBi (15.247(b)(3), (b)(4)), where EN 300 328 caps wideband data equipment at 20 dBm e.i.r.p. The US-EU mutual recognition agreement lets an EU-designated lab or TCB apply the FCC rules; it does not make EU results valid in the US.

Does a firmware update need a new FCC filing?

It depends on what it changes. Software changes that do not affect RF emissions need no filing (2.1043(a)). Changes to maximum power ratings, the basic modulator or the frequency determining circuitry need a new grant, except Class III changes, which only exist for software defined radios and need FCC acknowledgement before the software is loaded (2.1043(b)(3)).

Where do the Part 15 statements go?

The 15.19(a)(3) two-condition statement goes on the device, in a conspicuous location, for certified and SDoC devices alike. The 15.21 warning on unapproved changes and the 15.105 Class A or Class B text go in the user manual. Only a device too small for four-point text and without a display moves the 15.19 statement to the manual plus the packaging or a removable label (15.19(a)(5)).

FCC pitfalls: 12 errors and the rules behind them

Hugues Orgitello updated 7 Oct 2026 15 min read

Twelve errors that recur in FCC projects, each tied to the section of 47 CFR that it breaks, read from the eCFR on October 7, 2026. They fall into three families: scoping errors (which procedure, which limits, which US party), reuse and modification errors (modules, antennas, firmware, several radios in one product), and marking and marketing errors (FCC ID, statements, e-label, online sales). For each one, the page gives the rule and what to do about it, and leaves out what no text fixes: prices, review times and failure rates.

The twelve pitfalls at a glance

#	Pitfall	Rule that settles it	What the rule says
1	Self-declaring a radio product	15.201(b), 15.101, 15.3(k)	Intentional radiators need Certification; the host digital device has its own authorization
2	Reusing the CE file	15.247(b), 2.948(f), 2.960(d)	Different limits; the MRA designates EU labs and TCBs to apply FCC rules, not EU results
3	No US agent for service of process	2.911(d)(7), 2.909(b)	Every Certification applicant designates one; SDoC needs a US responsible party
4	Treating 6 GHz as one band	15.407(a), (d)	Several device classes, each with its own bands, limits, indoor rule and statement
5	Using a module outside its grant	15.212, 15.3(k), 2.1043(b)(4)	Conditions of the grant, host label, host authorization, RF exposure in the final configuration
6	Swapping the antenna	15.203, 15.204(c)(4)	Same type and equal or lower gain only; otherwise 2.1043
7	Changing radio parameters in firmware	2.1043(a), (b)(3)	Power, modulator and frequency changes need a new grant; Class III only for software defined radios
8	Testing radios one at a time	2.947(f), 1.1307(b)(3)(ii)	Sources designed to emit together are measured together; RF exposure sums them
9	Printing an FCC ID before the grant, or in the wrong form	2.925(a)(1), 2.926(d), (e)	No FCC ID on marketed equipment before a grant; fixed format
10	Putting the 15.19 statement in the manual	15.19(a)(3), 15.21, 15.105	15.19 on the device; 15.21 and 15.105 in the manual
11	An e-label that does not meet 2.935	2.935	Integrated display, three steps from the settings menu, identification on device or packaging
12	Selling before the grant, or online without the FCC ID	2.803 as amended by FCC 26-50	Pre-grant marketing limits; marketplace FCC ID duties from March 1, 2027 or June 1, 2027

Family 1: Scoping errors

1: Self-declaring a radio product

Under 15.201(b), an intentional radiator (Wi-Fi, BLE, Zigbee, LoRa, NFC readers) is authorized under the Certification procedure, through a TCB, with an FCC ID. 15.201(a) keeps SDoC for a short list of transmitters only: carrier current systems, devices under 15.211, 15.213 and 15.221, and devices below 490 kHz whose emissions are 40 dB under the 15.209 limits. The EU habit of self-assessing radio equipment under RED module A has no US counterpart for a Wi-Fi or BLE product.

The mirror error is forgetting the host. 15.3(k) only spares the digital circuitry of a radio product from the digital device rules when it is used only to enable the radio; a product with its own processor, display or interfaces needs its Part 15 Subpart B authorization as well, by SDoC or Certification (15.101). 2.925(b) allows one FCC ID on such a composite device.

How to avoid it: list every radiator in the product at the scoping stage, intentional and unintentional, and write down the procedure each one needs. FCC scope gives the full table by device type.

2: Reusing the CE file

The CE marking has no standing in FCC rules, and the limits differ. In the 2.4 GHz band, 15.247(b)(3) allows 1 W peak conducted output for digitally modulated systems, assuming antennas of up to 6 dBi; above 6 dBi, conducted power drops dB for dB (15.247(b)(4)). EN 300 328 caps wideband data equipment at 20 dBm (100 mW) e.i.r.p. in the EU. The two figures are not the same quantity: 15.247 sets conducted power plus an antenna assumption, not an e.i.r.p. cap.

The US-EU mutual recognition agreement lets a lab or TCB designated in the EU test or certify to FCC rules (2.948(f), 2.960(d)). It can put both campaigns in one lab; it does not make an EU report or a CE declaration valid for the FCC.

How to avoid it: plan an FCC test campaign to ANSI C63.10-2020 and the KDB procedures, separate from the EN 300 328 campaign, and design the firmware with region-specific power tables. See FCC tests and CE vs FCC for EMC.

3: No US agent for service of process

Since FCC 22-84 took effect on February 6, 2023, every applicant for Certification designates an agent for service of process located in the United States, whatever its own location; a US-located applicant may designate itself (2.911(d)(7)). The agent is kept for at least one year after marketing and importation end, or after any related FCC proceeding ends, whichever is later. The agent details and the signed 2.911(d)(7) certifications are also required with every Class II and Class III permissive change (2.1043(b)(2)(i)(D), (E) and (b)(3)(i)(D), (E)).

For SDoC, the rule is stricter on location: the responsible party itself must be in the United States, the manufacturer or assembler, or the importer for imported equipment (2.909(b)).

How to avoid it: name the agent before the application is drafted, with a written agreement that covers the retention period above, and keep its details current for later permissive changes.

4: Treating 6 GHz as one band

15.407 splits 5.925-7.125 GHz into device classes with different rules:

Device class	Band	Key condition	Text
Standard power access point, fixed client	5.925-6.425 GHz (U-NII-5) and 6.525-6.875 GHz (U-NII-7)	Under an AFC system; 36 dBm e.i.r.p., 23 dBm/MHz; outdoor devices also limited above 30 degrees of elevation	15.407(a)(4)
Indoor access point	5.925-7.125 GHz	30 dBm e.i.r.p., 5 dBm/MHz; indoor locations only	15.407(a)(5), (d)(3)
Subordinate device	5.925-7.125 GHz	Under the control of an indoor access point; indoor only	15.407(a)(6), (d)(3), (d)(5)

Standard power is not an "outdoor" class: the rule applies to indoor and outdoor devices and adds an elevation limit for the outdoor ones. Three other points catch product teams: indoor access points and subordinate devices must carry the 15.407(d)(4) statement on the device and in the manual; standard power access points, fixed clients and indoor access points are prohibited on vehicles and boats (15.407(d)(1)); and client devices must operate under the control of an access point (15.407(d)(5)). Very low power and geofenced variable power devices were added in 2024 and 2026 with their own limits (see FCC Parts).

How to avoid it: decide the 6 GHz device class before the radio design is frozen, then follow KDB 789033 for the U-NII measurement procedures and KDB 987594 for the 6 GHz specifics.

Family 2: Reuse and modification errors

5: Using a module outside its grant

A certified module carries its approval into a host only within the conditions of its grant. 15.212(a)(1) lists what a single modular transmitter must have: its own RF shielding, buffered modulation and data inputs, its own power supply regulation, an antenna meeting 15.203 and 15.204, stand-alone testing, its own label, integration instructions and RF exposure compliance in the final configuration. A limited modular approval (15.212(b)) is tied to the host conditions stated in the grant. Guidance is in KDB 996369.

What the host manufacturer still owes:

a "Contains FCC ID:" label followed by the module FCC ID when the module label is not visible (15.212(a)(1)(vi));
the host digital device authorization, unless the host circuitry only enables the radio (15.3(k));
RF exposure compliance in the final configuration (15.212(a)(1)(viii));
no Class I or Class II change on the module grant: those belong to the grant holder (2.1043(b)(4)); a party that modifies the equipment outside the grantee's authority becomes responsible for its compliance (2.909(a)).

Since FCC 25-71 (effective December 26, 2025), a covered modular transmitter, and any host that incorporates one, cannot be authorized (2.903).

How to avoid it: obtain the module integration instructions and grant conditions before the layout, check each one against the host design, and plan the host Subpart B authorization and RF exposure assessment.

6: Swapping the antenna

An intentional radiator must be designed so that only the antenna furnished by the responsible party can be used: a permanently attached antenna or a unique coupler satisfies 15.203, while a standard antenna jack or connector is prohibited (with exceptions for professionally installed devices). It may then only be operated with an authorized antenna type (15.204(c)). An antenna of the same type and equal or lower directional gain may be used with no retesting (15.204(c)(4)); "type" means similar in-band and out-of-band radiation patterns (15.204(c)(1)). A different type, or a higher gain, is not permitted unless the 2.1043 procedures are followed: a permissive change where it qualifies, otherwise a new grant. An unauthorized change is a ground for revocation of the grant (2.939(a)).

How to avoid it: list every intended antenna type, at its highest gain, in the original application (15.204(c)(2), (c)(3)), and treat any other antenna as a 2.1043 decision, not a purchasing one.

7: Changing radio parameters in firmware

2.1043(a) is explicit: changes to the basic frequency determining and stabilizing circuitry (including clock or data rates), the basic modulator or the maximum power or field strength ratings need a new grant. The exception is a Class III permissive change, which exists only for software defined radios (2.1043(b)(3)): software that moves frequency range, modulation type or maximum output power outside the approved parameters, filed with test results, acknowledged before the software is loaded, and only for a device with no Class II change. A software change that degrades spurious or out-of-band emissions counts as a change in frequency or modulation (note to 2.1043(b)(3)). At the other end, software changes that do not affect RF emissions need no filing and may be made by anyone (2.1043(a)).

U-NII devices also have to carry security features against unauthorized software changes to their RF parameters (15.407(i)), and software defined radios describe their protection in the application (2.944).

How to avoid it: classify each firmware release against 2.1043 before release, and keep the radio parameter tables under the same change control as the hardware.

8: Testing radios one at a time

When a product combines several transmitters (Wi-Fi, BLE, cellular), the rule is in 2.947(f): if a composite system contains more than one radiating source designed to emit at the same time, conducted and radiated emissions are measured with all those sources emitting. RF exposure follows the same logic: 1.1307(b)(3)(ii) exempts multiple RF sources only under its own conditions (for example 1 mW sources at least 2 cm apart, or a sum of fractional contributions not above 1); otherwise the simultaneous transmission is evaluated. No FCC rule asks for a "co-existence test" between the radios.

How to avoid it: identify which radios can transmit at the same time, test those combinations, and carry the result into the RF exposure exhibit of the application (2.1033).

Family 3: Marking, documentation and marketing errors

9: Printing an FCC ID before the grant, or in the wrong form

The FCC ID is the Grantee Code immediately followed by the product code. Grantee Codes issued since May 1, 2013 have five characters, earlier ones three (DA 13-669). The product code is capital letters, Arabic numerals and dashes, 14 characters at most, never used before with the same Grantee Code (2.926(d)). There is no separator between the two parts. The label reads "FCC ID" followed by the identifier, permanently affixed and visible from outside the enclosure (2.925(a)(1), (d)).

The more expensive error is timing: no FCC ID may be used on equipment to be marketed until that identifier has been validated by a grant (2.926(e)). Pre-sale shipments allowed by 2.803 carry a temporary label, and the expected FCC ID only if it is obscured.

How to avoid it: generate the identifier from the Grantee Code and a product code checked against 2.926(d), and release label artwork for production only once the grant is published (2.915(d)).

10: Putting the 15.19 statement in the manual

Text	Where it goes	Who needs it
15.19(a)(3), two-condition statement	On the device, in a conspicuous location	Every Part 15 device under Certification or SDoC, except the two categories in 15.19(a)(1) and (a)(2)
15.21, unapproved changes warning	In the user manual	Every intentional or unintentional radiator
15.105(a) or (b), Class A or Class B text	In the user manual	Class A or Class B digital devices
15.407(d)(4), indoor use statement	On the device and in the manual	6 GHz indoor access points and subordinate devices

Only when a device is too small for four-point text and has no display for an e-label does the 15.19 statement move to the manual, plus the packaging or a removable label (15.19(a)(5)). A manual supplied only in electronic form may carry the 15.21 and 15.105 texts (15.21, 15.105(e)).

How to avoid it: keep the device statement in the label artwork and the manual texts in the manual template, and check both against the table above at each new product.

11: An e-label that does not meet 2.935

2.935 allows the FCC ID and statements to be shown electronically only on a device with an integrated display, or one that works only with a device that has one (2.935(a)). The conditions:

Condition	2.935
Prominent access instructions in the manual, a packaging insert or another format at purchase	(b)
No special codes, accessories or permissions; at most three steps from the device settings menu, screen locks and passcodes not counted	(c)
Legible without magnification	(d)
Programmed by the responsible party and secured against third-party modification	(e)
The device or its packaging still carries the FCC ID or other identifying information, such as a model number and a web page	(f)

A device without a display cannot use an e-label; a very small one follows 2.925(f). Guidance is in KDB 784748.

How to avoid it: write the menu path into the specification, count the steps from the settings menu, and add the access instructions to the manual or packaging insert.

12: Selling before the grant, or online without the FCC ID

Before the grant, 2.803 allows only limited activity: display or advertising with a conspicuous notice that the device is not authorized, conditional sales contracts with no delivery to end users, and, for Certification, pre-sale transfer after testing and TCB submission. Importing beyond the 2.1204 quantities needs OET approval.

Online sales get their own rules with FCC 26-50 (published September 11, 2026, effective October 13, 2026):

Date	What applies	Text
October 13, 2026	Listing on an online marketplace combined with fulfilment, warehousing or similar services counts as marketing, even when a third-party seller makes the sale	2.803(a)(1)
March 1, 2027	A marketplace that sells the device, or has physical access to or title over it, displays a valid FCC ID at the point of sale	2.803(c)(1)
June 1, 2027	Other marketplaces display a valid FCC ID, verify it against the Equipment Authorization System and require the seller to certify it	2.803(c)(2)

How to avoid it: put the FCC ID, as published in the EAS, in the product data sent to every marketplace, and do not list a radio product before its grant. See FCC 26-50 in force, but marketplaces wait until 2027.

Dated changes behind these pitfalls

Date	Text	Pitfall it affects
May 1, 2013	DA 13-669	9: five-character Grantee Codes
November 2, 2017	82 FR 50827	11: electronic labeling rule 2.935
February 6, 2023	FCC 22-84, 88 FR 7592	3: US agent for every Certification applicant, also in permissive changes
October 30, 2025	15.37(s)	2: ANSI C63.10-2020 only for Part 15 intentional radiators
December 26, 2025	FCC 25-71, 90 FR 53227	5: covered modular transmitters and their hosts barred
October 13, 2026	FCC 26-50, 91 FR 57798	7, 12: changes by Covered List entities need a new grant; marketplace listings count as marketing
March 1, 2027 and June 1, 2027	FCC 26-50, 2.803(c)	12: marketplaces display the FCC ID

Claims the texts contradict

Common claim (several made by this page before October 2026)	What the text says
Wi-Fi 2.4 GHz is "1 W in the US vs 100 mW EIRP in the EU"	15.247(b)(3) sets 1 W conducted with antennas up to 6 dBi, reduced dB for dB above; EN 300 328 sets 20 dBm e.i.r.p. for wideband data
Since 2023 the FCC no longer assigns an FCC ID to non-US manufacturers without a US agent	2.911(d)(7) applies to every Certification applicant, US-based ones included; a US applicant may name itself
A US agent costs a known yearly range	No FCC text prices it
6 GHz standard power with AFC is for "U-NII-5/-7 outdoor", LPI for indoor	Standard power covers indoor and outdoor devices in U-NII-5 and U-NII-7, with an extra elevation limit outdoors (15.407(a)(4)); indoor access points use 5.925-7.125 GHz and are restricted to indoor locations
A firmware change to power or modulation is a "C2PC (limited) or C3PC (substantial)"	Power rating, modulator and frequency changes need a new grant (2.1043(a)); Class III exists only for software defined radios (2.1043(b)(3))
Any antenna substitution triggers at least a Class II permissive change	Same type and equal or lower gain: no retesting (15.204(c)(4)); a different type or higher gain goes through 2.1043
Co-located transmitters "may require co-existence tests"	2.947(f) requires emissions measured with all simultaneously emitting sources on; 1.1307(b)(3)(ii) governs RF exposure of multiple sources; no co-existence test is in the rules
The 15.19 and 15.105 texts go in the user manual, and omitting them is a systematic ground for rejection	15.19(a)(3) goes on the device; 15.105 and 15.21 go in the manual; no rule describes a systematic rejection
The e-label must be reachable in at most three steps "from the main menu"	Three steps from the device settings menu, screen locks not counted (2.935(c))
An average user must find the FCC ID "in under 30 seconds"	No FCC text sets a time; 2.935 sets the step count, legibility and access instructions
The FCC ID has a "separator" between Grantee Code and product code	2.926(a) and (d): the Grantee Code followed by the product code; dashes are allowed inside the product code
Marketplaces have required FCC IDs "since 2024" under FCC enforcement pressure, and listings without one are removed	The binding rules are FCC 26-50: marketing definition from October 13, 2026, FCC ID display from March 1, 2027 or June 1, 2027 (2.803)

In summary

Scoping (1 to 4): Certification for intentional radiators and a separate authorization for the host digital device; US limits, not EU ones; a US agent for every applicant; a 6 GHz device class chosen deliberately.
Reuse and modification (5 to 8): module grant conditions, authorized antenna types, firmware classified against 2.1043, simultaneous transmitters measured together.
Marking and marketing (9 to 12): an FCC ID used only after the grant, the 15.19 statement on the device, an e-label that meets 2.935, and FCC IDs on marketplace listings from 2027.

For practical implementation, see FCC procedure, FCC technical file and the FCC FAQ.

Frequently asked questions

Can a CE-marked Wi-Fi product be sold in the United States on its EU test reports?: No. The product needs its own FCC authorization, usually Certification by a TCB (15.201(b)), against US limits: in the 2.4 GHz band, 1 W peak conducted output with antennas up to 6 dBi (15.247(b)(3), (b)(4)), where EN 300 328 caps wideband data equipment at 20 dBm e.i.r.p. The US-EU mutual recognition agreement lets an EU-designated lab or TCB apply the FCC rules; it does not make EU results valid in the US.
Does a firmware update need a new FCC filing?: It depends on what it changes. Software changes that do not affect RF emissions need no filing (2.1043(a)). Changes to maximum power ratings, the basic modulator or the frequency determining circuitry need a new grant, except Class III changes, which only exist for software defined radios and need FCC acknowledgement before the software is loaded (2.1043(b)(3)).
Where do the Part 15 statements go?: The 15.19(a)(3) two-condition statement goes on the device, in a conspicuous location, for certified and SDoC devices alike. The 15.21 warning on unapproved changes and the 15.105 Class A or Class B text go in the user manual. Only a device too small for four-point text and without a display moves the 15.19 statement to the manual plus the packaging or a removable label (15.19(a)(5)).