Certification before styling: what CE, FCC and friends do to a hardware timeline
Compliance testing is rarely the reason a product is late. Not planning for it is. What to decide in the first month so the last month is not a surprise.

Every product sold in Europe carries a CE mark, and most products with electronics need testing to earn it. The same is true, under different names, in the United States, the United Kingdom and most other markets. None of this is a surprise to anyone. Yet certification is where many hardware schedules break, because the work was planned as a final step rather than a design input.
This is not legal advice. It is what we do on every project so that compliance does not become the critical path.
Decide the markets first
Which countries the product will sell in decides which directives, standards and marks apply. Europe (CE), the UK (UKCA), the US (FCC for radio and emissions, UL or equivalent for safety where required) and others each have their own route. Selling in all of them is possible; designing for all of them from the start is much cheaper than adding one later.
Identify the standards during discovery
For most products we work on, the relevant standards fall into a few families:
- Electrical safety for anything mains-powered or with a battery of meaningful size.
- Electromagnetic compatibility (EMC) for anything with electronics.
- Radio for anything with Bluetooth, Wi-Fi or another transmitter.
- Battery transport and safety for lithium cells.
- Product-specific safety standards: children's products, medical devices, machinery, toys, lighting.
- Material and chemical restrictions such as RoHS and REACH.
Naming them in the first month is not expensive. A conversation with a test house, with the product architecture sketch in hand, usually settles the list and gives a budget for testing.
Design to them
Standards contain geometry. Creepage and clearance distances, enclosure openings, pinch-point sizes, surface temperatures, label areas, battery compartment rules. These are design constraints and we treat them like any other: in the requirements list, with an owner, before styling.
A product designed without them is redesigned with them later, after the tooling quote.
Use modules where you can
A radio module that is already certified saves the full radio test. A power supply that already carries the relevant marks saves most of the electrical safety work. The module costs more per unit; the saving in time and testing often covers it for the first years of production.
Plan the samples
Testing needs units. Typically several, in production-representative form, including packaging and manuals. Those come from the pilot batch, which means the pilot batch has to be scheduled before certification, which means the timeline has to have room between them. Put it there from the start.
Budget it
Testing is paid to the test house and we pass it through at cost. The amount depends on the standards list, which is why we want the list early. Expect it to be a visible line in the project budget, not a rounding error.
What goes wrong
The usual failures are not dramatic. An EMC test fails by a small margin and a cable needs a ferrite. A label is in the wrong place. A battery compartment opens without a tool when the standard says it must not. Each is a small fix if there is time, and a shipping delay if there is not.
The way to have time is to decide, in the first month, which marks the product needs, and to design for them from then on.
