The DMF reference on a peptide listing: what a Drug Master File is, and what invoking one would require

A recurring pattern on peptide product pages is the invocation of a regulatory artifact as though it were a property of the material. “GMP-grade” is the common example — a claim about a manufacturer’s quality system presented as if it were a measured attribute of the contents of a vial. A “Drug Master File” or “DMF number” reference belongs to the same family. It sounds like a credential, and in its proper setting it corresponds to real work. But a DMF is a specific kind of submission that acquires meaning only inside a particular process, and that process is the review of an application to market a drug. Detached from that pathway, a DMF number is not a grade, not an approval, and not something a certificate of analysis can substantiate. This post sets out what a Drug Master File actually is, how one is referenced, and why the reference does not transfer to material sold outside the application pathway it was built to support.

What a Drug Master File actually is

A Drug Master File is a submission to the U.S. Food and Drug Administration, governed by 21 CFR 314.420, that provides confidential detailed information about facilities, processes, or articles used in the manufacturing, processing, packaging, and storing of human drug products. The mechanism exists to solve a specific problem: a supplier — for instance, the maker of an active ingredient or a packaging component — often possesses proprietary manufacturing detail it does not want to hand to its customer, yet that detail is exactly what FDA needs to see in order to evaluate the customer’s application. The DMF lets the supplier file that information directly with the agency, so a customer’s application can rely on it without the customer ever seeing it.

Two features of the mechanism are easy to miss and important to state plainly. First, a DMF is not required by any statute or regulation; it is a voluntary convenience for handling confidential information. Second, and more consequential for how the term gets used commercially, FDA neither approves nor disapproves a Drug Master File. There is no such thing as an “approved DMF.” The agency reviews the technical contents of a DMF only in connection with its review of an application that references it — a New Drug Application, an Abbreviated New Drug Application, an Investigational New Drug application, or a Biologics License Application. Absent such a referencing application, the file simply sits on record, unexamined on its merits. A DMF number confirms that a submission was assigned an identifier. It does not certify that anyone at the agency has evaluated, let alone endorsed, its contents.

The four current types, and the one that vanished

DMFs are organized by the kind of information they hold. Under current FDA classification there are four types:

Type II — a drug substance, drug substance intermediate, or material used in their preparation; or a drug product. This is the category that covers active pharmaceutical ingredients, and it is the one most often invoked in a supplier context.
Type III — packaging material.
Type IV — an excipient, colorant, flavor, essence, or material used in their preparation.
Type V — FDA-accepted reference information not covered by the other types.

A fifth designation, Type I, once existed and covered manufacturing sites, facilities, operating procedures, and personnel. It was discontinued by a Final Rule published on 12 January 2000 (65 FR 1776); that category of information now belongs directly in the Chemistry, Manufacturing, and Controls section of the application itself rather than in a separate file. The numbering of the remaining types was left unchanged, which is why the current set reads II through V with no Type I — a small historical artifact that occasionally causes confusion when older references are consulted alongside current ones.

The distribution matters for peptides specifically. A synthetic peptide offered as a drug substance would sit in the Type II category. That placement says what kind of article the file describes. It says nothing, on its own, about the quality of any particular lot, because — as above — the file’s technical adequacy is assessed only when an application leans on it.

The letter of authorization

The device that connects a DMF to an application is the letter of authorization. When an applicant wants FDA to consult a supplier’s DMF during review of the application, the DMF holder issues a letter authorizing that reference and identifying the specific application and the specific information to be relied upon. The applicant files a copy; FDA then reads the referenced DMF as part of reviewing that application.

The letter of authorization is worth dwelling on because it clarifies who sees what. The DMF holder discloses nothing to the applicant — the confidentiality that motivated the DMF in the first place is preserved. FDA sees the contents; the referencing party does not. This is the entire point of the arrangement, and it has a direct consequence for how the concept can and cannot be marketed. A meaningful DMF reference is inherently tied to a named application and a specific authorization. A number presented in the abstract, unattached to any referencing filing, has skipped the only step at which the file’s contents come under review. Whatever assurance a DMF can offer is delivered through the review of the application that references it, not through the existence of the number.

What GDUFA changed for Type II API files

The one context in which a DMF undergoes a defined administrative check independent of a full application review is worth describing accurately, because it is sometimes stretched into more than it is. The Generic Drug User Fee Amendments (GDUFA) introduced, for Type II DMFs used to support ANDAs, a set of provisions: an annually set user fee, a completeness assessment, and a public list of DMFs that have passed that assessment and are “available for reference.” These provisions apply specifically to Type II API DMFs supporting generic-drug applications; they do not extend to other DMF types, nor to Type II files used exclusively to support NDAs or INDs.

The completeness assessment is precisely what its name says and no more. It is a series of administrative questions a DMF must satisfy before it is placed on the available-for-reference list. FDA is explicit that it does not replace the full scientific review that determines whether the DMF is adequate to support a regulatory action. In other words, appearing on the availability list means the paperwork is administratively complete, not that the chemistry has been judged sound. Type V files have seen their own procedural developments — a January 2025 Federal Register notice opened a public docket on using a Type V DMF for model master file submissions to support ANDAs, and draft guidance has addressed Type V files for certain CDER-led combination products — but these refine how the mechanism is used, not what a DMF fundamentally is. Across all of it, the through-line holds: administrative steps confirm that a file is present and complete; scientific adequacy is established only against a referencing application.

Why the reference does not travel to a research-use listing

Assemble the pieces and the relevance question answers itself. A Drug Master File is a supporting document within the drug-application pathway. Its contents are examined when an NDA, ANDA, IND, or BLA references it through a letter of authorization. Its value is realized inside that review and nowhere else.

Material offered for research use only as a bulk chemical is, by the terms of that offer, not in the application pathway at all. There is no NDA or ANDA to reference the file, no letter of authorization tying it to a specific filing, and therefore no juncture at which the file’s contents have been reviewed on behalf of the purchaser. A DMF number quoted on such a listing is describing infrastructure that exists for a different purpose — and even taken at face value, it certifies existence, not endorsement, because FDA neither approves nor disapproves these files. The invocation is a category error of the same shape as “GMP-grade”: a term from the regulated-manufacturing vocabulary applied where the conditions that give it meaning are absent.

None of this bears on whether a given material is well made. A supplier may hold a genuine, complete, technically sound Type II DMF and also sell bulk material; the two facts can coexist. The point is narrower and it concerns evidence. A DMF reference is not evidence of lot quality, and it is not the kind of thing a certificate of analysis documents. The certificate reports measurements — which method, which parameters, which lot, which numbers — and those remain the evaluable content. Whether analytical methods were validated and reference standards qualified are questions with documentary answers on the certificate itself. The existence of a master file somewhere in FDA’s records is not among them.

Reading the claim for what it is

A Drug Master File is a real and useful instrument in its own domain. It lets a supplier protect proprietary detail while still enabling a customer’s application to be reviewed on complete information, and for Type II API files supporting generic drugs it carries a defined fee-and-completeness regime on top. What it is not is a mark stamped on a molecule. It is not approved, because FDA does not approve DMFs; it is not evaluated except through a referencing application; and it is not disclosed to anyone but the agency except through a letter of authorization tied to a specific filing. Presented on a bulk research-use listing, a DMF number has been lifted out of every one of the conditions that would make it informative. The disciplined reading is the same one that applies to every regulatory-sounding phrase on a product page: identify the process the term belongs to, ask whether that process has actually run, and treat what remains on the certificate — the methods, the parameters, the results — as the part that can be checked.