NDC 12: What the FDA’s 12-Digit NDC Rule Actually Changes

The FDA’s NDC 12 rule is two changes, not one: a uniform 12-digit National Drug Code, and the end of the linear barcode requirement. Here's what changes, why the 2033 date will not move, and where to start.

The FDA’s NDC 12 rule does two things. It moves every FDA-assigned National Drug Code to a uniform 12-digit 6-4-2 format, effective March 7, 2033, with a labeling transition through 2036. And it eliminates the requirement to carry a linear barcode. Because a 12-digit NDC will not fit inside a GTIN-14, the NDC moves into its own application identifier, AI 715, so any system that derives an NDC by parsing a GTIN will break.

‍

What is the NDC 12 rule?

Every FDA-assigned NDC moves to a uniform 12-digit format arranged 6-4-2: six digits for the labeler, four for the product, two for the package size. Today three 10-digit configurations are in use (4-4-2, 5-3-2 and 5-4-1), normalized to an 11-digit form for HIPAA claims. NDC 12 replaces all of it with one format.

Scope covers human drugs, biologics and animal drugs, prescription and over-the-counter. Anything with an NDC is in scope, which reaches well past what DSCSA covers.

One detail worth knowing early: an existing NDC 11 becomes its NDC 12 by adding a leading zero. True new NDC 12s start with a 1.

As Ullrich Mayeski of GS1 put it, the NDC is probably the most important master data attribute in healthcare, and the list of organizations that have to adjust for it reaches well beyond the supply cha

‍

What are the two parts of the rule?

The biggest misconception, named at the panel by GS1’s Ullrich Mayeski, is that this is only the jump from 10 digits to 12.

The second part eliminates the linear barcode requirement, and that is where manufacturers are actually starting, because it decides packaging artwork and artwork has long lead times. The practical sequence is barcode decisions first, then the digit change in data exchange. Anyone planning the digit change alone is planning half the project.

‍

When does it take effect?

Seven years sounds generous but is not, once system changes, testing and artwork are sequenced. Most organizations are still assessing rather than implementing.

‍

Will the deadline be extended?

Plan as though it will not. FDA has said there will be no extensions, and as LSPedia’s John Monsour put it, DSCSA was phased while NDC 12 is everybody at once, driven by number exhaustion rather than policy. The FDA is running out of five-digit labeler codes, which is why the date is arithmetic rather than preference.

The consequence of betting wrong is financial: if a trading partner cannot consume 12-digit data and reimbursements or chargebacks are affected, you do not get paid.

‍

Why doesn’t a 12-digit NDC fit inside a GTIN-14?

There is no room. Many systems today embed the NDC in the GTIN and recover it by parsing digit positions. GS1’s answer is to associate rather than embed: carry the NDC in AI 715. Three consequences follow.

• The GTIN-to-NDC relationship becomes arbitrary. It will no longer be derivable, which is why a separate NDC field is now necessary.

• Any system that parses an NDC out of a GTIN is carrying a defect, whether or not it has surfaced yet.

• UPC-A cannot carry AI 715, which makes 2D barcodes necessary rather than preferable.

‍

Who is most exposed?

Manufacturers carry the biggest lift, and Bruce Harold of KeySource flagged OTC-only manufacturers as the sharpest concern. Prescription manufacturers were pulled through DSCSA already: they have serialization systems, they have moved to 2D, they are in the working groups. OTC-only manufacturers largely are not.

The other gap is government. NDC 12 is an FDA rule, but FDA cannot change the rules other agencies make about NDC reporting. HIPAA drove the 11-digit NDC for billing and has to change through a separate process. DEA, Customs and Border Protection and Veterans Affairs all consume the NDC and each needs its own rulemaking. Agency timelines are long, and an agency finishing in 2034 rather than 2033 would leave a year where required data cannot be received.

Solution providers sit in between. As Ilir Ivezaj noted, the work is not only supporting 12 digits but continuing to support the old format at the same time, and the hard part is getting integrated systems to exchange it cleanly.

‍

What are the risks of not being ready?

• Transactions stop. The NDC is tied to billing and reimbursement across healthcare.

• Product cannot be scanned or consumed, interrupting supply and reaching patients.

• Silent acceptance becomes a recall. A rejection is visible and gives you somewhere to start. Product quietly matched to the wrong item gets dispensed or referenced downstream, and what should have been a handled exception becomes a recall.

‍

How do you prepare?

Two things, per the panel. Mayeski: have a plan. Harold: do your inventory, and know everywhere you use the NDC, because it is in more places than you think. In practice:

1. Inventory every place the NDC is used, including systems you do not own and reporting you do not control. Organizations consistently underestimate this.

2. Find every system that derives an NDC from a GTIN. Each has to move to reading AI 715.

3. Get format-tolerant across 10, 11 and 12 digits, and make barcode parsing skip unrecognized application identifiers cleanly.

4. Plan EDI. HDA is advocating a move from version 4010 to 8050, which adds a qualifier for a 12-digit NDC.

5. Ask trading partners and third parties about capacity, not just compliance. Many reimbursement and chargeback vendors do not know this is coming.

‍

Starting now rather than in 2032

The Y2K comparison came up at both ends of the session and holds in both directions. It was a real engineering problem, and the date passed quietly because people started early.

This draws on the NDC 12 Readiness Panel at the 2026 LSPedia Logistics Forum, with Ullrich Mayeski of GS1, Bruce Harold of KeySource, and LSPedia’s John Monsour and Ilir Ivezaj. The full Forum recap covers the rest of the agenda.

‍