Adulteration vs Misbranding: FD&C Act 501 and 502 Explained

Adulteration vs Misbranding is the distinction between two FD&C Act classifications for drugs and devices: adulteration under §501 (21 U.S.C. 351) and misbranding under §502 (21 U.S.C. 352).

In plain terms, adulteration concerns the product itself and the conditions under which it was made, packed or held, while misbranding concerns what the label and labeling say or fail to say. Section 501(a)(1) treats a drug or device as adulterated if it consists in whole or in part of any filthy, putrid, or decomposed substance. Section 501(a)(2)(A) reaches products prepared, packed, or held under insanitary conditions whereby they may have been contaminated with filth or rendered injurious to health. Section 501(a)(2)(B) applies to a drug whose methods, facilities or controls for manufacture, processing, packing, or holding do not conform to or are not operated or administered in conformity with current good manufacturing practice. Misbranding is different in kind: section 502(a) applies if the labeling is false or misleading in any particular, and section 502(f) applies unless the labeling bears adequate directions for use and the warnings that subsection describes.

The practical consequence is that one batch can raise neither question, one, or both. A correctly labeled lot made under nonconforming controls raises a §501 question without any §502 question. A lot made under well-controlled conditions but packed with labeling that omits required directions raises a §502 question without implying contamination or a manufacturing failure. When both sets of facts exist, each ground is assessed separately against its own wording, with its own supporting evidence, rather than one classification being inferred from the other.

For investigation purposes, treat the statutory grounds as separate questions, not opposite ends of a quality scale. Ask which ground the facts support rather than assigning a legal label from an internal defect severity code. The manufacturing and labeling distinctions receive detailed treatment below; neither classification should be reduced to “minor,” “major,” or “critical.”

The operational terms in the table reflect common manufacturing practice, not statutory definitions. They describe observations, investigation activities, or controls that help organize a review without answering the legal question themselves.

A practical record therefore keeps the observed fact, the internal quality-system status, and the provision-specific assessment in separate fields. For example, out-of-specification handling can organize a result investigation, while the quality assurance process assigns review and disposition responsibilities. Record the reasoning behind any classification explicitly; do not make reviewers infer it from a deviation number, a CAPA title, or a hold status.

Start the assessment with the product category and destination market, then select the provision. Use this table as an applicability screen, not a classification decision.

The manufacturing-practice branch in 21 U.S.C. 351(a)(2)(B) expressly begins with a drug-specific condition. Do not treat that cGMP branch as a product-neutral shortcut.

21 CFR 211.1(b) addresses overlapping applicable drug regulations, including regulations pertaining to drugs that are also biological products for human use. Its conflict rule gives precedence to the regulation specifically applicable to the drug product. Include that overlap review when mapping 21 CFR 211 applicability.

Keep authority categories separate

• Binding law: statutory and regulatory rules, assessed within their product and jurisdictional scope.
• Official guidance: identify separately where relevant to an applicability assessment; do not label it statutory text.
• Recommended practice: the investigation workflows and record designs in this article are recommendations, not additional legal requirements.
• Software support: keep supporting technology distinct from legal authority and human assessment.

These three grounds distinguish the substance of a drug or device, the conditions surrounding its handling, and the composition of its container. Each calls for a different factual inquiry; a contamination-test result is not the starting point for every assessment.

What does the product contain?

21 U.S.C. 351(a)(1) addresses a drug or device consisting wholly or partly of a filthy, putrid or decomposed substance. The inquiry concerns the product itself.

Recommended evidence includes direct observations, photographs, material identity and relevant test results. Record what was observed and where it was found, rather than replacing the description with a conclusion such as “contaminated.”

How and where was it handled?

21 U.S.C. 351(a)(2)(A) addresses preparation, packing or holding under insanitary conditions whereby the product may have been contaminated with filth or rendered injurious to health. “May have been” does not make a positive contamination test a prerequisite: the assessment concerns the conditions and their potential effect on the product.

As a fact-gathering practice, reconstruct location, timing, exposure history and protective barriers. Production context tagging can help organise those facts; spillage and cross-contamination control provides related operational context for examining possible exposure routes.

What does the container contain?

21 U.S.C. 351(a)(3) addresses a container composed wholly or partly of a poisonous or deleterious substance that may render its contents injurious to health. This is a container-composition inquiry, not simply a search for visible product contamination.

Recommended evidence includes container specifications, material identity and relevant test results tied to the container actually used. Keep these evidence recommendations distinct from the statutory grounds themselves. The manufacturing-control branch is the separate subject of the next section.

21 U.S.C. 351(a)(2)(B) addresses the methods, facilities and controls used in drug manufacture, processing, packing or holding. Its test is whether they conform to—and are operated or administered in conformity with—current good manufacturing practice. The statutory purpose connects those controls to safety and to the identity, strength, quality and purity the drug purports or is represented to possess.

The interpretive consequence is important: a passing finished-product result does not answer the separate statutory question about conformity of methods, facilities or controls. That is not a shortcut from every documentation error to adulteration. The assessment must identify the suspected nonconformity and explain how the evidence supports it under this control-based ground.

Two evidence streams, different questions

In practical review, finished-product measurements describe tested samples and measured attributes. Process-control evidence addresses how manufacture or holding actually occurred: equipment status, operating conditions, material handling and recorded interventions. Neither evidence stream should be stretched beyond what it establishes.

For example, assume a drug passes its finished-product assay but an equipment-status entry is missing. The assay supports the measured attribute; it does not reconstruct equipment status. The missing entry is an observation, not proof that the equipment was unsuitable. Review contemporaneous records and their data integrity before deciding whether the gap reflects missing documentation, an actual control failure or an unresolved condition.

Four questions for a control-focused review

Use these as a recommended investigation method, not a statutory checklist:

1. What control was applicable? Identify its purpose, operating criteria and relevance to the drug and operation.
2. What actually happened? Describe the observed event without inserting a presumed cause.
3. What evidence establishes or contradicts the suspected control failure? Consider both supporting and contrary records, including limitations of the test results.
4. What products, equipment, time periods or lots may share that condition? Define the potential scope from common exposure or control history, not merely the lot initially reviewed.

Keep the observation, root-cause hypothesis and statutory assessment separate. A useful conclusion explains what is established, what remains uncertain and why the identified condition does—or does not—support the proposed classification.

False or misleading labeling

21 U.S.C. 352(a)(1) establishes a misbranding ground when labeling is false or misleading in any particular. Straightforward examples for assessment include a drug bottle labeled “60 tablets” that actually contains 30, or device labeling stating “latex-free” when the product contains latex. These examples assume the stated product facts are established. The review question is what the labeling represents about the product, not simply whether the artwork contains a typographical error. For quantitative representations, keep the label claim distinct from the release limit when organizing the comparison.

Registration, listing and restricted-device advertising

21 U.S.C. 352(o) includes manufacture, preparation, propagation, compounding or processing in an establishment not duly registered under section 360, and omission from a list required by section 360(j). Assess whether the referenced registration or listing obligation applies to the establishment and product concerned; do not assume identical obligations for every site or product. A label-only checklist is therefore insufficient for assessing all these selected grounds.

21 U.S.C. 352(q)(1) also addresses false or misleading advertising, specifically for a restricted device distributed or offered for sale in any State. Both the restricted-device status and the distribution or offer-for-sale condition matter; this provision should not be restated as a rule covering every advertisement for every device.

Three evidence groups for operational review

As recommended review practice—not an additional statutory checklist—organize the assessment around three evidence groups:

1. Representations: retain the exact labeling or advertising version, its dates of use and the statements being assessed. Preserve the complete context rather than only a cropped phrase.
2. Applicability identifiers: record the establishment identity, relevant activity, product identifiers and registration or listing records needed for the applicability review. A blank internal database field is not, by itself, evidence of a registration failure.
3. Affected population: connect each version and establishment record to the relevant products, lots and distribution period. Use the batch record where it helps establish that relationship; distinguish confirmed associations from unresolved ones.

These hypothetical cases separate assumed facts from the evidence needed to document scope. The statutory classifications apply to those assumptions; the suggested evidence checks are review practice, not additional statutory requirements.

Case 1 — Control failure despite passing assay results

Assumed facts: A U.S. drug investigation establishes an applicable cGMP control failure during holding. Tested samples meet the laboratory acceptance criteria. No separate labeling issue is assumed.

Supported classification: The established control failure supports adulteration under 21 U.S.C. 351(a)(2)(B). Applying the control-based reasoning above, passing assay results do not establish that the holding methods or controls conformed. These facts do not independently support a misbranding classification.

Evidence still needed: Document which lots experienced the failed control, the relevant holding period, and how tested samples relate to those lots. Preserve the investigation finding alongside original holding records and assay reports; do not substitute the latter for the former.

Case 2 — False strength statement

Assumed facts: Independently confirmed tablets contain 10 mg per tablet, but a packaging error places them in cartons stating 20 mg per tablet. There are 12,000 saleable cartons, with one bottle per carton. A traceability review identifies 1,800 cartons bearing the wrong artwork.

Supported classification: The false strength statement supports assessing misbranding under 21 U.S.C. 352(a)(1). Do not infer an additional legal ground merely from the numerical discrepancy.

Population calculation: 1,800 ÷ 12,000 × 100 = 15%. This is the fraction of cartons identified by the review—not a statistical estimate, a legal tolerance, or proof that the remaining cartons are unaffected.

Evidence still needed: Retain the strength confirmation and actual carton artwork, then substantiate the carton-to-bottle mapping and review coverage. Production context tagging is relevant to connecting packaging runs, artwork versions and identified units.

Case 3 — Potential overlap with separate support

Assumed facts: A U.S. device was held under insanitary conditions whereby it may have been contaminated with filth. Separate evidence establishes that its labeling falsely claims sterility.

Supported classifications: Assess adulteration under 21 U.S.C. 351(a)(2)(A) and misbranding under 21 U.S.C. 352(a)(1) independently. The assumed facts support both grounds, but the insanitary condition alone does not prove that the sterility representation was false.

Evidence still needed: Identify the devices exposed to the holding conditions and those bearing the sterility claim. Retain condition records, labeling and the separate evidence disproving sterility, with each linked to its own assessment. Do not assume the two affected populations coincide without tracing them.

Use the following recommended investigation workflow within the quality assurance process. It is not a statutory procedural sequence; its purpose is to move from an observation to a reasoned, reviewed classification.

1. Capture the original observation. Record what was seen, when, where and by whom. Separate direct observations from initial explanations.
2. Identify product and jurisdiction. Establish the product category, intended use and relevant market before selecting provisions for assessment.
3. Define a provisional affected population. Identify potentially affected lots, units, operations and time periods. Retain each scope revision and its rationale, including reasons for excluding material.
4. Preserve evidence. Retain original records, samples and labeling versions as relevant. Use an audit trail review workflow where record changes could affect the assessment.
5. Assess each relevant ground independently. Give each provision a status: pending, supported, not supported or unresolved. Do not force adulteration and misbranding into mutually exclusive selections. Explain the evidence and remaining uncertainty behind each status.
6. Document the reviewed decision. Record the reviewer, date, reasoning and disposition of open questions rather than replacing the investigation history with a final label.
7. Track corrections and follow-up. Assign actions, owners and review dates; check completion and whether new findings warrant reassessment.

Route questions according to the facts: manufacturing for operations, laboratory personnel for analytical findings, labeling personnel for content and versions, quality for investigation coordination, and regulatory personnel for applicability. Give every open question an owner and designate an escalation point for unresolved applicability.

Use a case-centered record design as recommended investigation practice—not an application database schema or legally prescribed form. Link each case to its product scope and affected population; link observations to preserved evidence; keep provision-specific assessments separate from those observations.

Use consistent identifiers for production context tagging, so evidence from different locations or time periods remains distinguishable. Where a discrepancy is under investigation, a corrected entry should remain distinguishable from the original observation rather than replacing it.

An assessment should explain how its cited evidence supports or contradicts the conclusion. Identify unresolved questions explicitly: an empty result field is not a negative finding, and missing evidence is not evidence that a condition was absent.

Use bin-level lot genealogy references where location history helps define the population. Keep confirmed, potential and excluded populations distinct as evidence develops. These statuses organize investigation scope; they do not substitute for the statutory assessment.

Treat cross-system handoffs as evidence-management design, not as proof of compliance or a promise of application connectors. Link production records to laboratory samples and results, inventory lots and movements, controlled labeling versions, and investigation cases. Reconcile stable product, lot, sample, case and record identifiers plus record versions; free-text product names alone are insufficient matching keys. Consistent production context tagging helps preserve these relationships.

For MES–QMS handoffs, define the authoritative source for each record type and retain its identifier in the receiving record. Use these recommended recovery controls:

• Missing imports or delayed laboratory results: flag the gap rather than treating absence as an acceptable result.
• Duplicate events: reconcile event identifiers before counting observations or affected units.
• Mismatched lot identifiers: resolve the mapping before attaching evidence to a case.
• Superseded artwork: establish which version was actually used, not merely which is current.

Route unresolved records to an exception queue, preserve original content, and reconcile against the authoritative source before changing the case conclusion. Keep technical delivery status separate from evidence review status: a successfully transferred record may contain a disputed observation; a failed transfer does not itself establish a product defect.

Treat the following as risk-based investigation practices, not a list of mandatory actions under §§501–502.

• Contain provisionally. Consider segregating identified stock, restricting further use while facts are assessed, and preserving implicated labeling and production records. Suitability depends on the product, distribution status and investigation facts. For distributed units, use the distribution traceability work described in recall readiness to inform the assessment—not to presume a recall decision.
• Match remediation to the established cause. Correcting an artwork file changes future labeling; it does not correct already labeled inventory or resolve a separate manufacturing-control failure. Define how affected units will be addressed and what changes apply to future production, with separate completion evidence for each.
• Escalate unresolved questions. Refer uncertain legal applicability and distribution questions to qualified regulatory and legal reviewers. Keep the case classification, operational response and assessment of potential regulatory action as separate decisions. Record each decision’s owner and rationale; do not treat completed remediation as an automatic legal cure.

Keep the decision boundary explicit: human reviewers determine the adulteration or misbranding classification, approve decisions and release product. Record assembly is not a compliance certification or an automatic legal conclusion. Treat the assembled record as an input to review, not a substitute for assessing what the evidence establishes.

Use these recommended practice checks before closing an investigation; they are not additional statutory requirements.

• Confirm product and jurisdiction.
• Identify the exact ground being assessed.
• Preserve original evidence and its version.
• Reconcile the affected population.
• Document supporting and contrary facts.
• Assign unresolved questions to named owners.
• Record the reviewed rationale.
• Connect corrections to their cause.
• Define a follow-up review and an effectiveness check.