On this page
How do you assess a biological proper-name suffix proposal?
First establish the product’s licensing and naming context and the current FDA instructions for the application. The 2017 guidance describes a nonproprietary, meaningless four-lowercase-letter suffix with at least three distinct letters, but syntax alone does not establish acceptability. Screen meaning, clinical abbreviations, confusion and legal barriers. Preserve the 2019 update’s draft status and the 2017 PDF’s qualification on applicant-submission information collection.
Before you begin
Biological proper-name suffix preparation where applicable. The January 2017 final guidance and March 2019 draft update have different status; previously licensed, transition, vaccine and interchangeable-product contexts need specific assessment.
What you will prepare: A candidate proposal with product identity, naming-context rationale and documented screening evidence for FDA review.
Resolve naming scope before generating candidates
Identify the biological product, application pathway, core name and licensure history. The 2019 update remains draft and discusses contexts including products already licensed without suffixes and transition products. Do not automatically retrofit the 2017 convention to every existing biological product or present the draft as a final universal rule. If the context is uncertain, obtain regulatory clarification before representing a suffix as required.
Screen candidates against the actual criteria
Section VI of the 2017 final guidance describes a meaningless, nonproprietary suffix of four lowercase letters, with at least three distinct letters, joined to the core name by a hyphen. Evaluate candidates for misleading implications, clinical abbreviations, legal restrictions and confusion with existing products or suffixes. Document the searches and reasoning; a syntactically valid candidate is not necessarily acceptable.
Build a reviewable proposal
If current FDA instructions for the application call for an applicant proposal, provide the exact core-name relationship, requested candidate preferences and supporting analyses, with the product/application and responsible contact. The January 2017 PDF cover still states that the information collection provisions for proposed-suffix submissions are under OMB review and not for current implementation. Do not infer a current filing mandate or process from that dated notice alone; verify the actual application instructions and current status. Keep proposed names clearly labeled proposed in draft labeling and internal records. FDA determines acceptability; a search with no obvious match or an internal naming decision does not assign the official proper name. Reconcile the ultimately designated name across labels, forms and controlled product records.
Fictional example: syntax passes, meaning fails
A four-letter candidate repeats a familiar clinical abbreviation and could be read as an instruction. Record that risk rather than declaring the candidate valid because it has the right length. If the product changes from a new BLA to a previously licensed transition product, revisit applicability before carrying over the suffix-generation task.
Resolve applicability before treating candidate generation as a submission task
A biological proper name identifies the licensed product; it is not a brand slogan. Establish the core name, application pathway, licensure history and actual agency naming interaction before preparing candidate records. The existence of a four-letter naming convention does not prove that every previously licensed product must be renamed or that a sponsor may assign its own official suffix.
The January 2017 PDF, reopened October 6, 2026, still carries a cover notice that the information-collection provisions about submitting proposed suffixes are under OMB review and not for current implementation. That dated notice is a limit on what this PDF alone establishes; it is not proof of the status of every later information-collection decision. This guide does not infer a current applicant filing mandate, candidate-count requirement or submission clock from that file. Confirm the current instructions for the actual application. Independent screening can still make the naming discussion better informed.
| Screening area | Record | What a syntax check misses |
|---|---|---|
| Product context | Core name, pathway, licensure history and actual naming instructions | A proposal may not be the applicable task for this product |
| Character form | Four lowercase letters, at least three distinct, with the specified core-name relationship | Correct form says nothing about acceptability or designation |
| Meaning | Word, abbreviation, drug-substance, safety or efficacy implications | Apparently random letters can convey an unintended message |
| Clinical interpretation | Relevant prescription/order abbreviations and use context | A suffix could be mistaken for another instruction or field |
| Confusion | Similarity to marketed product names and FDA-designated suffixes | An exact-match search misses near matches |
| Nonproprietary status | Legal barriers and possible connection to a license-holder name | A company-coded identifier conflicts with the described naming intent |
| Decision record | Search date, sources, method, reviewer and unresolved questions | A search result cannot assign the official proper name |
Fictional syntax exercise: a candidate repeats only two distinct letters across four positions. It fails the stated distinct-letter criterion even though its length and case are correct. Another candidate has four distinct lowercase letters but resembles a clinical abbreviation or the license holder's name. It needs substantive assessment rather than an automatic pass. These examples do not propose an actual suffix for a product.
The March 2019 update remains labeled draft, not for implementation, on FDA's page. It discusses previously licensed products without suffixes, transition products, vaccines and interchangeable products. Read those distinctions with the actual product record; do not recast the draft as final or apply the 2017 retrospective approach automatically to every older product.
When current FDA instructions call for a proposal, present the requested candidates and supporting record with their status explicitly identified. After designation, reconcile the exact proper name across labeling, forms and controlled product records. Do not decode a suffix as a claim about quality or treat it as evidence of interchangeability. Use the proprietary-name guide for the separate brand-name task.
Your preparation checklist
0/3 checkedUse this to track your review in this visit. Checks are not saved and do not establish regulatory compliance.
Frequently asked questions
Does any four-letter lowercase string qualify as a biological suffix?
No. The 2017 guidance also specifies at least three distinct letters and substantive criteria concerning meaning, misleading implications, clinical abbreviations, confusion and legal barriers. Screening form is only an initial check. FDA designation and the actual product context remain separate from a syntactically valid candidate.
Does the 2017 PDF alone establish a current requirement to submit candidate suffixes?
No. Its downloaded cover still qualifies the applicant-submission information-collection provisions as under OMB review and not for current implementation. Do not infer a current mandate or universal submission procedure from that file alone. Confirm the actual application instructions and relevant current status before treating a candidate list as a required filing.
Should every previously licensed biological product be retrofitted with a suffix?
Do not make that assumption. The March 2019 update remains draft and discusses previously licensed products without suffixes and transition products differently from the original approach. Establish the actual licensure and naming history, current FDA position for the product and designated name rather than applying a blanket renaming rule.
Is the proper-name suffix a brand identifier or proof of interchangeability?
No. The described suffix is nonproprietary and devoid of meaning; it should not be treated as a brand claim or decoded into a clinical conclusion. Use the actual FDA product designation and regulatory record for naming and interchangeability questions, and keep the separate proprietary-name review identifiable.
Sources and revisions
Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.
Guidance
FDA: Nonproprietary Naming of Biological Products ↗January 2017 final; section VI suffix criteria. Read with the separately identified March 2019 draft update and actual product status. Checked September 22, 2026.
Draft guidance
FDA draft: Nonproprietary Naming of Biological Products: Update ↗March 2019, still draft/not for implementation on September 22, 2026. Addresses previously licensed and transition products, vaccines and interchangeable products.
Technical specification · placement only
FDA eCTD v4.0 comprehensive hierarchy ↗Version 2.2, February 2025. Section 1.18.2. A heading identifies placement, not mandatory applicability.