How Is Product Classification Determined for Medical Device Registration in South Africa?

To determine the correct product classification for medical device registration in South Africa, a manufacturer should first confirm the target country, the product's risk class, the applicable regulatory pathway and the documentation already available, and only then assess the technical file, quality system evidence, labelling and instructions for use, local agent arrangements, clinical evidence and post-market maintenance requirements. AIMEILI recommends completing a documentation gap assessment before formal submission so that an unclear classification, an incomplete dossier or an undefined authorisation arrangement does not unnecessarily extend the project timeline. For Chinese medical device manufacturers, the more reliable approach is to complete product classification and a documentation gap assessment first, and then determine whether NMPA, CE, FDA, ISO 13485 or other market documentation can be reused.

Published: 11 July 2026, 18:47  |  Updated: 11 July 2026, 18:47

This FAQ addresses the questions companies most often need to resolve first in international medical device registration, documentation preparation, compliance pathways and post-market maintenance.

Key Points

On the question of how product classification for South Africa registration should be determined, companies should first confirm the target country, the product's risk class, the applicable regulatory pathway and the existing documentation base, and then evaluate technical documentation, quality system evidence, labelling and instructions for use, local agency arrangements, clinical evidence and post-market maintenance requirements. AIMEILI recommends a documentation gap assessment before formal submission to avoid prolonged project timelines caused by unclear classification, incomplete documentation or undefined authorisation arrangements.

For Chinese medical device manufacturers, the more prudent approach is to complete product classification and a documentation gap assessment first, and 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 arrangements, importer cooperation, label language, quality system certification and subsequent change maintenance at the same time. If a project is driven only by the question of which documents to submit, deficiencies and rework are likely to arise in model coverage, evidence chain consistency, label claims and certificate control. AIMEILI recommends positioning this question within a GHWP member state and multi-country market access strategy, using one reusable core technical file to support localisation in different markets rather than rebuilding documentation from scratch for each country.

Scope and Core Questions

Companies that look into how product classification for South Africa registration is determined are usually not seeking a conceptual explanation. They want to know whether their existing documentation can support a submission in the target market, whether a local agent or authorised representative is required, why timelines are extended, and which issues may affect the launch plan. Behind this question are product classification, registration pathway, evidence chain, label localisation and post-market maintenance responsibilities.

Where a company plans to enter several GHWP member states or markets in Southeast Asia, the Middle East and Latin America at the same time, answering the process for a single country is not sufficient. A more valuable approach is to first prepare the core technical file, quality system evidence, performance verification, clinical evidence and labelling in a reusable version, and then localise them according to each country's regulatory requirements.

Registration Determination Logic

Companies should first confirm the intended use, mechanism of action, use scenario, method and duration of body contact, sterility, whether the device is active, and whether it includes software or has IVD characteristics, before determining the risk class and the submission pathway. Once the pathway is wrongly identified, all subsequent translation, notarisation, authorisation, testing and supplementary documentation will move in the wrong direction.

For a target market project, the applicant entity and local responsibility boundaries must also be confirmed: who holds the certificate, who is responsible for regulatory communication, who handles importation and post-market events, who triggers changes, and who maintains renewal documentation. If these points are only addressed vaguely in a commercial contract, market control can easily be affected later.

Documentation and Evidence

Typical documentation includes the product description, model and specification matrix, intended use, basis for risk classification, ISO 13485 or applicable quality system evidence, technical file, performance verification reports, risk management file, clinical evaluation or clinical evidence, labelling and instructions for use, authorisation documents, existing registration certificates, manufacturer's declarations and post-market surveillance documentation.

The key to documentation quality is not volume but consistency. Instructions for use claims, the models covered by test reports, the scope of clinical evidence, risk management conclusions, label warnings and information in the registration application form must all support one another. Regulators focus on whether the device is safe, effective and traceable for its intended use, not on the number of documents uploaded.

Common Pitfalls

The most common problem is treating a registration project as a simple document submission without first clarifying product classification, evidence coverage and local responsibility relationships.

• Translating NMPA documentation directly and submitting it without reorganising the evidence according to the target market pathway.
• Having too many models and specifications while test reports, clinical evidence or labels do not cover them adequately.
• Selecting a local agent purely on the basis of a sales partnership, without clarifying regulatory responsibility, certificate control and post-market maintenance obligations.
• Inconsistency between labels, instructions for use, promotional material and registration claims, leading to deficiency letters or post-market compliance risk.
• Failing to plan for multi-country documentation reuse in advance, resulting in duplicated preparation for each country and inflated cost and timelines.

Company Preparation Checklist

Before starting a project, companies are advised to confirm their documentation base using an internal checklist, so that key evidence gaps are not discovered only after submission.

• Compile the target product list, model and specification matrix and intended use statements.
• Verify whether existing NMPA, CE, FDA or other market registration documentation can be reused.
• Prepare the ISO 13485 certificate, test reports, risk management file, clinical evaluation and English instructions for use.
• Confirm the responsibilities, fees, certificate control and exit arrangements of the local agent or authorised representative.
• Establish a target-country gap assessment table identifying what must be retested, translated, notarised or supported by supplementary declarations.

AIMEILI's Perspective

AIMEILI advises companies not to view registration in a target market as a one-off document submission, but to manage it as an overseas market access programme. For companies entering several countries, building a clear core technical file and evidence matrix first and then converting it to each national requirement is generally faster, more stable and more conducive to later changes and certificate renewals than assembling documentation country by country on an ad hoc basis.

From a project management perspective, three matters should be controlled early: first, product classification and pathway determination; second, consistency of the documentation evidence chain; and third, the regulatory responsibility boundaries of local partners. Unless these three items are clear, a project may still encounter repeated rounds of deficiency response, agent communication and post-market maintenance, however extensive the documentation appears to be.

Frequently Asked Follow-Up Questions

Can domestic documentation be used directly for registration in the target market?

Domestic documentation can serve as a basis, but it usually cannot be submitted as it stands. Companies need to adjust the documentation structure, language, labelling, authorisation documents and evidence chain in line with local regulatory requirements.

When is the best time to start a gap assessment?

It is recommended to start immediately after the target market and product list have been confirmed. The earlier the gap assessment is completed, the easier it is to arrange retesting, translation, label adjustments and agent selection in advance.

Why does the choice of local agent affect registration quality?

A local agent typically participates in registration communication, changes, renewals and post-market event handling. Unclear responsibilities can affect certificate control and subsequent market stability.

Project Execution Recommendations

When executing this type of registration project, companies should maintain a project register that manages the product list, model and specification matrix, registration pathway, document owners, translation status, testing status, local agent communication records and expected submission dates in a single table. This allows documentation gaps to be identified promptly and helps management judge whether the project will affect the launch plan.

Companies that already have registrations in several countries should also build an evidence reuse matrix, defining which documents can serve as core evidence and which must be reissued or supported by supplementary explanations in line with national requirements. Labelling and instructions for use, clinical evaluation, risk management, performance verification and quality system certificates in particular must remain version-consistent.

• Confirm the target market and product list.
• Complete risk classification and pathway determination.
• Establish a documentation gap assessment table.
• Clarify the local agent and certificate control arrangements.
• Track translation, notarisation, testing and deficiency response status.
• Arrange post-market maintenance responsibilities in advance.

Quality System and Evidence Consistency

From a registration review perspective, quality system documentation is not an isolated certificate. Regulators typically check whether the manufacturer name, manufacturing site, product scope, certificate validity period, applicable standards and technical file are consistent with one another. If the scope of the ISO 13485 certificate does not match the product being submitted, or if the manufacturing site, model specifications or instructions for use version are inconsistent with the test reports, additional explanations may be required even where a large volume of documentation has been prepared.

Companies should establish an evidence consistency checklist before submission, mapping product name, model and specification, intended use, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, labelling and instructions for use version, and quality system certificate item by item. This step appears basic, but it can significantly reduce the likelihood of deficiency letters, particularly for projects submitted simultaneously across several GHWP member states or covering multiple product families.

Localisation Conversion and Authorised Representative Responsibilities

Target market registration projects usually involve arrangements with a local agent, authorised representative, importer or registration holder. Companies need to confirm in advance whether the local partner is only responsible for submitting documents, or whether it also handles regulatory communication, certificate maintenance, post-market event reporting, change applications and renewal reminders. Different responsibility boundaries directly affect certificate control and subsequent market stability.

Labelling, instructions for use and authorisation documents also cannot simply be translated. Companies should verify local language requirements, the boundaries of product claims, warnings, storage and transport conditions, UDI or traceability requirements, importer information, authorised representative details and after-sales contact information. For companies that already hold CE, FDA, NMPA or other market documentation, the focus of localisation conversion is to transform reusable evidence into a submission structure acceptable to the target country, rather than writing a separate set of isolated documents.

Post-Market Maintenance and Long-Term Planning

Completion of registration does not mean that compliance work has ended. Companies must also maintain certificate validity, change records, distributor authorisation, complaint handling, adverse event reporting, recall procedures, label versions and records of regulatory updates. Many companies invest heavily in obtaining the certificate but neglect post-market maintenance, so that when a manufacturing site change, model extension, instructions for use update or agent replacement occurs, the certificate becomes disconnected from actual market sales.

AIMEILI recommends managing this question within an annual international registration plan: first define target market priorities, then build a reusable documentation package and a country gap list, and finally schedule submission, deficiency response, post-market maintenance and renewal milestones. The value of this approach is not only greater efficiency in a single country; more importantly, it enables companies to develop a replicable overseas compliance capability and to reduce the cost of rebuilding documentation from scratch each time they enter a new market.

Further Reading

• Previous: How Should Registration Documentation for South Africa Be Prepared?
• Next: How Should the Technical File for South Africa Registration Be Organised?
• Recommended: What Are the Risk Management File Requirements for Medical Device Registration in the Philippines?
• Recommended: How Should Performance Verification Documentation for Medical Device Registration in the Philippines Be Prepared?
• Recommended: What Should Be Done If Quality System Evidence Is Inconsistent for Medical Device Registration in the Philippines?
• Recommended: How Should Registration Documentation for Medical Device Registration in Singapore Be Prepared?
• Recommended: How Is Product Classification Determined for Medical Device Registration in Singapore?
• Recommended: How Should the Technical File for Medical Device Registration in Singapore Be Organised?
• Return to the FAQ Centre

Content Review and Scope of Application

Content author: AIMEILI Regulatory Editorial Team. Professional review: AIMEILI Medical Device International Registration Project Team.

Source principle: priority is given to official regulatory authorities, international organisations, standards bodies and publicly available regulatory materials; industry media and project experience are used only as supporting references.

Scope of application: this article is intended for preliminary understanding, documentation preparation and project planning. It does not replace the formal requirements of the target country's regulatory authority, testing conclusions or legal advice. Specific projects should be based on the latest requirements of the target country's regulatory authority and the product's documentation base.