Interpreting Mass Spectrometry on Peptide COAs: A Lab Guide

Recent independent investigations have emphasized the importance of rigorous analytical documentation for peptide materials. In 2026 reporting highlighted a notable rate of mislabeled or poorly characterized peptide products, reinforcing why laboratory researchers and quality personnel must know how to read mass spectrometry outputs on Certificates of Analysis (COAs) and how to pair MS identity data with HPLC purity data and lot-traceability records.

Why mass spectrometry appears on a peptide COA

Mass spectrometry (MS) is commonly used on COAs to demonstrate molecular identity by reporting observed masses or m/z values. Published literature and regulatory guidance note that MS is an identity technique that is most reliable when documented with instrument metadata, calibration records, and orthogonal confirmation methods (e.g., chromatographic fingerprinting or amino‑acid analysis) rather than as a standalone proof of composition [1][2][3].

Key MS outputs and how to read them

Reported mass values: monoisotopic vs. average

COAs may report monoisotopic mass, average mass, or an observed m/z and charge-state assignment. Each convention has a different numerical expectation; the COA should state which is presented. Monoisotopic masses are most common for small to mid-size peptides and are the basis for exact-mass comparisons.

Observed m/z, charge states, and deconvoluted spectra

High-resolution instruments produce multiple charge-state peaks. Deconvolution collapses these into a single neutral mass for comparison with the theoretical peptide mass. A compliant COA will include the raw spectrum or a labeled deconvoluted trace, plus the deconvolution parameters (software, algorithm, smoothing, and charge-state range).

Mass accuracy and precision (ppm)

Mass measurement error is often reported in parts-per-million (ppm). Methodology papers recommend reporting mass accuracy and precision statistics across replicate spectra rather than a single nominal match [2]. Look for stated calibration dates, QC samples run within the sequence, and a numeric ppm error or tolerance window on the COA.

How to cross-check MS with the HPLC chromatogram

HPLC chromatograms on COAs provide purity profiles and retention-time data. Identity and purity are complementary: MS indicates molecular identity while HPLC shows whether a single predominant chromatographic species corresponds to the mass signal in question. Published characterization workflows emphasize a mass-balance approach where HPLC area percent, counter‑ions, residual water, and other contributions feed into final content assignment [1].

Retention time and UV trace alignment

On-lot HPLC traces should include the retention time (RT), detection wavelength, and a labeled peak corresponding to the target compound. Where available, look for an LC–MS extracted ion chromatogram (EIC) or overlay demonstrating that the MS signal co-elutes with the main UV peak—this is direct evidence linking chromatographic purity to mass identity.

Common red flags on COAs and MS reports

• Missing method details: no instrument model, no calibration date, or no description of deconvolution parameters.
• Single-number claims: an MS-only COA that lists only a nominal mass with no spectrum, charge states, or ppm error.
• No HPLC chromatogram or an HPLC trace lacking labeled peaks and analysis parameters.
• Unclear sample traceability: COA lacks a lot number, vial ID, or chain-of-custody references that match the product label.
• Accreditation ambiguity: laboratory claims accreditation but omits scope, certificate number, or which tests are covered by ISO/IEC 17025.
• High-intensity unexplained peaks: MS spectra showing additional high-intensity masses without discussion of adducts, oxidations, or expected by‑products.

Checklist for verifying lot-matched third-party test records

Use this practical checklist when evaluating a COA and its associated MS/HPLC records:

• Lot number traceability: confirm the COA lot number matches the product label and any shipment/sample IDs.
• Method metadata: instrument model, method ID, analyst, run date, calibration record/date, and software/version for deconvolution.
• MS details: raw spectrum or deconvoluted trace, reported m/z values with charge states, monoisotopic/average designation, and ppm error statistics.
• HPLC details: chromatogram image, retention time, detection wavelength, column and mobile-phase conditions, and area-percent reporting.
• QC evidence: system suitability results, control-sample traces, and replicate runs or statistical sampling information.
• Accreditation and scope: ISO/IEC 17025 certificate number, accreditation body, and whether MS and HPLC methods are covered within the scope.
• Reference materials: indication of reference standard used, lot of the standard, and traceability to a characterized material.
• Raw data access: availability of raw LC–MS files or chromatograms on request for independent review.

Standards, accreditation, and documentation to expect

Regulatory and methodological guidance recommends method validation and orthogonal confirmation. The FDA’s analytical procedure guidance and ISO/IEC 17025 detail expectations for method validation, calibration, and traceability; method summaries and validation attributes (specificity, accuracy, precision, LOD/LOQ) strengthen confidence in reported COA values [3][4]. Accreditation does not guarantee error-free data but is an important indicator that the laboratory follows documented quality practices [5].

Practical next steps for laboratory researchers

When reviewing a COA for research materials, consider requesting additional metadata or raw files if any of the checklist items are absent. Asking for run sequences that include system suitability and control samples, or for an LC–MS EIC overlay linking UV and mass signals, is a reasonable step for laboratory verification. Keep all communications documented and maintain lot-level records in your own laboratory information management system (LIMS) for traceability.

Staying conversant with MS terminology, deconvolution conventions, and HPLC reporting expectations helps researchers and quality staff interpret COAs critically and consistently—especially in an environment where independent investigations have highlighted the value of robust, lot-matched analytical documentation.

References

Related Peptide Titans Resources

• Peptide Titans research library
• Research-use peptide catalog
• Third-party lab results and COAs

Research Sources

Primary references and source materials used for this research-focused overview:

• pmc.ncbi.nlm.nih.gov/articles/PMC10338602
• pmc.ncbi.nlm.nih.gov/articles/PMC10093877
• fda.gov/regulatory-information/search-fda-guidance-documents/analytical-procedures-and-methods-validation-drugs-and-biologics
• pmc.ncbi.nlm.nih.gov/articles/PMC7838891

Frequently Asked Questions

What does a ppm error on a COA mean?

ppm (parts-per-million) expresses the mass-measurement error relative to the theoretical mass. A COA should state the measured mass, the theoretical mass, and the calculated ppm error or tolerance window, along with instrument calibration information.

Should a COA include raw spectra and chromatograms?

Best practice is that COAs include labeled chromatogram and MS traces. Many labs will provide raw LC–MS files on request; availability of raw data allows independent review of peak assignments and deconvolution parameters.

How important is lot number traceability on third-party reports?

Lot number traceability links analytical results to a specific manufactured batch. For meaningful verification, COAs and third-party reports should carry matching lot identifiers, sample IDs, and dates to prevent misattribution of results between lots.

Does ISO/IEC 17025 accreditation guarantee accuracy?

Accreditation documents that a lab follows competency and quality-management practices; it does not guarantee error-free results. It does increase the likelihood that methods are controlled, documented, and that COAs include relevant metadata such as calibration records and method IDs.