Digital tablet displaying a 2D barcode scan screen with device verification checkmarks alongside a stethoscope.
China’s Next UDI Wave: A Practical Playbook for the 2027/2029 Expansion
Why This Matters to Medical Device Manufacturers
By Sumit Joshi
I

f you sell medical devices into China, you’re about to enter the final stretch of China’s UDI (unique device identification) rollout. The newest announcements widen UDI coverage to the remaining device categories on a clear timeline: Class II devices and Class I IVDs in 2027, and Class I devices in 2029. That sounds straightforward – until you connect it to labeling, packaging hierarchies, regulatory submissions, database uploads, distributor workflows, and hospital usage.

This article gives you a practical, engineer‑friendly playbook. I’ll translate the policy into concrete actions you can take across product, labeling, IT, quality, and regulatory operations. I’ll also highlight where the announcements reduce effort (for example, when a product identifier update does not trigger a regulatory variation) and where they raise the bar (premarket database uploads and supply‑chain traceability expectations).

The Expanded UDI Scope: What Changes and When
China’s new approach follows a familiar pattern: expand scope in phases, set future “manufactured-on-or-after” compliance dates, and exempt legacy inventory produced before those dates. In practical terms, manufacturers get a runway to update labels, establish UDI-DI/UDI-PI rules, integrate systems, and train partners.

Here are the major thresholds:

  • June 1, 2027: UDI applies to all remaining Class II medical devices and Class I IVDs, if manufactured on or after this date.
  • June 1, 2029: UDI applies to all Class I medical devices, if manufactured on or after this date.
Exemption for older inventory: products manufactured before the relevant date are not required to comply.

The policy also fits into a broader rollout that already had implementation batches in 2020, 2021, and 2023. That matters because many organizations already have partial UDI infrastructure, which they can now build on to cover the remaining portfolio.

What “Manufactured On or After” Means for Your Program
Treat these dates as manufacturing gate checkpoints, not “ship-by” deadlines. Your real deadline will arrive earlier because you need time for:
  • Assigning UDIs;
  • Printing/approving label artwork;
  • Validating scanning/printing quality;
  • Loading UDI data into the national database;
  • Updating ERP/MES/labeling systems; and
  • Aligning distributor and hospital workflows.
If you wait until 2027 or 2029 to begin, you’ll be rushing the most error-prone part: data accuracy and packaging hierarchy alignment.
Regulatory Submissions: Where UDI Shows Up (and Where It Doesn’t)
One of the most helpful parts of the announcement is its clarification on regulatory integration. It answers a question that teams often debate: “Will UDI become a new technical review burden?”

The answer is that UDI is required for filings, but it is not treated as a technical review item in registration evaluation. Instead, it functions more like an administrative and traceability element. That distinction matters because it shapes how you staff your program. You need strong regulatory operations and data governance, not a new clinical/technical test package.

Here’s how UDI fits into submissions:

  • New registrations/filings submitted after the implementation date: include the UDI for the smallest sales unit in the registration/filing system.
  • Existing (already approved) products: provide UDI during renewal or when you submit change applications.
  • A key simplification: updates limited to product identifiers do not constitute a regulatory variation, reducing administrative churn.
  • UDI is not a technical review item in the registration evaluation process.
How to Use This Clarification Strategically
If your internal teams fear that UDI will “re-open” the technical file, use this language to align expectations. Your biggest compliance risks are typically:
  • UDI assignment errors (wrong issuing agency format)
  • Mismatched packaging levels (unit vs carton vs case)
  • Database entries that conflict with labeling
  • Delayed uploads (database not updated before commercialization)
  • Poor change control (identifier changes not pushed consistently)
So, build your controls around data integrity and lifecycle change management rather than adding unnecessary design verification tasks.
Database Uploads: The “Before Commercialization” Requirement That Drives Everything
The announcement is clear: you must submit UDI data to the national database prior to commercialization. This requirement drives program sequencing because it forces you to finalize identifiers and packaging hierarchy early.

UDI data upload obligations include the following:

  • Mandatory upload before market launch
  • Coverage of both smallest sales unit identifiers and higher‑level packaging identifiers
  • Data must be accurate, complete, and traceable
  • Where applicable, keep UDI aligned with medical insurance coding databases for reimbursed devices
  • Timely updates whenever product identifier information changes
Why This Is Often the Hardest Part
Most UDI delays aren’t caused by label printing. They are caused by data readiness. If your device master data is fragmented across regulatory, ERP, labeling, and distributor portals, your team will spend weeks reconciling issues, such as:
  • Product names and model descriptors
  • Packaging configurations and GTIN/DI relationships
  • Sterilization status and unit-of-use logic
  • Shelf-life or manufacturing date fields tied to PI rules
  • Language localization and translation consistency
The best way to prevent late-cycle friction is to treat UDI like a data product: define owners, establish validation rules, and audit record completeness before you attempt bulk uploads.
Supply Chain Responsibilities: UDI Succeeds or Fails at the Interfaces
UDI is not only a manufacturer labeling obligation. The announcement emphasizes coordinated responsibilities across the supply chain.

Key expectations include:

  • Manufacturers should establish UDI-based traceability systems that support recalls and adverse event monitoring.
  • Distributors should implement UDI-based inbound/outbound management and upload relevant data.
  • Healthcare institutions should integrate UDI into clinical use, billing, and reporting workflows.
  • Authorities coordinate system integration across sectors.
Practical Implications for Engineers and Program Leads
Even if you execute labeling perfectly, UDI fails if downstream partners don’t scan, store, and transmit the data. Treat distributor and hospital readiness as part of your verification plan. A simple way to do this is to run a “UDI data path test,” using the following steps:
  1. Print label with UDI carrier;
  2. Scan at distribution receiving;
  3. Scan at hospital receiving;
  4. Scan at point of use (or inventory pull);
  1. Confirm billing/reporting systems capture the correct DI/PI fields; and
  2. Confirm traceability report can link device to shipment/lot/serial.
This process will help you to uncover interface gaps early, and before they become field issues.
Exemptions and Special Scenarios: Where the Rules Flex
The second announcement introduces exemptions and tailored requirements. These are not “get out of UDI free” cards. Instead, they’re targeted accommodations for practical realities like multi-unit packaging, customized builds, transport containers, and software.

Common exemption scenarios include:

  • Single-use devices inside multi-unit packages (for example, masks), where the outer package carries UDI
  • Customized medical devices
  • Transport-level packaging
  • Export-only products (subject to the destination country’s requirements)
  • Certain drug-device combination products that may rely on existing drug traceability systems
Tailored Rules for Specific Product Types
The announcements also address “how” to implement UDI for tricky categories:
  • Reusable devices: adopt direct marking where feasible; otherwise, use alternative traceability solutions.
  • Class I reusable surgical instruments: may require only UDI-DI (not UDI-PI).
  • Standalone software: may present UDI digitally through an interface or API, without a physical carrier.
Engineering Takeaway
Your implementation approach should match the product’s lifecycle and usage:
  • For reusable instruments: evaluate marking durability and readability under reprocessing cycles.
  • For software: define what “displayed” means (UI location, access controls, versioning).
  • For multi-unit packs: ensure outer pack DI is linked to inner contents in your packaging hierarchy, so traceability remains meaningful.
A Step-by-Step Plan for Overseas Manufacturers (What to Do in 2026-2029)
Overseas manufacturers often face a double challenge: global UDI alignment and China-specific database requirements. The solution isn’t to build a parallel system but, rather, to build a harmonized system with localized outputs.

Here is a practical, multi-step sequence you can follow.

Step 1: Classify Your Portfolio for China and Map Deadlines
Start by mapping each product family to China classification and the corresponding deadline:
  • Class II devices and Class I IVDs → June 1, 2027
  • Class I devices → June 1, 2029
If your classification strategy is unclear, resolve it early. Classification ambiguity can derail your entire schedule because you won’t know which products require 2027 readiness versus 2029 readiness.
Step 2: Define Your UDI Issuing Strategy and Data Model
Align global UDI standards (such as GS1 or HIBCC) with China’s database expectations. Your aim is to provide one consistent DI/PI logic across regions wherever possible, plus localized record requirements where needed.

At minimum, define or specify the following:

  • The issuing agency and DI type
  • PI rules (lot, serial, expiration, manufacturing date)
  • Packaging hierarchy model (unit → carton → case)
  • Unit-of-use requirements (if applicable)
  • Software versioning logic for Software as a Medical Device (SaMD)
Step 3: Build Labeling and Packaging Change Control That Won’t Break Your Supply Chain
Label changes touch many systems. Build a controlled pipeline by:
  • Updating artwork templates;
  • Validating barcode/2D code quality;
  • Confirming scanner compatibility;
  • Training production/packaging operators; and
  • Confirming “manufactured on or after” gating in MES/ERP so compliant labels are applied at the right time.
Do not underestimate packaging hierarchy changes. In many organizations, packaging configuration lives in multiple systems, and mismatches cause rejected uploads or downstream confusion.
Step 4: Prepare the National Database Uploads as a “Release”
Treat database upload like a product release with quality gates, including the following:
  • Completeness checks (mandatory fields)
  • Naming conventions and translations
  • Packaging level consistency
  • Validation against label proofs
  • Traceability and audit logs
Plan for updates. Your DI may remain stable, but your PI rules, packaging, or product descriptors may change over time. Make sure you can update records quickly without manual chaos.
Step 5: Synchronize Reimbursement-Related Data Where Relevant
If your products are listed in reimbursement systems, enforce alignment between UDI records and insurance coding databases. Misalignment creates operational friction (billing rejects, procurement confusion, compliance questions). Build a reconciliation step into your governance process.
Step 6: Validate the End-to-End Traceability Workflow with Partners
Coordinate with local agents, distributors, and key hospital accounts to test scanning, data capture, and reporting. Your goal is not just “barcode scans.” It’s “UDI enables traceability.”
Step 7: Decide How to Handle Exemptions (and Whether to Go Voluntary)
Even if you qualify for an exemption (export-only, customized, or certain packaging cases), consider whether voluntary UDI adoption improves global consistency and reduces future rework. Voluntary adoption can simplify:
  • Global labeling standardization
  • Internal traceability processes
  • Future regulatory changes
  • Customer expectations in other markets
Common Pitfalls (and How to Avoid Them)
Below are the most frequent issues that slow UDI programs – and the engineer-friendly fixes that prevent them.

Pitfall A: Treating UDI as “just labeling”
Fix: Assign a cross-functional owner and treat UDI as a lifecycle data system. Tie it into change control, complaints, and recalls.

Pitfall B: Packaging hierarchy mismatches
Fix: Build a single “source of truth” for packaging levels and ensure ERP, labeling, and database records match exactly.

Pitfall C: Late database readiness
Fix: Schedule UDI database upload readiness earlier than label rollout. The upload requirement before commercialization makes data the pacing item.

Pitfall D: Distributors and hospitals aren’t ready
Fix: Run an end-to-end data path test with at least one distributor and one healthcare site, and document gaps.

Pitfall E: Identifier change chaos
Fix: Implement governance: who approves DI changes, how updates propagate, and how historical traceability is maintained.

The Bigger Picture: UDI as a Strategic Capability, Not a “Box to Check”
China’s trajectory is clear: regulation is becoming increasingly data-centric. UDI supports that shift by making device identification machine-readable, traceable, and interoperable across procurement, logistics, clinical workflows, reimbursement, and post‑market surveillance.

If you execute well, UDI becomes more than compliance. It also helps to ensure:

  • Faster and more accurate recall execution;
  • Improved adverse-event signal quality;
  • Better inventory and expiry management;
  • Reduced manual re-entry errors; and
  • Clearer product master data discipline across regions.
The companies that win will be the ones that build durable infrastructure: strong data governance, validated labeling processes, and partner-ready traceability workflows. Start early, build it once, and scale it across your portfolio.
References
  1. National Medical Products Administration, “National Medical Products Administration Announcement No. 66 of 2019: Announcement on the Issuance of the Rules for the Unique Device Identification System for Medical Devices,” Chinese Government Website (State Council Gazette), Published August 23, 2019.
  2. National Medical Products Administration, “Announcement of the National Medical Products Administration on Matters Concerning the Implementation of Unique Device Identification in Specific Circumstances (No. 15 of 2026),” Shanghai Municipal Medical Products Administration, Published March 13, 2026.
  3. National Medical Products Administration, National Health Commission, and National Healthcare Security Administration, “Announcement of the National Medical Products Administration, National Health Commission, and National Healthcare Security Administration on Implementing Unique Device Identification for Subsequent Product Categories (No. 21 of 2026),” Shanghai Municipal Medical Products Administration, Published March 13, 2026.
  4. National Medical Products Administration (NMPA), “Rules for Unique Device Identification System,” Updated June 30, 2022.
Share this story:
Sumit Joshi headshot
The Author
Sumit Joshi is a Staff Electrical Engineer at Waters Biosciences (formerly BD Biosciences) specializing in Device Safety and EMC/EMI Compliance. Sumit supports global regulatory conformity for medical, IVD, and laboratory research instruments. He can be reached at sumit.joshi@bd.com.
Back to Issue