Peptide COA, HPLC, LC-MS, and SDS: A B2B Documentation Review Guide

Quick Answer

COA, HPLC, LC-MS, SDS, and specification sheets are not interchangeable, and collecting all of them does not automatically mean a supplier has been adequately evaluated. Each document answers a specific question — purity, identity, safety, specification, batch scope — and each has limits that are relevant to how a buyer uses it in a sourcing decision.

A COA confirms batch results against a specification but does not independently verify compound identity. An HPLC report may support purity review but does not confirm molecular weight. An LC-MS report may support identity confirmation but does not replace a purity assessment. An SDS is a handling and safety document, not a quality review.

A useful documentation review is not about collecting every file. It is about matching the right document to the right question, confirming that the document refers to the correct product, batch, and format, and establishing which documents will be available before order confirmation — not after.

Why Documentation Review Matters Before Quotation

In most B2B peptide sourcing conversations, documentation comes up after price. A buyer receives two quotations, selects a supplier on price, and then requests documents before finalising the order. This sequence works — until the document review reveals something the price comparison did not account for.

The most common documentation-related problems at this stage are not about document forgery or poor quality. They are about scope mismatch and timing:

The COA references a different batch or product format than the one being ordered. The HPLC report was generated by an in-house instrument rather than an accredited external laboratory — a difference that matters to the buyer’s downstream documentation process but was never discussed. The SDS is not in the language required for the destination country. The LC-MS confirmation the buyer assumed was standard turns out to be an optional addition that extends lead time by ten days.

None of these problems are inherently serious, but all of them require follow-up. And follow-up after an order is nearly confirmed is more expensive — in time and, sometimes, in cost — than if the document scope had been established as part of the initial RFQ.

For buyers comparing multiple suppliers, the documentation review also affects the validity of the price comparison itself. If one supplier’s quotation includes HPLC, LC-MS, and a destination-formatted SDS as standard, while another quotes COA only, the two unit prices are not on the same basis. Before treating the lower figure as a better offer, it is worth establishing what is and is not included.

Common Peptide Documents and What They Help Verify

The table below provides a reference overview of the documents most commonly encountered in B2B peptide sourcing. Document availability may vary by product, batch, format, and project scope; the notes below apply generally and should be verified against the specific supplier and order.

Document What It May Help Verify Buyer Note
COA (Certificate of Analysis) Identity, HPLC purity result, appearance, and batch results against specification Must reference the correct product name, batch number, and format; confirm by current batch COA — a COA for a different batch is not equivalent
SDS (Safety Data Sheet) Handling requirements, storage conditions, and hazard classification of the material Required for import clearance in most markets; confirm language and format meet destination country requirements before placing the order
HPLC Report / Chromatogram Purity data and peak profile from the actual production batch, where available Provides more detail than a COA purity summary; confirm whether from an in-house instrument or an accredited third-party laboratory
LC-MS Report Molecular weight data; may support verification that the compound matches the expected peptide, where available Standard practice for identity review on first orders from a new supplier; confirm testing source and scope before using as a qualification reference
Specification Sheet Nominal product specification — purity target, appearance, and parameters the material is expected to meet Defines the product as specified, not as produced; does not replace batch documents for order confirmation
Packaging Specification Container size, fill amount, label format, outer box configuration Confirm before production for custom fill, vial, or private label projects; a packaging specification that does not match the order creates problems at the delivery stage
Quotation Sheet Documents the agreed specification, unit price, quantity, incoterms, and delivery scope The reference document for all scope and pricing discussions; gaps in a quotation sheet predict gaps at the delivery or documentation review stage

COA: What Buyers Should Check

The COA is the document buyers encounter most frequently, and it is also the one most often assumed to answer more questions than it actually does. A COA confirms that a specific batch was tested against a stated specification — it does not independently verify compound identity, confirm that the batch was produced under a specific set of conditions, or guarantee the format the buyer ordered.

Product Name and INCI Designation

The first thing to check is whether the product name on the COA matches the INCI name or specification in the buyer’s RFQ. For cosmetic peptide ingredients like Palmitoyl Pentapeptide-4 or Copper Tripeptide-1 GHK-Cu, the INCI name on the COA should match the buyer’s formulation documentation exactly. A COA that references an abbreviated name, a supplier trade designation, or a different INCI format may create discrepancies downstream in regulatory or import documentation.

Batch or Lot Reference

A COA without a batch or lot number is a general product reference, not a batch-specific document. For order confirmation purposes, the COA should reference the specific batch being shipped. A sample COA and a production batch COA are not interchangeable, even for the same product. Before treating a COA as confirmation of the order being placed, confirm that the batch reference corresponds to the actual production run.

Test Items Listed

The COA should list the tests that were performed, the method used, and the results against specification. Buyers should note what is listed — and what is not. A COA that lists appearance, purity by HPLC, and loss on drying is not the same as a COA that includes these items plus residual solvent testing or endotoxin results. If additional test items are relevant to the project, confirm whether they are available — as separate documents or as part of the COA — before the order is placed.

Purity Result and Test Method

The purity result on a COA typically reflects HPLC analysis. It is worth noting the method and the stated specification limit — not just the result. Two COAs that both report purity within specification may be using different specification thresholds if the buyer’s RFQ did not specify the required minimum. A result that passes one supplier’s internal specification may or may not meet the buyer’s own specification requirement.

Document Source and Issuing Authority

A COA issued by an internal quality team and a COA supported by results from an accredited third-party testing laboratory are both COAs — but they represent different levels of independent verification. If the buyer’s procurement process or downstream customer requires third-party documentation, this should be specified in the RFQ rather than assumed from the document title.

HPLC and LC-MS: Why Buyers Should Not Treat Them as the Same

HPLC and LC-MS are often mentioned together in B2B peptide documentation discussions, and buyers sometimes assume they serve the same function or that one can substitute for the other. In a sourcing review context, they address different questions — and understanding the distinction helps buyers specify which document they actually need.

The table below covers the key review differences relevant to a B2B sourcing evaluation. It is not intended as a technical laboratory comparison, but as a practical reference for what each document may support and when each might be requested.

Review Point HPLC Report LC-MS Report Buyer Note
Primary purpose in sourcing review May support purity assessment by measuring the relative amounts of components in the sample, where available May support molecular weight confirmation, which helps verify that the compound matches the expected peptide, where available The two documents address different questions; confirm which question is relevant before requesting documents
Typical output Chromatogram and percentage purity summary from peak area calculation Mass spectrum and measured molecular weight result Both outputs should reference the correct product name and batch number to be useful
What it may help answer How pure is this material, and are there detectable impurities or related substances? Does the molecular weight of this material match the expected peptide compound? Neither question fully substitutes for the other in a complete sourcing review
What it does not address Does not confirm compound identity or molecular weight independently Does not provide a purity percentage in the same manner as HPLC Buyers who need both purity and identity review may need to request both documents
Testing source Can be performed in-house or by an accredited third-party laboratory Specialized equipment; may be available from an external testing provider depending on supplier capability Confirm the testing source — in-house vs. third-party — before treating either document as independent verification
When buyers may request it Useful for most B2B orders where purity specification is part of the evaluation criteria More commonly requested for first orders from a new supplier, or where compound identity is a formal qualification criterion Document availability should be confirmed before quotation, not requested as an afterthought after price is agreed
Availability Where available; confirm per supplier and batch Where available; confirm per supplier capability and project scope Do not assume availability based on document title; verify before order placement

A low unit price is not a meaningful comparison point if one supplier’s quotation includes both HPLC and LC-MS documentation and another’s includes neither. The documentation scope is part of the effective cost of the order, even when it does not appear as a separate line item on the quotation.

SDS and Handling Documents

The SDS is sometimes treated as a low-priority administrative document in B2B peptide sourcing — something to request at the end of the process rather than at the beginning. In practice, SDS availability and format have direct implications for both logistics and regulatory compliance, particularly for international shipments.

An SDS is a handling and hazard document. It confirms how the material should be stored, transported, and handled — and what to do in the event of exposure or spillage. It does not provide quality or purity information, and it should not be used as a substitute for COA or HPLC review.

For B2B buyers, the relevant questions about SDS are:

Language and format. Import clearance in many markets requires an SDS in the local language or in a specific regulatory format. Buyers who discover this requirement after confirming an order may face delays. For Aminexil (Diaminopyrimidine Oxide) or Copper Tripeptide-1 GHK-Cu sourced for markets with specific SDS requirements, confirming the format early is worth the time.

Product match. An SDS should reference the actual product being ordered — the correct INCI name, CAS number, and physical form. An SDS for a different product designation, concentration, or physical form may not satisfy import documentation requirements.

Version and date. SDS documents are updated periodically. An older SDS may not reflect the current formulation, hazard classification, or regulatory requirements. Requesting a current version, dated within a reasonable timeframe, is standard practice.

Downstream use. If the buyer is supplying the ingredient to a downstream customer who has their own documentation requirements, the SDS format may need to match those requirements — not just the buyer’s own internal standards.

Batch-Level Documents vs General Reference Documents

One of the most useful distinctions in B2B peptide documentation review is between general reference documents and batch-level documents. Buyers who conflate these two categories often proceed further into a sourcing decision than their actual documentation position warrants.

General reference documents describe the product as defined — what it is supposed to be, what properties it should have, and how it should be handled. The specification sheet is the clearest example. A specification sheet tells the buyer what the purity target is, what the expected appearance is, and what the test limits are. It does not tell the buyer what a specific production run actually produced.

An SDS is also a general reference document in this sense — it describes the handling requirements for the material as a category, not for a specific batch.

Batch-level documents are generated from actual production runs and tied to a specific lot or batch number. A COA with a batch reference, an HPLC chromatogram from a specific production batch, and an LC-MS report corresponding to that batch are all batch-level documents. They answer the question: what was this specific batch, and how did it perform against specification?

The gap between these two document types is where sourcing decisions become uncertain. A buyer who has reviewed a specification sheet and a product-level SDS knows what the ingredient is supposed to be. A buyer who also has a current batch COA and HPLC chromatogram knows what a specific production run actually produced. For order confirmation, the second level of documentation is more relevant.

For early supplier screening, buyers may not need batch-level documents immediately. But it is useful to confirm which batch-level documents will be available — and in what format — before placing an order, rather than discovering limitations at the confirmation stage.

Documentation Review Checklist for B2B Buyers

The following checklist covers the documentation-related details worth confirming before quotation or order confirmation. A well-specified documentation request reduces follow-up rounds and increases the likelihood that the documents received are useful for the actual sourcing decision.

Product and batch identification

  • Correct product name and INCI designation on all documents
  • CAS number or sequence reference, if applicable to the project
  • Batch or lot number stated (for batch-level documents)
  • Document date and version (particularly for SDS and specification sheets)

Document types required

  • COA (confirm required fields, batch reference, and purity test method)
  • SDS (confirm language and format for destination country)
  • HPLC chromatogram (confirm whether the batch-level report is required; confirm testing source)
  • LC-MS report (confirm scope and testing source; confirm availability before requesting)
  • Specification sheet (confirm whether issued per batch or per product)
  • Packaging specification (for vial, kit, or private label projects)

Testing source and independence

  • Confirm whether HPLC and LC-MS results are from an in-house instrument or an accredited third-party laboratory
  • If third-party testing is required, confirm availability and lead time impact before quotation

Format and packaging context

  • Confirm the document refers to the correct product format (bulk powder, lyophilized vial, etc.)
  • Confirm packaging specification is documented if ordering in a non-bulk format

Sourcing stage and timing

  • Confirm whether early-screening documents or batch-level order confirmation documents are needed at this stage
  • Confirm whether document availability affects the order decision or lead time expectation

How Documentation Affects Supplier Comparison

When two or more supplier quotations are being compared, documentation scope is one of the variables that affects whether the comparison is valid. The table below identifies common documentation-related issues in supplier comparison, what can go wrong when they are not addressed, and what buyers should clarify.

For a broader supplier comparison framework, see the Cosmetic Peptide Supplier Qualification Checklist.

Comparison Issue What Can Go Wrong What Buyer Should Clarify
Same product name but different product format COA references bulk powder; buyer needed vial-format documentation Confirm every document refers to the product format being ordered, not a different batch or format on file
COA not matched to requested batch stage A sample COA or old batch COA is presented for a new commercial order Request batch-specific documents corresponding to the actual production run being confirmed
HPLC or LC-MS requested after price comparison Adding documents after quotation raises cost or extends lead time — a gap that was not visible in the original price comparison Specify documentation requirements in the RFQ; do not treat documents as add-ons after a price is agreed
Quotation unit unclear A per-gram price is compared against a per-vial price; the comparison is not valid without adjustment Confirm quotation unit in writing before treating any figures as comparable
Packaging format not explicitly stated Different packaging assumptions lead to incomparable MOQ and total cost Confirm packaging format is explicitly stated in every quotation before comparison
Destination documentation needs unknown SDS in the wrong language or format delays import clearance; cost may arise late in the process Confirm destination country requirements at the RFQ stage, not after the order is confirmed

When to Request Documents Before Submitting an RFQ

The timing of document requests is one of the more practical decisions buyers make in the sourcing process. The right approach depends on the stage of the project.

Early supplier screening At this stage, the goal is to confirm that a supplier can provide the material in the required format, and to understand what documentation is generally available. Requesting a specification sheet, a sample COA, and an SDS is a reasonable starting point. These documents help establish whether the supplier is worth pursuing further without committing to a batch-specific evaluation.

Serious quotation stage When the project is far enough along to submit a formal RFQ, documentation requirements should be included in the RFQ itself — not left as a follow-up discussion. Specifying COA format, SDS language requirements, HPLC and LC-MS requirements, and whether third-party testing is needed produces a quotation that includes documentation cost in the price comparison, rather than surfacing it as a separate discussion after a price is agreed.

Order confirmation stage Before confirming a commercial order, batch-specific documents should be available — or their availability should be confirmed with a lead time that fits the project timeline. A COA that references the actual production batch, an HPLC report from that batch, and documentation appropriate for the destination country are the baseline for a well-documented order confirmation.

Private label or packaged format projects For vial, kit, or private label orders, packaging specification documentation should be confirmed before production begins. Packaging changes after production typically add cost and delay. Including packaging specification as a documentation requirement in the RFQ prevents this.

A full documentation request reference is available at the Peptide Documentation Center. For MOQ, lead time, and cost structure considerations related to documentation scope, see the Bulk Peptide Purchasing Guide.

How WUMO Handles Documentation Review

When a buyer requests documentation from WUMO, the first step is usually a clarification: which product, which format, which batch stage, and what documents are needed for this specific sourcing decision?

The reason for this is practical rather than procedural. A COA, SDS, or HPLC report that does not match the product format or batch scope being evaluated does not help the buyer — it just produces another round of follow-up. Sending documentation quickly against an unclear request is not the same as providing useful documentation.

For a buyer at the early screening stage, a specification sheet, sample COA, and standard SDS is often the right package — enough to evaluate the supplier without committing to a batch-level review. For a buyer at the order confirmation stage, the documentation set is different — batch-specific, format-matched, and destination-ready.

WUMO prefers to clarify the product name, format, destination, and sourcing stage before assembling a documentation response, because a well-matched document package takes only slightly more preparation than a generic one — and produces significantly fewer follow-up questions from both sides.

For buyers who are not sure which documents their project requires, or who are reviewing documentation from multiple suppliers and want a second perspective on scope and completeness, a pre-quotation documentation conversation is a reasonable starting point.

Frequently Asked Questions

What documents should peptide buyers review before quotation?

For early supplier screening, a specification sheet, sample COA, and SDS are a reasonable starting point. For formal quotation comparison, documentation requirements should be specified in the RFQ so that all suppliers are responding with the same document scope. At a minimum, a COA with batch reference, SDS in the correct destination language, and confirmation of HPLC and LC-MS availability are worth establishing before quotation is used as the basis for a sourcing decision.

Is a COA enough to compare peptide suppliers?

A COA is a starting point, not a complete comparison tool. Two COAs may report similar purity values but differ in the batch scope, the specification threshold, the test method, or the testing source. A COA issued for a different batch or format is not verification for the order being evaluated. For a more complete supplier comparison, an HPLC chromatogram and LC-MS confirmation alongside the COA provide substantially more review coverage.

What is the difference between HPLC and LC-MS in peptide sourcing review?

In a B2B sourcing context, HPLC may support purity review — confirming the relative proportion of the target compound and detecting impurities or related substances, where available. LC-MS may support identity review — confirming that the molecular weight of the material matches the expected peptide compound, where available. They address different questions and are not interchangeable. Buyers who need both purity and identity review will typically request both documents, and should confirm availability and testing source for each separately.

When should buyers request batch-level documents?

Batch-level documents — COA with batch reference, HPLC from the specific production run, LC-MS tied to that batch — become most important at the order confirmation stage, when it matters that the specific material being shipped has been tested and the results are documented. For early screening, general reference documents may be sufficient. For buyers placing a first commercial order from a new supplier, batch-level documentation is a reasonable requirement to specify in the RFQ rather than leave for post-confirmation follow-up.

Are all documents available for every peptide project?

No. Document availability varies by product, batch, supplier capability, and project scope. HPLC and LC-MS reports from accredited third-party laboratories are not universally available for all products or batch sizes. Endotoxin testing and residual solvent documentation are more commonly available for specific project types. Buyers should confirm document availability with the supplier before placing an order — specifying requirements in the RFQ is the most reliable way to ensure the documentation received matches what was expected.

How does documentation affect MOQ or lead time?

Documentation scope can affect both. An order that includes third-party HPLC, LC-MS, and destination-specific SDS preparation requires more coordination time than a standard COA and SDS package. If these requirements are not established at the RFQ stage, adding them after quotation may extend the stated lead time — which was not priced or scheduled on that basis. MOQ can also shift if the documentation requirement changes the minimum viable batch scope. Establishing documentation requirements early prevents these adjustments from arising mid-project.

Can WUMO help clarify documentation scope before RFQ?

Yes. For buyers who are uncertain which documents are relevant to their project stage, or who are reviewing documentation from multiple suppliers and want guidance on whether the scope is adequate, WUMO can help clarify which documents to request, what each should contain, and how to specify documentation requirements in an RFQ to produce comparable responses. Contact details are at contact.

Request Documentation or Prepare Your RFQ

For documentation review support, availability checks, or RFQ preparation, WUMO is available for qualified B2B project inquiries.

If you are still working through which documents your project requires, or evaluating documentation from multiple suppliers before confirming a sourcing decision, a pre-quotation conversation is a practical starting point.

Related reading: Peptide Documentation Center · Cosmetic Peptide Supplier Qualification Checklist · Custom Peptide Sourcing and CMO Project Support · Bulk Peptide Purchasing Guide: MOQ, Lead Time, and Cost Considerations · Palmitoyl Pentapeptide-4: B2B Sourcing Reference · Copper Tripeptide-1 GHK-Cu · Aminexil (Diaminopyrimidine Oxide)