Product Safety

When should OEMs conduct electromagnetic compatibility testing?

Lead Author

Marcus Trust

Published

2026.11.20

Views:

OEMs should plan electromagnetic compatibility (EMC) testing before the design is fixed, screen representative prototypes during development, and complete the required formal assessment on a production-representative product before market release. Testing may also be needed after release when changes to components, layout, software, installation or intended markets affect electromagnetic behavior or the basis of the original assessment.

For project leaders, the timing decision has two parts: when an early test can still influence the design, and when the product is stable enough for results to support a release decision. Waiting for the final laboratory appointment can expose a project to late redesign; testing only an early prototype leaves uncertainty about the product that will actually ship.

Set the test strategy before detailed design

EMC work should begin when the team defines the product’s intended markets, operating environment and main interfaces. At this stage, the project does not need a complete unit for a laboratory test, but it does need a working view of what must be assessed and what evidence the release will require.

A payment terminal intended for a commercial counter, for example, may have different installation conditions from a kiosk deployed in an industrial facility. The relevant assessment depends on factors such as power supply, cables, radio functions, connected equipment and intended use. Requirements also depend on the product category and destination market; a single test plan should not be assumed to cover every jurisdiction.

Before design choices become expensive to change, the engineering and compliance teams should agree on:

  • The intended markets and the applicable EMC requirements or standards for the product and its functions.
  • The product configurations, operating modes, cables and accessories likely to be relevant during testing.
  • Whether the release requires testing by a particular type of laboratory, third-party involvement or other supporting evidence.
  • The design milestones at which a representative unit can be screened and a final configuration can be assessed.

This early review also identifies schedule dependencies. If the product relies on an external power adapter, display, radio module or host system, its availability and configuration can affect the test setup. A certificate or test report for an individual component may be useful evidence, but it does not by itself establish the EMC performance of the assembled product.

Test prototypes while the design can still change

The first useful physical screening should occur once a prototype contains the elements likely to influence EMC: the main electronics, power conversion, enclosure concept, cable interfaces and representative operating functions. It does not have to look like a finished product, but the team should understand which differences from the planned release could limit the results.

At this stage, pre-compliance testing is a practical way to find emissions and immunity problems before committing to tooling, production boards or an enclosure design. Depending on the product and available equipment, the team may use bench measurements, near-field probes or a laboratory’s preliminary test setup. These checks can help locate interference sources and compare design changes, even when they do not reproduce every condition of a formal assessment.

Both sides of EMC deserve attention. Emissions testing examines whether the product generates unwanted electromagnetic disturbance; immunity testing examines whether it continues to operate acceptably when exposed to relevant disturbances. A terminal that appears quiet in an emissions scan may still reset during a disturbance, lose a communication link or behave unpredictably at a user interface.

The value of this screening depends on how the unit is exercised. Test modes should activate meaningful combinations of functions, such as display operation, network communication, printing, charging or connected peripherals where applicable. Teams should also consider cable lengths and routing, because a favorable bench arrangement may conceal a problem that appears in the intended installation.

Early results are most useful when the team records the configuration alongside the measurements: board and firmware versions, enclosure condition, power source, cables, peripherals and operating mode. That record gives engineers a basis for comparing the next prototype and helps prevent a passing result on one arrangement from being applied too broadly.

When should OEMs conduct electromagnetic compatibility testing?

Use pre-compliance results to decide when the design is ready

A prototype that passes an informal scan is not automatically ready for release testing. The project team should first ask whether the screened unit represents the intended production design closely enough, and whether the checks covered the emissions and immunity risks relevant to that product.

Pre-compliance is particularly valuable at design transition points: after the first integrated prototype, after a major layout or enclosure change, and before a design freeze. The exact number of iterations depends on the product’s complexity and the changes made. A simple device with a stable architecture may need a different program from a kiosk combining multiple power supplies, displays, communication modules and peripherals.

When a check reveals a problem, allow time for diagnosis, a corrective change and a repeat measurement. Potential remedies might include changes to filtering, grounding, shielding, cable routing or circuit layout, but the right correction depends on the source and coupling path. A project schedule that reserves only a laboratory slot and no engineering time for rework leaves little room to respond.

Results close to a limit also deserve a project decision. Measurement setup, configuration and normal variation between units can affect results, so a narrow pass in an early setup offers less confidence than a result with comfortable margin. The team can use another screening round to investigate the sensitive frequency range or operating mode before committing the final sample to formal testing.

Schedule formal assessment on a representative release configuration

Formal EMC testing should take place when the product’s hardware, firmware, enclosure, power arrangements and accessories are sufficiently stable to represent what will be placed on the market. The assessment should use the applicable methods and configurations identified in the compliance plan, with the necessary documentation and laboratory arrangements for the intended markets.

Do not interpret “final” as “after every other project decision.” The assessment needs to happen early enough for the team to respond if the product fails or if the test setup reveals an overlooked configuration. Laboratory availability, sample preparation, troubleshooting and repeat testing should all be visible in the launch schedule.

Before the appointment, the project lead should make sure the laboratory can operate the product in relevant modes and determine whether its performance remains acceptable during immunity tests. That may require test software, monitoring equipment, a way to exercise communications, or clear instructions for observing and recording failures. For a payment terminal, for instance, the plan might need to distinguish a temporary display disturbance from a reset or interruption of a transaction function, using criteria appropriate to the applicable requirements and product use.

Several product variants can complicate this decision. Different power supplies, cable arrangements, display sizes or peripheral combinations may affect EMC behavior. The team should agree on how variants will be assessed and document the technical basis for selecting representative or potentially challenging configurations. A result for one variant should not be extended to another solely because the products share a name or enclosure.

Once testing is complete, retain the report with the configuration and supporting technical records. That gives the release team a clear link between the evidence and the product version it covers, and gives later engineering teams a starting point when assessing changes.

Revisit EMC when the product or its use changes

EMC is a lifecycle concern because a product can change after its initial assessment. A replacement power supply, revised circuit board, new enclosure material, altered cable, firmware update or added wireless function may affect emissions, immunity, operating modes or the assumptions behind the original test. A new installation environment or destination market can also introduce different assessment needs.

Not every change calls for a complete test program. The first step is an engineering impact review: identify what changed, which electrical or mechanical paths may be affected, and whether the original test configuration and requirements still represent the product. The outcome may be a documented rationale for no additional testing, a targeted check, or a broader reassessment. The applicable market requirements and the significance of the change shape that decision.

Change control is especially important when several small substitutions accumulate. A replacement connector may appear minor in isolation, but its effect should be considered alongside changes to shielding, cable routing or the connected accessory. Keeping test reports linked to specific configurations makes that review more reliable.

For a project manager, the most useful milestone is therefore not simply “EMC passed.” It is an agreed release configuration supported by appropriate evidence, with a clear owner for reviewing later changes. That gives the team a practical basis for deciding when the next test is needed and how much of the original assessment remains relevant.

Tags

Recommended for You