Product and item master data
Locate every system that stores, transforms, validates, or displays an NDC.
The FDA's uniform 12-digit NDC format takes effect on 7 March 2033. Start by mapping the systems, labels, data flows and trading-partner dependencies affected, then build a practical testing and validation plan for the transition.
Plan ahead of 7 March 2033, with time to assess dependencies, testing and validation.
The identifier travels through data, labels, interfaces, partner connections, reporting, and validated processes. Readiness means understanding the full path before implementation starts.
Locate every system that stores, transforms, validates, or displays an NDC.
Review templates, print controls, line systems, barcode content, and approval cycles.
Test platform logic, interfaces, validation rules, repositories, and event processing.
Map where manufacturers, CMOs, 3PLs, wholesalers, and customers depend on the value.
Find assumptions in analytics, regulatory reporting, finance, reimbursement, and support tools.
Sequence SOP, testing, documentation, training, release, and business-continuity changes.
A yes-or-no capability answer is not a readiness plan. The real work is identifying dependencies, transition states, ownership, and the cost of carrying the current setup forward.
Where is the NDC parsed, normalized, converted, or used as a key?
Which internal and external systems still assume a 10- or 11-digit representation?
Can operations safely support 10- and 12-digit formats during the transition?
Which label, line, repository, and partner changes need coordinated validation?
What will upgrades, renewal and ongoing support cost with your current provider?
Could this review also reduce the work your team handles every day?
Compare improving your current setup with moving to a new provider. Understand the cost, migration work and ongoing support each option requires.
Keep your current provider if the technology, validation plan, commercial terms and ongoing support meet your needs.
Consider a change if upgrades, rising renewal costs or gaps in support are adding work and uncertainty.
Systems, labels, integrations, partners, and validated processes affected by the format change.
What must change, what can wait, and how to support the transition without operational disruption.
Compare updating your current setup with moving to a new provider on a timetable that works for you.
Validation, integration, partner, service, and operating costs made visible before commitment.
Supported interoperability can help preserve existing connections. Your migration assessment identifies what can stay in place and where testing, qualification or re-onboarding is needed.
Customer migrations from other providers completed by SoftGroup over three years.
Compare three-year costs across software, service delivery, staffing, validation and migration.
No. The final rule was published on 5 March 2026 and takes effect on 7 March 2033. FDA intends the intervening period for affected parties to update systems, processes, infrastructure, and labeling.
FDA says affected parties should be capable of handling both formats during the three-year labeling transition from 7 March 2033 through 6 March 2036.
The preparation period runs through 6 March 2033. Begin by mapping affected systems and partner dependencies, then allow time for updates, coordinated testing and validation before the format takes effect.
No. FDA states that the final rule affects FDA-assigned NDCs and does not change NDC formats used for other purposes, including the HIPAA standard 11-digit format.
Not automatically. The readiness review should show whether the current path remains the best technical, operational, and commercial choice. It should also show whether this is the least disruptive time to change.
Discuss your systems, partner connections and renewal plans. We’ll help you identify where to start your readiness review.