Skip to main content
  1. Home
  2. Technical Blog
  3. Standards Explained
  4. EMC access to the EU: how UN ECE R10 relates to CE marking

EMC access to the EU: how UN ECE R10 relates to CE marking

Key takeaways

EMC access for automotive electronics exported to the EU centres on UN ECE R10 (mirrored domestically by GB 30512), which covers electromagnetic compatibility of vehicles and their electrical and electronic systems and forms part of whole-vehicle type approval. On the component side, CISPR 25 is normally used for pre-compliance, while formal certification is carried out by a body holding issuing authority; we provide testing together with global certification support.

For a whole vehicle exported to the EU, EMC is not "what the customer asked for" — it is an access condition. UN ECE R10 is that threshold, and it is adopted identically in China as GB 30512.

1. What R10 covers

R10 covers the electromagnetic compatibility of vehicle electrical and electronic systems: on the emission side it limits interference the vehicle causes to radio reception and the power network; on the immunity side it verifies that the vehicle can be driven safely in an interference field, with specific criteria for steering- and braking-related functions. Passing it yields the e-mark, one of the prerequisites for registration in an EU member state.

2. How it relates to CE

A common confusion: CE is the conformity mark under the EU directive framework, and whole vehicles fall under the whole vehicle type approval (WVTA) system, where the EMC element is delivered through R10. It is electronic components fitted to the vehicle (charging posts, aftermarket electronics) that more often go through the CE framework. Before starting export work, be clear whether the object is a whole vehicle or a component — the routes are entirely different.

3. What suppliers should prepare

  • Pre-compliance: run emission and immunity pre-compliance on the component to CISPR 25 / ISO 11452, so problems are solved before the vehicle is submitted
  • Check the revision: R10 has amendments and transition arrangements — use the version currently in force in the target market
  • Technical file: test reports, circuit diagrams and the critical component list must be able to support the approval audit
  • Formal approval: carried out by a body with issuing authority — the test data can be reused

4. The usual timeline mistake

Treating "pre-compliance passed" as "approval granted" is the most common misjudgement — pre-compliance only answers the technical risk, while approval also involves documents, sample confirmation and the issuing process. Start both tracks in parallel: pre-compliance and corrective work on one side, technical documentation on the other, so components do not let the vehicle submission down.

Turnaround time is arranged according to the actual project. You are welcome to state your target date when submitting samples; we will check it against the current schedule, confirm a feasible plan with you, and update you at each milestone.

Related Q&A

Related questions

Frequently asked questions on the same topic. The first paragraph of each answer is the conclusion.

What is the difference between a test report and an inspection report?

A test report is data-centric—measured values and verdicts, mostly for R&D pre-scan and process records. An inspection report is issued under the accreditation process and is usable for formal scenarios such as customer acceptance and supply-chain audits. Confirm the intended use before commissioning, to avoid redoing it with the wrong type.

How are reports delivered—electronic or paper?

Electronic by default (PDF with signature and seal); paper copies are stated at commissioning and shipped with the report. Chinese and English versions can be issued on request; the English version follows the Chinese original.

If you need data first for internal review, a staged delivery arrangement can be agreed separately.

Do reports have an expiry date?

A report has no statutory validity period—it attests to the submitted sample's performance under the test conditions. The accepting party (customer, OEM, certification body, tender) sets its own limits, usually tied to product version and standard revision.

After design, critical component or supplier changes, the original report generally no longer represents the current product and should be reassessed.

These answers share the same data source as the FAQ page.

Have a testing requirement? Send us your product details

Tell us the product model and test requirements. Our engineers will map out the test plan, the applicable standards and the item combination, and provide a quotation reference. The more specific the request, the sharper the answer.

  • Free scoping of the test plan and standards
  • Pre-scan testing during R&D to cut rework cost
  • On-site visits and witnessed testing supported
  • Scheduling per project, with progress updates at each milestone

Received — we will contact you shortly and follow up with a test plan and quotation.

By submitting you agree to be contacted by phone or email. Scheduling follows the project’s actual availability and is subject to mutual confirmation.

13510907826