Peptide Sequence Notation Checklist for Canadian RUO Labs

Quick answer: what should a peptide sequence notation checklist confirm?#

A peptide sequence notation checklist confirms that the peptide named on a product page, vial label, invoice, certificate of analysis, and internal research record is the same material. It should not stop at “the page says BPC-157” or “the COA says 99% purity.” The useful question is narrower: can the buyer trace the exact sequence, terminal chemistry, salt form, lot number, analytical method, and storage expectation from supplier claim to batch file without guessing?

For Canadian research-use-only buyers, the checklist should confirm nine things before a lot is accepted:

1. Name and synonym control: product name, common abbreviation, catalogue name, and any synonym are mapped to the same material.
2. Sequence direction: the sequence is read from the N-terminus to the C-terminus unless a document clearly states another convention.
3. Amino-acid code clarity: one-letter codes, three-letter codes, and full residue names are not mixed in a way that creates ambiguity.
4. Terminal chemistry: free amine, free acid, amidation, acetylation, cyclization, lipidation, PEGylation, or other terminal features are stated when relevant.
5. Modification and salt language: acetate, trifluoroacetate, hydrochloride, copper complexing, disulfide bridges, isotopic labels, or other changes are visible in the file.
6. Blend and fragment clarity: each component, ratio, and sequence is documented when the product is a blend, fragment, analogue, or mixture.
7. COA identity evidence: HPLC/UPLC purity, MS/LC-MS/MALDI mass confirmation, method notes, test date, lab attribution, and lot code are attached.
8. Vial-label and order matching: the vial, invoice, packing slip, COA, product page, and internal receiving record all agree.
9. RUO claim boundary: the record does not contain dosing, administration, treatment, cure, bodybuilding-cycle, cosmetic-result, or fake testimonial language.

That checklist is intentionally boring. Boring is the point. Peptide identity errors rarely look dramatic at first. They look like a missing amidation note, a product page that uses a familiar abbreviation without a sequence, a COA that shows purity but not mass, a blend whose ratio changed between page and invoice, or a vial label that cannot be matched to the COA lot number.

Use this article beside the peptide COA verification checklist, the research peptide analytical methods glossary, the research peptide supplier scorecard, the batch documentation template, and the documentation audit trail checklist. Sequence notation is not the whole quality system. It is the identity spine that lets the rest of the file mean something, while the analytical-method glossary explains which evidence row HPLC, UPLC, LC-MS, MALDI-TOF, endotoxin, sterility, residual-solvent, and storage terms can actually support.

This page is editorial research context only. It is not medical advice, legal advice, dosing guidance, injection guidance, treatment guidance, procurement instruction for personal use, or a recommendation to administer any compound to humans or animals.

The sequence notation scorecard#

Use this scorecard as a one-page acceptance screen. A lot does not need perfect supplier prose, but it should not require the buyer to invent missing identity information.

A good score does not prove biological performance, safety, legality, or suitability for human use. It proves that the buyer has a coherent identity record. That is the only claim this checklist should make.

Why sequence notation belongs in the procurement file#

Peptide names are often short because people need shorthand. BPC-157, TB-500, Semaglutide, Tirzepatide, GHK-Cu, Selank, and SS-31 are easier to read than a long chemical or sequence line. Shorthand is fine for navigation. It is weak for acceptance.

A catalogue name can hide several identity questions:

• Is the material a full-length peptide, a fragment, an analogue, a blend, or a complex?
• Is the C-terminus amidated, free acid, esterified, or otherwise modified?
• Is the N-terminus free, acetylated, pyroglutamyl, lipidated, or part of a conjugate?
• Is the supplier describing the base peptide, the salt form, a copper complex, or a formulated mixture?
• Does the observed mass on the COA match the expected form named on the page?
• Does the lot label identify the same material as the invoice and COA?

Those questions are not academic hair-splitting. They determine whether a research file can be audited later. If a freezer inventory lists “Semaglutide” but the COA uses a lot code that cannot be tied to the vial, the sequence line will not save the file. If a page lists a sequence but omits terminal amidation, the same common name may point to a different molecular mass than the COA expects. If a blend page lists two familiar names but not a ratio or component-level COA evidence, the record cannot support a clean comparison.

Sequence notation also protects content quality. Northern Compound articles should not cite a supplier page as if a name alone proves material identity. The better editorial move is to separate compound identity, analytical evidence, storage/handling record, and research endpoint language. A page may discuss a recovery compound, a cognitive peptide, a skin peptide, a GLP-1 research material, or a mitochondrial peptide. The identity file still needs the same spine.

Amino-acid code basics: one-letter, three-letter, and full names#

Most peptide sequences use either one-letter amino-acid symbols or three-letter residue symbols. A one-letter sequence is compact. A three-letter sequence is slower to read but often easier for audit notes because each residue is explicit.

For example, a short sequence can be written as a continuous one-letter string, as hyphenated three-letter residues, or as a full chemical description. The checklist does not require every file to use the same style. It requires the style to be clear enough that a second reviewer can reproduce the intended identity.

Three practical rules help:

1. Read left to right as N to C unless documented otherwise. Peptide sequences are conventionally written from the amino terminus to the carboxyl terminus. If a supplier uses unusual formatting, capture a screenshot or ask support to clarify.
2. Do not mix notation styles casually. A product page that uses one-letter code, a COA that uses three-letter code, and a label that uses only a name can be acceptable if the mapping is clear. It is not acceptable if the mapping depends on memory.
3. Treat non-standard residues and modifications as separate fields. A modified residue, D-amino acid, disulfide bridge, terminal cap, lipid chain, fluorescent label, or metal complex should not be hidden inside a familiar peptide name.

Amino-acid notation also creates two common failure modes. The first is ambiguous residues. Some older or database-style notation may use symbols such as B, Z, X, or J in ways that are not acceptable for a procurement file unless the supplier defines them. The second is copy errors. A one-letter sequence is easy to paste incorrectly because a missing residue or transposed letter can be visually subtle. For high-value or endpoint-sensitive lots, compare the supplier page, COA, and internal record line by line.

A useful internal note looks like this:

Product page sequence captured 2026-05-20. COA sequence uses three-letter notation. Reviewer mapped the sequences and found no residue difference. COA observed mass matches expected mass for the supplier-stated form. Vial label lot NC-2026-0520-A matches COA and invoice. No human-use claims copied into batch record.

That note is not glamorous. It is audit-friendly.

Terminal chemistry: the small field that changes the mass#

The termini of a peptide often matter as much as the residue string. A peptide with a free C-terminal acid is not the same mass as an otherwise identical peptide with C-terminal amidation. N-terminal acetylation changes identity. Cyclization changes how the sequence should be read. Lipidation or conjugation can turn a short amino-acid sequence into a materially different molecule.

The checklist should ask:

• Is the N-terminus free, acetylated, pyroglutamyl, lipidated, or otherwise modified?
• Is the C-terminus free acid, amidated, esterified, or otherwise modified?
• Does the supplier state whether the peptide is linear, cyclic, bridged, or conjugated?
• Does the COA expected mass reflect the same terminal chemistry as the product page?
• Is the terminal chemistry visible on the vial label, COA, product page, or support record?

Do not assume terminal chemistry from a common name unless the supplier’s documentation supports it. Some research materials are sold under familiar abbreviations while the exact form is buried in a PDF, an image, or support response. That is a weak file. If the terminal state affects identity, it belongs in the batch record.

This matters for internal links too. When a Northern Compound page points readers to the batch documentation template, the identity section should not be reduced to a brand-like name. It should preserve whatever sequence and terminal fields the supplier provides. When the aliquot labeling template creates child vials, the label does not need to print a full long sequence if space is limited, but the child-vial map should point back to the parent record that contains it.

Modifications, salts, complexes, and blends#

Sequence notation becomes more fragile when the material is not a simple linear peptide. Canadian RUO files should be explicit about four categories: modifications, salts/counterions, complexes, and blends.

Modifications#

A modification is any feature that changes the peptide from a plain chain of standard L-amino-acid residues. Examples include amidation, acetylation, D-amino acids, disulfide bridges, cyclization, lipidation, PEGylation, phosphorylation, fluorescent labels, biotinylation, isotope labels, and other conjugates. The supplier does not need to teach a chemistry course on the product page, but the batch file should show where the modification appears and how identity was confirmed.

A weak record says: “modified peptide, high purity.” A stronger record says: “sequence plus stated modification; expected mass calculated for that form; observed mass shown by MS; chromatographic purity shown by HPLC; lot code matches vial.”

Salts and counterions#

Peptides may be supplied as acetate, trifluoroacetate, hydrochloride, or another salt/counterion form depending on synthesis and purification. Salt language can affect mass interpretation, handling notes, and comparison between suppliers. It should not be ignored just because most searchers care about the common compound name.

The acceptance question is modest: does the supplier name the form consistently, and does the COA match the product page? If the page says acetate and the COA says TFA, open a supplier question before accepting the file. If the COA does not mention the counterion but the page does, preserve the page capture and ask whether the analytical report confirms the same form.

Complexes#

GHK-Cu is a useful example because the name itself signals a copper complex rather than a plain tripeptide reference. A skin or anti-aging archive page should not collapse GHK, GHK-Cu, and a cosmetic topical product into one identity. If the procurement file concerns an RUO research material, it should state whether the supplier documentation supports the copper complex, what analytical evidence is provided, and how the product page avoids cosmetic-result claims.

Blends#

Blends require component-level clarity. A blend name is not a sequence. A blend file should state each component, ratio or amount basis, lot mapping, COA evidence, and whether each component’s identity was tested. If a blend page gives only a combined purity percentage, treat that as a hold signal until support clarifies the method.

The research peptide supplier scorecard should penalize vague blends heavily. A polished page cannot compensate for missing component identity.

COA identity evidence: purity is not identity#

A certificate of analysis is often the first document buyers open, but many reviews overread it. HPLC purity and mass spectrometry identity are related but different.

HPLC or UPLC purity usually describes how much of the chromatographic signal appears under the main peak under a specific method. It can help screen for impurities, truncation products, synthesis by-products, or degradation-related peaks, depending on the method. It does not, by itself, prove that the main peak is the intended peptide.

Mass spectrometry, LC-MS, MALDI, or a similar mass-confirmation method supports identity by comparing observed mass with expected mass. It does not, by itself, prove storage history, sterility, biological activity, safety, or suitability for human use. It also depends on whether the expected mass was calculated for the correct terminal chemistry, salt/form, modification, or blend component.

A strong COA package usually includes:

• supplier name or testing lab attribution;
• product name and sequence or identity field;
• lot or batch number;
• test date;
• HPLC/UPLC purity result with chromatogram or method reference;
• MS/LC-MS/MALDI identity result with expected and observed mass;
• appearance or physical description when relevant;
• storage recommendation;
• fill amount or net content field;
• signatures, QR code, or document-control identifier when available;
• RUO language that does not drift into therapeutic or human-use claims.

A weak COA package often has one or more of these problems:

• purity percentage with no chromatogram;
• identity claim with no observed mass;
• lot number missing or not matching the vial;
• product name but no sequence, terminal chemistry, or modification detail;
• test date missing or stale without retest context;
• sequence screenshot too low-resolution to audit;
• page claim says one form while COA implies another;
• supplier watermark but no lab or method detail;
• human-use marketing language in the same file.

If the COA is incomplete, do not “fix” it in the internal record by adding assumptions. Use a support question, attach the answer, and document whether the lot was accepted, accepted with limitation, quarantined, or rejected. The research peptide supplier response log template exists for that reason.

Product-specific notation traps#

This checklist is not a product guide, but common product families create repeatable documentation traps.

For example, a recovery article may mention BPC-157 and TB-500 because readers compare supplier pages. That does not permit claims about healing, pain relief, or administration. The sequence checklist asks whether the material identity is documented. Endpoint interpretation belongs in a separate research article and must stay inside RUO language.

A GLP-1 article may mention Semaglutide or Tirzepatide because product pages and COAs contain long modified peptide identities. The checklist should preserve modification/form evidence without turning the page into weight-loss guidance.

A skin article may mention GHK-Cu, KPV, LL-37, or melanocortin-related compounds. The checklist should separate skin biology research vocabulary from cosmetic promises. If the page says “collagen boost,” the product-page claims audit should flag it; the sequence record should stay focused on identity.

A cognitive article may mention Selank or Semax. The checklist should not turn a sequence record into a nootropic claim. It should ask whether the material, lot, sequence, and COA are clear enough to support non-clinical research documentation.

The acceptance workflow: from product page to batch record#

A practical sequence notation workflow has six steps.

1. Capture the product page before ordering or receiving#

Save the product page title, URL, date captured, product name, sequence, form, storage language, COA link, and RUO language. Do not rely on memory. Product pages can change. If a supplier later updates sequence, storage, or claim language, the batch file needs the version that informed the purchase.

If the page lacks sequence or form information, mark it as a supplier question. Do not assume the missing field from another vendor, a forum, or a paper unless the supplier confirms that their lot matches that identity.

2. Compare the invoice and packing slip#

The invoice should not introduce a new name, SKU, amount, or form without explanation. If the invoice says one product name and the product page says another, preserve both documents and ask support to map them. Abbreviations can be harmless, but unexplained identity drift is not.

3. Match the vial label to the COA#

The vial label should connect to the COA through lot number, batch number, QR code, SKU, or supplier mapping. If the vial says lot A and the COA says lot B, the lot is not accepted until the supplier explains the mapping in writing. A close name is not enough.

4. Review sequence, termini, modifications, and salt/form#

Use the sequence notation checklist before reviewing purity. If the expected identity is unclear, a high purity number is not meaningful. Record whether the sequence is present, whether the termini are clear, whether modifications are stated, and whether the salt/form language is consistent.

5. Review analytical evidence#

Check HPLC/UPLC purity and MS/LC-MS/MALDI identity separately. Attach chromatograms, mass reports, and method notes when available. Record observed mass against expected mass if the COA provides it. If only a purity percentage is shown, mark identity evidence as incomplete rather than upgrading the score because the number looks high.

6. Decide accept, accept with limitation, quarantine, or reject#

The disposition should match the evidence. Accepted means the file is coherent enough for the intended non-clinical research context. Accepted with limitation means the lot may be usable for low-risk or non-critical context but has documented uncertainty. Quarantine means the lot is held pending clarification. Reject means the identity or documentation gap is too large.

Tie the final decision into the receiving SOP, batch documentation template, deviation log template, and record retention schedule. Sequence notation should not live as a loose note in someone’s inbox.

Copy/paste checklist for batch files#

Use this block as a starting point. Adjust it for the lab’s own quality system and risk level.

Peptide sequence notation review

Material name:
Supplier:
Catalogue/SKU:
Order number:
Vial label lot/batch:
COA lot/batch:
Product page captured on:
Reviewer:
Review date:

1. Name and synonym check
[ ] Product page, invoice, vial, and COA use consistent identity language.
[ ] Any abbreviation or synonym is mapped in notes.
[ ] No human-use, dosing, treatment, cosmetic-result, or performance claim copied into the batch record.

2. Sequence check
[ ] Sequence is present on product page, COA, or supplier support record.
[ ] Sequence direction is clear, normally N-terminus to C-terminus.
[ ] One-letter and three-letter notation agree if both are present.
[ ] No undefined ambiguous residue symbols appear.
[ ] Any sequence discrepancy is documented as a supplier question.

3. Terminal chemistry and modifications
[ ] N-terminus status recorded.
[ ] C-terminus status recorded.
[ ] Amidation, acetylation, cyclization, disulfides, lipidation, PEGylation, isotope labels, copper complexing, or other modifications recorded if present.
[ ] Salt/counterion or form language recorded if supplied.
[ ] Expected mass reflects the stated form.

4. COA evidence
[ ] COA is lot-specific.
[ ] HPLC/UPLC purity result reviewed.
[ ] Chromatogram or method reference attached if available.
[ ] MS/LC-MS/MALDI identity evidence reviewed.
[ ] Observed mass compared with expected mass if provided.
[ ] Test date, lab attribution, and document-control fields recorded.

5. Traceability and disposition
[ ] Vial, invoice, product page capture, and COA can be matched.
[ ] Storage instruction captured.
[ ] Support questions and answers attached.
[ ] Disposition selected: accept / accept with limitation / quarantine / reject.
[ ] Next record created: receiving record, batch record, aliquot map, deviation log, or supplier response log.

How to use this checklist in content review#

Sequence notation is also useful before publishing articles. If an article compares compounds or links to a product, the editor should ask whether the article uses precise identity language.

For Northern Compound, the content review should flag these issues:

• A product name appears as if it guarantees identity, purity, storage quality, or research outcome.
• A modified peptide is discussed without acknowledging the modification/form layer.
• A blend is described as if it were a single sequence.
• A supplier page is treated as live evidence when the product link may be stale or dead.
• A dead or unavailable slug is used as a direct product route rather than falling back safely.
• A human-use claim appears near a ProductLink.
• A citation supports a mechanism, but the article uses it to imply an outcome the paper did not measure.

Product links on this site should preserve attribution and avoid raw product URLs. If a page needs to route readers toward live research-material documentation, use ProductLink components such as BPC-157, Semaglutide, or GHK-Cu. If a product route is not live or the slug is uncertain, omit the direct slug and use a broader supplier or category path rather than sending readers to a 404.

The editorial rule is simple: a ProductLink is a documentation path, not a claim. It should help readers find product-page identity fields, COAs, storage notes, and RUO language. It should not imply endorsement, therapeutic effect, dosing, safety, approval, or personal suitability.

Supplier questions to send when notation is unclear#

Do not send broad “is this good?” messages. Ask narrow identity questions that can be attached to the file.

Examples:

1. “Can you confirm the full amino-acid sequence and whether it is written N-terminus to C-terminus for lot [lot]?”
2. “Can you confirm whether the C-terminus is amidated or free acid for lot [lot]?”
3. “Can you provide the expected mass and observed mass for the lot-specific MS or LC-MS identity result?”
4. “The product page lists acetate, but the COA does not state the counterion. Which form applies to lot [lot]?”
5. “Can you confirm whether the COA lot number [x] maps to vial label [y]?”
6. “For this blend, can you provide component-level identity evidence and the stated ratio or amount basis?”
7. “Can you provide a current batch-specific COA with HPLC/UPLC and MS/LC-MS evidence?”
8. “Can you confirm whether the sequence or terminal chemistry changed between the archived product page and current page?”

Record the answer in the supplier response log template. If support replies with marketing language rather than identity evidence, that is still useful evidence. It tells the buyer not to upgrade the file.

Red flags that should stop acceptance#

These red flags should trigger quarantine, rejection, or at minimum a documented limitation:

• no lot-specific COA;
• no sequence or identity field for a sequence-dependent material;
• terminal chemistry missing where it affects expected mass;
• product page, vial, and COA use different names without a mapping;
• observed mass absent or inconsistent with the supplier-stated form;
• HPLC purity shown without method, trace, or test date;
• blend listed without component-level identity;
• vial label lot does not match the COA lot;
• storage instructions missing for a temperature-sensitive material;
• supplier page claims human benefits, dosing, treatment, cure, fat loss, bodybuilding cycles, cosmetic results, or “patient” outcomes;
• support refuses narrow identity questions or answers with unverifiable claims;
• product route is dead or unavailable while content still points to it as a live source.

The product page claims audit handles the claim-risk side. This checklist handles the notation and identity side. Use both when a supplier page is commercially polished but analytically thin.

Example review scenarios#

The easiest way to use the checklist is to walk a file from name to disposition. These examples are deliberately generic. They show documentation logic, not product recommendations.

Scenario 1: short-name recovery material with a clear COA#

A buyer reviews a recovery-archive material sold under a short common name. The product page lists the common abbreviation, a sequence, fill amount, storage recommendation, RUO language, and a current COA link. The vial label shows the same product name and lot number as the COA. The COA includes HPLC purity, a chromatogram, expected mass, observed mass, test date, and the same lot code.

The sequence notation review is straightforward: product-page sequence captured with date; sequence direction confirmed as N-to-C by the supplier legend; no terminal modification claimed; expected and observed mass reviewed; vial lot, COA lot, and invoice lot matched; no human-use claim copied into the batch file.

Disposition can be “accept” if the rest of the receiving file also passes. The reviewer should still attach storage, package-condition, and batch-record notes. A good notation file does not replace receiving documentation.

Scenario 2: high purity number but no mass evidence#

A catalogue page shows a familiar peptide abbreviation and “>99% purity.” The COA repeats the purity number and includes a clean-looking HPLC trace, but there is no MS, LC-MS, MALDI, expected mass, observed mass, sequence, or terminal-chemistry field. The vial lot matches the COA, but identity evidence is thin.

This is not an automatic rejection in every setting, but it is not a complete identity record. The correct action is to mark the lot “clarify” or “accept with limitation” depending on the research risk, then send a narrow supplier question: “Can you provide lot-specific mass confirmation and the expected mass basis for this material?” If support supplies the missing identity evidence, attach the response and update the decision. If support replies with only “all products are third-party tested,” the gap remains.

The key point: HPLC can support purity without proving the main peak is the intended peptide. A reviewer who upgrades the file because the percentage looks high is not doing COA verification; they are trusting catalogue confidence.

Scenario 3: modified incretin-pathway material with incomplete form language#

A long incretin-pathway research material is listed with a common commercial-style name, but the page does not state the modification pattern or salt/counterion. The COA shows observed mass but does not state what expected mass was calculated from. The invoice and vial label match the product name, but not enough information exists to know whether the supplier, COA, and page are describing the same form.

The sequence notation checklist should force a pause. The reviewer can ask support to confirm the supplier-stated form, terminal chemistry, modification basis, counterion language, expected mass, and whether the observed mass table corresponds to the current lot. Until that answer arrives, the lot should not be treated as a clean reference material in an article or batch record.

This kind of file is where internal discipline matters. The page may be commercially useful and the product name may be widely searched, but the batch record still needs exact identity language. A Northern Compound article can acknowledge reader search behaviour while refusing to turn an incomplete product page into a verified source.

Scenario 4: blend with component-level ambiguity#

A supplier sells a two-component blend. The product name lists both components, but the sequence section is blank, the ratio is stated only in marketing copy, and the COA provides one combined purity figure with no component-level identity table. The vial label and COA lot match, but the analytical package does not explain whether both components were confirmed.

That file should be scored cautiously. A blend is not a single sequence. The buyer needs each component, amount basis or ratio, lot mapping, component-level identity evidence where available, and a method description that explains what the purity result means. If a blend page cannot provide that information, a supplier scorecard should penalize it even if the page is easy to order from.

Scenario 5: copper-complex or skin peptide identity drift#

A skin-archive page uses a familiar name that could refer to a plain tripeptide in one place, a copper complex in another, and a cosmetic ingredient claim in the FAQ. The COA title uses one name, the product page headline uses another, and the support answer says “same thing” without attaching analytical evidence.

This is a product-page claims issue and an identity issue. The claims audit should flag cosmetic-result language. The sequence notation checklist should flag unclear complex identity. The audit-trail checklist should preserve the page capture, COA, and support response so future reviewers can see why the file was limited or rejected.

How this asset should be linked from older Northern Compound pages#

This checklist is a hub for pages where identity notation is easy to skip. It should be linked when the article asks readers to review a COA, capture a product page, compare supplier documentation, score a vendor, create a batch record, label aliquots, or preserve a documentation audit trail.

Good internal-link placements include COA review sections that mention sequence, molecular weight, expected mass, or observed mass; batch documentation templates where “material name” might otherwise be too vague; product-page claims audits where the page uses abbreviations, blends, salts, complexes, or modified peptides; supplier scorecards where identity evidence is one score category among many; receiving SOPs where the vial label, COA, invoice, and product page must match; and aliquot labels where a short child-vial label needs a parent record with the full identity file.

Bad placements are promotional. Do not link this checklist from a sentence that says a peptide “works,” “helps,” “supports recovery,” “improves focus,” “burns fat,” “improves skin,” or “is best.” The asset is about documentation quality. It should pull content back toward evidence, not decorate claims.

Glossary of notation fields#

Amino-acid sequence: the ordered residue string for a peptide, usually written from N-terminus to C-terminus. It may use one-letter or three-letter symbols.

N-terminus: the amino-terminal end of the peptide. It may be free or modified.

C-terminus: the carboxyl-terminal end of the peptide. It may be free acid, amidated, esterified, or otherwise modified.

Terminal modification: a change at either end of the peptide, such as acetylation or amidation.

Internal modification: a change within the sequence, such as a D-amino acid, phosphorylated residue, disulfide bridge, lipidated residue, isotope label, or conjugated tag.

Salt or counterion: acetate, TFA, HCl, or another form associated with the supplied material. It should be documented when the supplier uses the term.

Expected mass: the theoretical mass for the stated peptide form. It should match the sequence, termini, modifications, and form being claimed.

Observed mass: the measured mass reported by MS, LC-MS, MALDI, or a similar method. It supports identity when compared with the expected mass.

HPLC purity: a chromatographic purity estimate under the method used. It does not replace identity confirmation.

Lot mapping: the documented connection between vial label, COA, invoice, product page capture, and internal batch record.

Disposition: the final documented status: accept, accept with limitation, clarify, quarantine, reject, retire, or exclude from a specific endpoint.

Reviewer roles and handoffs#

Small teams often have one person do everything. Larger teams may split the review. Either model can work if the handoff is explicit.

The procurement reviewer confirms product-page capture, supplier name, order record, lot mapping, invoice, vial label, and support questions. The technical reviewer checks sequence notation, terminal chemistry, expected mass, observed mass, chromatogram context, and whether the COA method is adequate for the intended non-clinical use. The compliance reviewer checks whether the page and batch notes stay inside RUO boundaries. The archive owner confirms file names, storage location, versioning, and retention status.

The important handoff is not a meeting. It is a record. Each reviewer should leave a dated note that says what they checked, what evidence they relied on, what remains unresolved, and which decision they recommend. If a later reviewer cannot reconstruct that chain, the checklist failed even if every box was ticked.

Common mistakes to avoid#

1. Treating a product abbreviation as identity. Abbreviations are navigation aids. They do not replace sequence, form, and lot evidence.
2. Treating purity as identity. HPLC purity and mass confirmation answer different questions.
3. Ignoring termini. A missing amidation or acetylation field can change the expected mass and the identity record.
4. Copying supplier marketing into the batch file. Batch files should preserve documentation fields, not outcome claims.
5. Assuming another supplier’s sequence applies. The record must describe the supplied lot, not a generic internet definition.
6. Accepting blend shorthand. A blend requires component-level clarity.
7. Letting support answers vanish. If support clarifies identity, attach the answer to the batch file.
8. Linking dead product routes. Editorial links should route to live documentation paths and preserve attribution.
9. Skipping page captures. A live page can change after ordering. Save the reviewed version.
10. Using the checklist as a safety claim. It is a documentation tool, not proof of human-use suitability.

FAQ#

References#

• IUPAC-IUBMB Joint Commission on Biochemical Nomenclature. Nomenclature and symbolism for amino acids and peptides.
• IUPAC. Compendium of Chemical Terminology: peptide.
• U.S. Food and Drug Administration. Analytical Procedures and Methods Validation for Drugs and Biologics.
• Health Canada. Think twice before injecting peptides bought online: unauthorized products can seriously harm your health.
• International Council for Harmonisation. ICH Q2(R2): Validation of Analytical Procedures.
• World Health Organization. Good storage and distribution practices for medical products.