Preparing for NDC-12: A Practical Readiness Guide for Pharmaceutical Organizations

The NDC Is Changing. The Impact Goes Much Further.

FDA’s move to a uniform 12-digit National Drug Code represents a significant change for the pharmaceutical supply chain.

Beginning March 7, 2033, FDA will move from today’s 10-digit to a uniform 12-digit format. FDA is providing a three-year transition period through March 6, 2036, during which 10- and 12-digit NDCs may appear on product labeling.

The timeline may appear long; the potential scope of preparation is not.

For pharmaceutical organizations, NDC-12 isn’t simply a labeling or serialization change. NDC information can flow through systems and processes spanning packaging, master data, inventory, transactions, financial operations and trading partner relationships.

Organizations that begin mapping those dependencies now will be better positioned to manage the transition without creating unnecessary disruption later.

1. Know Everywhere Your NDC Goes

The first step toward readiness is understanding the full lifecycle of the NDC within your organization.

Don’t just ask where the NDC is stored.

Ask:

• Where is it created or maintained? Consider product and material master data.
• Where is it consumed? Identify systems and processes dependent on the identifier.
• Where is it displayed? Examine labels, packaging, reports and user interfaces.
• Where is it shared? Map EDI, EPCIS and other exchanges with trading partners.
• What business processes depend on it? Consider inventory, contracts, customer eligibility, financial reporting and other downstream activities.

The goal should be a dependency map of NDC-related systems and processes, not simply a list of applications.

2. Determine How You’ll Manage 10- and 12-Digit NDCs

FDA says affected parties should ensure their systems can handle both 10- and 12-digit formats during the three-year transition.

That creates an important operational question: How will your organization represent and manage products during coexistence?

For example, organizations may need to determine how their master-data strategy will accommodate the change and whether downstream processes will treat the updated identifier as the same product or require a different item configuration.

Those decisions can cascade into:

Master data → Inventory → Financial reporting → Trading partner setup → Transaction processing

This is why NDC-12 planning needs representation from more than regulatory or serialization teams.

3. Look From the Packaging Line Through the Enterprise

Readiness should be evaluated end to end. A change that begins on packaging can affect multiple layers of technology and operations before information ultimately reaches a trading partner.

Organizations should assess dependencies across:

Packaging & labeling → Site systems → Enterprise serialization and traceability → ERP/business systems → External transactions and trading partners

FDA also permits qualifying 2D Data Matrix barcodes to encode the 12-digit NDC alongside the other DSCSA product identifier elements beginning March 7, 2033, reinforcing the connection between identification, packaging and downstream traceability processes.

Testing one system independently may therefore miss problems created at the handoff between systems.

4. Plan for the Exceptions, Not Just the Happy Path

Any large identifier transition can introduce operational exceptions.

Potential issues can emerge when systems interpret identifiers differently, master data is inconsistent, trading partners transition at different times, or barcode information doesn’t align with electronic transactions.

Organizations should incorporate exception scenarios into their testing strategy—not simply confirm that a correctly configured 12-digit NDC passes through the expected workflow.

That means asking: What happens when it doesn’t?

Teams should understand how quickly they can identify an issue, determine where it originated and resolve it before it affects product movement.

5. Build Your NDC-12 Readiness Team Now

NDC-12 shouldn’t belong to a single department. Depending on the organization, preparation may require participation from serialization and traceability, packaging, supply chain, IT, regulatory, quality, master data, finance and commercial operations—as well as external manufacturing and trading partners.

A practical starting point is to establish ownership for four activities:

Map → Assess → Plan → Test

Map every NDC touchpoint. Assess the systems and processes affected. Plan how the transition and coexistence period will be managed. Then test across systems and trading partners—not just within individual applications.

Start Preparing Before NDC-12 Becomes an NDC-12 Project

FDA has intentionally provided the pharmaceutical ecosystem years to prepare, encouraging manufacturers, distributors, pharmacies, providers, payors and other affected parties to begin updating their systems, processes and infrastructure ahead of the March 2033 transition.

Organizations should use that runway.

Understanding dependencies today creates more time to address system limitations, align trading partners, establish processes and test changes without the pressure of an approaching compliance deadline.

At Systech, we help pharmaceutical organizations navigate evolving serialization and traceability requirements across the packaging line, site, enterprise and supply chain—helping them prepare not only for today’s requirements, but for what’s next.

Ready to assess your NDC-12 readiness? Talk to a Systech expert.