What the Rule Actually Says

On 28 July 2026 the FCC’s Public Safety and Homeland Security Bureau added foreign-produced advanced robotic devices to the Covered List maintained under the Secure and Trusted Communications Networks Act. The mechanism is equipment authorization. Almost any device that emits or uses radio frequency energy needs an FCC authorization before it can be imported, marketed, or sold in the United States, and a device on the Covered List cannot receive a new one.

Two features of the drafting matter more than the headline. First, the listing reaches a device category rather than a list of named manufacturers. The test is where and how a product is made, not who makes it, which means a vendor cannot escape it by rebranding or by changing corporate parentage. Second, it applies to new authorizations. Machines already authorized keep their authorizations, and inventory already in the country can still be sold.

The practical consequence for a buyer is narrow but real: the platform you are evaluating today may not have a successor model you can buy in 2029. That is a planning problem, not an operating one, and the two get conflated constantly in the coverage.

This is a procurement guide, not legal advice. The rule is new, the Commission has published FAQs that continue to be updated, and counsel are still working through edge cases. Anything with contractual or compliance consequence should go past your own attorney, and the Commission’s own guidance is the authority over any summary, including this one.

How to Tell Whether a Machine Is in Scope

The determination is functional. A device is caught when it meets all of the following, as described in the coverage and the client alerts published since:

  • The combined weight of the device and, where applicable, its ground station or docking station exceeds 4.4 pounds.
  • It contains a component capable of network connectivity — wired or wireless, including Wi-Fi, Bluetooth, cellular or satellite — at connection speeds of at least 200 kbps in either direction.
  • It carries sensors together with software enabling autonomous movement or remote control.

Read those three together and the reach becomes obvious. Autonomous mobile robots and automated guided vehicles used in logistics are in. Cleaning machines are in. Delivery and service robots in hospitals, hotels and dining rooms are in. Quadrupeds are in. Consumer robot vacuums and robot lawn mowers are in, which is why this became a mainstream news story rather than a trade one.

What is carved out is equally instructive. Fixed industrial arms — articulated, delta, gantry and SCARA — are outside the scope, as are drones, connected vehicles, and FDA-regulated medical and mobility devices, which are governed elsewhere. Mobility is the trigger. A robotic arm bolted to a bench in a clinical laboratory is untouched; a machine that carries a rack of specimens from that bench to the next department is not.

If you are unsure where a specific machine falls, the weight and connectivity thresholds are the fastest screen. A tabletop unit under 4.4 pounds with no network radio is almost certainly outside. Anything that drives itself around a building is almost certainly inside.

Machines You Already Own Are Not Affected

This is the part worth saying first to a nervous facilities committee. A robot that was authorized before the listing keeps its authorization. It can continue to operate, and the Commission issued a waiver alongside the order that permits Class I and Class II permissive changes — the mechanism covering software and firmware updates — for previously authorized devices through at least 1 January 2029. Your fleet does not become unsupportable, and your vendor is not barred from patching it.

What changes is the replacement question. If a unit is destroyed, or you want to add a twelfth robot to a fleet of eleven, the model you would buy has to be authorizable at the moment you buy it. Fleet standardization — one platform, one set of spares, one training programme — has been the right answer for years and is now harder to sustain across a long refresh cycle. Plan for the possibility that your next tranche is a different platform, and ask now what that means for your maps, your integrations and your staff training.

The Domestic Content Test, and Why Sixty Five Percent Is Harder Than It Sounds

The exemption counsel have identified is the domestic end product standard drawn from the Buy American rules at 48 CFR 25.101(a). A device produced in the United States, by whoever designed it, can fall outside the prohibition. That standard has two limbs: the product must be manufactured in the United States, and the cost of its domestic components must exceed a stated percentage of total component cost.

The percentage is not set by the Commission. It is inherited from the federal acquisition schedule, which currently requires domestic components to exceed 65% of total component cost for items delivered through 2028, rising to 75% for items delivered from 2029. Because the number comes from the acquisition schedule rather than from this rulemaking, it is unlikely to be negotiated down as part of any reconsideration of the robotics listing.

Sixty five percent of component cost is a demanding bar for a mobile robot. Consider what a service robot is made of. The drive train, chassis, castors and enclosures are relatively straightforward to source or fabricate domestically. Batteries, lidar units, depth cameras, motor controllers and the compute module are not, and they are also the expensive parts. A vendor who imports the sensing and compute stack and assembles the rest in a US facility will not clear the threshold, and that appears to be the intended effect rather than an oversight.

What this means when a salesperson tells you a machine is “made in America”: assembly is not manufacturing, and manufacturing is not the whole test. The question is the percentage of component cost, and a vendor who has done the work will be able to give you a number.

Eleven Questions to Put in Your RFP

Origin and authorization now belong on the same page of the evaluation matrix as payload, runtime and service coverage. These are the questions we would put in writing, and we would ask them of every vendor including ourselves:

  1. What is the FCC ID of the exact model you are proposing, and on what date was it authorized?
  2. Where is this model manufactured, at the level of the facility rather than the country of incorporation?
  3. What percentage of this model’s total component cost is domestic today, measured the way the acquisition rules measure it?
  4. What is your plan to reach 65%, and separately to reach 75% for units delivered from 2029?
  5. Which subassemblies do you expect to remain foreign-sourced, and what is your contingency if a supplier becomes unavailable?
  6. Is the model you are proposing the one you expect to sell in three years, or is a successor planned? If a successor is planned, will it be authorizable?
  7. If we need to add units in year three, what specifically will we be buying?
  8. What is your written commitment on software, firmware and security updates for units we buy now, and for how long?
  9. What happens to our maps, integrations and staff training if the replacement platform differs from the one we deploy now?
  10. What spare parts inventory do you hold in the United States, and for how many years after end of production?
  11. Will you warrant in the contract that the units delivered hold a valid equipment authorization at the time of delivery?

Most vendors cannot answer all eleven yet. That is not automatically disqualifying — nobody has a finished answer nine months into a rule this new. What is disqualifying is a vendor who treats the questions as hostile, or who answers the origin question with a marketing phrase instead of a percentage. How a supplier handles this line of questioning tells you a great deal about how they will handle the next hard thing.

What Belongs in the Contract

Three provisions are worth the negotiation. The first is a delivery warranty: the vendor warrants that each unit delivered holds a valid FCC equipment authorization on the delivery date, with a remedy if it does not. This costs a legitimate vendor nothing and protects you from a unit that cannot lawfully be commissioned.

The second is a support commitment with a date on it. “We will continue to support the platform” is not a term. A stated number of years of software, firmware and security updates, and a stated spare-parts availability period, are terms. Given the update waiver currently runs to at least 1 January 2029, a support commitment that stops short of that date should prompt a question.

The third matters most for multi-year and Robots-as-a-Service arrangements: what happens if the vendor cannot supply a replacement or an additional unit of the same model during the term. Options range from a substitution right at no additional cost, to a price-protected upgrade to the successor platform, to a termination right. Any of these is better than discovering in year three that the contract is silent.

Planning a Refresh Cycle Through the Change

Analysts have started putting numbers on the transition. IDC has cut its United States robotics growth forecast from a 13% compound annual rate to 9% through 2030, and expects the professional and commercial category to run roughly 43% below its own prior baseline by 2030. Reasonable people disagree about the policy, and estimates of near-term price effects vary widely because a domestic supply chain that does not exist yet is difficult to model. But the direction is not really in dispute: fewer platform choices in the near term, higher prices during the transition, and a strong incentive for anyone selling into the US market to manufacture here.

For a facility planning a refresh, three adjustments follow. Bring the decision forward rather than back, because the platforms available now are known quantities and the ones available in 2029 are not. Standardize on fewer platforms, since managing two fleets through a supply transition is harder than managing one. And write the origin question into the specification now, so that the evaluation you run next year does not have to be redone.

We are working through this ourselves. Our own ground-based platforms are built in Europe, the definition captures them, and the long-term answer for us is manufacturing in the United States to the domestic content threshold. We would rather set that out plainly, and let customers plan against it, than have it surface at renewal.

Working Through a Specification?

We will answer the origin and authorization questions in writing, for our platforms and honestly about where they stand. Send us your RFP language and we will tell you what we can and cannot commit to.

Get in Touch