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 reported amount)
- Method details and supporting instrument data, where included or separately available
Those results describe the submitted sample. Lot records must connect that sample to the inventory being supplied; results 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:
A limit such as “Purity: >98.0%” is not a measured percentage. A pass/fail result can be legitimate, but the document should identify the sampled lot, test method, and acceptance limit.
No identifiable sampled lot or record connecting the sample to the supplied stock. A results table can still be batch-specific; missing graphs alone do not make a report generic.
| Feature | Batch-specific report | Generic spec sheet |
|---|---|---|
| Lot / batch number | Identifies the sampled lot and can be matched to inventory records; a SKU alone is not a unique lot number. | Missing, blank, or placeholder (Batch: N/A or Batch: All). |
| Test results | Specific measured numbers (e.g. 99.748% purity, 11.75 mg reported amount). | Broad ranges (e.g. ≥98.0% or Conforms). |
| Analysis date | Date the submitted sample was analyzed, linked to its lot records. | Static or missing date reused across years. |
| Test graphs | May include graphs or a results table. Supporting instrument data can be separate. | Graph presence alone does not distinguish a specification sheet from a lot-specific report. |
| Independent verification | For published Janoshik records, verify the task number and key on verify.janoshik.com. | An issuing laboratory may use another verification method; check the issuer and sampled-lot link. |
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
Match the sampled lot to the vial and inventory records. A shared product SKU does not establish a unique lot match.
Task number vs lab portal
For Janoshik records, use the task number and verification key to compare the original laboratory record.
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. Sterility, endotoxins, and biological activity require their own reported tests; a purity or identity result does not establish them. A laboratory report does not establish regulatory approval or suitability for human or animal use.
How PSL Labs documents lots
We follow a verification-before-release standard:
1. Published docs for active SKUs: Active catalog listings link to the original published Janoshik reports. Read the stated sample identifiers and reported results before relying on a claim.
2. Batch-specific scope: Results apply to the submitted sample. The product code shown in a report is not, by itself, proof of a unique production lot or a match to every vial. Ask us to clarify the link between a vial, its inventory lot, and the laboratory record when needed.
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
Compare the sampled lot on the report with the vial and inventory records. A product SKU alone does not uniquely identify a production lot.
Tip: If identifiers differ or the lot link is unclear, ask for traceability records.
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 the report does not establish
If sterility, endotoxin, or other results are missing, those properties are not established by this report. Look for separate documentation; a missing result does not prove that a test was never performed.
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 published Janoshik report. Peptide reports list tested-sample purity and reported amount; the solution report lists benzyl alcohol concentration. Open the original file and match the batch.
Examples of published reports
Each report covers the sample and lot named on that document. Materials are for laboratory research only.
Related Analytical Guides
How to Verify a Peptide Lab Report: A Practical Batch Checklist
Check a report with the issuing lab, match the batch to your order, and save a useful research record. Includes a published Tesamorelin report example.
Peptide COA Checklist: Fields and Warning Signs
Check the fields on a peptide COA: laboratory, lot number, methods, reported results and verification details. Know which gaps need clarification.
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.