When a medical device manufacturer engages an external software team, that team becomes a supplier within the manufacturer's quality management system. ISO 13485:2016 does not prohibit offshore suppliers, and the MDR does not either. What both require is control proportionate to risk: you must evaluate and select the supplier against defined criteria, specify what you are buying, verify what you receive, and monitor performance over time. For software development, the supplier is often critical, because its output directly determines device safety and performance. This guide sets out a practical configuration: classification, qualification steps, quality agreement content, and monitoring that will make sense to a notified body auditor.

Why supplier control is under pressure

Supplier control is becoming a capacity question as much as a quality question. BVMed counts 1,529 German medtech companies with 20 or more employees and around 212,100 people employed in the industry in 2024, with roughly 93 percent of companies classed as SMEs. Industry revenue reached 42.72 billion euros in 2025. Few of these firms can staff every software role internally while the IT labour market remains tight: Bitkom counted 79,000 unfilled IT positions in Germany in 2026, and 97 percent of companies with IT roles reported difficulty filling them. Notified bodies are busy at the same time. Team-NB reported 16,453 MDR and IVDR certificates issued in 2025, and under Regulation (EU) 2023/607, legacy certificates expire on 31 December 2027 for class III and implantable class IIb devices and on 31 December 2028 for most other classes. Audit time is scarce, and a supplier file that already answers the auditor's questions saves it.

The relevant clauses

  • ISO 13485 clause 4.1.5: when the manufacturer outsources a process that affects product conformity, it must monitor and ensure control over that process, proportionate to the risk involved and the supplier's ability to meet requirements. Controls must include written quality agreements.
  • Clause 7.4.1: the purchasing process must establish criteria for evaluation and selection of suppliers, based on their ability to provide product meeting requirements, their performance, and the effect of the purchased product on the quality of the medical device, proportionate to the associated risk. Monitoring and re-evaluation must be planned, and records kept.
  • Clause 7.4.2: purchasing information must describe the product, including, where applicable, a written agreement that the supplier notifies the manufacturer of changes before implementation.
  • Clause 7.4.3: the manufacturer must verify that purchased product meets requirements.
  • MDR Annex IX section 3.4: the notified body must carry out unannounced audits at least once every five years, which may, where appropriate, extend to the manufacturer's suppliers and subcontractors.

The last point is often overlooked. If your software supplier is critical, a notified body may want to see their site or their processes, possibly without notice. Your contract must make that possible.

Step 1: Classify the supplier

Most manufacturers use a supplier classification with two to four tiers. For software development, a simple decision rule works:

What the supplier deliversTypical classificationControl depth
Software of class B or C under IEC 62304, or software implementing risk control measuresCriticalOn-site or remote audit, quality agreement, process integration, periodic re-evaluation
Class A software, or tools used in development and testing whose output is verifiedMajorQuestionnaire, quality agreement, performance monitoring
Non-device software (internal tools, marketing website)MinorStandard purchasing controls

Document the rationale. An auditor will accept many classification schemes, but not one that is applied inconsistently.

Step 2: Qualify before work starts

For a critical software supplier, qualification typically includes:

  1. A supplier questionnaire covering organisation, quality system, development process, configuration management, information security and staff qualification.
  2. A remote or on-site audit focused on how the supplier will work inside your process, not on generic certifications.
  3. Evidence of relevant competence: engineers' experience with regulated software, familiarity with IEC 62304 and ISO 14971 concepts.
  4. A trial task or pilot sprint with full lifecycle records, evaluated by your QA.
  5. A documented approval decision and entry in the approved supplier list.

An ISO 13485 or ISO 9001 certificate at the supplier is helpful but not required, and it does not replace your evaluation. Many capable software teams are not certified, because the software development work happens under the manufacturer's QMS.

Step 3: The quality agreement

The quality agreement is the core document. For software development it should cover at least:

  • Scope: which products and software items, which IEC 62304 activities.
  • Applicable procedures: the supplier works according to the manufacturer's SOPs, listed by number and version.
  • Personnel: named roles, training on the SOPs before work, training records kept and provided on request.
  • Records: all records created in the manufacturer's systems. Retention follows the manufacturer's obligations; under MDR Article 10(8) technical documentation must be available for at least 10 years after the last device is placed on the market, or 15 years for implantable devices.
  • Change notification: the supplier informs the manufacturer before changing key personnel, locations, subcontractors, or tools that affect the work.
  • Subcontracting: not permitted without written approval.
  • Audit rights: for the manufacturer and its notified body, including unannounced audits, on site or remote.
  • Nonconformities and CAPA: how defects in delivered work are reported, investigated and corrected.
  • Information security and data protection: access model, handling of any personal data, and, where personal data is accessed from India, a data processing agreement and Standard Contractual Clauses.

The quality agreement complements the commercial contract. Under a Werkvertrag, the Leistungsbeschreibung describes what is delivered and accepted (BGB §640). The quality agreement describes how it is produced and controlled. Keep them consistent.

Step 4: Monitor and re-evaluate

Monitoring should rely on data you already generate:

  • Sprint acceptance results: share of deliverables accepted at first submission.
  • Defects found after acceptance, by severity.
  • Completeness of lifecycle records at review.
  • Timeliness of change notifications.
  • Findings from audits and their closure.

Re-evaluate at a defined interval, for example annually, and after significant events such as a major nonconformity or a change of supplier location. Record the outcome in the approved supplier list.

Common audit findings to pre-empt

  1. Supplier classified as critical but no audit performed.
  2. Quality agreement does not mention notified body audit access.
  3. Supplier staff changed without notification or training records.
  4. Records stored only in the supplier's tools.
  5. Open-source components introduced without SOUP evaluation.

This article is general information and not legal or regulatory advice. Align your supplier controls with your notified body and qualified advisors.

An offshore software supplier that cannot be qualified cleanly becomes a finding in the next audit, however good the code. niogod™ pods are designed to be qualified as a critical supplier: they work in the manufacturer's tools and SOPs, support audit access, deliver under a Werkvertrag with documented Abnahme, and have a German-speaking Projektleiter as the contact for QA and regulatory affairs, with controls summarised on our security page. If supplier qualification for software is on your agenda for 2027, it is a conversation worth having early.

Talk to niogod™

Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.

Book consultation
← All insights