CertificationHardwareCompliance

Does Your Product Actually Need Certification? (Almost Certainly, Yes)

September 11, 20266 min

EMI, safety, and hazardous-materials certification — why pre-certified modules aren't enough and how to plan the path early.

Electronics under compliance and test review

"It uses a pre-certified module, so we should be fine." "There's no wireless functionality, so certification doesn't apply." "It's such a simple product — surely it's harmless enough to skip this."

These are some of the most common — and most costly — assumptions in hardware development. The reality is straightforward: certification applies to the entire finished product, not just the individual parts inside it. Even a design built entirely from pre-certified components still has to meet regulatory requirements once it's assembled into a final product. Understanding why, and what actually triggers which certification, can save months of delay and thousands of dollars in rework.

The Three Categories of Regulatory Certification

Broadly, product certification falls into three categories:

  • Electromagnetic Interference (EMI) — governed by the FCC in the U.S., ISED in Canada, and CE marking in Europe
  • Safety — governed by UL in the U.S., CSA in Canada, and again folded into CE marking in Europe
  • Hazardous materials — governed by RoHS compliance, relevant wherever the product is sold

Each category has its own triggers, its own cost profile, and its own failure modes if it's ignored.

EMI Certification: Why "Pre-Certified" Doesn't Mean "Done"

Using a pre-certified wireless module makes EMI certification significantly easier and cheaper — but it doesn't eliminate the requirement.

If the wireless radio isn't modified, the product is classified by the FCC as a non-intentional radiator. That classification allows for a Supplier's Declaration of Conformity (SDoC) — a comparatively simple, self-administered process where compliance is verified through basic testing and documentation, rather than full formal certification.

If the radio design is custom, or a pre-certified module's antenna is altered, the product becomes an intentional radiator — and that changes everything. Even something as small as swapping a wireless module's external antenna for a different one voids the module's original certification and shifts full FCC approval responsibility onto the product itself. Intentional radiators require rigorous RF testing in an FCC-accredited lab and a formal, months-long approval process. If the product fails testing, it's back to the design table for rework and retesting — adding further cost and delay.

This is exactly why using pre-certified wireless modules, and keeping their antenna design unmodified, is generally the smarter path: it keeps a product firmly in SDoC territory instead of triggering full FCC certification.

What If the Product Has No Wireless Radio at All?

It's a common assumption that no wireless functionality means no FCC involvement. Unfortunately, that's not how the regulation works.

The FCC regulates any device containing a circuit that oscillates above 9 kHz — a threshold that captures the overwhelming majority of modern electronics, wireless or not. Microcontrollers, switching regulators, and most other core components can generate electromagnetic interference on their own, and that interference still needs to be tested. In practice, almost every electronic product will need to go through the FCC's SDoC process, regardless of whether it has a radio.

Safety Certification (UL): Not Legally Required, But Often Non-Negotiable

Unlike FCC certification, UL certification isn't legally mandated in most cases. But "not legally required" and "optional" aren't the same thing — UL is frequently required by retailers and liability insurers, particularly for anything that plugs directly into an AC wall outlet.

There's a practical way to sidestep this in some cases: if a product runs on DC power, bundling it with an already UL-certified AC/DC adapter usually avoids the need for UL certification on the product itself. AC-powered devices don't have that option — they need UL certification both to limit liability exposure and, often, simply to get retailers to carry the product at all.

Beyond the business case, UL certification genuinely makes a product safer — which is worth pursuing on its own merits, independent of liability concerns.

For certain categories, UL certification is effectively mandatory rather than optional in practice:

Smart home devices that plug into an AC outlet — most retailers won't carry them without UL approval

Products with large lithium battery packs, such as e-bikes or power tools, which often face additional, stricter safety requirements

In the U.S., outside of medical devices, FCC and UL certifications are typically the two most complex and expensive hurdles a product will face. RoHS compliance for hazardous materials also applies broadly, but it's generally far cheaper and simpler to obtain. Any rechargeable lithium battery in the product needs its own appropriate certifications as well.

How This Changes by Region

Canada uses ISED certification in place of FCC, and CSA in place of UL — the underlying requirements are usually nearly identical, and in many cases the same test data can support both the U.S. and Canadian submissions.

Europe consolidates things differently. Rather than separate RF and safety certifications, most products require CE marking, which covers both RF emissions and electrical safety under a single certification process, along with RoHS compliance for hazardous materials. Many CE-marked products can be self-certified, though higher-risk product categories require sign-off from an independent certification lab.

  • So — Does Your Product Need Certification?

Almost certainly, yes. Skipping certification isn't a shortcut; it's a liability. Non-compliance discovered after launch can mean product recalls, import bans, and significant fines — all considerably more expensive than the certification process itself would have been.

The right time to think about certification is at the start of development, not after the design is finished. It's far cheaper to design with compliance in mind from day one than to redesign a finished product to fix a certification failure.

One practical timing tip: certification is worth delaying as long as reasonably possible — ideally folding it into initial manufacturing setup rather than doing it earlier than necessary. If a product qualifies as a non-intentional radiator and doesn't plug directly into an AC outlet, small-scale sales tests can often happen before certification costs are incurred at all. Certifying too early carries its own risk: any subsequent design change can trigger a full round of retesting, turning an early "safety net" into a repeated cost.

Conclusion

Certification isn't a checkbox to clear at the end of a project — it's a set of constraints that shape antenna design, power architecture, component selection, and even go-to-market timing from the very beginning. The products that move through certification smoothly are almost always the ones where the engineering team understood which category their product fell into, and designed around those requirements early, rather than discovering them after the design was already locked.

At CoBuild Labs, we treat regulatory strategy as part of the engineering process from day one — mapping out EMI, safety, and hazardous-materials requirements alongside component selection via product certification — and for medical claims, FDA clearance.

Need a certification roadmap before you freeze the design? Talk to CoBuild Labs — our product certification and electrical teams plan EMI/safety early. Also see FDA clearance for wearables.

Next step

Let's build your product

See more on our project portfolio or contact CoBuild Labs to discuss your hardware roadmap.