Using an Existing CE Certificate for Overseas Medical Device Registration: FAQ for Manufacturers

Published: 10 July 2026, 22:23 · Last updated: 10 July 2026, 22:23

Key Takeaways

A CE certificate does not act as a stand-alone registration approval outside the European Union. Where a manufacturer already holds a CE certificate, the first question to settle is whether the target country recognises CE marking as a basis for market access or requires its own local registration. In most markets, the CE technical documentation is accepted only as part of the registration dossier, and the certificate itself cannot replace a registration application.

Before any submission, confirm that the product falls within the target country's definition of a medical device, then establish the local risk classification and the corresponding registration route. Core documents normally include the CE technical file, ISO 13485 certificate, quality management system documentation, risk management report, clinical evaluation or clinical evidence, and labelling and instructions for use.

Some markets, including parts of Southeast Asia, the Middle East and Latin America, may permit partial reuse of CE documentation, but still require localisation: a local agent or authorised representative, labels in the local language, and a post-market surveillance plan. A frequent mistake is submitting the CE certificate in place of a registration application, or overlooking local differences and receiving a deficiency notice. Manufacturers are advised to confirm target-country requirements at the start of the project, assess documentation gaps, prioritise reuse of core technical documents, and settle arrangements for the local agent and certificate control.

For Chinese medical device manufacturers, the more reliable approach is to complete a product classification and documentation gap assessment first, and only then decide whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused. Registration in a target market typically affects the technical file, authorised representative, importer cooperation, label language, quality system evidence and subsequent change maintenance at the same time. If the project is driven only by the question of which documents to submit, deficiency letters and rework are likely to arise in model coverage, consistency of the evidence chain, label claims and certificate control. AIMEILI recommends planning this question within a unified GHWP member-state and multi-country market access strategy, using one reusable core technical file set to support localisation across markets, rather than rebuilding documentation country by country.

This article is compiled from AIMEILI's regulatory practice question bank, its knowledge base on international medical device registration, and publicly available regulatory information. For any specific project, the latest requirements of the target-country regulator and the product's documentation base should prevail.

Scope and Core Questions

After obtaining a CE certificate, manufacturers often want to use it for medical device registration in other countries in order to save time and cost. However, the degree to which different countries recognise a CE certificate varies considerably. The core question is: can a CE certificate be used directly as the basis for registration? Most countries do not recognise a CE certificate directly, but treat it as part of the technical file. Manufacturers must first confirm whether the target country treats CE as a reference or requires an independent local registration. For example, most ASEAN countries accept the CE technical file but still require local registration; some Middle Eastern countries recognise CE; Latin American countries require local registration and may ask for local clinical data. Manufacturers need to determine product classification at an early stage in order to identify the registration pathway.

Another key point is the scope covered by the CE certificate. If the certificate covers only certain models or a specific clinical intended use, it cannot simply be claimed as applicable to all products. Manufacturers must ensure that the certificate content matches the product being registered; otherwise a re-assessment is required.

How to Determine the Registration Pathway

• Step 1: Confirm whether the product falls within the target country's regulatory scope for medical devices. Each country has its own definition and exemption list; for example, wellness devices may not be treated as medical devices.
• Step 2: Determine the risk class. CE classification and local classification may differ; for instance, a Class IIa device may be treated as Class B in Southeast Asia, with different registration requirements.
• Step 3: Determine the registration route. Some countries offer simplified procedures, such as market access based on CE, but most require local registration.
• Step 4: Assess the applicant entity. A local agent or legal entity is usually required, and the CE certificate holder cannot apply directly.
• Step 5: Analyse the reusability of existing documentation. General sections of the CE technical file, such as risk management, biocompatibility and performance verification, can usually be reused, but the clinical evaluation may need localisation.
• Step 6: Confirm local requirements, such as language, format and additional testing.
• Step 7: Develop a plan covering agent appointment, document translation and submission of supplementary information.

Manufacturers should note that some countries require the manufacturing site to match the one stated on the CE certificate. If a different production line is used, additional explanation is needed. In addition, post-market changes or certificate renewals must be reflected in overseas registration information in a timely manner.

Documentation and Evidence

The following documents are usually required: a copy of the CE certificate (notarised or translated); the product technical file (including design description, raw materials and principle of operation); the quality management system certificate (ISO 13485); the risk management report (ISO 14971); performance verification and test reports; the clinical evaluation report or clinical evidence; labels and instructions for use (including versions in the local language); the local agent authorisation letter; the post-market surveillance plan; and the product registration application form. Some countries also require a Certificate of Free Sale (CFS), which can be obtained from the CE notified body or the competent authority. Manufacturers should treat the CE technical file as the core basis, but reorganise it according to local formats.

For example, Brazil requires the ANVISA format and Saudi Arabia requires the SFDA format, so local templates must be used. Incomplete documents or format mismatches are common causes of deficiency notices. Manufacturers are advised to build an internal documentation gap analysis table and check it item by item against the target-country checklist.

An existing FDA or MDSAP certificate can also help demonstrate the quality system, but the CE certificate remains the foundation. For high-risk products, local clinical data or expert review may be required, and manufacturers should prepare in advance.

Common Mistakes

• Submitting the CE certificate in place of a registration application, on the assumption that the certificate alone covers overseas requirements.
• Ignoring differences in product classification and mapping the CE class directly onto the target-country class, resulting in the wrong pathway.
• Failing to appoint a local agent or authorised representative, or appointing one whose qualifications do not meet local legal requirements.
• Submitting labels and instructions for use without a local-language version, or with content that is inconsistent with the CE labelling.
• Using an outdated clinical evaluation report, or citing data from the CE approval where the target country requires data from its own population.
• Using a quality management system certificate that has expired or does not cover the product concerned.
• Confusing the use of a CE certificate with that of a Certificate of Free Sale, and treating the CE certificate as proof of free sale.
• Failing to consider how post-market changes affect overseas registration, for example where a product improvement is not reflected in the registration information in time.

Pre-Project Checklist for Manufacturers

• Identify the target-country regulator and its official website, and download the latest registration guidance.
• Obtain a Chinese translation and notarised copy of the CE certificate, and confirm that it remains valid.
• Organise the product technical file, numbering chapters or providing an index in line with local requirements.
• Update the risk management report to take account of country-specific risks, such as climate and power grid differences.
• Sign an agreement with the local agent that clearly defines responsibilities and the obligations of both parties.
• Translate and adapt labels and instructions for use, ensuring compliance with local language and regulatory requirements.
• Prepare a post-market surveillance plan, including an adverse event reporting process.
• Confirm whether additional annual updates or certificate renewals are required.
• Establish a document control process to ensure that overseas registration documents are updated whenever the CE certificate changes.
• Plan the budget, covering registration fees, agent fees, translation and notarisation costs, and additional testing fees.

AIMEILI's Perspective

The most common misjudgement is treating the CE certificate as a master key that can be used directly overseas. In practice, a CE certificate can usually serve only as part of the technical file, and it must still pass through the local registration process. At the start of a project, manufacturers should prioritise regulatory research on the target country rather than applying CE documentation as it stands. We recommend building a matrix of product classification and registration pathways. Core technical documents, such as risk management, biocompatibility and electrical safety, can generally be reused, but the clinical evaluation and labelling must be localised. The choice of local agent is critical: the agent must not only hold the required qualifications, but also be able to take continuous responsibility for post-market surveillance and change management.

On certificate control, the CE certificate is issued by a notified body, while overseas registration certificates belong to the local regulator; manufacturers must ensure that all registration information is updated in a synchronised way when changes occur. For multi-country registration, a single core document set plus country-specific difference packages is advisable, to avoid duplicated work. Deficiency notices are a common risk, and an early gap analysis can significantly reduce wasted time and money. Finally, manufacturers should build an internal regulatory knowledge base and accumulate registration experience across countries.

Frequently Asked Questions

If we already hold a CE certificate, do we still need a local clinical evaluation?

It depends on the market and the product. Some countries, such as Saudi Arabia and Brazil, require local clinical data or expert review for high-risk products. Even where the CE clinical evaluation report is accepted, additional local population data or epidemiological information may be requested. Manufacturers are advised to consult the local agent or a regulatory consultant at the start of the project.

Can an expired CE certificate still be used for an overseas registration application?

No. The CE certificate must be within its validity period. Some countries do allow registration applications submitted before expiry to continue through review. If the certificate has expired, it must first be renewed or transitional arrangements documented. Applying with an expired certificate is not advisable.

Can the same set of CE documentation be used for registration in multiple countries?

It can serve as the basis, but formats must be adjusted and local content added in line with each country's requirements. For example, the order of technical file sections may differ, and label languages will differ. We recommend building a core document library and preparing a conversion package for each country, covering format adjustments, translation and additional declarations.

Practical Implementation Guidance

In practice, manufacturers should break this question into five tasks: regulatory assessment, document preparation, evidence reuse, localisation conversion and post-market maintenance. It should not be left to a single department to assemble documents at short notice. This approach identifies documentation gaps earlier and helps sales, R&D, quality and regulatory teams form a consistent understanding of target-country requirements.

Where a manufacturer plans to enter several markets at the same time, it is advisable to establish a unified core technical file first, and then add authorisations, labels, languages, forms and local agent documents for each country. The efficiency of multi-country registration usually depends on whether the upfront documentation framework is unified, rather than on how quickly a single country submission can be filed.

• Confirm first whether the product falls within the target country's medical device regulatory scope.
• Then confirm the risk class, registration pathway and applicant entity.
• Check that the technical file, quality system and clinical evidence support one another.
• Clarify the local agent, authorised representative and certificate control arrangements.
• Establish mechanisms for post-market change, certificate renewal and vigilance event maintenance.

Related Reading

• Previous: How should multiple models be grouped for overseas medical device registration?
• Next: How can existing FDA documentation be converted for overseas medical device registration?
• Preparing technical documentation for overseas registration of software as a medical device
• How to validate algorithms for overseas registration of AI-based medical devices
• How to plan documentation for Southeast Asian medical device registration in a unified way
• What are the risks of using a local agent for Middle East medical device registration?
• Why do Latin American medical device registration timelines tend to be extended?
• How to determine product classification for overseas medical device registration

Content Review and Scope of Application

Author: AIMEILI Regulatory Editorial Team. Professional review: AIMEILI Medical Device International Registration Project Team. Source principles: official regulatory authorities, international organisations, standards bodies and publicly available regulatory materials are given priority; industry media and project experience are used only as supporting judgement. Scope of application: this article supports preliminary understanding, document preparation and project planning. It does not replace the formal requirements of the target-country regulator, testing conclusions or legal advice.