Stood Up by the FDA. Again.
The FDA has missed its date to publish the final rule for NDC12. This heightens the risk for the industry. This article explores one option the FDA can use to extend the deadline, but it carries consequences we must understand.
How to Survive a Bad Boyfriend Who Won’t Commit to NDC12.
The final NDC12 rule was supposed to be here on January 31, 2026.
Not proposed.
Not hinted at.
Final.
Instead, the pharmaceutical industry is still waiting.
Again.
This marks the third time the FDA has missed its expected timeline for publishing the final NDC12 rule. No revised date. No formal explanation. Just continued uncertainty layered on top of an already complex transition.
That uncertainty has consequences.
NDC12 is not a policy debate. It’s a capacity problem. NDC labeler codes continue to be consumed, systems across the healthcare supply chain remain tightly coupled to drug identifiers, and organizations are being asked to plan significant system changes without a firm regulatory anchor.
Missed dates do not stop the clock.
They just make preparation harder.
Why the Third Miss Hurts More
One missed date is understandable.
Two creates hesitation.
Three change behavior.
Budgets pause.
Projects slow.
“Let’s wait and see” becomes the default response.
Not because teams are careless. Because committing resources without final guidance carries real risk. Meanwhile, the underlying issue that triggered NDC12 has not changed.
Identifier exhaustion is still real.
Dual-format complexity is still coming.
And the industry remains deeply interconnected.
Venting to Someone Who Gets It
Last week, I was lamenting with my friend Alex Colgan (alex.colgan@ledgerdomain.com) from ledgerdomain.com about being stood up so many times by the FDA.
“If the FDA keeps missing dates, what does that actually mean?”
“Could they buy more time?”
“Is there another move we’re not talking about?”
Alex is a longtime industry colleague. A friend. Someone who works closely with the industry and is one of the smartest people I know. I once heard Alex use the word “ameliorate” in a sentence, as if everyone understood its meaning. Most of us did not, but pretended that we did.
So I asked him to weigh in.
Because there is a scenario people quietly speculate about. One that could extend the runway. And one that carries real risk if misunderstood.
I’ll let him take it from here.
Guest Perspective
Alex Colgan on Reusing Labeler Codes
Alex’s perspective below focuses on one scenario being discussed quietly across the industry and why it’s far riskier than it sounds.
FDA running out of NDCs is a mathematical certainty.
And like a lot of long-term unresolved issues, it can blow up (data) relationships at the worst possible time. But you might be surprised to learn that a huge share of the NDC “real estate” is sitting unused.
The first segment of the NDC, the labeler code, identifies the organization responsible for labeling the product. Over decades, the pharmaceutical supply chain has accumulated mergers, acquisitions, bankruptcies, closures, and quiet market exits.
The result is predictable: out of roughly 10,000 available labeler-code slots, only about 5,300 are currently claimed and active. That leaves roughly 4,700 empty slots: namespaces tied to companies and product portfolios that are no longer actively on the market.
On paper, that looks like an obvious way to buy time without making the hard commitment. FDA could repurpose those vacant assignments and delay the rollout of NDC 12. This would avoid constraining new entrants and new therapies, and reduce the risk of a system-wide “error-pocalypse” across devices and software that have hardcoded assumptions about today’s NDC format and length.
The problem is the downstream reality of how NDC data actually gets used.
NDC databases aren’t only consumed live. They’ve been scraped and archived for as long as the public files have existed. Solution providers across inventory, dispensing, billing, claims, analytics, and compliance routinely operate on older snapshots. Sometimes, because that’s what their customers deployed years ago, sometimes because auditability and reproducibility require it.
A product’s commercial retirement doesn’t erase its operational footprint. Historical NDCs still surface during audits, chargebacks, returns, reconciliations, pharmacovigilance lookbacks, and long-tail account cleanups. Systems still need to resolve those codes years later.
Recently, we encountered an issue where a long-retired product code reappeared elsewhere in a totally different context. This caused a major exception, and resulted in product being quarantined. A workaround eventually got it released, but the incident was costly and disruptive.
If unique labeler codes start getting reused, that kind of failure mode stops being a rare edge case and becomes part of normal operations.
Unique identifiers play by different rules. Once you reuse them, you’re blurring the meaning across every historical system and audit trail, and that kind of confusion never helps a long-term relationship.
We have a lot of work ahead of us on NDC 12, and while delay tactics might buy some time, they ultimately cost the industry more.
Waiting by the Phone Doesn’t Change the Outcome
Let’s be honest.
Whether the FDA publishes the final NDC12 rule tomorrow or next year, the ultimate deadline remains the same. We will need to upgrade before we run out of labeler digits. This is a Y2K-type problem. The industry is still moving toward a 12-digit identifier. Dual formats are still unavoidable. And the work still lands inside each organization.
Reused labeler codes may buy time, but they come with consequences.
In relationships, being stood up once is annoying.
Being stood up three times is a real problem.
The question is no longer when the call will come.
It’s what you do while waiting.