What a Certificate of Analysis is

A Certificate of Analysis (COA) is a laboratory report for a specific sample from a specific batch or lot. It documents what was measured—typically identity and purity—using analytical methods chosen by the laboratory. Results apply only to the tested sample identified in that report, not to every vial that might share a similar label elsewhere.

What a legitimate COA should include

Not every PDF labeled “COA” is equally useful. A report that supports careful research documentation usually includes the following elements. If several of them are missing, treat the document as incomplete until you can confirm the details another way.

1. The testing laboratory’s full name and contact information. You should be able to identify who performed the analysis and how to reach that organization. A logo alone is not enough; look for a clear legal or trade name and contact details.
2. A batch or lot number that matches the vial. The identifier on the report should correspond to the lot marked on your container. If the numbers do not match—or if the report has no lot identifier—you cannot connect the data to the material in hand.
3. The analytical method used. For peptide purity work, that is often HPLC (high-performance liquid chromatography), which separates compounds in a sample so each can be detected and measured. Useful reports note the method and, when available, column specifications so another chemist can understand how the measurement was made.
4. A full chromatogram graph, not only a summary number. A chromatogram is the plot produced by the instrument over time. It shows peaks that correspond to detected components. A purity percentage without the underlying graph leaves out context that trained readers use to judge whether the run looks clean and complete.
5. A specific quantitative purity result. Prefer a precise figure such as 99.8% over rounded ranges like “greater than 98%” or vague claims of “high purity.” Exact values are easier to compare across reports and to archive in laboratory records.
6. A report date and an analyst identifier. Dates establish when the work was performed. An analyst name, initials, or other identifier shows that a person was associated with the release of the result. Together they make the document easier to audit later.

Common red flags in fake or unreliable COAs

Unreliable documents often fail in predictable ways. Watch for these warning signs when you review a report:

• No lab name — or only a generic phrase such as “independent laboratory” with no organization you can look up.
• Summary-only pages with no graph — a purity figure without a chromatogram or other primary data is easy to fabricate and hard to evaluate.
• Batch number mismatch or a missing batch number — if you cannot match the report to your vial, the numbers do not support that specific material.
• Old or missing dates — undated reports, or dates that look unrelated to the lot you received, weaken the trail from sample to result.
• Cropped or blurry images — heavy cropping, low resolution, or obvious editing can hide headers, footers, task numbers, or other fields needed for verification.
• No way to verify with the lab — if there is no task number, report ID, or public verification path, you are left trusting a file that cannot be checked at the source.

How to independently verify a COA

Reading a PDF on a supplier’s website is not the same as confirming that the laboratory still hosts the original record. Independent verification means checking the report against the lab’s own system whenever that option exists.

One example is Janoshik’s verification tool at janoshik.com/verify. When a Janoshik report lists a task number, you can enter that number on the verification page. The tool retrieves the original report from the laboratory’s server rather than from a copy stored only by a reseller. If the task number is valid, you see the same underlying record the lab issued—not a retyped summary.

This step matters because screenshots and downloaded files can be altered, renamed, or attached to the wrong lot. Pulling the report directly from the lab reduces that risk. If verification fails, or if the online report does not match the file you were given, pause and resolve the discrepancy before you treat the batch as documented.

Other laboratories may use different portals or require email confirmation. The principle is the same: prefer a path that returns the original report from the testing organization, and keep a copy of what you verified with your research records.

Why third-party testing matters

Third-party testing means an independent laboratory—not the seller’s own quality desk alone—performed the analysis and issued the report. Independence is the key factor. When the same organization both sells the material and writes the only available test summary, conflicts of interest are harder to rule out, even when the staff are careful and competent.

In-house vendor testing can still be useful for internal process control. It is a weaker substitute for an external COA when the goal is documentation that another party can scrutinize. US-based suppliers that publish third-party reports make it easier for research buyers to compare lots against original lab data rather than against marketing copy.

Equally important is the difference between a full original report and a vendor summary. A summary may list purity in a sentence or table without chromatograms, method details, or verification IDs. An original report from the laboratory includes the primary data and identifiers needed for independent checks. When both exist, archive the original; treat the summary as a pointer, not a replacement.

Make batch verification part of procurement

Build a simple habit: match the lot on the vial, open the full laboratory report, confirm the method and purity figures, and verify the record with the lab when a tool such as Janoshik’s portal is available. Doing this for every batch takes little time and keeps research documentation tied to primary data instead of unverified files.