Verification
What a COA proves, and what it does not
A COA proves lab results for a submitted sample—not every vial or future lot. How BatchVerity separates Tested Sample from Batch-Linked evidence.
A Certificate of Analysis (COA) is a laboratory report that records what was measured on a specific submitted sample, under named methods, on a stated date. It can support a sourcing decision when the report identifiers, product description and evidence scope line up with the goods under discussion. It does not automatically validate every vial in a shipment, a future production lot, or a supplier claim that is not documented on the report.
This note explains how professional buyers should read COA scope—especially the difference between Tested Sample and Batch-Linked—and how BatchVerity publishes and uses that evidence on the China side of an order.
Start with the tested item
The first question is not whether a PDF looks professional. It is whether the report can be tied to the physical sample that entered the laboratory.
Before treating a COA as order evidence, align at least these fields with the source records you hold:
- Product name and stated strength or format
- Sample or submission identifier used by the laboratory
- Report number / BatchVerity report ID (where applicable)
- Report date and laboratory name
- Any lot, batch or vial mark printed on the submitted unit (if present)
When those fields disagree—or when only the product name matches—the document is not yet usable as decision evidence. A clean layout does not repair a broken chain of custody.
Public records in our COA library are authentic third-party reports for submitted samples. Public copies are redacted so another seller cannot reuse the file as proof for unrelated goods. Qualified buyers can request full-version verification against a BatchVerity report ID via Contact.
Tested Sample vs Batch-Linked (threshold)
BatchVerity labels evidence by documented relationship, not by hope or marketing language.
| Label | What it means | Threshold to use the label |
|---|---|---|
| Tested Sample | A real independent laboratory report for the material submitted to the lab. | Product, sample/report identifiers and test fields are present; the result applies to that submitted sample. Default for the public library. |
| Batch-Linked | The tested sample is connected to a stated sales batch or lot by verifiable correspondence. | Lot/batch marks (or equivalent controlled identifiers) on the submitted unit and on the proposed goods match, and that match is recorded—not assumed from product name alone. |
Explicit threshold: We use Batch-Linked only when the relationship between the submitted sample and the stated sales batch is documented rather than assumed. Matching product name, matching strength, or a supplier verbal assurance is not enough. Absent verifiable lot correspondence, the correct public and working label remains Tested Sample.
What this also means:
- The public COA library should be read as Tested Sample evidence unless a specific record is explicitly elevated under the Batch-Linked threshold above.
- A Tested Sample result does not automatically prove a future sales batch.
- Batch-Linked evidence still does not guarantee that every unit in that lot is identical to the tested unit, or that a later lot will match. It narrows scope; it does not erase batch-to-batch variation.
Related product evidence pages (examples): BPC-157, Retatrutide, Tirzepatide, TB500. Those pages organize public report records by product. They do not claim stock, destination eligibility, or that an earlier tested sample represents a future order.
Read identity, purity and content as separate questions
Identity, purity and content answer different procurement questions. Mixing them is a common sourcing error.
Identity asks whether the measured material is consistent with the named compound (and method constraints stated by the laboratory). An identity result does not establish fill weight, net peptide content, residual solvents, or any panel that was not run.
Purity (often reported as an area-% or related chromatographic figure) describes relative composition under the method used. A high purity figure does not, by itself, prove how much peptide is in a vial, and it does not stand in for identity when identity was not reported.
Content / assay / net peptide content (when present) addresses quantity-related questions under the laboratory’s method. Content is not interchangeable with purity. Absence of a content field means content was not established by that report.
Only panels actually performed belong in the decision record. Do not infer sterility, endotoxin, residual solvent, water or packaging integrity from identity or purity alone. If a buyer requires those controls for an order, they must be written into the specification and, where needed, commissioned as separate evidence—not read into a COA that never tested them.
Use evidence at the right scope
A COA is useful when the proposed goods and the tested material are properly connected. Scope discipline matters more than a single headline number.
Practical rules for B2B buyers:
- Connect before you escalate. Use a Tested Sample report to support early source review, written specs and pilot-order design—not to close a large commitment that depends on an unlinked sales lot.
- Require lot correspondence when volume rises. For larger releases, ask what identifiers will appear on labels, packing lists and retained samples, and whether independent testing will be tied to those marks. That is the path from Tested Sample toward Batch-Linked review.
- Keep records dated and versioned. Current and historical statuses exist so evidence history is not silently rewritten. A newer report for a different sample does not erase an older one; it adds a dated data point.
- Treat each order as its own evidence file. Written product, format, strength, packaging, quantity, batch requirements and documents should be confirmed before money moves. China-side coordination is about controlling those gaps between supplier, laboratory and carrier—not treating any one PDF as a blanket clearance.
A report cannot prove future batches in advance. That is why every BatchVerity public record remains dated, scoped and versioned, and why publication status (Current, Historical, and related states) stays visible on the COA library.
What a COA does not prove
Even when authentic and correctly scoped, a COA does not prove:
- That every vial in a shipment matches the submitted sample
- That a future lot will match a prior result
- That product name alone equals lot correspondence
- That untested attributes (for example, panels never commissioned) are within any stated limit
- That destination eligibility, customs outcome or delivery condition are settled
- That a supplier’s marketing claim outside the report text is laboratory-backed
In short: the COA proves the laboratory’s stated findings for the submitted sample (and, where documented, a linked lot relationship). Everything else remains a separate control—written specification, source qualification, payment milestones, and delivery terms.
How BatchVerity uses COAs in China-side control
On an eligible enquiry, we treat laboratory reports as one control among several:
- Source role and documentation review before naming a production role
- Written specification before ordering
- Independent laboratory coordination with retained originals and stated scope per record
- Payment and release decisions tied to completed checks, including batch marks and documents where required
- Delivery and exception handling attached to the order record
The supplier remains responsible for production. The laboratory remains responsible for its report. BatchVerity coordinates evidence and decisions across those parties so professional buyers can see what was confirmed—and what still needs verification—before scaling volume.
Browse public records in the COA library, or open a product evidence page such as BPC-157 or Retatrutide to see how reports are grouped without being presented as a retail catalog.
Related Insights
FAQ
Does a COA prove my entire shipment?
No. A COA proves laboratory findings for the submitted sample described on the report. Unless you have documented lot correspondence that meets the Batch-Linked threshold, do not treat the result as proof of every unit in a shipment.
What is the difference between Tested Sample and Batch-Linked?
Tested Sample means an authentic independent report for the material submitted to the laboratory. Batch-Linked is used only when verifiable identifiers connect that sample to a stated sales batch or lot. Product name match alone is not enough. Public library records should be read as Tested Sample unless a record explicitly documents Batch-Linked correspondence.
Can I rely on a public COA in the BatchVerity library for a future order?
Use it as scoped evidence for the tested sample and date shown—not as a standing guarantee for future production. For a new order, confirm written specifications and whether new testing or lot-linked verification is required before larger payment releases.
Why are public COAs redacted?
Sensitive identifiers are concealed so another seller cannot present the document as evidence for unrelated goods. Qualified buyers can send a BatchVerity report ID through Contact or WhatsApp to request full-version verification.
If purity looks high, does that mean content and identity are also fine?
No. Identity, purity and content are separate fields. Only panels actually performed belong in the record. Read each result against the method and scope stated by the laboratory.
When should a buyer ask for Batch-Linked evidence?
When order volume, risk or contractual exposure requires a documented link between tested material and the sales lot you will receive. That typically means controlled lot marks, retained samples and independent reports that cite those identifiers—not a generic product PDF.
Scope note: This article explains BatchVerity’s operating approach. It is not medical, legal or regulatory advice, and it does not establish product availability for a destination.