Have a regulatory question?
Talk to a Korea regulatory specialist about your device, your timeline, or your next submission.
Talk to a specialist
Korea's UDI system runs on Korean GS1 codes and ties to the MFDS database. A practical implementation guide aligned with FDA UDI and EU MDR EUDAMED requirements.
This document is not yet available for download. Please contact us if you need it urgently.
No previous versions available.
Korea's UDI (Unique Device Identification) system has been mandatory for Class IV devices since 2019 and was phased into Class III in 2020, Class II in 2022, and Class I in 2024. The system uses GS1 Korea-issued codes integrated into the MFDS UDI database (UDI-DI registration).
A Korean UDI consists of:
Korean UDI is not identical to FDA UDI or EU EUDAMED UDI. Manufacturers shipping to multiple regions cannot rely on a single UDI implementation; the carriers and databases differ.
| Element | FDA UDI | EU EUDAMED | Korea UDI |
|---|---|---|---|
| Issuing agency | GS1, HIBCC, ICCBBA | GS1, HIBCC, ICCBBA, IFA | GS1 Korea (preferred) |
| Database | GUDID | EUDAMED | MFDS UDI-DI System |
| Submission party | Labeler (manufacturer or specification developer) | Manufacturer | KLH (in most cases) |
| Carrier requirement | One carrier (DataMatrix or linear) | DataMatrix preferred | DataMatrix preferred |
| Reusable devices | Direct marking required on Class II+ | Direct marking on reusable Class III | Direct marking on Class III/IV |
| Implant card | Not required | Required (Annex XIII) | Required for implantables |
| Effective dates | Class III: 2014; Class II: 2018; Class I: 2022 | Class III: May 2021; ramping by class | Class IV: 2019; ramping to Class I: 2024 |
Three practical implications:
A single UDI carrier can serve all three markets if structured as GS1 DataMatrix containing GTIN + production data. The carriers are reusable.
The database registrations are not reusable. FDA GUDID, EU EUDAMED, and MFDS UDI-DI each have their own data schema. Records must be submitted to each system.
The submitting party differs. FDA: the labeler. EU: the manufacturer. Korea: the KLH (acting as importer for foreign manufacturers). The submission workflow has to accommodate three different filers.
The MFDS UDI-DI registration captures product metadata including:
For multi-SKU portfolios, the UDI-DI database becomes the canonical product master in Korea. Maintaining the database is an ongoing responsibility, not a one-time submission.
For a foreign manufacturer launching in Korea, UDI implementation runs in parallel with the MFDS registration:
Obtain GS1 Korea company prefix (if not already a GS1 member globally). Assign GTINs to each Korean SKU. The GTIN is the same product identifier used in FDA and EU systems — manufacturers with existing global GS1 membership can reuse their GTINs.
Design the UDI carrier on the Korean label:
Carrier design is often the area where existing label templates need refresh. Pre-UDI Korean labels typically have lot number and expiration in human-readable form but no machine-readable encoding.
For reusable devices in Class III/IV, direct marking on the device itself is required. This is typically laser engraving or chemical etching, integrated into manufacturing. Direct marking adds a step to manufacturing process validation and KGMP scope.
The KLH submits the UDI-DI record to MFDS through the MFDS UDI Information Service Center portal. The submission is per SKU, with the metadata listed above. Approval is typically 5–10 business days.
Once registered, the UDI-DI record must be updated when:
The maintenance burden is light per SKU but adds up across portfolios.
UDI is the connective tissue between several otherwise-separate Korean regulatory regimes:
Manufacturers running clean UDI implementation report significant operational benefits beyond pure compliance — particularly in recall scope reduction and complaint analysis speed.
For a manufacturer with 10–20 SKUs in Korea:
Total implementation: ~3–6 months for a clean portfolio without direct-marking complexity; 6–12 months when direct marking is involved.
Mistake 1: Treating UDI as just labeling. UDI is a regulatory data system that happens to have a labeling component. Implementing only the label and skipping the database registration leaves the manufacturer non-compliant.
Mistake 2: Single-region implementation. Building a Korea-only UDI program when FDA UDI and EU EUDAMED are also in scope is duplicative. A multi-region UDI strategy designed once is cheaper than three sequential single-region implementations.
Mistake 3: KLH not in the implementation loop. The KLH is the submitter for Korean UDI-DI records. Manufacturers implementing UDI without involving the KLH end up with incomplete submissions or submissions made under the wrong party.
Mistake 4: Ignoring compatibility relationships. UDI-DI records require cross-references to compatible accessories. Building these out for the first SKU is straightforward; retrofitting them across an existing portfolio is significant work.
UDI implementation runs through the Labeling service, which handles carrier design, label redesign, GS1 setup, and database registration coordination. For multi-region UDI strategy and the integration across FDA/EU/Korea, Regulatory Foundations sets the architecture. Korean UDI database maintenance specifically integrates with Korea License Maintenance.
Talk to a Korea regulatory specialist about your device, your timeline, or your next submission.
Talk to a specialist![[TEST] OTP Download Verification – Whitepaper](/images/whitepapers/mes-vs-erp.jpg)
Test post used to validate the OTP email + verified-download flow on the whitepaper detail page.

MFDS approval gets your device into Korea; HIRA and NECA decide whether hospitals can afford to use it. A guide to navigating Korea's two-stage reimbursement system.

Annex II/III for MDR, Annex I/II for IVDR. GSPR checklists, Notified Body engagement, and the Korean cross-reference for manufacturers entering both regions.