Sample COA

This page provides a reference COA structure for EU-focused THCA wholesale procurement.
It is not a promise of results and not legal advice. The goal is consistency: buyers should be able to review COAs quickly,
spot missing fields immediately, and archive batch files that are audit-ready.

Start with the standards behind this template:
COA requirements ·
Testing standards ·
Lab verification ·
Batch traceability

How to use this sample

  • Use as a checklist: if a supplier COA is missing key fields below, treat it as incomplete.
  • Use for internal SOPs: adopt the field set as your minimum standard for procurement approvals.
  • Use for disputes: a complete COA improves clarity, but still requires verification and traceability.

Sample COA: required header fields

A COA must read like a technical document. These fields are the baseline.

Section A — Report & Lab Identity

  • Laboratory legal name
  • Laboratory address
  • Laboratory contact (email/phone)
  • Accreditation reference (where applicable; scope should match analytes)
  • Report/COA number (unique identifier)
  • Issue date
  • Report authentication (signature or verifiable digital validation)

Section B — Sample & Batch Identity

  • Product name / description (matrix: flower/extract/etc.)
  • Batch/Lot ID (must match invoice/packing list/labels)
  • Sample ID (lab receiving ID)
  • Client / submitter (as applicable)
  • Sample received date
  • Test date(s) (by panel if possible)

Section C — Methods & Reporting Controls

  • Method name/ID for each panel (e.g., potency, pesticides, metals)
  • Units (%, mg/g, ppm, CFU/g, etc.)
  • LOQ/LOD where relevant (especially contaminants)
  • Measurement uncertainty notes where provided
  • Disclaimers (sample representativeness, scope limits)

Sample COA: potency panel (cannabinoids)

Potency should include at least THCA and Δ9-THC, and must state how “Total THC” is calculated or reported.
Buyers should standardize a single calculation approach in their SOP and apply it consistently.

Potency Results (example structure)

Analyte Result Units LOQ
THCA [value] % [value]
Δ9-THC [value] % [value]
Total THC [value] % —
CBD [value] % [value]
CBDA [value] % [value]

Required note: “Total THC calculation method used: [state method/calc].”
If not stated, buyers should treat “Total THC” as ambiguous.

Sample COA: contaminants panels (risk-based, strongly recommended)

Your contaminant scope should match your buyer risk model and destination requirements. At a conservative baseline, buyers often request:
pesticides, heavy metals, mycotoxins, and appropriate microbial screens. Results should include LOQ/LOD and clear units.

Pesticides (example structure)

  • Panel list documented (which analytes were screened)
  • Result format: “Not Detected” (ND) must reference LOQ
  • Units clearly stated (often ppm)

Heavy metals (example structure)

  • Common targets: As, Cd, Pb, Hg
  • Units (often ppm) and LOQ/LOD stated

Mycotoxins (example structure)

  • Common targets: aflatoxins and ochratoxin A
  • Units and LOQ/LOD stated

Microbials (example structure)

  • Scope and method stated (organisms tested)
  • Units (often CFU/g) and pass/fail logic defined by buyer specs

For baseline panels and sampling discipline, see /compliance/thca-testing-standards/.

COA authenticity & verification notes (buyers should store this)

A COA is not decision-grade until the lab and report are verifiable. Buyers should store a short verification note as part of the batch file.

Verification Note Template (copy/paste)

  • Verified by: [name/role]
  • Date: [YYYY-MM-DD]
  • Lab verified via: [portal/QR/direct contact/public listing]
  • Report number confirmed: [yes/no + method]
  • Scope check: [ISO/IEC 17025 scope aligned / validated method evidence]
  • Notes: [any anomalies or clarifications]

Verification workflow: /compliance/lab-verification/.

Common COA red flags (do not ignore these)

  • Missing batch/lot ID or mismatched identifiers across documents
  • Missing test dates, received date, or issue date
  • Methods not stated, units unclear, or LOQ/LOD missing for contaminants
  • Total THC shown with no calculation method or explanation
  • Lab cannot be verified independently

For how to handle non-conforming documentation in a buyer SOP, see /documentation/quality-assurance/.

FAQ

Is this an official COA we can use for compliance?

No. This is a reference template showing the fields and structure buyers should require. Your COA must come from a real lab,
be batch-linked, and be verifiable. Start at /compliance/certificate-of-analysis/.

Do we need contaminants testing for every batch?

That depends on your buyer policy and destination risk model. A conservative approach is to require contaminants screening routinely,
especially at scale. See /compliance/thca-testing-standards/.

What’s the single biggest COA mistake buyers make?

Accepting a COA with no batch linkage or no verification pathway. Fix that with
traceability and lab verification.

Where do I learn how this connects to shipping paperwork?

Use /documentation/shipping-flow/ and
/compliance/shipping-documents/.