How to request and verify a COA before you buy
Reading a COA correctly is the second step. The first is getting one. Many research-peptide vendors do not surface batch-specific Certificates of Analysis on their public product pages, which means the documentation has to be requested before purchase to confirm what you would actually be receiving. This article walks through how to make the request, how to read the vendor's response, and how to confirm the returned document is real. The structural reference for what a COA should contain is in the field-by-field cornerstone.
How should the request actually be phrased?
A specific request is harder to deflect than a generic one. The vendor should know which product you are evaluating, that you understand how COAs work, and that you are asking for batch-specific documentation rather than a marketing summary. The request can be short — three or four lines is sufficient — but every element matters.
The minimum viable request includes:
- The product name and SKU/catalog number. Identifies which compound you are asking about; ambiguity here gives the vendor an easy out.
- A request for the COA matching the current shipping batch. Phrase it as "the batch-specific COA matching the lot I would be receiving" — this signals that you understand a generic document is not what you are after.
- Any specific fields you want to confirm. If you care about endotoxin EU/mg or the ISO/IEC 17025 accreditation status of the testing lab, name them. Vendors who can produce the document already include these; vendors who cannot will sometimes try to substitute marketing language for the missing fields.
- Your order reference if you have one. If the vendor has placed a hold on a specific lot for your order, the lot reference accelerates the lookup.
The longer-form context — why the request matters and how to read the document once received — lives in batch-matched vs. generic COAs, which covers the operational gap between a real document and a recycled house template.
How do you read the vendor response?
Three response patterns appear consistently in this category. Each has a different operational implication.
| Response pattern | What it implies | Next step |
|---|---|---|
| Document delivered within one business day, batch number visible | Vendor maintains batch-to-document traceability; documentation is real | Verify the document contents against the field-by-field reference |
| Stalls, repeated requests for clarification, deflection to marketing pages | Vendor likely cannot produce a batch-matched document | Treat absence of documentation as the answer |
| Generic "house COA" sent without a batch reference | Vendor recycles a single document across batches | Re-request with explicit "matching the lot I would receive" framing; if same response, treat as undocumented |
| Document delivered but batch number does not match the lot you would receive | Document is from a previously-tested batch being reused as evidence | Ask for the matching batch; if not produced, treat as undocumented |
| Refusal — "we don't share COAs publicly" | Either documentation does not exist or the vendor has policy reasons unrelated to existence | Push back; if refusal stands, the practical effect is the same as no documentation |
What checks do you actually run on the returned document?
Once a vendor produces a document, the verification protocol from the cornerstone applies — five quick checks that take less than five minutes and confirm whether the document is what it claims to be.
- Match the batch number. The number on the COA should match the lot you would be receiving. If you do not yet have the physical material in hand, the vendor's email or order page should specify the lot they have allocated.
- Match the date. The date of analysis should be reasonable for the material — within months, not years. A 2018 COA on a 2026 batch is referencing material that no longer exists.
- Match the methodology references. If the COA cites USP <85> for endotoxin or USP <621> for HPLC, those are verifiable against published standards. References to methods that don't exist are red flags.
- Look up the issuing laboratory. A real lab has a website, a phone number, and ideally an ISO/IEC 17025 accreditation registration that can be verified against the registrar's database.
- Cross-request from the vendor. If the document was sent in response to one request, send a follow-up question with a specific factual point (e.g., "What is the integration threshold used for HPLC purity?") — vendors who actually have the underlying data can answer it; vendors who recycled a generic document often cannot.
The five-minute version of these checks is the routine verification any researcher should do once before establishing a relationship with a vendor — and a quick spot-check on subsequent batches.
When does a vendor stall justify walking away?
A vendor that consistently cannot produce batch-specific documentation, that substitutes marketing material for technical fields, or that refuses to engage with specific factual questions about its testing is signaling that the underlying documentation infrastructure does not exist. The signaling is the answer; further effort to extract documentation that is not maintained is not productive.
Whether to accept material on undocumented terms is application-dependent. For research uses where the documentation is structurally important — sensitive cell-culture work, immunogenicity studies, applications with strict reagent provenance requirements — sourcing from a vendor with verified documentation infrastructure is the operational path forward. For routine in-vitro biochemistry on materials that are also independently characterized in published literature, the threshold may be lower. Either way, the explicit decision is preferable to the implicit one.
Frequently asked
- How do I ask for a batch-specific COA from a research peptide vendor?
- Send a short specific email naming the product (with SKU or catalog number), asking explicitly for "the batch-specific COA matching the lot I would be receiving" rather than a generic certificate, and naming any specific fields you want to confirm (endotoxin EU/mg, ISO/IEC 17025 accreditation, methodology references). Include your order reference if one exists. A vendor with real documentation infrastructure produces the matching document within one business day.
- How long should it take a vendor to produce a COA on request?
- For a vendor with batch-to-document traceability, one business day is typical. The lookup is straightforward — the order references a lot number, the lot number is the join key to the COA on file, and the document is retrieved and emailed back. Stalls beyond a few business days, repeated requests for clarification, or deflection to marketing pages are signals that the underlying documentation may not exist.
- What if the vendor sends a COA that doesn't match my batch number?
- The COA does not document your material. Re-request with explicit "matching the lot I would receive" framing and the lot number if known. If the vendor cannot produce a matching document, the practical effect is that the material is undocumented for your batch. Whether to accept on those terms depends on the research application and your tolerance for documentation gaps.
- Should I worry if a vendor "doesn't share COAs publicly"?
- Possibly, but not necessarily. Some vendors have legitimate policy reasons for not posting COAs to public product pages — usually preferring to deliver them on request to confirmed customers or order references. The concern is when "we don't share publicly" extends to "we won't share with you on request either." Push back; a vendor that cannot or will not produce documentation under specific request is functionally undocumented.
- How do I know an issuing laboratory on a COA is a real lab?
- Three quick checks: the lab has a working website with contact information; a phone number that connects to a person who can confirm the document on file; and ideally an ISO/IEC 17025 accreditation registration that can be verified against the registrar's public database. Real labs are externally audited and listed; "labs" that have only a name on a letterhead and no verifiable presence are red flags.
Sources and further reading
- ISO/IEC 17025:2017 General requirements for the competence of testing and calibration laboratories — the international accreditation standard whose audit-trail requirements underpin batch-to-document traceability.
- USP <1226> Verification of Compendial Procedures — methodology for verifying that a stated test procedure actually produces the result claimed.
- FDA Guidance: Drug Substance Chemistry, Manufacturing, and Controls Information — regulatory context on how identity, purity, and contamination testing are documented in regulated submissions.