Why Compliance Should Be Considered Before Your Electronic Product Is Finished
Compliance is often treated as something that happens near the end of electronic product development. The product is designed, prototypes are built, testing is booked, and certification is seen as one of the final steps before launch. For startups and SMEs, that approach can create avoidable cost, delay, and redesign.
Compliance is not just a box to tick after the engineering work is complete. It can affect product architecture, component selection, PCB layout, enclosure design, battery integration, firmware behaviour, user instructions, labelling, and production testing. If those requirements are only considered once the product is already finished, the team may discover that a design decision made months earlier now needs to be changed.
A better approach is to consider compliance early enough that it can guide practical design decisions without slowing the project unnecessarily.
Compliance is part of product development
Most electronic products need to meet some form of regulatory, safety, or verification requirement before they can be sold. The exact requirements depend on the product type, market, environment of use, power source, wireless features, battery system, user access, sector, and intended application.
For some products, the main concerns may be EMC, electrical safety, radio performance, battery safety, and environmental requirements. For others, there may be additional sector-specific expectations around traceability, documentation, software behaviour, risk management, or long-term support.
The important point is that compliance requirements do not sit outside the design process. They often shape the design itself.
A product that needs to pass EMC testing may require careful PCB layout, grounding, shielding, filtering, cable routing, enclosure decisions, and component selection. A battery-powered product may need appropriate charging, protection, thermal behaviour, labelling, and transport consideration. A product used in an industrial or healthcare environment may need stronger evidence of reliability, safety, and controlled change.
These are not details that can always be added after the product is built.
Late compliance thinking can lead to expensive redesign
When compliance is left until the end, problems tend to appear at the point where the design is least flexible. Tooling may already have been ordered. The PCB may already be laid out. The enclosure may be fixed. Suppliers may have been selected. Marketing material may be prepared. Production dates may be planned.
At that stage, a failed test can cause disruption across the whole project.
An EMC issue may require PCB layout changes, additional filtering, enclosure changes, or cable routing changes. A safety issue may require changes to insulation, spacing, materials, user access, battery protection, or power architecture. A thermal issue may require a different enclosure design or component placement. A labelling or documentation issue may be easier to resolve, but it can still delay launch if it is not planned.
For startups, the commercial impact can be significant. A late redesign can consume budget that was intended for production, sales, or the next stage of development. For SMEs, it can disrupt customer commitments, manufacturing schedules, and supply planning.
Considering compliance earlier does not eliminate all risk, but it helps prevent obvious issues from being designed into the product.
The right requirements need to be identified early
A common mistake is assuming that compliance is a single generic process. In reality, the required route depends on what the product is, where it will be sold, how it is powered, how it communicates, and how it will be used.
A simple low-voltage device, a mains-powered product, a wireless sensor, a battery-powered consumer product, a motor-driven system, and a medical-adjacent device may all face different expectations. Even small product features can change the compliance picture. Adding wireless communication, changing a charger, using a different battery pack, modifying an enclosure, or changing the intended use can introduce new requirements.
Early in the project, the aim is not always to complete a full certification plan. It is to identify the likely requirements and understand which design decisions they may affect.
This helps the team avoid building the wrong assumptions into the product. It also helps with planning, because test costs, documentation needs, sample quantities, lead times, and design reviews can be included in the development route rather than treated as surprises.
Compliance affects electronic design decisions
Electronic design choices can have a direct effect on compliance performance.
PCB layout, grounding strategy, power supply design, clock speeds, switching regulators, motor drivers, wireless modules, cable connections, connectors, filtering, isolation, and component placement can all influence how a product behaves during testing.
For example, a product may work perfectly in normal use but still emit electrical noise that causes EMC failure. A switching power supply may be efficient but noisy if not designed and laid out carefully. A motor driver may create transient behaviour that needs to be managed. A cable may act as an antenna. A poorly placed connector may make filtering difficult. A processor or wireless module may require layout constraints that need to be understood early.
These issues are much easier to manage when compliance is part of the electronic development process. Once a PCB is designed and space is limited, fixing problems may require compromise or a full board redesign.
Mechanical and enclosure design matter too
Compliance is not only an electronics issue. The enclosure can influence safety, EMC performance, thermal behaviour, battery protection, ingress protection, labelling, access to hazardous parts, and mechanical durability.
A plastic enclosure may need suitable material properties, wall thickness, fixing points, ventilation, and labelling surfaces. A metal enclosure may support shielding, but it may also affect antennas, grounding, corrosion, weight, and user-accessible conductive parts. A sealed enclosure may improve environmental protection but make heat harder to manage.
Mechanical decisions also affect how the product is assembled and inspected. If compliance relies on a gasket, shield, earth connection, insulation barrier, or cable position, the production process must be able to repeat that condition consistently.
This is where design for manufacture and compliance overlap. A product must not only pass a test once. It must be capable of being built repeatedly in a way that preserves the features needed for safety and performance.
Battery systems need early compliance attention
Battery-powered products deserve particular care because the battery system can affect safety, transport, enclosure design, charging, thermal behaviour, and user instructions.
The product may need protection against overcharge, over-discharge, short circuit, overcurrent, and unsafe temperature conditions. Charging behaviour may need to be controlled carefully. The enclosure may need to protect the battery from damage or prevent unsafe user access. The product may need clear indicators for charging, fault states, or low battery conditions.
Battery changes can be difficult late in development. A different cell or pack may affect size, weight, runtime, charging time, heat, compliance evidence, supply chain, and manufacturing process. If battery safety and charging requirements are not considered early, the design may need substantial changes before it can move towards production.
Firmware behaviour can be part of compliance risk
Embedded software is sometimes overlooked in compliance planning, but firmware can affect product safety, reliability, power behaviour, charging, motor control, fault handling, and user feedback.
A product may need to respond safely to low voltage, sensor failure, communication loss, overheating, stalled motors, charging faults, watchdog resets, or unexpected user behaviour. It may need to store settings safely, recover from power interruption, or prevent unsafe operation under defined conditions.
These behaviours should be designed and verified, not improvised late in testing. Firmware requirements should be connected to the product’s risk profile and operating environment.
For products with long service lives, teams should also consider how software updates will be controlled, tested, documented, and supported after launch.
Pre-compliance reviews reduce uncertainty
Pre-compliance activity can be extremely useful because it gives the team a chance to find likely problems before formal testing.
This may include design reviews, EMC pre-scans, safety reviews, thermal checks, battery system assessment, documentation review, and examination of production test requirements. The aim is not to replace formal certification where that is required. The aim is to reduce the chance that formal testing reveals avoidable design issues.
For startups and SMEs, this can be a practical way to manage risk. It is usually better to discover a layout, enclosure, grounding, charging, or documentation issue while the design is still flexible than after the product is ready for launch.
Pre-compliance thinking also helps teams make better trade-offs. Not every risk needs the same level of response, but the team should understand which risks are likely to matter.
Documentation should not be left behind
Compliance is not only about the physical product. Documentation is often part of the evidence that the product has been designed, assessed, built, and supported properly.
This may include specifications, risk assessments, test reports, bills of materials, drawings, firmware versions, user instructions, labels, declarations, production test records, and change control information. The required documentation depends on the product and market, but it is much easier to maintain when it is built into the development process.
Leaving documentation until the end can create gaps. Teams may struggle to explain why certain components were chosen, what tests were completed, which firmware version was assessed, or how production units will remain consistent with the tested sample.
Good documentation supports compliance, but it also supports manufacturing, servicing, redesign, and lifecycle support.
Common compliance mistakes
One common mistake is assuming that a product will pass because similar products already exist. The market may contain products that look comparable, but small differences in power architecture, enclosure design, wireless behaviour, battery integration, cables, or intended use can affect the requirements and test results.
Another mistake is treating compliance as the test lab’s responsibility. Test labs can assess products, but they do not remove the need for sound engineering decisions. Passing compliance depends on the design, not only the test process.
Teams may also underestimate the effect of late changes. A component substitution, PCB revision, enclosure change, battery replacement, firmware update, or supplier change can affect compliance assumptions. For in-market products, this becomes especially important when managing redesign or obsolescence.
Better practice is to design with compliance in mind
Compliance should be considered early, but that does not mean development needs to become slow or overly cautious. The practical approach is to identify likely requirements, understand which design decisions they affect, and review the product at sensible points during development.
For many products, this means considering compliance during system architecture, electronic development, enclosure design, battery selection, firmware planning, prototype testing, and preparation for manufacture. It also means involving specialist input where it changes the quality of the decision.
Analogue Consultants’ approach is built around practical product outcomes: defining the problem clearly, developing the right engineering route, preparing for manufacture, and supporting products through their lifecycle. Compliance fits naturally into that journey because it affects whether a product can be launched, built consistently, and supported with confidence.
For startups and SMEs, the main lesson is simple: do not wait until the product is finished to ask whether it can comply. By then, the answer may be more expensive than it needed to be.
Analogue Consultants
