CE to EAC: Why Conversion Is Not Possible

Bottom line first: CE and EAC are two legal systems, and "converting a certificate" does not exist. EU CE is a manufacturer's commitment of conformity with EU directives; EAC certification or declaration in Russia and the Eurasian Economic Union (EAEU) is a mandatory conformity assessment completed by an entity inside the Union under Union technical regulations. The two run in parallel and do not recognise each other. What is sold as "convert your CE report to EAC", "pay more and swap the certificate" or "no retesting needed" is, plainly, the reuse of technical data dressed up as inherited legal validity.

Only part of the technical data can be reused — circuits, construction, key components and some test methods may overlap. What cannot be reused is legal validity: who signed it, under whose regulation, who holds the permission, and who carries the liability when something goes wrong. The CE system and the EAC system give completely different answers to those four questions.

This article lays it out plainly: where the two systems differ, why "conversion" does not hold, the two EAC routes, who is eligible to apply, how testing and factory audits are handled, and the misconceptions that keep coming up.

1. The essential difference between CE and EAC: not two versions of one standard

People often argue for mutual conversion on the grounds that the EN standards in their CE report look much like the requirements of an EAC technical regulation. That reasoning has some merit technically and none at all legally. The table makes it clear:

In other words: CE governs whether you can enter the EU; EAC governs whether you can enter Russia, Belarus, Kazakhstan, Armenia and Kyrgyzstan. Two customs territories, two regulators, two penalty regimes. To an EAEU customs officer, that CE certificate in your hand carries about as much information as a product manual — you may read it, but it is not a pass.

2. Why the "conversion" route does not work: three breaks

What is called "conversion" is really an invalid substitution at three points. Break any one of them and the whole thing collapses.

① Legal break: a different signatory, a different party to answer to

A CE self-declaration is the manufacturer's commitment to the EU market; an NB certificate is a type-examination conclusion reached by a notified body under EU directives. An EAC certificate or declaration is a conformity assessment conclusion issued by a certification body inside the EAEU system under Union technical regulations. The issuing entity, the governing text and the regulator are all different, and no provision allows one to take over the legal standing of the other.

② Testing break: who issued the report decides whether it can be used

This is a frequently asked practical question. EAEU conformity assessment requires testing to be completed in a laboratory within the Union's accreditation system. Reports from EU notified bodies, third-party laboratories in China, or even the overseas branches of large international organisations usually serve only as technical reference in the EAEU system and cannot directly serve as the test basis for conformity assessment. Russia's acceptance of foreign reports and foreign laboratories has been tightening in recent years; the current Russian requirements prevail.

③ Applicant break: who is eligible to "be" the applicant on the document

This one is often overlooked, and it is why many projects stall. The applicant for an EAC certificate or declaration must be a legal entity in the EAEU. You may be a Chinese manufacturer with the product, reports and documents all complete, and still cannot apply in your own name — an entity inside the Union has to take on the filing and certificate-holding role. Until that is resolved, the other two preparations achieve nothing. See Section 4.

3. The two EAC routes: certification and declaration, so pick the right door

EAC is not a single document but two types of conformity assessment activity. Which one applies is determined by the Union technical regulation covering your product and its conformity assessment scheme — not chosen by the client or the supplier.

Three reminders, all of them drawn from real questions:

• The route is not a choice; it is set by law. The same product under a different technical regulation may be a certification or a declaration. Use the wrong form and neither customs nor the platforms will accept it — it is the same as not having done it.
• A declaration does not mean "no third party". A declaration puts conformity liability on the applicant, but the test evidence and document set behind it must be just as complete, and must withstand review. Printing a page yourself does not count.
• One certificate does not cover an entire product range. EAC scope is tied to the product, the technical regulation and the certification scheme. Changing construction, swapping a key component or adding a function can all touch the boundary where a variation or a fresh assessment is required.

If you are unsure whether your product takes the certification or the declaration route, do not copy a peer's "experience" — their product may fall under a different technical regulation. The EAC knowledge base sorts this by product category, or you can send us the product parameters for a determination.

4. Who is eligible to apply: the applicant must be an EAEU legal entity

This is the hard rule in the whole process, and the one that is often blurred by "we handle everything" sales talk.

Under EAEU conformity assessment rules, the applicant for an EAC certificate or declaration must be a legal entity in the Union. In real business, the lawful arrangements commonly look like this:

• Importer filing. The Union-based company that actually imports the consignment acts as applicant. This is fairly common in trading scenarios.
• Local representative arrangement. The manufacturer signs a formal authorisation and agency agreement with a Union legal entity, which then takes on the filing and certificate-holding role within the agreed scope.
• The manufacturer's own legal entity in the Union. For example a lawfully established subsidiary or representative office with the required legal standing, taking it on under local rules.

There is another layer to think through in advance: what legal liability the certificate holder and the filing entity each carry must be confirmed by the client against its own transaction structure, with local legal counsel where necessary. That is not something a certification body can decide for you, and not something we can cover for you in a contract. If a conformity problem arises on a certificate held in someone else's name — who is pursued, whether you can recover, whether recovery is enforceable — all of that should be written down before the agency agreement is signed.

So when a client asks "can the certificate be held in your name", the answer is no — we are not eligible for that and we do not make such arrangements. What we can do is make the technical side solid, determine the route clearly, and spell out what documents each party needs when you deal with a local entity. That is the extent of it.

5. Testing and factory audit: what CE data can and cannot be reused

This is the part of the article with some good news. Technical material built up during a CE project does save time and rework, but you need to separate what it saves from what it does not.

Testing. Core testing has to be completed in a Union-accredited laboratory. The value of a CE report is that the laboratory can look at your existing data, define the test list faster, judge which items need priority retesting and how the samples should be prepared. That is not "testing waived", but it does reduce wasted scheduling. Whether a specific item can be reduced or waived is subject to the assessment of the certification body and the laboratory — do not rely on a middleman's assurances, because the person giving assurances usually does not carry the consequences.

Factory audit. Some products and some certification schemes require an audit of the production site, examining whether the quality system can sustain batch consistency: incoming control, process control, final inspection, measuring instruments, change management. Under CE this step is rare outside specific categories, so many factories face it for the first time.

• Before the audit, assemble system documents, inspection records and equipment calibration records into a set — do not go rummaging through cabinets on the day;
• The audit asks whether you can consistently make what you submitted for testing, not how nicely the documents are written;
• Nonconformities raised on site usually require a corrective action plan, and how quickly it is closed directly affects the certificate timeline.

Annual surveillance. Certificates with a longer validity (for example 5 years) usually involve an annual surveillance audit, to confirm that production and the system have not drifted since certification. The specific requirements and frequency are subject to the current Russian rules; different schemes and different bodies may apply them differently, so ask at project kick-off rather than remembering in year two that this arrangement exists.

6. Timeline and cost structure: where the money goes, and why we cannot quote a figure

I will not give figures in this section; giving them would be irresponsible. EAC project timelines and costs vary widely with the product, the technical regulation, the certification scheme, the test items, whether a factory audit is needed and whether corrective retesting is required. Any "fixed price" quoted before the product documentation has been seen will either grow add-ons later or quietly cut the depth of testing.

What can be explained is the structure. Match these blocks against a quotation and you will see what belongs in it and what is missing:

Timelines run the same way: they depend on body scheduling, laboratory slots, factory audit arrangements and how fast corrective actions are closed. Subject to the body's assessment. If you genuinely face a delivery deadline, the right move is to give the product documentation to the assessing party first, so that scheduling and test scope are fixed together — not to promise a date and then compress the testing backwards from it.

7. Four common misconceptions, taken one by one

① "I already have CE, so why do I need EAC?"

Because CE's effect stops at the EU border. Once a product enters the EAEU customs territory, customs and market surveillance look for the conformity assessment document under Union technical regulations. The technical content overlaps; the legal effect is entirely different — hold on to that sentence. Having CE means your product's design, components and safety approach are likely to hold up, which makes the EAC project easier to pass; but "easier to pass" and "does not need to be done" are two different things.

② "Can I use a foreign report?"

Usually not, or at least not as the basis for a conformity assessment conclusion. Testing has to be completed within the Union accreditation system, and foreign reports generally serve as technical reference only. Russia's acceptance of foreign reports and foreign laboratories has been tightening; the current Russian requirements prevail. One case to watch: some product schemes allow existing test material to be submitted for the body's evaluation, but "allowed to be submitted for evaluation" is not "accepted directly" — the conclusion still comes from the body and the laboratory.

③ "Can I find someone to hold the certificate in their name?"

Not advisable, and not worth spending time on. EAC applicant eligibility belongs to EAEU legal entities; that is a threshold set by regulation, not a procedural formality. Holding a certificate under someone else's name, borrowing a certificate or using a nominee looks convenient but takes on three risks at once: the certificate's authenticity will not survive review; the goods will not match the entity at customs or on a platform review; and when a conformity problem arises, the liability split among holder, importer and manufacturer becomes a mess — and as the actual manufacturer you usually cannot walk away.

The correct posture is to make it a lawful commercial structure: sign a formal agreement with a Union importer or local representative, setting out the scope of authorisation, the certificate-holding role, fees, variation and termination conditions, and liability and recourse if something goes wrong. At the same time, the respective legal liability of the certificate holder and the filing entity must be confirmed by the client — we always raise this before a project starts, because afterwards it cannot be remedied.

④ "EAC only covers Russia; I will need another set for Kazakhstan"

It is the other way round. EAC is a Union-level system, and one conformity assessment document is valid across member states, provided the product, the technical regulation and the certification scheme all line up. What actually deserves attention is the other end: product changes, key component substitution and added functions may trigger a fresh assessment; and some categories carry member-state national requirements on top of Union rules. Both undercut the idea of "do it once and forget it for five years".

8. The right approach: replace "conversion" with "rebuilding", in four steps

Change the framing and things flow: do not ask "can my CE be converted", ask "which technical regulation does this product fall under in the EAEU, which scheme applies, and who will be the applicant". Once those have answers, the project has a route.

Three of the four steps take real time; preparing early saves a lot:

• Rebuild the technical file to Union conventions. Translating the CE technical documentation is not enough — clause mapping, test coverage, and label and manual language all have to be reorganised to Union requirements.
• Self-check samples and key components first. Samples submitted for testing that do not match the production state are a common cause of rework. If a key component changed brand or rating without a BOM update, the testing may pass and the factory audit will still expose it.
• Settle the entity arrangement before testing. Many projects finish testing only to find the applicant is not in place, wasting a whole cycle. This should be fixed in the same week the project starts.

Action checklist

1. Identify which technical regulation the product falls under. Match by function and use, not by a peer's product.
2. Confirm certification or declaration. Get this step wrong and everything downstream is redone.
3. Secure the EAEU applicant entity. Use a formal agreement and write the scope of authorisation and liability clauses clearly; the legal liability of the certificate holder and the filing entity is confirmed by the client.
4. Organise existing technical material. Circuits, BOM, construction, key component certificates, manuals — archive what is reusable first; the time saved comes from here.
5. Arrange testing at a Union-accredited laboratory. Submit CE reports as reference, not as the test basis.
6. Confirm whether a factory audit is required. If it is, prepare system documents and inspection records early and allow time for corrective action.
7. Plan annual surveillance and change management. Arrange surveillance for longer-validity certificates under current rules, and route product changes through the filing process.
8. Build the records into a system. Certificates, test reports, technical files and audit records filed in one place, so they can be produced at customs or marketplace checks.

One more thing: do not let the CE side lapse either. The EU and the EAEU are two markets, and only by maintaining and updating two document sets separately will one not collapse while the other advances. For CE route decisions see the CE/RED knowledge base and more CE route analysis; the boundaries of reusing reports across countries are set out in more detail in the report transfer map.

The threshold to the Russian market was never "do you have a certificate", but "who signed this certificate under what rules, and can you clear customs and list your product with it". Once that is clear, many shortcuts that looked worthwhile naturally stop looking worthwhile.

▍Questions about this article? Leave a comment or message me, with the note "Russia"

▍One-line value proposition: We help you get export certification done and clear customs smoothly.

Further reading: EAC knowledge base, Russia e-commerce rules and EAC/GOST-R, report transfer map across countries, export certification services overview, EU CE certification services, certification quick lookup tool.