Key takeaways
- Use one controlled product name and retain synonyms with their sources.
- Preserve sequence order, terminal groups, residue modifications and conjugates when they distinguish the material.
- Record salt, counterion and physical-form information separately from the base peptide name.
- A blend name does not replace the identity and amount of every component.
- Database identifiers are useful cross-references only when the database, record type and retrieval date are recorded.
A catalog name is a starting point
Research peptide listings often use a short common name, development code or acronym. That label can be convenient and still be insufficient for procurement. The same shorthand may appear with different punctuation, capitalization or modifiers, while a base name can be shared by chemically distinct forms. Record the supplier’s displayed name exactly, then map it to a controlled internal name supported by the specification.
Keep aliases in a separate field rather than deleting them. They help with search and document matching, but they should point back to the controlled identity. Add the source for each alias so later reviewers can tell whether it came from the supplier, a primary publication or a curated database.
Sequence notation carries structural information
A peptide sequence is more than a string of letters. IUPAC-IUB recommendations establish symbols for amino-acid residues and conventions for representing peptide structures and derivatives. Preserve the sequence exactly as supplied, including whether one-letter or three-letter residue symbols are used, and state the writing direction when it is not explicit.
Do not normalize case, spacing or punctuation in a way that can erase meaning. Nonstandard residues, D-residues, isotopic labels and other qualifiers need an accompanying definition. If two sources show different sequences, keep both citations visible until the discrepancy is resolved rather than selecting the more familiar version.
Modifications belong to the identity
Terminal groups, side-chain modifications, cyclization, lipidation, conjugation and other structural changes can distinguish one material from another. Include them in the controlled name or in linked identity fields. A report for an unmodified sequence should not be matched to a modified listing solely because the base peptide name is the same.
Positions matter. When a modification is residue-specific, record the residue and position using the convention stated by the source. If the supplier provides only a marketing suffix without defining the underlying modification, request the structural description and keep the suffix as an alias rather than treating it as a complete chemical identity.
Separate the peptide from its salt, counterion and presentation
A peptide’s base sequence, its salt or counterion and its physical presentation are related but separate fields. A salt descriptor can affect the formula and mass basis, while “lyophilized powder” describes the presentation. Neither should be dropped when it is part of the supplied specification, and neither should be invented when the listing is silent.
This separation helps resolve quantity statements. A labeled mass may be expressed on a peptide basis, a salt basis or a formulated-material basis. The nomenclature record should point to the supplier’s definition rather than assuming that every product with the same common name uses the same convention.
Name every component in a blend
A blend name identifies a commercial or project-level combination; it does not fully specify its components. Record the controlled identity, form and amount or ratio of each component, followed by the total amount and vial count. If the composition is not published, the blend remains incompletely specified even when its shorthand is widely used.
Combination punctuation is not a composition statement. A plus sign, slash or hyphen can show that names are grouped, but it does not establish equal proportions, chemical linkage or co-formulation details. Preserve the supplier’s display name for traceability and maintain the component table as the authoritative purchasing description.
Use database identifiers with their context
Identifiers can improve cross-checking, but different databases organize records differently. PubChem, for example, distinguishes depositor-provided Substance records from standardized Compound records and assigns SIDs and CIDs respectively. A CID is therefore not interchangeable with every submitted substance description or supplier catalog number.
Record the database name, identifier type, identifier value, source URL and access date. When a registry number appears as a synonym, verify it with the authoritative registry or source identified by the database. PubChem notes that depositor-supplied CAS numbers are not comprehensively covered or independently verified by PubChem, so the presence of a synonym is not by itself an authoritative assignment.
Normalize names without overwriting evidence
A practical nomenclature record can contain: controlled name; supplier display name; aliases; sequence; sequence direction; modifications and their positions; salt or counterion; declared formulation components; blend composition; database cross-references; catalog number; and the source and date for each field. Use explicit “not provided” values where the source is silent.
Version the normalized record when a source changes. Preserve the earlier supplier label, report and mapping so a reviewer can understand why two documents use different terms. Normalization should connect evidence, not make discrepancies disappear. When identity remains ambiguous, resolve it before using price or analytical claims to compare materials.
Apply the same name across the document chain
Check the controlled identity against the product page, order confirmation, container label, lot report and internal batch record. Small formatting differences may be harmless, but a missing modifier, changed sequence or different salt description can signal a substantive mismatch. Record both versions and the basis for any conclusion that they refer to the same material.
Consistent nomenclature improves search, certificate matching and handover between laboratory staff. It also keeps the limits of the record clear: a well-formed name identifies the intended material, but it does not establish that a received lot conforms to that identity. Lot-specific analytical evidence remains a separate requirement.
Sources and further reading
These sources describe the cited methods, reference compounds or published studies. They do not verify the identity, purity or performance of any Peptine Labs lot.