How Should Multiple Models of a Medical Device Be Grouped for South Africa Registration?

Short answer: multiple models can be grouped into one South Africa registration file only when they form a genuine product family — same manufacturer and manufacturing site, same risk classification and regulatory pathway, same intended use and underlying technology, and an evidence set (testing, risk management, clinical evaluation and labelling) that explicitly covers every model in the group. Before filing, a manufacturer should confirm the target country, the device risk class, the applicable regulatory pathway and the status of existing documentation, and then run a structured gap assessment covering the technical file, quality system, labels and instructions for use (IFU), local authorised representative, clinical evidence and post-market maintenance obligations. AIMEILI advises completing this gap assessment before formal submission, because unclear classification, incomplete evidence or ill-defined authorisation arrangements are the most common causes of prolonged project timelines.

Published: 11 July 2026 · Updated: 11 July 2026

Key Summary

On the question of how multiple models should be grouped for South Africa registration, the first step is not selecting forms but confirming the target country, the product risk class, the applicable regulatory pathway and the current documentation base. Only then should the manufacturer assess the technical file, quality system, labels and IFU, local agent, clinical evidence and post-market obligations. AIMEILI recommends completing a documentation gap assessment before formal filing so that classification, evidence or authorisation issues do not 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. Registration in a target market typically affects the technical file, authorised representative, importer cooperation, label language, quality system evidence and subsequent change control at the same time. If the project is driven purely by the question “which documents must be submitted”, the manufacturer is likely to face deficiency letters or rework in model coverage, evidence chain consistency, label claims and certificate control. AIMEILI advises positioning this question within a broader GHWP member state and multi-country access strategy, using one reusable core technical file to support localisation in different markets rather than rebuilding documentation country by country.

Applicable Scenarios and Core Questions

Companies searching for guidance on grouping multiple models for South Africa registration are usually not looking for a conceptual explanation. They need to judge 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 there are usually several linked topics: product classification, registration pathway, evidence chain, label localisation and post-market maintenance responsibilities.

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

Registration Decision Logic

The manufacturer should first confirm the intended use, mechanism of action, use scenario, mode and duration of body contact, sterility, whether the device is active, and whether it incorporates software or has IVD characteristics. The risk class and submission pathway can then be determined. If the pathway is judged incorrectly, all downstream translation, notarisation, authorisation, testing and supplementary documentation will move in the wrong direction.

For a target market project, the applicant entity and the boundaries of local responsibility must also be confirmed: who holds the certificate, who handles regulatory communication, who manages import and post-market events, who triggers changes, and who maintains renewal documentation. If these points are left vague in a commercial contract, market control can easily be compromised later.

Documentation and Evidence

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

The key to documentation quality is not volume but consistency. IFU claims, the models covered by test reports, the scope of clinical evidence, risk management conclusions, label warnings and the information in the registration application form must support one another. What a regulator assesses is whether the device is safe, effective and traceable for its intended use in the target market — not how many documents have been uploaded.

Common Pitfalls

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

• Submitting translated NMPA documentation directly, without restructuring the evidence around the target market pathway.
• Listing 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 sales cooperation, without clarifying regulatory responsibility, certificate control or post-market maintenance duties.
• Inconsistency between labels, IFU, promotional material and registration claims, leading to deficiency letters or post-market compliance risk.
• Failing to plan multi-country documentation reuse in advance, so that documentation is rebuilt for each country and both cost and timelines are inflated.

Company Preparation Checklist

Before the project starts, manufacturers should use an internal checklist to confirm the documentation base, so that critical 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-language IFU.
• Confirm the duties, fees, certificate control and exit arrangements of the local agent or authorised representative.
• Build a target-country gap assessment table identifying what must be retested, translated, notarised or supported by additional declarations.

AIMEILI's View

AIMEILI advises manufacturers not to treat target-market registration as a one-off document submission, but to manage it as an overseas market access programme. For companies entering several countries, establishing a clear core technical file and evidence matrix first, and then converting it to national requirements, is usually faster, more stable and better for subsequent changes and renewals than preparing documentation ad hoc for each country.

From a project management perspective, three things should be controlled up front: first, product classification and pathway determination; second, consistency of the documentation evidence chain; third, the regulatory responsibility boundaries of local partners. If these three items are unclear, the project may still encounter repeated rounds of deficiency responses, agent communication and post-market maintenance, no matter how extensive the documentation appears.

Frequently Asked Follow-Up Questions

Can domestic registration documentation be used directly for a target-market submission?

Domestic documentation can serve as the basis, but it usually cannot be submitted as it stands. Manufacturers need to adjust the document structure, language, labelling, authorisation documents and evidence chain to meet local regulatory requirements.

When is the best time to start a gap assessment?

As soon as 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?

The local agent usually participates in regulatory communication, change notifications, renewals and post-market event handling. Unclear rights and responsibilities can affect certificate control and the stability of the market after approval.

Project Execution Recommendations

When executing this type of registration project, manufacturers should maintain a project register that manages the product list, model and specification details, registration pathway, document owners, translation status, testing status, records of communication with the local agent and expected submission dates in a single table. This makes documentation gaps visible early and helps management judge whether the project will affect the launch plan.

Companies that already hold 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 statements for a specific country. Labels and IFU, clinical evaluation, risk management, performance verification and quality system certificates must in particular be kept at consistent versions.

• Confirm the target market and product list.
• Complete risk classification and pathway determination.
• Build the documentation gap assessment table.
• Clarify the local agent and certificate control arrangements.
• Track translation, notarisation, testing and deficiency response status.
• Assign 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 address, product scope, certificate validity period, applicable standards and technical file are consistent. If the scope of the ISO 13485 certificate does not match the products being submitted, or if the manufacturing address, model specifications and IFU version are inconsistent with the test reports, the manufacturer may still be asked for supplementary explanations even after preparing a large volume of documents.

Before submission, manufacturers should create an evidence consistency checklist that maps product name, model and specification, intended use, applicable standards, test report numbers, clinical evaluation conclusions, risk management version, label and IFU version, and quality system certificates item by item. This step looks basic, but it can noticeably reduce the probability of deficiency letters, especially for projects covering several GHWP member states or several product ranges at the same time.

Localisation Conversion and Representative Responsibilities

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

Labels, IFU and authorisation documents also cannot simply be translated. Manufacturers 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 turn reusable evidence into a submission structure acceptable in the target country, rather than writing a separate set of isolated documents.

Post-Market Maintenance and Long-Term Planning

Registration approval does not mark the end of compliance work. Manufacturers must also maintain certificate validity, change records, distributor authorisations, complaint handling, adverse event reporting, recall procedures, label versions and regulatory update records. Many companies invest heavily in obtaining the certificate but neglect post-market maintenance; when a manufacturing address change, model extension, IFU update or agent replacement occurs, the certificate can quickly become disconnected from actual market sales.

AIMEILI advises manufacturers to manage this question within an annual international registration plan: first set 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; it allows the company to build a repeatable overseas compliance capability and reduces the cost of starting from scratch every time it enters a new market.

Continue Reading

• Previous: What should be prepared before renewing a South Africa medical device registration?
• Next: What are the requirements for a risk management file in South Africa medical device registration?

Recommended reading

• What are the requirements for a risk management file in Philippines medical device registration?
• How should performance verification documentation be prepared for Philippines medical device registration?
• What should be done if quality system evidence is inconsistent in Philippines medical device registration?
• How should registration documentation be prepared for Singapore medical device registration?
• How is product classification determined for Singapore medical device registration?
• How should the technical file be organised for Singapore medical device registration?

Back to the FAQ Centre · News · Contact AIMEILI

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 judgement.

Scope: 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.