Understanding the rule’s impact on systems, product identification, and barcoding is the first step toward a practical implementation strategy.
In March 2026, the FDA finalized the NDC Format and Barcoding Rule. The rule establishes a uniform 12-digit NDC in a standardized 6-4-2 format and updates the barcode requirement for prescription drugs and over-the-counter drugs commonly used in hospitals. The changes take effect March 7, 2033. Learn more about the NDC Format and Barcoding Rule at https://ndcforum.org/resources#rule-overview.
The FDA’s transition to a standardized 12-digit National Drug Code (NDC) may appear to involve adding two digits to an existing product identifier. Its implications extend across data models, product identification, packaging, scanning, and downstream trading-partner workflows.
For implementation planning, organizations should evaluate three connected impacts:
Systems must accommodate 12-digit NDC fields and representations.
The NDC and Global Trade Item Number (GTIN) must be managed as distinct identifiers, with explicit mappings where needed.
Barcode formats and scanning infrastructure for prescription drugs and OTC drugs commonly used in hospitals must evolve.
Each presents a different set of challenges and requires a different planning strategy.
1. What the 12-Digit NDC Means for Systems
The first and most obvious impact is technical.
Today, FDA-assigned NDCs use three segments totaling 10 digits, with several permitted configurations. Beginning March 7, 2033, the FDA will use a single standardized 12-digit format consisting of a six-digit labeler code, four-digit product code, and two-digit package code. Existing NDCs will be converted by adding leading zeros to the appropriate segments.
Organizations will need to ensure that every system and interface that stores, processes, validates, displays, or transmits FDA NDCs can accommodate the new format.
That includes product master data, pharmacy applications, inventory platforms, databases, interfaces, reporting tools, analytics platforms, application programming interfaces, and legacy software.
Expanding a field alone may leave hidden dependencies unresolved. Applications may contain hard-coded assumptions about NDC length, segment structure, or conversion rules, and leading zeros must be preserved throughout the data lifecycle.
Organizations will also need to accommodate multiple NDC representations during the transition. For a period of time, systems may encounter legacy 10-digit FDA NDCs, 11-digit billing formats used in reimbursement transactions, and the new standardized 12-digit format. Each version may include different padding conventions or segment structures, so organizations must define clear rules for storing, converting, displaying, validating, and exchanging each representation. Without consistent crosswalks and controls, the same product could be interpreted differently across internal systems or by trading partners, creating risks for claims processing, inventory management, reporting, and other workflows.
How to begin preparing:
Start with a comprehensive inventory of systems and processes that use NDCs. Identify where the identifier is stored, transformed, validated, exchanged, or used in business logic.
Engage your technology vendors early, establish requirements, and incorporate NDC-related changes into existing modernization plans.
For OTC drugs not commonly used in hospitals, this may represent the largest portion of the implementation work. For prescription drugs and OTC drugs commonly used in hospitals, the systems work also connects to product-identity and barcode decisions.
2. Why NDC and GTIN Must Be Managed Separately
The second impact is a major systems-architecture consideration.
Today, many pharmaceutical products use a GTIN structure that incorporates the NDC. In these environments, the NDC and GTIN are closely coupled, allowing organizations to use a single underlying product identification value across regulatory and commercial processes.
This has important practical advantages. Companies have not always needed to make a clear architectural distinction between systems organized around the NDC and those organized around the GTIN.
The move to a 12-digit NDC changes that relationship and requires organizations to revisit their product-identity architecture.
The new 12-digit NDC cannot be embedded in the existing GTIN structure using the same approach. Organizations that currently rely on this relationship will need to manage the NDC and GTIN as separate identifiers, with explicit mappings between them.
Organizations should answer a fundamental architectural question:
Should product identification systems be anchored around the NDC, the GTIN, or another internal product identifier, and how should those identifiers relate to one another?
The answer can affect enterprise resource planning systems, product masters, packaging and labeling applications, warehouse systems, serialization platforms, ordering, inventory, and trading-partner interfaces.
This challenge is best evaluated through the structure of an organization’s existing product-identification architecture rather than product classification alone.
The key question is whether the existing product-identification architecture embeds the NDC within the GTIN.
Many consumer-oriented OTC products, such as toothpaste or deodorant, already maintain separate regulatory NDC and commercial GTIN identifiers. For these products, the transition may primarily involve expanding the NDC field and updating related mappings.
Prescription products and certain OTC products that use NDC-derived identifiers, including OTCs commonly used in hospitals that are subject to the barcode rule, may require more significant architectural changes.
Two products with the same regulatory classification may therefore have very different implementation requirements depending on how their identifiers are structured today.
How to begin preparing:
Determine whether your organization currently embeds the NDC within the GTIN or derives one identifier from the other.
Identify systems that treat NDC and GTIN as interchangeable.
Establish a target product-identification architecture that explicitly manages the relationship among NDCs, GTINs, and internal product identifiers.
This is an enterprise data and product-identity decision that should be made early enough to guide downstream development.
3. How Barcode and Scanning Infrastructure Will Change
The third major impact is closely connected to the second: barcoding.
Today, prescription drugs and OTC drugs commonly used in a hospital use UPC-A linear barcodes to encode the NDC and GTIN on the package. Because the standardized 12-digit NDC cannot be incorporated into that existing structure in the same way, the current NDC-derived UPC-A approach will need to change.
Organizations will need to evaluate alternative barcode strategies. Current industry planning often points to the 2D Data Matrix required by the Drug Supply Chain Security Act for prescription drugs. OTC products and certain packaging configurations may require different linear symbologies capable of representing the NDC.
This is occurring alongside another major industry development. GS1’s Sunrise 2027 is advancing the ability of retail point-of-sale systems to process two-dimensional barcodes.
The NDC transition and Sunrise 2027 are distinct initiatives, but their interaction creates an important strategic consideration. Organizations making investments in packaging, labeling, barcode generation, scanning, and data infrastructure should consider how those investments support both near-term requirements and longer-term product identification needs.
The impact will vary by product and existing architecture.
Products that already use commercial GTINs independently from their NDCs may have fewer changes to existing retail barcode structures. Products whose barcodes depend on an NDC-derived identifier may require more substantial changes.
The implications extend well beyond the manufacturer.
Distributors, pharmacies, hospitals, wholesalers, automation providers, and other downstream organizations must be able to scan, interpret, and exchange information from the barcode formats that manufacturers ultimately adopt.
How to begin preparing:
Inventory current barcode formats and identify where they depend on NDC-derived identifiers.
Evaluate packaging and labeling equipment, scanning hardware, software, and downstream workflows.
Engage GS1, technology vendors, and trading partners to understand emerging standards and implementation approaches.
Barcode decisions should be made together with product-data architecture and downstream scanning requirements.
Bringing the Three Impacts Together
These three impacts can be analyzed separately, but implementation decisions are closely connected.
A decision about product-identification architecture affects how NDCs and GTINs are stored and mapped. That decision can influence barcode strategies, which in turn affect packaging equipment, warehouse operations, pharmacy systems, and trading-partner interfaces.
The transition therefore requires an integrated program that connects technology, product data, packaging, barcoding, testing, and partner coordination.
Organizations should begin by establishing an accountable implementation lead, inventorying affected systems and identifier relationships, identifying external dependencies, and developing an integrated roadmap for system changes, product-data decisions, barcode updates, and testing.
They should also recognize that some of the most consequential decisions will depend on standards organizations, regulators, technology vendors, and trading partners.
The NDC Coordination and Implementation Forum brings these stakeholders together to develop shared visibility into implementation milestones, align technical approaches, identify emerging dependencies, and work through cross-sector challenges.
Through its ecosystem-wide roadmap, Quarterly Forums, and focused Strike Forces, the Forum provides a way for organizations to understand how their implementation strategies connect to decisions being made elsewhere.
The 2033 deadline may seem distant, but the architecture, standards, and infrastructure decisions that determine readiness must begin much sooner.
Organizations that start now and coordinate their approaches with the broader ecosystem will be better positioned to reduce rework and achieve a successful transition.
Learn more about the NDC Forum, become a member, and find opportunities to participate at https://ndcforum.org/get-involved.