FDA Drug Shortage Reporting Under Section 506C: When and What to File

If your company holds an approved NDA, ANDA, or BLA, or manufactures active pharmaceutical ingredients that feed into a covered finished product, Section 506C of the Federal Food, Drug, and Cosmetic Act is not a discretionary courtesy notification. It is a statutory reporting obligation, and getting the timing or the content wrong is one of the few compliance failures the FDA makes publicly visible by name.

This guide goes deep into who must report under Section 506C, exactly when a notification is due, what the FDA expects inside that notification, and what actually happens to companies that miss the deadline. If you are searching for FDA 506C reporting requirements, drug shortage notification FDA, how to notify FDA of manufacturing discontinuance, or FDA drug shortage compliance consultants, this is written for you.

What Section 506C Actually Requires

Section 506C of the FD&C Act requires manufacturers of certain drugs and biologics to notify the FDA of a permanent discontinuance, or a temporary interruption, in manufacturing that is likely to lead to a meaningful disruption in the supply of a covered drug in the United States. The obligation was added by Title X of the FDA Safety and Innovation Act, FDASIA, in 2012, and was significantly expanded by the CARES Act in 2020, which brought active pharmaceutical ingredients into scope for the first time.

The purpose is preventive, not just administrative. Early notification gives the FDA’s Drug Shortage Staff time to work with manufacturers, and where relevant other producers of the same or therapeutically equivalent product, before a shortage actually reaches patients and pharmacies. FDA’s own annual reports to Congress credit this early notification requirement with materially reducing the number of shortages that would otherwise have occurred.

Who Must Report

The notification requirement applies broadly, and one detail that gets missed constantly is that it applies to each individual sponsor separately, regardless of:

• Market share held by that manufacturer
• The number of other companies marketing therapeutically equivalent products
• The volume of product currently in distribution

In other words, a company cannot assume it is exempt simply because its product represents a small slice of the overall market, or because three other manufacturers make the same drug. Every covered sponsor carries an independent reporting obligation.

The requirement covers:

• Manufacturers with an approved New Drug Application, NDA
• Manufacturers with an approved Abbreviated New Drug Application, ANDA
• Manufacturers with an approved Biologics License Application, BLA
• Manufacturers of certain finished products that do not require approval but meet specific statutory criteria
• Since the CARES Act amendments, manufacturers of active pharmaceutical ingredients that are intended for incorporation into a covered finished product

Biological products licensed under section 351 of the Public Health Service Act are also covered, including vaccines and blood products, with the notable exception of source plasma and products that also meet the legal definition of a device.

A point that is genuinely underappreciated: even though API manufacturers are now covered under the statute, they are only responsible for estimating the impact of their own API on the availability of their own finished products, not for assessing the broader market. This is a narrower obligation than many compliance teams assume when they first read the CARES Act amendments, and over-scoping the analysis wastes internal resources that would be better spent on getting the finished-product notification right.

When You Must File

Timing is where most 506C failures actually happen, and the rule is more specific than a simple deadline.

• The default requirement is to notify FDA at least six months before a permanent discontinuance or a manufacturing interruption takes effect
• If six months’ advance notice is genuinely not possible, the manufacturer must notify FDA as soon as practicable
• Regardless of circumstance, notification must occur no later than five business days after the discontinuance or interruption actually occurs

This creates three distinct scenarios companies need to plan for separately: a fully planned discontinuance where six months’ notice is realistic, a shorter-notice interruption where “as soon as practicable” applies, and an unplanned event, such as a contamination finding or equipment failure, where the five business day backstop becomes the operative deadline. Treating all three scenarios under a single internal SLA is a common structural mistake that leads to missed windows during genuine emergencies, precisely when the notification matters most.

For interruptions in API manufacturing specifically, the same general framework applies, but the guidance is explicit that the analysis stays limited to that API’s effect on the sponsor’s own finished product supply, not a market-wide impact assessment.

What Must Actually Be Included in the Notification

FDA’s regulations implementing Section 506C, found at 21 CFR 310.306, 314.81, and 600.82, together with the agency’s guidance on the topic, describe the information a notification needs to contain. In practice, a compliant notification should address:

• The identity of the product, including strength, dosage form, and NDC where applicable
• Whether the event is a permanent discontinuance or a temporary interruption
• The reason for the discontinuance or interruption, described with enough specificity for FDA’s Drug Shortage Staff to assess real impact
• The expected duration of the interruption, where known, or a realistic estimate if the exact timeline is not yet confirmed
• For finished products, an assessment of whether the event is likely to lead to a meaningful disruption in US supply
• For APIs, an assessment limited to the impact on the sponsor’s own finished product, not the wider market

One detail that rarely gets covered outside specialist guidance: the notification obligation does not disappear if a company believes another manufacturer will simply absorb the demand. FDA’s stated position treats the sponsor’s own notification duty as independent of what other manufacturers in the market are doing, which means internal legal and regulatory teams should not build a “someone else will cover it” assumption into their reporting decision tree.

What Happens if You Do Not Report

This is the part of Section 506C that most compliance guides skip over, and it is the most consequential. The statute does not just require manufacturers to notify the FDA. It also requires the FDA to send a formal noncompliance letter to any firm that fails to notify the agency in accordance with Section 506C.

These noncompliance letters, and the manufacturer’s written response, are published on FDA’s website by product and by company name. Companies that have appeared on this public list include major, well-resourced manufacturers, not just smaller generic producers, covering products such as injectable oncology drugs, sterile injectables, and other clinically significant medicines. This is a rare instance of the FDA making an individual company’s compliance failure a matter of public record by name, rather than folding it into aggregate enforcement statistics, and it is a reputational exposure that many regulatory affairs teams underweight when they assess the real cost of missing a 506C deadline.

Beyond the public noncompliance letter, missed or incomplete notifications also remove the FDA’s ability to work proactively with a manufacturer, and in some cases with competing manufacturers, before a shortage becomes acute. That lost lead time can directly affect patient access to critical medicines, which is the underlying reason Congress built a mandatory public disclosure mechanism into the statute rather than leaving compliance purely to voluntary good practice.

How FDA Uses the Information Once Filed

Once a notification is received, FDA’s Drug Shortage Staff works to determine whether the event is likely to actually cause a shortage, and if so, what mitigation options exist. This can include working with the notifying manufacturer on timelines, coordinating with other manufacturers of the same or therapeutically equivalent products, and in some cases supporting temporary importation or other regulatory flexibilities to bridge a gap in supply. FDA also maintains a public, continuously updated list of drugs currently in shortage under section 506E of the FD&C Act, with biologics tracked on a separate list, so a well-timed 506C notification is often the first data point that eventually feeds into that public shortage list.

Practical Steps for Building a Compliant 506C Process

• Map every NDA, ANDA, BLA, and covered API against the 506C obligation individually, rather than assuming coverage at the company or product family level
• Build three separate internal timelines, one for planned discontinuances, one for shorter-notice interruptions, and one for the five business day emergency backstop, rather than a single generic SLA
• Assign clear ownership for API-related notifications separate from finished product notifications, since the scope of impact assessment differs between the two
• Draft notification content templates in advance that map directly to the elements FDA’s guidance expects, so a real event does not become a drafting exercise under time pressure
• Review the FDA’s published noncompliance letters periodically as part of ongoing regulatory intelligence, since they reveal the specific patterns of failure the agency has actually penalised
• Treat the six month advance window as the default target even for events that feel operationally minor, since FDA’s own data credits early notification with preventing a meaningful share of potential shortages before they occur

Getting Ready for Section 506C Compliance

Section 506C sits at the intersection of regulatory affairs, manufacturing operations, and supply chain risk management, which is exactly the kind of cross-functional regulatory work Quality and Vigilance Ltd supports clients through, alongside its core pharmacovigilance and regulatory affairs remit covering EMA, FDA, and MHRA requirements. Missing a 506C deadline does not just create a compliance gap, it creates a public record that customers, competitors, and regulators can all see. For companies that want to build a defensible, audit-ready 506C process rather than a reactive one, the practical support that actually moves the needle looks like this:

• Building sponsor-level 506C obligation maps across your full NDA, ANDA, BLA, and API portfolio
• Structuring separate notification playbooks for planned, short-notice, and emergency discontinuance scenarios
• +
• Reviewing existing SOPs against FDA’s current guidance to close gaps before they turn into a noncompliance letter

Get in touch with Quality and Vigilance Ltd today to build a Section 506C reporting process that keeps your company off the FDA’s noncompliance list.