Global UDI Compliance Strategy for Medical Device Manufacturers
A practical guide to FDA GUDID, EU Basic UDI-DI and EUDAMED, Australia TGA AusUDID and 2026 Consent to Supply, China NMPA UDID, Saudi-DI, labeling, master data, and enterprise implementation.
Executive summary
UDI is no longer just a barcode requirement. It is a regulatory master-data system connecting product identifiers, packaging levels, labels, regulatory databases, post-market surveillance, recalls, and supply-chain traceability.
The 2026 Australia TGA milestone makes the issue urgent: Class III and Class IIb devices must meet UDI labelling and AusUDID submission requirements from 1 July 2026, with a streamlined UDI-related Consent to Supply pathway available only for UDI-only Essential Principles issues.
Key findings
- FDA, EU, TGA, NMPA, and SFDA all use UDI, but their database fields, responsible parties, timing, and change triggers differ.
- Existing FDA or EU UDI assets can be reused, but they must be mapped to local obligations such as AusUDID, ARTG entries, Sponsors, Basic UDI-DI, and local labelling.
- UDI must be governed through QMS change control, not manually maintained by regulatory affairs after labels are finalized.
Market comparison
Labeler responsibility, DI/PI, direct marking, GUDID submission, legacy identifier policies.
Basic UDI-DI for documentation and certificates; UDI-DI for device and packaging levels.
Class III / Class IIb from 1 July 2026; Sponsor-managed ARTG entry mapping and UDI CtS decisions.
Registrant or filing entity creates, maintains, uploads, and updates UDI data before marketing.
UDI requirements tied to SFDA device listing, local importer, and Arabic/home-use information needs.
Sign up to view the UDI execution package
The public report explains the regulatory update. The signed-in workspace adds practical checklists, TGA 2026 triage logic, and a 30/60/90-day rollout plan.
- TGA 2026 Class III / Class IIb readiness triage
- UDI master-data field map across FDA, EU, TGA, NMPA, and SFDA
- 30/60/90-day rollout plan for labels, databases, and QMS change control
Enterprise solutions
Exporters with existing FDA or EU approvals
Class IIb, Class III, AIMD, or higher-risk products entering Australia, the Middle East, or additional mature-regulator markets.
- Build a FDA/EU/TGA mapping table covering DI, Basic UDI-DI, EUDAMED, ARTG entries, AusUDID fields, and Sponsor responsibility.
- Separate reusable UDI data from local-only obligations such as Australia Sponsor information and ARTG linkage.
- Global UDI master-data map, AusUDID gap report, Sponsor RACI, and UDI CtS decision table.
China-first manufacturers preparing for overseas filings
Companies with NMPA registration but no mature global UDI architecture yet.
- Select an issuing agency strategy before label design, considering FDA, EU, TGA, NMPA, and target distributors.
- Model product families, variants, packaging levels, sterilization status, batch/serial rules, and Basic UDI-DI grouping.
- Global UDI coding strategy, NMPA/FDA/EU/TGA label matrix, packaging-level model, and UDI SOP.
Australia-listed Class III / Class IIb suppliers
Sponsors or manufacturers facing the 1 July 2026 TGA UDI deadline and possible continued-supply risk.
- Classify every ARTG entry as ready, recoverable before 1 July 2026, UDI-only CtS candidate, or standard CtS / non-UDI issue.
- Control old and new labels, consignment stock, surgical loan kits, distributor inventory, and Sponsor-controlled supply.
- TGA UDI readiness dashboard, CtS application pack, inventory transition plan, and Sponsor communication pack.
OEM / ODM and multi-brand manufacturers
Factories serving multiple labelers, private-label owners, importers, and regional registrants.
- Define who is the FDA labeler, EU manufacturer, Australia Sponsor, China registrant, and database owner for every product-brand-market combination.
- Add UDI responsibilities, change-notice timelines, database correction duties, and recall data duties into customer contracts.
- OEM UDI responsibility matrix, multi-brand coding tree, and contract clause checklist.