Batch-Specific COAs vs Generic COAs: Why Lot Traceability Matters
How a real batch lab report differs from a generic spec sheet, and why the lot number links your vial to the test data.
A batch-specific COA is a real lab report tied to one production lot. A generic COA is often just a spec sheet with no lot link to your vial.
A generic sheet says what the supplier aims to make. A batch-specific COA says what an independent lab measured on a sample from that run.
This guide covers how the paper trail should work, why batch numbers matter, and how to spot a generic sheet dressed up as a lab report.
What batch-specific really means
A batch-specific COA is an empirical record for one production lot. It typically includes:
- The unique batch code for that production run
- The sample vial sent to the testing lab
- The analysis date
- Measured results (for example, 99.805% purity and 13.03 mg net mass)
- The test graphs that support those numbers
Those results belong to that lot. They do not automatically cover earlier runs, later runs, or material from a different synthesis site.
How to spot a generic “COA”
Some PDFs look polished but are really static specification sheets. Common tells:
Instead of “99.74%,” you see “Purity: >98.0%” or “Conforms” on every row.
Only a typed table. No test graphs, no chromatogram, no identity spectrum.
| Feature | Batch-specific report | Generic spec sheet |
|---|---|---|
| Lot / batch number | Matches vial label and invoice (e.g. PSL-BPC157-10MG). | Missing, blank, or placeholder (Batch: N/A or Batch: All). |
| Test results | Specific measured numbers (e.g. 99.748% purity, 11.75 mg mass). | Broad ranges (e.g. ≥98.0% or Conforms). |
| Analysis date | Exact date of lab testing for that production run. | Static or missing date reused across years. |
| Test graphs | Full chromatogram with peak data and run times. | Summary table only; no instrument graphs or spectra. |
| Independent verification | Task number you can look up on the lab server (verify.janoshik.com). | No task number; cannot verify on the lab site. |
Why lot numbers matter
Peptide production involves many steps. Even under controlled conditions, lots differ:
- Small process shifts change byproduct levels.
- Purification cuts at slightly different points produce different purity profiles.
- Freeze-drying conditions change residual moisture and salt content.
- Fill amounts can drift slightly between runs.
Two runs of the same peptide are not chemically identical. The lot number is what connects the vial on the bench to its analytical record.
From product to published report
In a verifiable setup, the paper trail looks like this:
Product released
Compound is finished and assigned a unique synthesis lot ID.
Lot printed on packaging
Same code appears on vial labels and cartons.
Sample sent to a third-party lab
A representative vial goes to an independent facility (Janoshik).
Lab analyzes and issues a task ID
Purity and identity tests are logged under a unique Task Number.
Signed report published
Original report lives on the lab server and is mirrored in PSL COA Lookup.
Break any link (missing task number, unlabeled vial) and the chain is no longer verifiable.
Identifiers to compare
When an order arrives, line up these four checks across the physical goods and the records:
Vial label vs report batch code
The batch on the vial should match the batch header on the COA.
Task number vs lab portal
Enter the task number at verify.janoshik.com and confirm the original PDF.
Nominal strength vs reported mass
See whether the report gives net active mass (for example 10.34 mg) or only relative purity.
Analysis date vs order timing
The analysis should sit in a reasonable window for the active production you are buying.
Old reports vs current stock
A common shortcut is reusing a strong historical report. A supplier tests a pilot lot, gets 99.8%, then keeps showing that same PDF for later production years later.
That does not hold up scientifically. Reagents, amino acid lots, and equipment cycles change. If the analysis date is years old while the SKU is still being replenished, ask for current lot-specific testing.
Sampling limits
Consistency across vials depends on controlled production and filling. No lab can test every finished unit without destroying the inventory.
What batch reports do not prove
The report only covers the tests shown on the original laboratory file. A batch report does not cover sterility, endotoxins, biological activity, or regulatory approval unless those tests are listed.
How PSL Labs documents lots
We follow a verification-before-release standard:
1. Published docs for active SKUs:We do not sell under vague “testing pending” promises. Active catalog items ship with a published Janoshik COA.
2. Batch-specific scope: We do not stretch historical data across new production runs. When a lot changes, new third-party analysis is completed and published.
3. Pipeline gating: “Coming Soon” items stay non-purchasable until verification is finalized and indexed in View Batch Reports.
Batch traceability checklist
Use this checklist whenever you inspect third-party documentation:
Lab report checklist
Who issued the report?
Look for a real lab name, contact details, and a way to verify the file. A logo alone is not enough.
Tip: Check the header for the laboratory name.
Find the task or report ID
Legitimate reports usually include a unique tracking number (for Janoshik reports, a Task #). Without that ID, independent checks are hard.
Tip: Look for Task # or Report ID near the top.
Verify it on the lab's site
Open the lab's verification page (for Janoshik: verify.janoshik.com) and check the task number and key against the original file.
Tip: Do not rely only on a screenshot or vendor summary.
Match the batch number
The batch or lot on the report should match the code on the vial or package.
Tip: If the numbers do not match, the report is not for that vial.
Check identity testing
Confirm the lab actually tested identity (often with mass spectrometry), not only a purity percentage.
Tip: A purity peak alone does not prove identity.
Check the analysis date
Make sure the test date fits the lot you are evaluating. Older reports may belong to earlier lots.
Tip: Compare the date to the active lot you received.
See which tests were run
Note whether the report lists purity percentage, measured amount, or both. Those are different results.
Tip: Purity % is not the same as total milligrams.
Note what was not tested
If sterility, endotoxin, or other tests are missing, treat them as untested unless another report covers them.
Tip: Write down what is missing for your records.
Continue with What Peptide Analytical Testing Can, and Cannot, Establish or open View Batch Reports.
Research Use Only
This guide is for researchers and lab staff reviewing lab reports. Materials discussed are for laboratory research only. They are not for human or veterinary use.
Check our published batch reports
Every active catalog lot has a third-party Certificate of Analysis from Janoshik Analytical. You can review purity, measured amount, and check the original file yourself.
Examples of published reports
Each report covers the sample and lot named on that document. Materials are for laboratory research only.
How to Verify a Peptide Laboratory Report: Batch, Report ID, Test Method & Traceability
Step-by-step help for checking task IDs, matching batches, confirming test methods, and verifying a report on the lab's own website.
How to Verify a Peptide Certificate of Analysis
A checklist for reading third-party lab reports, spotting unreliable documents, and confirming results directly with the testing lab.
Peptide Identity vs Purity vs Content: What Each Analytical Result Actually Tells You
Identity, purity, and content answer three different questions. Learn what each result means and how to read them together on a lab report.