What the transition means for your systems, data and operations—and what to do now.
The move to a uniform 12-digit National Drug Code (NDC) may look like a small change on paper. It is not.
For pharmaceutical manufacturers, CDMO, repackagers and their trading partners, NDC-12 will reach well beyond the product label. It can affect packaging lines, artwork, master data, serialization, ERP, warehouse systems, financial processes, reporting interfaces and the data exchanged across the supply chain.
The U.S. Food and Drug Administration (FDA) has given the industry until March 7, 2033, before it begins assigning 12-digit NDCs. That sounds like plenty of time—until you factor in product portfolios, validated systems, label change cycles, competing IT priorities and the coordination requis across CMOs, 3PLs, wholesalers and other partners.
This is not a two-digit update. It is a multi-year operational transition.
The organizations that wait for NDC-12 to become an urgent compliance deadline may find themselves managing avoidable data mismatches, labeling constraints, validation bottlenecks and partner-readiness issues under pressure.
Those that start now have time to map dependencies, make deliberate decisions and test changes before product movement is at stake.
This guide outlines where to begin.
1. Know everywhere your NDC goes
The first step toward readiness is understanding the full lifecycle of the NDC within your organization.
That means looking beyond where the NDC is stored.
Ask these questions:
The goal is not simply a list of affected applications. It is a clear picture of how NDC data moves across the organization and where a change in format could create downstream consequences.
2. Plan for a period when both 10- and 12-Digit NDCs may be in use
During the three-year transition period, organizations may encounter both 10- and 12-digit NDCs. That creates a practical question: how will your systems, data and workflows recognize and manage both formats?
This is not only a technical issue. It can affect how teams represent products, manage item records, reconcile transactions and coordinate with trading partners.
For instance, organizations may need to determine whether a 12-digit NDC will be treated as an update to an existing product record or as a new item configuration in certain systems. Those decisions can affect processes well beyond master data.
A change in one place can cascade through the enterprise:
Master data → Inventory → Financial reporting → Trading partner setup → Transaction processing
This is why NDC-12 planning needs representation from more than réglementaire or serialization teams. It requires shared decisions across the functions that create, use and exchange product information.
3. Look from the packaging line through the enterprise
NDC-12 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.
A practical assessment should consider dependencies across:
Packaging & labeling → Site systems → Enterprise serialization and traceability → ERP/business systems → External transactions and trading partners
Le FDA’s rule also allows also permits qualifying 2D Data Matrix barcodes to encode the 12-digit NDC alongside the other Loi sur la sécurité de la chaîne d'approvisionnement en médicaments (DSCSA) product identifier elements beginning March 7, 2033. That reinforces the connection between identification, l'emballage and downstream traceability processes.
Testing a single system in isolation may not reveal the problems that emerge at the handoff between systems. The key question is whether the updated identifier can move accurately and consistently from the packaging line through the enterprise and across the supply chain.
4. Plan for the exceptions, not just the happy path
Most transition plans begin by confirming that the intended process works. That is necessary, but it’s not enough.
Large identifier changes can introduce exceptions when systems interpret data differently, master data is incomplete or inconsistent, trading partners transition at different times, or barcode data does not 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 identifier an issue, determine where it originated and resolve it before it affects product movement.
5. Build the right 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 traçabilité, packaging, supply chain, IT, regulatory, quality, master data, finance and commercial operations. Contract manufacturers, repackagers, 3PLs and other trading partners may also need to be part of the conversation.
A practical starting point is to establish ownership across four activities:
Map → Assess → Plan → Test
Clear ownership and early cross-functional alignment can help prevent NDC-12 from becoming a last-minute compliance project.
Start preparing before NDC-12 becomes an NDC-12 project
The FDA has provided the pharmaceutical ecosystem with time to prepare. Manufacturers, distributors, pharmacies, providers, payors and other affected parties can use that time to update systems, processes and infrastructure ahead of the March 2033 transition.
Organizations should use that runway.
Starting now creates more time to identifier system limitations, align internal teams, work with partners, establish data governance and test changes without the pressure of an imminent conformité deadline.
Au Systech, we help pharmaceutical organizations navigate evolving serialization and traceability requirements across the packaging line, site, enterprise and supply chain. That means helping teams prepare not only for the next requirement, but for the operational realities that follow.
The U.S. Food and Drug Administration is moving to a uniform 12-digit National Drug Code format for FDA-assigned NDCs. Beginning March 7, 2033, the agency will assign only 12-digit NDCs, and previously assigned 10-digit NDCs will transition to the new format.
The change applies to human drugs, including biologics, and animal drugs. It does not apply to HIPAA-standard 11-digit reimbursement formats.
The transition begins March 7, 2033, but readiness work should begin well before then. The FDA will continue assigning 10-digit NDCs until March 6, 2033, followed by a three-year labeling transition period through March 6, 2036.
That may sound like a long runway, but label updates, system changes, validation and coordination with CMOs, 3PLs and trading partners can take years. Organizations that begin now will have more time to identifier dependencies and test changes without creating unnecessary operational pressure.
No. NDC-12 may begin with a product identifier, but its impact can extend across packaging, artwork, master data, serialization, ERP, warehouse systems, financial processes, rapport and trading partner transactions.
The key issue is not simply whether individual systems can accept 12 digits. It is whether NDC data can move consistently from the packaging line through the enterprise and across the supply chain.
During the three-year transition period for labeling, both formats may appear under certain circumstances. Organizations should plan for how their systems, workflows and trading-partner processes will recognize and manage both formats.
This includes deciding how the updated identifier will be represented in master data, inventory records, transactions and reporting. Teams should also test exception scenarios, such as when a trading partner, barcode and electronic transaction do not yet use the same format.
NDC-12 should be treated as a cross-functional business initiative, not a project owned by one department. Core stakeholders may include serialization and traceability, packaging, supply chain, IT, regulatory, quality, master data, finance and commercial operations.
Contract manufacturers, repackagers, 3PLs and other trading partners should also be part of the conversation. A practical first step is to assign ownership to map, assess, plan and test every NDC touchpoint across systems, processes and partners.
FR 
EN 
PT 
DE 