Selling a connected gadget in the United States requires more than a working prototype. Anything that intentionally emits radio energy needs federal authorization before it can be marketed at all.
The rule applies to almost everything now
Wireless earbuds, trackers, doorbells, thermostats and toys all contain radios. The obligation attaches to the radio, not to the product category, so ordinary consumer goods fall inside it.
Devices with digital circuitry but no intentional transmitter still face limits on unintentional emissions. Very few electronics escape the framework entirely.
Marketing is defined broadly enough to include showing a product for sale, which catches teams who assume authorization can wait until units are shipping.
Testing happens at accredited labs, not in-house
Compliance measurement requires a chamber, calibrated instruments and an accredited body. A startup rents that capability rather than building it.
The lab produces a report against the applicable rule parts, covering emitted power, spurious emissions, band edges and exposure limits for devices used near the body.
Failures are common on first submission and usually require hardware changes, not just firmware. Each iteration means a new lab booking and a new schedule slip.
The paperwork continues after the certificate
An authorization is tied to a specific hardware and firmware configuration. Meaningful changes to the radio, antenna or enclosure can require a filing to extend or replace it.
Devices must carry the required identifiers, which for small products often means an electronic label displayed in software rather than a printed mark.
Records supporting the authorization have to be retained and produced on request. That obligation survives staff turnover, which is how small companies lose track of it.
Module reuse is the standard shortcut
Buying a pre-certified radio module transfers much of the burden, because the module already carries its own authorization when used within its stated conditions.
Those conditions are strict: specified antennas, specified separation distances, and integration guidance the host product must follow to inherit the coverage.
Departing from them, often to shave cost or thickness, quietly invalidates the inheritance and pushes the host product back into full authorization.
The cost is structural rather than large
For a single product the fees and lab time are survivable. The difficulty is that they recur with every variant, every region and every significant revision.
A company shipping one device absorbs it once. A company shipping a family of devices carries it as an ongoing engineering function it did not plan for.
That asymmetry is why hardware roadmaps at small companies stay narrow. Each additional model multiplies a compliance workload that does not scale with team size.