What a COA is (and is not)
A Certificate of Analysis is a lot-level laboratory report. It describes one manufactured or tested batch — not every future vial sold under the same catalog name, and not a clinical or regulatory dossier. For research peptides, the COA is the primary document that lets receiving staff and principal investigators confirm that the material in hand matches what the supplier claimed for that specific lot.
On Nextday Peptides, COAs in the COA Library are provided by our manufacturing vendors and/or their contracted testing laboratories. Nextday Peptides does not independently test each lot in-house and is not the analytical laboratory named on those reports. We share vendor documentation so buyers can file lot paperwork; methods and results remain those of the issuing lab or vendor.
Think of it as chain-of-custody for analytical claims. The file usually lists identity of the compound as tested, measured purity under a stated method, physical appearance, and administrative metadata such as batch number and test date. Those data points support procurement records, audit trails, and method development notes. They do not authorize a use outside the laboratory.
A COA is not medical advice, not a full safety data sheet by itself, and not permission to apply the compound outside Research Use Only boundaries. Nextday Peptides supplies RUO materials; COAs exist to support analytical and experimental documentation. For the use restriction that sits around every SKU, see Research Use Only peptides explained and the articles disclaimer.
Formats differ by testing partner and by compound class. A lyophilized peptide lot may emphasize HPLC assay and mass spectrometry. A small-molecule research reagent may emphasize different residual-solvent panels. Learn the structure of the documents you receive most often, then treat outliers as a reason to ask questions rather than as noise to skip.
Buyers sometimes conflate a COA with a full product monograph or with a supplier brochure. Those documents answer different questions. Marketing pages describe what a catalog aims to sell; a COA reports what a defined sample measured under a defined method. Keeping that distinction sharp protects both purchasing decisions and experimental records when colleagues ask “is this the same as last time?”
Start with the vial, then open the PDF
Before you dig into chromatograms, confirm the paperwork belongs to the bottle you are holding. Match product name or catalog identifier, stated fill amount when printed (for example 5 mg or 10 mg), and — most important — the batch or lot number on the label. A COA for a neighboring lot of the “same” SKU is the wrong file for your notebook.
Label typography varies. Some vials print a short lot code; others print a longer alphanumeric string. Transcribe what you see, then search the PDF for that exact string. If the lot on the vial does not appear on the COA, stop. Do not assume a close match is close enough. Request the correct file before the vial enters active use in an experiment.
Our COA Library is searchable by compound and batch. If a lot is missing after you check spelling and hyphenation, email orders@nextdaypeptides.com with the order number and the batch printed on the label. Attach a clear photo of the label when that helps resolve ambiguous characters.
Receiving SOPs at many institutions also call for a visual check of seal integrity and powder appearance before filing. Note those observations next to the lot ID. The COA describes the tested sample; your receiving notes describe the package that arrived. Together they form a stronger record than either alone.
Handwritten receiving logs still work, but shared drives and LIMS fields reduce transcription drift when staff rotate. Whatever system you use, make the lot string the primary key that joins the physical vial, the PDF filename, and the notebook entry. Synonym-heavy catalog titles are secondary metadata — useful for humans, unreliable as unique keys.
Fields most labs check first
Layouts vary by testing lab, but research-peptide COAs commonly include a predictable core set of fields. Treat missing critical items as a prompt to follow up, not as optional decoration. Your institutional SOP may require additional fields; treat the list below as a practical baseline rather than a complete regulatory checklist.
When you open a new supplier relationship, compare the first few COAs against this checklist and write down which fields your lab will always require. That habit prevents “we will ask next time” from becoming permanent gaps in your archive.
Print or pin a one-page field map near the receiving bench if your team processes many peptide lots. People under time pressure skim; a visible map keeps the minimum bar from quietly shrinking when the lab is busy.
- Product or compound name (and sometimes CAS, molecular weight, or sequence)
- Batch / lot number tied to the vial label
- Appearance (for example white to off-white lyophilized powder)
- Assay or purity by HPLC (often reported as ≥99% or a measured percentage)
- Identity method (HPLC retention-time match, MS, or both)
- Test date and, when provided, lab identity or accreditation note
- Optional panels: residual solvents, water content, endotoxin — when the method and product class call for them
Reading the HPLC purity line
HPLC purity answers a narrow question: of the peaks the method detects under stated conditions, what share is attributed to the main analyte? A high percentage is useful for many in-vitro and analytical workflows, but it is only as good as the method, the detector wavelength, and the sample preparation behind it.
Compare the reported value to the product-page claim. Across much of the products catalog, we publish a ≥99% HPLC expectation for research peptides. If the COA shows a measured percentage (for example 99.4%), record that number in your lab notebook alongside the lot. Rounding conventions differ; copy the figure as printed rather than “cleaning it up.”
Method footnotes matter. Column chemistry, gradient program, and integration rules can change how closely related impurities resolve. Two COAs with similar headline percentages are not interchangeable evidence if the methods differ. When your protocol depends on a specific impurity profile, ask for the method summary rather than relying on the percentage alone.
For a deeper treatment of what the percentage does and does not mean, see HPLC purity for research peptides. That companion article pairs with this guide: here you locate the field; there you interpret its limits.
When a chromatogram image is attached, glance at baseline noise, peak shape, and whether minor peaks are labeled or simply integrated into the total. You do not need to re-process the raw data to notice an obviously truncated figure or a missing method header. Those visual cues often tell you to request a cleaner PDF rather than to invent an interpretation.
Identity versus purity
Purity does not prove identity by itself. A clean chromatogram still needs a stated identity check — often mass spectrometry, a reference retention-time match, or both. When both purity and identity appear on the COA, you have stronger lot documentation than an assay line alone.
Mass spectrometry typically reports an observed mass consistent with the expected molecular ion or adduct. Retention-time identity compares the sample to a reference under the same HPLC method. Neither replaces the other in every context; they answer different questions. Record both when present.
Synonym collisions are common in peptide catalogs. Marketing names and spelling variants (for example Epitalon versus Epithalon) can diverge across vendors. Rely on sequence, CAS when listed, and the COA identity section rather than the storefront title alone. Our guide to catalog names, CAS, and peptide identifiers covers how to reconcile those strings before you open a vial.
If identity language on the PDF is vague — for example “conforms” without a method — treat that as incomplete for protocols that require documented confirmation. Request clarification or plan in-house confirmation before the lot is committed to a long series of experiments.
Cross-check identity fields against the purchase order text, not only against the vial nickname. Purchasing sometimes abbreviates; receiving sometimes expands. The COA is a good referee when those two strings disagree and nobody remembers which one matched the protocol.
Appearance, fill claims, and physical checks
Appearance lines are easy to skim past, but they catch gross discrepancies early. A COA that describes a white lyophilized cake paired with a vial that arrives as an unexpected oil or deeply colored residue is a stop condition. Photograph the vial, quarantine it per your SOP, and contact the supplier with the lot number before any further handling beyond secure storage.
Fill amount on the label is a manufacturing claim for that SKU presentation; the COA may or may not restate it. Do not treat the COA purity percentage as a check of milligram fill. Gravimetric or reconstitution checks belong to your lab’s receiving or QC procedures when a protocol requires them.
Lyophilized cakes can look different across lots even when both are within specification — denser plugs versus fluffy powder, slight color variation within “white to off-white.” Train receiving staff on what “unexpected” means for your inventory so minor cosmetic variation does not generate false alarms while true outliers still get flagged.
Compounds such as BPC-157 research vials, TB-500, and NAD+ illustrate how catalog SKUs share documentation patterns even when chemistry differs. Always pull the lot file for the exact SKU you received rather than a sibling presentation.
Copper-containing research materials such as GHK-Cu and mitochondrial-derived sequences such as MOTS-c follow the same lot-match discipline. Different chemistry does not excuse a “close enough” PDF from another catalog family.
Residual solvents, water, and other optional panels
Not every research-peptide COA includes residual-solvent or moisture data. When those panels appear, read the units and the acceptance criteria printed on the report. A result without a stated limit is harder to interpret than one with a clear specification line.
Water content can matter for hygroscopic lyophilized materials and for long-term storage planning. Residual-solvent panels matter when your downstream analytical method is sensitive to particular process solvents. If your institution requires either panel and the COA omits it, escalate before the lot is released for use.
Endotoxin or bioburden language, when present, is still lot documentation for research materials — not a statement about suitability for any non-laboratory use. Keep interpretation inside your institution’s research quality framework.
If you regularly need panels that a given lot file omits, ask at order time whether additional testing can be arranged, or plan confirmatory testing in-house. Waiting until the day of an experiment is how documentation gaps turn into schedule problems.
Some labs maintain a “required vs nice-to-have” panel list by assay type. Screening plates may accept a leaner file; quantitative analytical work may demand moisture or solvent data every time. Write that distinction into purchasing notes so suppliers and receiving staff are not guessing which bar applies.
Test dates, lab identity, and versioning
Note the test date relative to manufacture or release when both appear. Extremely old test dates paired with newly labeled vials deserve a second look: confirm you have the current file for that lot, not an archived PDF from a previous production cycle reused by mistake.
Lab identity and accreditation notes, when provided, help you understand who generated the data. Third-party lab names and methods can change over time as suppliers rotate partners. Prefer the file tied to your exact lot over an older PDF for a different batch of the “same” catalog item.
Version control inside your archive matters. If a corrected COA is issued, replace the prior file and note the revision in your receiving log. Do not keep two conflicting PDFs for the same lot without a clear “superseded” marker.
Digital hygiene helps audits later. Store the PDF under a filename that includes compound, lot, and date received. Screenshots of chromatograms without the full PDF are weak substitutes when an auditor asks for the original report.
Cloud folders that auto-sync are convenient until someone overwrites a file with a renamed duplicate. Prefer append-only naming (lot + revision letter) over “final_final2.pdf.” Small naming rules prevent large archive confusion.
Red flags that should pause release
Certain mismatches deserve an immediate hold, not a hopeful note in the margins. Lot numbers that do not match, compound names that describe a different sequence family, purity values far below the catalog claim without explanation, and identity sections that are blank or purely boilerplate are the usual stop conditions.
Less obvious flags include cut-off headers, missing page two of a multi-page report, chromatograms with no axis labels, and files that appear to be photocopies of photocopies with illegible batch strings. Ask for a clean original PDF before the vial leaves quarantine.
Be wary of “generic” documents that name a compound class but never list your lot. A template without lot linkage is marketing residue, not receiving evidence. Likewise, a COA emailed for a different customer order number — even for the same catalog SKU — is the wrong chain of custody for your notebook.
If pressure from a schedule tempts the lab to “use it and sort paperwork later,” resist. Experimental work performed under the wrong lot file is harder to unwind than a delayed start. Quarantine exists for that reason.
Limits worth keeping in mind
A COA reflects the tested sample and method at a point in time. It does not replace your institution’s receiving procedures, solubility checks, or in-house confirmation when a protocol requires them. Storage after arrival still matters; a correct COA will not rescue a vial that sat warm on a loading dock for days. Pair this guide with lyophilized peptide storage for laboratory use when you write receiving SOPs.
COAs also do not transfer across presentations. A 5 mg vial and a 10 mg vial of the same catalog family may share a manufacturing campaign or may not. Always match lot numbers rather than assuming shared paperwork.
Blend SKUs deserve extra care. Confirm whether the uploaded file covers the blend as formulated or documents each component separately. Ambiguous blend documentation is a common source of filing errors; request clarification in writing and keep that email with the PDF.
Finally, a COA is not a substitute for Research Use Only compliance. High HPLC purity does not imply suitability outside laboratory contexts. Keep experimental design, institutional approvals, and supplier terms aligned — paperwork quality is necessary, not sufficient.
A practical receiving workflow
A short, repeatable workflow beats ad-hoc PDF skimming. Many labs use a pattern like the following: (1) verify outer packaging and seal, (2) record lot from the vial, (3) retrieve the matching COA, (4) check identity and purity fields against purchase expectations, (5) file PDF and receiving notes together, (6) release the vial to storage or quarantine per SOP.
Assign who owns each step. Confusion between purchasing, receiving, and the bench is how lots get opened before documentation is complete. If your group is small, a single checklist still helps — especially when temporary staff handle deliveries.
When something fails a check, pause. Document the discrepancy, contact the supplier with order and lot details, and keep the material segregated. Resolving paperwork after experiments have started creates avoidable integrity problems for the study record.
Over time, keep a simple log of which product lines routinely have complete files and which need follow-up. That log informs future purchasing decisions and reduces last-minute scrambles before grant reports or internal audits.
For multi-site groups, publish the checklist once and refuse local “shortcuts” that skip lot matching. Consistency across freezers matters more than perfect identical hardware. A shared template in the lab wiki beats three slightly different oral traditions.
Training receiving staff without overloading them
Not everyone who unpacks a box needs to interpret every chromatographic footnote. Separate the job into tiers: everyone matches lot to PDF and flags gross mismatches; designated reviewers read method notes and optional panels; PIs or QA decide when in-house confirmation is required.
A thirty-minute walkthrough with three real PDFs from your own archive teaches more than a generic slide deck. Show one clean file, one missing-lot example, and one blend ambiguity. People remember patterns they have seen on your letterhead paths.
Refresh training when suppliers change report layouts. Layout churn is normal; treating every new template as “probably fine” is how critical fields get skipped. Keep a short changelog in the receiving binder: “as of date X, purity moved to page 2.”
Celebrate catches. When a technician stops a bad match, say so in the lab meeting. Culture that rewards careful pause beats culture that only rewards speed to freezer.
Using the Nextday Peptides COA Library
Browse the COA Library on this site to pull batch documents for compounds we stock. Availability varies by product and lot; newer lots appear as testing files are posted. Bookmark the library page if your group orders regularly so receiving staff are not hunting through order emails for attachments.
Keep COAs with your experimental records, and treat them as research documentation only — consistent with our Educational Articles Disclaimer and Research Use Only terms. Questions about a missing lot file or a mismatch between label and PDF go to orders@nextdaypeptides.com.
If you are building a binder or shared drive for a multi-year project, download the PDF at receipt rather than relying on a live link forever. Lot pages can be updated; your archive should freeze the document that accompanied the material you used.
Educational articles on this hub — including this COA guide — exist to make procurement and documentation clearer for qualified laboratory buyers. They are not protocols for non-research use. When in doubt about labeling or intended use, start from the RUO article and the sitewide terms before you open a vial.
When you email support, include order number, catalog name, lot string exactly as printed, and a description of what you already checked. That context shortens the path to the correct file and keeps the thread inside procurement documentation rather than open-ended product speculation.
If your group orders the same SKUs monthly, consider a shared folder template with subfolders per compound and lot. Consistency in where PDFs live is half of documentation quality; the other half is reading the fields before the vial leaves quarantine.
Keeping COA files audit-ready
Audits and grant close-outs rarely ask clever questions. They ask whether you can produce the lot file for the material cited in a methods section. Organize so the answer is a path, not a scavenger hunt across email inboxes.
Include order number and receipt date in the same record as the PDF. When a reviewer asks which shipment supplied a figure panel, you should not need to reconstruct logistics from memory.
Periodic spot checks help. Once a quarter, pick three active lots at random and verify that vial, freezer location, and PDF still agree. Small mismatches caught early are easy; mismatches found during a formal review are not.
Close the loop after experiments end. When a lot is exhausted, mark the ledger closed and keep the PDF with the study archive rather than deleting it to “tidy” the shared drive. Exhausted lots still matter for methods traceability.
If two labs collaborate on one order, designate a single documentation owner. Split ownership of the same PDF across two drives is how conflicting annotations appear with no clear source of truth.