How to Read a Pesticide COA: A Buyer Review Checklist

A pesticide COA should help an importer answer a concrete question: does the reported batch meet the specification agreed for this purchase? Start with the product identity and batch number, then compare each reported result with its limit, unit and test method. Resolve gaps before giving commercial approval. An attractive certificate layout is less useful than a clear connection between the order, sample, test results and goods being shipped.

This guide is for procurement teams reviewing supplier documents. The checklist below is a proposed purchasing workflow, not a universal regulatory form. Product-specific requirements and the destination registration still need their own review.

Quick answer: Check identity, batch traceability, specification version, methods, units, numerical results and authorization. Record unanswered questions against the shipment. Ask for clarification or appropriate testing instead of assuming that a missing result means a pass.

Start with the order and batch

Put the purchase specification, proposed label, packing list and COA side by side. Highlight the active ingredient name, concentration, formulation code and batch identifier in each document. If a mixture is being purchased, repeat the check for every declared active ingredient. Treat an unexplained difference as a question to resolve, even when the trade name is identical.

Ask whether the certificate belongs to the production batch being offered or to an earlier reference batch. A reference COA can help assess a supplier's document format, but procurement should not file it as evidence for a later shipment. When several batches are loaded, request a batch-to-quantity mapping so the receiving team can connect each certificate to the appropriate stock.

Use one controlled version of the agreed specification. FAO describes its pesticide specifications as quality references for trade and for national authorities; that makes them useful reference material when agreeing requirements. Confirm the applicability of the particular specification instead of treating a general reference to FAO as a product endorsement. See the FAO/WHO pesticide specifications framework.

Read the result, limit and method together

A useful review sheet separates three things: the requirement, the reported result and the method used to obtain it. Copy them into different columns. A line that simply says “complies” may require follow-up when your agreed document requirements call for a numerical result. Ask the supplier to explain omissions rather than filling them from an older certificate.

Keep units visible. For example, 500 g/L and 500 g/kg describe different concentration bases and are not automatically interchangeable. This is an illustrative unit comparison, not a specification for a particular pesticide. If the order and report use different units, request the applicable conversion basis and technical confirmation before comparing the figures.

Record the method identifier or laboratory procedure reference supplied with each relevant test. Where a method differs from the one agreed, send the question to the technical reviewer. Avoid accepting or rejecting a batch solely because two reports use different abbreviations; first establish whether they refer to the same procedure and reporting basis.

The website's guide to FAO/WHO specifications and CIPAC methods provides background for this discussion. Keep the COA review focused on the actual purchase rather than copying every possible test into every order.

A pesticide COA review checklist

Use the following template as a starting point. Add the product-specific requirements agreed by your quality and regulatory teams.

• Product identity: What to record: Ingredient, concentration, formulation; Question if incomplete: Does this match the purchase specification?.
• Batch mapping: What to record: Batch number and shipment quantity; Question if incomplete: Which containers does this report cover?.
• Specification: What to record: Identifier and revision; Question if incomplete: Which acceptance criteria were agreed?.
• Test result: What to record: Value, unit and limit; Question if incomplete: Is the comparison on the same basis?.
• Method: What to record: Method number or procedure reference; Question if incomplete: Is this the agreed analytical approach?.
• Document control: What to record: Report number, issue date, issuer; Question if incomplete: Who can confirm this version?.
• Review decision: What to record: Reviewer, date, open items; Question if incomplete: What still prevents approval?.

Do not turn this into a box-ticking exercise. Assign each unanswered item to a named person and keep its status visible. A short review with traceable decisions is more useful than a long spreadsheet where every entry is marked “checked” without supporting documents.

Resolve exceptions with a written question

An effective request identifies the exact mismatch. For example: “The packing list names batch A, while the attached COA names batch B. Please provide the report covering batch A and confirm its quantity in this shipment.” This is a hypothetical example, not an account of a supplier incident.

For a test issue, quote the result and the agreed acceptance criterion together. Ask whether the problem is a transcription error, a reporting-basis difference or a result requiring technical investigation. Retain the original report and any corrected version, with a short explanation of why the correction was issued.

When independent testing is appropriate, agree the sampling and laboratory arrangements before dispatch. FAO's quality-control guidance addresses sample selection and sampling procedures as part of pesticide quality control. A procurement team should establish who samples, how the sample is identified and which laboratory receives it, with qualified personnel defining the technical procedure.

Prepare the document request before ordering

A pesticide COA review works best when the supplier knows the requested format before production. Include the specification version, reporting units, batch mapping and review responsibilities in the purchasing brief. For a broader document overview, read the formulation quality documents guide.

To discuss a sourcing requirement, contact Averstar with the active ingredient, formulation, destination market and requested documentation. That gives the conversation a clear starting point without assuming that one certificate can answer every technical or market-entry question.