Verification

Tested Sample vs Batch-Linked COA

Tested Sample vs Batch-Linked COA: definitions, Batch-Linked threshold, public-library default, and buyer decision rules for B2B sourcing.

BatchVerity operations2026-09-208 min

Tested Sample means an authentic independent laboratory report for the material that was submitted to the lab — the result applies to that submitted sample and date. Batch-Linked means the same kind of independent report, plus a documented correspondence between that submitted sample and a stated sales batch or lot. Use Tested Sample for early source review and scoped decision files; reserve Batch-Linked only when verifiable lot marks (or equivalent controlled identifiers) connect the tested unit to the goods under discussion.

This note is for professional B2B buyers who need a clear decision rule on evidence scope during China-side peptide sourcing. It does not rewrite What a COA proves or the field-by-field buyer checklist; it isolates the two labels so procurement, QA and commercial teams can use the same language.

Comparison at a glance

BatchVerity labels evidence by documented relationship, not by product name, seller assurance or marketing language.

Tested Sample Batch-Linked
Definition Independent lab report for the submitted sample Independent lab report plus recorded lot correspondence to a stated sales batch
What it proves Findings for the material that entered the laboratory, under named methods, on the report date Those findings and a documented link between that sample and the named sales lot / batch
Threshold Product, sample/report identifiers, lab, date and result fields are present and usable Lot / batch marks (or equivalent controlled identifiers) on the submitted unit and on the proposed goods match, and that match is recorded
Not enough — Product-name match alone; strength match alone; verbal “same batch” claims; seller PDF reuse without identifiers
Public library default Yes — default reading for records in the COA library Only when a specific record explicitly documents correspondence under the threshold below
Typical buyer use Early source review, written-spec design, pilot / limited commitment Larger releases, higher contractual exposure, payment gates tied to lot marks
Still does not prove Every vial in a shipment; a future lot; untested panels Every unit in the linked lot is identical; a later lot will match; destination eligibility

Batch-Linked threshold (documented lot correspondence only)

Explicit rule: We use Batch-Linked only when the relationship between the submitted sample and the stated sales batch is documented rather than assumed.

Meeting the threshold typically requires all of the following to align in the order file:

  1. Controlled identifiers — lot / batch marks (or equivalent controlled IDs) appear on the submitted unit and on the proposed goods (labels, packing lists, retained samples as applicable).
  2. Recorded match — those identifiers match, and the match is written into the evidence record — not inferred from product name or strength.
  3. Independent report scope — the laboratory report remains an authentic third-party result for the submitted material; the Batch-Linked label adds the lot relationship, it does not replace lab accountability.
  4. Order-specific citation — the correspondence is cited for this enquiry / release, not borrowed from an unrelated public PDF.

If any of those fail, keep the working and public label as Tested Sample. Matching product name, matching strength, a supplier verbal assurance, or a recycled “batch COA” without lot marks is not Batch-Linked.

Batch-Linked narrows scope. It still does not mean every unit in that lot is identical to the tested unit, or that a later production lot will match. Unit-to-unit and lot-to-lot variation remain separate controls.

What the public library defaults to

Public records in the COA library are authentic third-party reports for submitted samples. Read them as Tested Sample evidence by default, unless a specific record explicitly documents Batch-Linked correspondence under the threshold above.

Why the default matters:

  • Public copies are redacted so another seller cannot reuse the file as proof for unrelated goods.
  • A dated Tested Sample record supports review of what was measured on that sample — it is not a standing guarantee for future production.
  • Elevating a record to Batch-Linked without documented lot correspondence would misstate scope for every buyer who opens the library.

Qualified buyers can request full-version verification of a redacted public copy against a BatchVerity report ID via Contact. That is verification of the report record — not an approval or clearance of goods.

Example product evidence pages (organize public reports by product; not a retail catalog): BPC-157, Retatrutide, Tirzepatide, TB500. Browse the index on Verified products.

Buyer decision rules

Use the labels to decide what the document can support before deposit or balance release — not to invent a single “pass / fail” headline.

  1. Start as Tested Sample. If you only have product name + a laboratory PDF with sample/report fields, label it Tested Sample and use it for early review, written specs and pilot design.
  2. Escalate identifiers before you escalate volume. When commitment size, risk or contractual exposure rises, ask which lot / batch marks will appear on labels, packing lists and retained samples — and whether independent testing will cite those marks. That is the path toward Batch-Linked review.
  3. Do not close large gates on an unlinked PDF. A Tested Sample report does not, by itself, justify treating an unlinked sales lot as already proven.
  4. Require the match in writing. If a party claims Batch-Linked, the correspondence must be in the order file (identifiers + recorded match). Verbal assurance is not the threshold.
  5. Keep each order as its own evidence file. A prior public or historical Tested Sample result does not automatically cover a new release. Confirm written product, format, strength, packaging, quantity, batch requirements and documents for this order.
  6. Separate label from panels. Scope label (Tested Sample vs Batch-Linked) is not the same question as identity / purity / content. Read fields separately — see How to read a peptide COA and What a COA proves.

Sister checklists (upcoming): RFQ checklist for China peptide sourcing · How to vet a China peptide supplier.

China-side control is about closing gaps between supplier, laboratory and carrier with written specs and scoped evidence — not treating any one PDF as a blanket clearance.

Soft next step

If you are reviewing one product requirement and need help classifying report scope (Tested Sample vs Batch-Linked) against a written specification, request a complimentary preliminary review of your enquiry and evidence needs via Contact — not an approval, clearance, or “safe for use” determination.

WhatsApp: United States +1 303 961 4229 · China +86 180 0545 5057 · Email: sales@batchverity.com

Qualified B2B enquiries only. Laboratory testing, factory audits and extended investigations are quoted separately.


FAQ

What is a Tested Sample COA?

A Tested Sample COA is an authentic independent laboratory report for the material submitted to the lab. The findings apply to that submitted sample, under the methods and date stated on the report. It is the default reading for public records in the COA library.

What is a Batch-Linked COA?

A Batch-Linked COA is an independent laboratory report for a submitted sample plus documented correspondence between that sample and a stated sales batch or lot. Lot / batch marks (or equivalent controlled identifiers) must match and be recorded. Product name alone is not enough.

What is the threshold for calling evidence Batch-Linked?

Documented lot correspondence only. Matching product name, matching strength, or a verbal assurance does not meet the threshold. Absent verifiable, recorded identifiers connecting the submitted unit to the proposed goods, the correct label remains Tested Sample.

Does the BatchVerity public library default to Batch-Linked?

No. Public library records should be read as Tested Sample unless a specific record explicitly documents Batch-Linked correspondence. See also What a COA proves.

When should a B2B buyer require Batch-Linked evidence?

When order volume, risk or contractual exposure requires a documented link between tested material and the sales lot you will receive — typically controlled lot marks, retained samples and independent reports that cite those identifiers — before larger payment releases.

Does Batch-Linked prove every vial in the lot or a future batch?

No. Batch-Linked narrows scope to a documented lot relationship. It does not prove every unit in that lot is identical to the tested unit, and it does not prove a later lot will match. Treat each release as its own evidence file.

How do I check which label I actually have?

Confirm lab name, date, sample/report IDs and results first; then ask whether lot marks on the submitted unit and on the proposed goods match and are recorded. If they are not, keep Tested Sample. For a field-by-field page checklist, use How to read a peptide COA.


Scope note (retain on publish)

This article explains BatchVerity’s evidence-scope labels for professional sourcing. It is not medical, legal or regulatory advice; it does not establish product availability for a destination; and it does not approve, clear or certify goods for any human use.

Request a review