UDI and Traceability: Practical Implementation for Growing Companies

UDI and Traceability: Practical Implementation for Growing Companies

Unique Device Identification (UDI) and robust traceability are no longer requirements that apply only to large manufacturers. Under EU MDR, IVDR, and FDA regulations, even small and growing companies must establish complete, controlled device identification and tracking systems. These systems are foundational to product lifecycle management, complaint handling, vigilance, recalls, and supply-chain integrity. For expanding organisations, the challenge is not understanding the regulatory obligation—it is implementing UDI and traceability in a scalable, operationally disciplined way.

This article outlines how growing companies can implement UDI and end-to-end traceability aligned with ISO 13485, ISO 14971, MDR, IVDR, and FDA expectations without overbuilding complexity or relying on fragmented tools.

1. The Role of UDI and Traceability in a Modern QMS

UDI and traceability systems support multiple regulatory and operational objectives, including:

  • Identification of device models, batches, and production units
  • Control of labelling and packaging processes
  • Rapid execution of recalls and field safety corrective actions
  • Accurate complaint and vigilance evaluation
  • Lifecycle risk management and trend analysis
  • Supply-chain verification and anti-counterfeiting measures

Regulators evaluate traceability not only through documentation, but by assessing the company’s ability to retrieve device history and distribution records on demand.

2. Understanding UDI Requirements Across Global Markets

2.1 EU MDR and IVDR

UDI requirements include:

  • Issuance of a Basic UDI-DI for regulatory submissions
  • UDI-DI and UDI-PI assignment for each device configuration
  • Proper UDI labelling on packaging, direct marking (where required), and documentation
  • Submission of UDI data to EUDAMED

2.2 FDA UDI Requirements

FDA requirements include:

  • UDI compliant with accredited issuing agencies (GS1, HIBCC, ICCBBA)
  • Direct marking where applicable
  • Submission of UDI information to the Global UDI Database (GUDID)
  • Record-keeping and reporting aligned with 21 CFR 820.60 and 820.65

Growing companies often misunderstand the difference between UDI assignment, UDI labelling, and UDI database submission. All three must be controlled and traceable.

3. Building a Scalable UDI System

3.1 Establish Device Identifier Structure

Define:

  • Basic UDI-DI structure for regulatory submissions
  • UDI-DI assignment logic for product families, variants, models, and kits
  • UDI-PI structure capturing lot, serial number, date of manufacture, expiry, or other required attributes

The structure must align with the issuing agency and be locked under document control.

3.2 Implement Controlled UDI Labelling Processes

UDI labelling must integrate with:

  • Design outputs
  • Packaging specifications
  • Bill of materials and production routers
  • Inspection criteria
  • Document control and artwork change processes

Labelling errors are one of the most common sources of FDA 483 observations in small and growing companies.

3.3 Embed UDI in ERP or Traceability Tools

Growing companies benefit from incorporating UDI directly into:

  • Production batch records
  • Warehouse management systems
  • Distribution logs
  • Complaint handling tools

Manual spreadsheets become unmanageable as production scales. A structured digital tool—validated where required—helps maintain data integrity.

4. Designing a Practical, End-to-End Traceability System

4.1 Define the Required Traceability Depth

Traceability should support the manufacturer’s ability to:

  • Identify every device shipped
  • Trace back to production records and inspection results
  • Determine suppliers and components used
  • Determine distribution and consignee information
  • Retrieve risk-management and design-control evidence tied to that configuration

ISO 13485 and MDR require greater depth for implantable and higher-risk devices.

4.2 Build the Traceability Data Map

An effective traceability system connects:

  1. Design Records → specifications, materials, risk controls
  2. Manufacturing Records → DHR elements, validation evidence, in-process controls
  3. UDI and Labelling → DI/PI applied and verified
  4. Distribution Records → consignee and country-specific requirements
  5. PMS and Complaint Data → device history for each case

A traceability map ensures alignment and prevents fragmentation across departments.

4.3 Standardise Device History Record (DHR) Structure

DHRs must contain:

  • UDI information
  • Lot/serial number
  • Production dates and quantities
  • Inspection and release records
  • Equipment, materials, and deviations used in production

The FDA will request multiple DHRs during inspections and evaluate completeness and consistency.

4.4 Strengthen Distribution Traceability

Growing companies often overlook the distribution component of traceability. A compliant system must capture:

  • Consignee details
  • Quantities shipped
  • Dates of dispatch
  • UDI-PI for each shipped unit
  • Recall-ready records stored under controlled retention requirements

Recall effectiveness hinges on the quality of distribution traceability.

5. Integrating UDI and Traceability With Risk Management

ISO 14971 requires traceability between risk controls and manufacturing/field performance. UDI and traceability data feed into:

  • Complaint investigations and field performance analysis
  • Trend monitoring and vigilance decisions
  • CAPA investigations tied to specific devices or batches
  • Design-change decisions supported by real-world evidence

This integration provides actionable insight and reduces regulatory exposure during audits.

6. Common Weaknesses Observed in Growing Companies

  • Poorly defined UDI assignment rules
  • Inconsistent application of DI/PI on artwork and labels
  • Fragmented storage of DHRs across multiple formats
  • Distribution records incomplete or non-retrievable
  • No linkage between UDI, complaints, and risk files
  • Traceability systems that cannot scale as volumes increase

Addressing these weak points early reduces long-term compliance gaps.

7. Building a Scalable UDI and Traceability Roadmap

Growing organisations should adopt a phased approach:

  1. Define UDI structures and document issuing agency rules.
  2. Implement controlled labelling and artwork processes with verification steps.
  3. Map the full traceability workflow from design to PMS.
  4. Integrate UDI into ERP or QMS tools to replace manual tracking.
  5. Test recall readiness to ensure rapid retrieval of device history and distribution data.

This structured progression allows small and mid-sized companies to meet MDR, IVDR, and FDA expectations without operational overload.

Conclusion

UDI and traceability systems are critical to regulatory compliance, product safety, and operational stability. Growing companies can implement compliant, scalable systems by establishing clear UDI rules, strengthening labelling control, building end-to-end traceability, and integrating these systems with risk management and PMS. A disciplined approach delivers long-term regulatory durability and enables confident expansion into global markets.

Back to blog

Leave a comment

About ISO Cloud Consulting

Structured, regulator-aligned guidance for medical-device teams building ISO 13485 systems, MDR/FDA documentation, PMS/Vigilance frameworks, and validated digital QMS environments.

Ultra-clean white–blue regulatory workspace with structured binders labeled Document Control, Risk Management, Supplier Lifecycle, Training & Competence. Faint ISO 13485 documents layered in background. Crisp clinical lighting, no people.

Need a Fully Structured, Audit-Ready QMS?

Implement ISO 13485, MDR, FDA QMSR, and complete documentation systems with validated workflows and regulator-aligned templates.

Contact Us Today