A certificate of analysis, or COA, is the document that summarizes what a laboratory tested, how it tested it, and what result it found. A good one answers your questions in under two minutes. A weak one raises more questions than it settles. Knowing the difference is one of the most useful skills in research sourcing.
What a COA is actually for
At its core, a COA connects a specific batch to a specific compound and a specific result. It is a batch document, not a brochure. If you cannot trace the report back to the lot number printed on the vial in front of you, the document is decorative rather than useful.
The fields that matter
The compound name on the report should match the material being supplied — exactly.
The report should map to the label on the vial or the shipment it arrived in.
HPLC is the common method for estimating peptide purity. Some reports add heavy-metal or endotoxin screening.
The purity figure or pass/fail outcome should be easy to find and clearly tied to the tested batch.
Prefer lab-hosted verification over a loose file
A PDF emailed as an attachment can be edited by anyone with the right software. A stronger signal is a live verification page hosted by the testing laboratory itself, where you can confirm the result on the lab's own domain. That makes the document far harder to alter and lets a researcher validate it independently rather than taking a screenshot on faith.
Red flags worth slowing down for
- No batch or lot number anywhere on the document.
- No named test method — purity figures with no methodology behind them.
- No identifiable independent laboratory.
- A generic purity claim with no underlying report attached.
- A COA whose compound or vial size does not match what is being supplied.
A two-minute walk-through
Here is the order most experienced researchers read a certificate in. First, the compound name — does it match what was ordered? Second, the lot or batch number — does it match the vial? Third, the method — is HPLC, or another named technique, actually stated? Fourth, the result — is the purity figure clearly tied to that batch rather than floated as a general claim? Finally, the source — is there an independent lab, and ideally a way to confirm the result on that lab's own system?
Run that sequence and a weak document falls apart quickly. If you reach step two and there is no lot number to match against your vial, the remaining fields barely matter, because nothing connects the paper to the powder.
Why the format of the document matters
Two certificates can contain the same numbers and still differ in how much confidence they earn. A flat image with no source is easy to produce and hard to check. A record hosted on the testing laboratory's own system, tied to a lot number you can match against your vial, is a different class of evidence. The information may look similar at a glance, but only one of them lets a researcher confirm the result independently — and that independent check is the entire reason to ask for documentation in the first place.
How we think about COAs
Our own approach is built around batch documentation and third-party verification. The goal is unglamorous but important: a researcher should be able to connect a labeled lot number to a real analytical report before that material is ever used in an in vitro workflow. If a document cannot survive that simple test, it is not doing its job.
Read enough certificates and a pattern emerges — the trustworthy ones are boring in the best way. Clear identity, clear method, clear result, clear lot. When a COA tries to dazzle instead of inform, that is usually the tell.