How to Handle Inconsistent Quality System Certificates for Overseas Registration of Laboratory Equipment?

Key Summary

A practical guide for medical device manufacturers on addressing inconsistencies in quality system certificates (ISO 13485, CE, FDA, MDSAP, etc.) during overseas registration of laboratory equipment, including classification logic, evidence preparation, common pitfalls, and a compliance roadmap.

Published: August 26, 2026 17:57 | Updated: August 26, 2026 17:57

Key Summary

When registering laboratory equipment overseas, inconsistencies in quality system certificates are a common issue that can directly affect registration progress and certificate validity. Companies should first determine the regulatory classification of the device in the target country, confirm whether it is a medical device or in vitro diagnostic (IVD) product, and identify the risk class and registration pathway. Next, systematically review existing quality system certificates and audit reports, such as NMPA, CE, FDA, ISO 13485, and MDSAP, to identify differences and connection points across markets. Pay close attention to the quality management system scope, standard version, expiry date, issuing body, and audit findings, and align these with the product technical file. Common risks include: system certification scope not covering the manufacturing site, certificates not updated after regulatory requirements upgrade, submitting different versions of system certificates in multi-country filings, and lack of effective post-market surveillance evidence. Companies should clarify the responsibilities of the local agent or authorized representative, establish a unified system evidence package, and perform local adaptation to meet target country requirements, thereby reducing the risk of deficiency letters and rejection. For Chinese medical device companies, a prudent approach is to first conduct product classification and documentation gap assessment, then decide whether NMPA, CE, FDA, ISO 13485, or other market documentation can be reused. Registration in the target market typically affects technical files, authorized representatives, importer cooperation, label language, quality system evidence, and subsequent change management. If the project is driven only by a list of documents to submit, issues such as model coverage, evidence chain consistency, label claims, and certificate control can lead to deficiencies or rework. AIMEILI recommends integrating this issue into a broader GHWP member state and multi-country access strategy, using a reusable core technical documentation set to support local adaptation in different markets rather than preparing documents from scratch for each country.

Applicable Scenarios and Core Issues

Laboratory equipment is diverse, including analytical instruments, biosafety cabinets, centrifuges, PCR machines, and laboratory IVD devices. When registering overseas, companies generally need to submit quality system documentation to demonstrate that the product is designed and manufactured under a quality management system that meets international standards.

However, companies often face a challenging situation: the ISO 13485 certificate, CE system documents, FDA QSR audit reports, or MDSAP audit results they hold may not be fully consistent in scope, standard version, validity, issuing body, covered addresses, and product range.

For example, a company may hold an ISO 13485:2016 certificate, yet the CE system is based on Annex II of Directive 98/79/EC. Or an MDSAP audit report may cover Brazil, Canada, Japan, and other markets, but the target registration country requires an additional system declaration.

These inconsistencies can lead the registration review authority to question the adequacy and reliability of the quality system, prompting additional evidence requests, deficiency corrections, or even rejection. Therefore, companies must understand the reasons behind the inconsistencies and master effective response strategies.

Registration Judgment Logic

When faced with inconsistent quality system certificates, do not simply submit all existing certificates. Instead, follow a clear judgment framework.

Step 1: Determine if the product falls under medical device regulation in the target country

Not all laboratory equipment is regulated as a medical device. For example, general research instruments may not be, but laboratory instruments used for clinical testing may be classified as IVD or medical devices.

Step 2: Determine risk class and registration pathway

The target country will define the registration pathway, technical documentation requirements, and the form of quality system evidence based on the product risk classification (e.g., Class A/B/C/D or Class I/II/III).

Step 3: Assess reusability of existing NMPA, CE, FDA, ISO 13485, MDSAP, or other market documents

Focus on whether the standard version, certification scope, manufacturing address, and product description in the quality system evidence align with the device being registered.

Step 4: Confirm technical file, performance verification, risk management, clinical evaluation or evidence, labels and instructions, local agent, authorized representative, and post-market maintenance requirements

Quality system evidence is not isolated; it must corroborate the design control, risk management, and production control information in the product technical file.

For GHWP member states, multi-country registrations, Southeast Asia, the Middle East, Latin America, and other scenarios, companies should build a core technical document library, treat quality system evidence as foundational material, and then localize it according to target country regulations.

Documentation and Evidence

To address inconsistencies, companies need to systematically prepare the following materials and evidence:

Current copies of quality system certificates, including ISO 13485, CE system certificates, FDA establishment registration or QSR audit reports, and MDSAP audit reports.
System certification scope documents, such as certificate annexes, certification contracts, or audit reports, to clarify covered product categories, manufacturing addresses, and processes.
Most recent internal audit and management review reports to demonstrate the system continues to operate effectively.
Corrective action records for audit findings, especially critical nonconformities involving product design, production, and quality control.
Product technical file summaries, including design inputs/outputs, risk management reports, performance validation, and clinical evaluation materials, to prove the product is effectively controlled under the system.
Specific declarations or certificates required by target country regulations, such as free sale certificates, GMP certificates, or system declarations recognized by local regulatory authorities.

All documentation should form a complete evidence chain, not only proving that a system certificate exists but also that the system is effectively running and the product falls within the certificate scope.

If there are gaps in certificate validity, provide evidence of continuation after expiry, such as renewal acceptance notices or audit schedules.
If covered addresses are inconsistent, provide evidence of system updates when production sites moved, expanded, or new sites were added.
If multiple certificates with different standard versions exist, provide a standard version gap analysis explaining that the latest system already meets target country requirements.

Common Mistakes

Submitting only the most recent certificate and ignoring differences in coverage of other certificates, leading reviewers to question whether the product is actually within the system scope.
Not checking certificate expiry dates and using expired system certificates, resulting in invalid documentation.
Ignoring specific target country requirements for system standards, such as accepting only ISO 13485:2016 and not other equivalent standards.
Overlooking 'major nonconformities' in MDSAP audit reports and failing to explain corrective actions, making the system appear uncontrolled.
Not aligning certificates with product names, models, and descriptions in technical files, leading to model inconsistencies.
Submitting different versions of system documents to different markets in multi-country registrations, creating logical contradictions.
Not clarifying the role of the local agent or authorized representative in quality system communications, making it impossible for the issuing body to reach the responsible party.
Neglecting post-market surveillance records, such as adverse event reports, complaint handling, and CAPA evidence.

Company Preparation Checklist

Establish a cross-functional team involving quality, regulatory, production, and technical departments, with clear responsibilities.
Create a 'system certificate ledger' listing all quality system certificates, including number, issuing body, standard version, scope, expiry date, and audit status.
Review target country registration requirements item by item, defining the acceptance criteria for quality system evidence.
Compare existing certificates against target country requirements to produce a gap analysis report.
Contact the certification body to request scope expansion or version updates if necessary.
Prepare system operation evidence such as internal audit reports, management review reports, CAPA records, and complaint handling records.
Designate a local agent or authorized representative and sign an agreement clarifying their role in system communication.
Develop a post-market surveillance plan to ensure continuous compliance with target country quality system requirements after registration.

AIMEILI Insights

The most common mistake companies make is equating the possession of a system certificate with full compliance with all target country quality system requirements. In reality, the recognition approach, operational evidence, and scope requirements differ significantly across jurisdictions.

In the early phases of a project, the priority should be a 'system gap analysis' rather than rushing to prepare registration documents. First clarify the acceptable forms of system evidence and key review points in the target country, then work backward to identify gaps in existing system evidence.

Reusable materials include: ISO 13485 certificates, mature MDSAP audit reports, system operational records, and quality system elements within product technical files. Items that must be localized include: regulatory language for the target country, legal references, local agent declarations, adverse event reporting channels, and translation of system documents.

The local agent, certificate control, changes, and renewal are extremely important because the validity of quality system evidence is directly tied to certificate control. If the certificate is held by a third party or changes/renewals are not under your control, you cannot ensure ongoing validity or respond to unannounced inspections by the target country regulatory authority.

For multi-country registrations, AIMEILI strongly recommends establishing a unified quality system evidence package. Map all market system requirements onto the same core set of system documents to avoid duplicate preparation and multiple deficiency corrections. MDSAP multi-country audits can effectively reduce repeated audit costs, but additional preparation is still needed for markets not participating in MDSAP.

The ultimate goal is not to create a flawless certificate but to present a complete, coherent, and traceable quality system story that convinces reviewers the product has been manufactured under a controlled quality system and has ongoing compliance capability.

Common Follow-up Questions

Q: We do not have a valid ISO 13485 certificate, only a CE system certificate. Can we register directly?

It depends on whether the target country recognizes ISO 13485 as the exclusive system standard. Some countries accept CE system certificates as evidence, but may require proof of system scope and conformity. We recommend checking target country regulations or consulting the local regulatory authority. If only ISO 13485 is accepted, you must obtain that certification first.

Q: Can we use different versions of quality system certificates for the same product in different country registrations?

Yes, but consistency and logical coherence must be maintained. Different markets may accept different certificate versions, but during submission you should proactively explain why different versions are used and provide a standard gap analysis. The safest approach is to use the currently valid system as the basis and use the same version across all registration files to avoid unnecessary reviewer concerns.

Q: Can an MDSAP audit report be used directly as quality system evidence for all GHWP member states?

No. MDSAP is recognized by the International Medical Device Regulators Forum and includes the United States, Canada, Brazil, Japan, Australia, and other members, but not all GHWP member states participate. Some countries may reference MDSAP results but still require a country-specific system declaration or GMP certificate. Companies must verify whether the target country accepts MDSAP reports and prepare accordingly.

Q: What if the manufacturing address on the quality system certificate does not match the registered address?

First confirm whether there has been an actual address change. If the address changed due to relocation or expansion, the system certificate must be updated, and the updated certificate and supporting documents must be submitted. If the certificate simply does not include the new address, apply to the certification body for a scope extension or provide evidence demonstrating the new address is under the system, including audit arrangements.

Continuing Reading

Previous: How to prepare performance verification documentation for overseas registration of laboratory equipment?

Next: How to determine product classification for overseas registration of disinfection and sterilization equipment?

Content Review and Applicability Boundaries

Author: AIMEILI Regulatory Editorial Department

Professional Review: AIMEILI Medical Device International Registration Project Team

Source Principles: Priority is given to official regulatory authorities, international organizations, standards bodies, and public regulatory materials; industry media and project experience are used only as supplementary references.

Applicability Boundary: This article is intended for preliminary understanding, documentation preparation, and project planning. It does not replace the formal requirements of target country regulatory authorities, testing conclusions, or legal opinions.

Source and Language Notice

View Chinese original page

Need a registration pathway assessment?

Send product type, intended use, target countries and existing certificates. AIMEILI can help evaluate registration pathway, documentation gaps and compliance risks.

Contact AIMEILI