FCC Closes Covered List Component Loophole in Equipment-Authorization Rules

A component-level restriction enters the authorization process

The Federal Communications Commission has finalized a new component-based restriction within its equipment-authorization rules. Under revised 47 CFR § 2.903, a device may not receive equipment authorization when it incorporates a logic-bearing hardware component produced by an entity on the FCC Covered List, if the completed device would have been barred from authorization had that same entity produced the device itself. The final rule was published in the Federal Register on September 11, 2026. ([govinfo.gov](https://www.govinfo.gov/content/pkg/FR-2026-09-11/pdf/2026-18535.pdf))

The action closes a gap in which a prohibited producer could potentially supply a significant electronic component for a device assembled, labeled or sold by a different company. The FCC’s focus is not on every part in a product: it is directed to components capable of digital or RF data-processing functions and applies through the agency’s equipment-authorization program. ([docs.fcc.gov](https://docs.fcc.gov/public/attachments/FCC-26-50A1.pdf))

What counts as logic-bearing hardware

The FCC defines a logic-bearing hardware component broadly as a device, system, module, subassembly, integrated circuit or other physical component that uses digital techniques with timing signals above 9,000 cycles per second, or that uses RF energy for data-processing functions. In practical product engineering terms, the category can encompass programmable and data-handling electronics rather than just a radio module. ([govinfo.gov](https://www.govinfo.gov/content/pkg/FR-2026-09-11/pdf/2026-18535.pdf))

The Commission distinguishes those parts from passive or purely mechanical items. Its order identifies examples outside the definition such as housings, chassis parts, fasteners, basic resistors, capacitors, wiring, connectors, plain battery cells and bare motors without embedded digital control. The dividing line is whether the component performs programmable, digital or RF data-processing functions. ([docs.fcc.gov](https://docs.fcc.gov/public/attachments/FCC-26-50A1.pdf))

Effective date and transition treatment

The final rule is effective October 13, 2026—30 days after Federal Register publication. The component prohibition is prospective: it applies to new equipment-authorization applications and does not revoke or otherwise disturb existing equipment authorizations. Products already authorized may continue to be marketed, imported and used under their existing authorization, subject to other applicable FCC requirements. ([govinfo.gov](https://www.govinfo.gov/content/pkg/FR-2026-09-11/pdf/2026-18535.pdf))

Applications filed with the FCC or a Telecommunications Certification Body before the effective date and still pending are exempted. That exception is limited. If an applicant changes, substitutes or adds a logic-bearing hardware component after the rule takes effect, the FCC will treat that amendment as a new application for purposes of the prohibition. ([docs.fcc.gov](https://docs.fcc.gov/public/attachments/FCC-26-50A1.pdf))

Scope matters: entity-based listings, not every foreign-made component

Procurement teams should avoid reading the rule as a blanket ban on components made abroad. The FCC states that the new component restriction applies to logic-bearing hardware produced by entities covered through producer/provider-based determinations. It does not automatically apply merely because a component producer makes equipment that falls within the FCC’s production-location-based Covered List entries, such as specified foreign-produced routers or uncrewed aircraft systems, unless the producer is independently named on the Covered List. ([govinfo.gov](https://www.govinfo.gov/content/pkg/FR-2026-09-11/pdf/2026-18535.pdf))

That distinction makes supplier identity and the applicable Covered List determination central to compliance. A country-of-origin field alone will not provide the answer. Manufacturers, importers and private-label program managers instead need to identify the producer of relevant electronics, assess whether that entity is named on the list, and evaluate whether the completed device would be prohibited if the entity had produced it. ([docs.fcc.gov](https://docs.fcc.gov/public/attachments/FCC-26-50A1.pdf))

Practical actions for OEM and private-label programs

Teams planning new authorizations for wireless access points, routers, cellular gateways, RF-enabled cameras, alarm communicators and similar connected equipment should update their pre-certification controls before October 13. A practical workflow is to map logic-bearing components to their actual producers; preserve supplier declarations and change notifications; screen those producers against the Covered List; and require engineering, sourcing and compliance review before a component substitution reaches a certification application.

The final rule does not itself adopt a universal hardware bill of materials submission requirement for all certification applicants. The FCC instead sought comment on broader hardware and software bill-of-materials disclosures in the accompanying further notice of proposed rulemaking. Even so, maintaining an internal component record will be materially useful where a product’s eligibility depends on who produced a processor, controller, communications module or other logic-bearing part. ([docs.fcc.gov](https://docs.fcc.gov/public/attachments/FCC-26-50A1.pdf))

Other changes adopted at the same time

The same order also addresses post-authorization changes and online sales. It requires a Covered List entity seeking to modify equipment to use full certification rather than the narrower permissive-change process. It also clarifies when marketplace activities amount to marketing and requires specified online marketplaces to display FCC IDs for certified devices, with compliance dates of March 1, 2027 or June 1, 2027 depending on the marketplace’s role. ([govinfo.gov](https://www.govinfo.gov/content/pkg/FR-2026-09-11/pdf/2026-18535.pdf))

For installers and integrators, the immediate issue is documentation rather than a change to field deployment of already authorized products. For product-development and sourcing teams, however, the rule shifts the compliance review upstream: final-product branding and final assembly location are no longer sufficient checkpoints where a new device contains in-scope logic-bearing hardware from a Covered List entity. ([docs.fcc.gov](https://docs.fcc.gov/public/attachments/FCC-26-50A1.pdf))