Can One Test Report Cover Multiple Markets?

← All guides

You have the test report in hand. EMC measured, safety covered, the standards listed on page two. Then a US distributor asks for "compliance documents", a UK buyer wants evidence of marking, and a Korean importer mentions KC registration. The question shows up in some form almost every week: can one test report cover multiple markets?

The honest answer: the measurements inside a report can be reused far more than the report itself. Knowing which part travels and which part stays home is the difference between a small delta test and an unnecessary second full project.

First, be clear about what a report is and is not

A test report is a laboratory's record of what was tested, against which standards and editions, and what the results were. It proves what happened on that bench, to that configuration, on those dates. It is not an approval. A certificate is a third party's attestation, a Declaration of Conformity is the manufacturer's own declaration, and certification is the process a specific scheme puts a product through. If that distinction feels blurry, it is worth reading our breakdown of test report vs certificate first, because most cross-border confusion starts there.

Why does this matter here? Because "my report covers several markets" usually means one of two very different things: the data is reusable, or the document is accepted. Those are two different questions, and only the first one is usually yes.

Where one report genuinely does travel

Three mechanisms make reuse real.

Shared standard families. Many national frameworks are built on the same IEC, CISPR and ETSI base documents. EN 55032 is the European adoption of CISPR 32; EN 62368-1 is IEC 62368-1 with European deviations; ETSI EN 300 328 governs 2.4 GHz wideband equipment across Europe. When a laboratory tests to the base standard with each destination's deviations in mind, those measurements are valid inputs for several countries' frameworks at once.

The CB Scheme. The IECEE CB Scheme exists precisely for this: test reports and certificates mutually recognized among the member national certification bodies, with the destination country's body issuing its national certificate based on them. In practice it is used overwhelmingly for safety standards, and radio equipment approvals sit outside it entirely. Two limits matter even for safety: the destination certificate still has to be issued locally, and the country's national deviations are assessed on top of the shared report.

Aligned emission limits. The FCC Part 15 Subpart B limits for unintentional radiators align closely with the CISPR Class B limits, so a properly planned bench session can produce both an EN-based report and an FCC report from the same measurements. This only works when it is arranged in advance, with the FCC measurement procedures applied and the laboratory holding the accreditation the FCC route requires.

Four things that stop a report at the border

1. Different standard editions or citations. A report citing a superseded edition fails checks in another market even when the measurements themselves are unremarkable. Acceptance tracks the citation, not the test date.
2. Different test conditions. Europe runs on 230 V / 50 Hz, North America on 120 V / 60 Hz. Mains-dependent measurements such as conducted emissions differ between the two supply conditions, and the harmonic current limits of EN 61000-3-2 have no FCC equivalent at all. For radio products, band edges and regional frequency plans are not shared: the US 902–928 MHz band has no European counterpart, and even inside the common 2.4 GHz band the applicable rule parts, power limits and measurement procedures differ between the FCC and ETSI frameworks.
3. Local acceptance routes. Even with identical data, the approval paperwork is local. In the EU, the manufacturer signs a Declaration of Conformity against harmonised standards - no third-party certificate is required for most products. In the US, radio products need Certification with an FCC ID granted through a Telecommunication Certification Body, and since mid-2017 the FCC requires the laboratory performing the testing for such an application to be accredited; SDoC needs a responsible party based in the United States. Korea's KC scheme runs through designated laboratories and registration procedures, Japan's giteki registration goes through a registered certification body, and India's BIS registration requires testing at recognized laboratories. In each of these, a foreign report is an input at best - never the approval itself.
4. The document set differs even when the tests match. The same Bluetooth speaker ends up with an EU DoC, an FCC ID in a public database, a UK declaration citing designated standards, and an RCM supplier declaration for Australia. The report supports all four. It replaces none of them.

Destination	What often carries over	What normally does not
European Union	The report itself, if standards and editions are current	Nothing else - the DoC is yours to sign, and marking rules apply
United States	EMC measurements when planned as such; safety data as CB input	The report as approval - the FCC route needs its own procedures, an accredited laboratory, and an FCC ID where radio is used
United Kingdom	Measurements to EN-based designated standards	The EU DoC - the UK declaration cites UK regulations
Korea / Japan / India	Raw data as input, where arrangements allow	Direct use of the report - local registration or certification applies

Four situations where this actually comes up

The 230-volt-only report. A team completes CE testing on a mains-powered product, then finds a US distributor. Most of the radiated emissions data carries over. The conducted emissions were measured at 230 V, the FCC review expects the US supply condition, and the harmonic measurements have no US use at all. The fix is a short delta session - but only because the original scope was known to be EU-only. Nobody can retrofit 120 V data from a report that never contains it.

The radio tested for Europe. A product with a 2.4 GHz radio tested to ETSI EN 300 328 is not automatically FCC-compliant. The US filing needs measurements under the applicable FCC rule part - for 2.4 GHz devices typically §15.247 - including the US limits and procedures, performed by an accredited laboratory, and an FCC ID granted through a TCB. Some of the bench setup repeats; a good part does not. And if the radio module itself was certified separately, its grant does not transfer automatically to the finished product - permissive change rules decide what retesting applies.

The CB report doing its job properly. A buyer in a third country asked for a national safety certificate. Because the original project produced a CB test report alongside the EU file, the destination certification body issued the national certificate from it, assessing the country's deviations on top. That is the system working as designed - possible because the safety testing was done to an IEC base standard and the CB documents were produced within the same project.

The edition problem. A report was issued against a standard edition that had since been replaced in the destination market's list. The measurements were fine. The report still had to be assessed and re-issued against the current edition before the buyer's compliance team would accept it. Whether anything retests depends on what changed between editions - which is one of the reasons edition currency, not just the test date, decides how long a test report stays valid.

How to plan one project that serves several markets

Reuse is planned, never discovered. Before booking anything:

• List the destination markets first. "EU now, US later" usually costs more than "EU and US together" - a second bench session can often be avoided entirely when both scopes are declared at quotation time.
• Ask the laboratory to state, per market, the standards and editions, the supply conditions to be tested, and the document each market will need. If a quote cannot answer that, the scope is not really defined.
• Check accreditation against the route, not just the test. An accredited EMC laboratory without the recognition required for FCC Certification filings cannot support the US radio route, no matter how good its reports look.
• Decide who signs what. The EU DoC is signed by the manufacturer or the responsible person; the US SDoC needs a US-based responsible party; certificates come from the bodies each scheme names. Build these into the schedule - they take days, not minutes.

None of this requires the report to be rewritten. It requires the scope to be written correctly the first time.

How we plan multi-market projects

This is routine work for us. When a client sends a product with more than one destination market, the quotation maps each market to its standards, editions, supply conditions and required documents, and separates what one bench session can cover from what genuinely needs a second booking or a local body. Where a CB report or a delta test saves bench time, the quote says so; where it does not, the quote explains why. The aim is that when the first report is delivered, the second market is a decision, not a surprise. The testing and certification overview shows the routes we support, and the certification pages by destination describe what each market expects.