How to Audit a Pesticide Specification Against the COA Before Shipment

Before pesticides are ready for shipment, the most important step is not to check whether the COA concludes with “PASS,” but rather to retrieve the Product Specification approved by and then verify, item by item, exactly what this COA reports.

A practical audit logic is very simple:

Approved Specification → Test Method → Batch COA → Actual Result → Compliance Decision → Shipment Release

Only if the product identity, specification version, batch number, test items, test methods, and actual results all align, and all applicable acceptance criteria are met, does this batch have the technical basis to proceed to the shipment approval stage.

Conversely, if the COA does not clearly identify the batch, lacks key test items, uses units that are not comparable, or if the results exceed the approved quality limits, the batch should not be released simply because the shipping deadline is approaching.

It is important to note: The COA itself is not a Specification.

A Specification answers the question:

“What standards must this product meet?”

A COA answers the question:

“What were the actual test results for this specific batch? ”

These two documents must be reviewed together.

For pesticide importers, distributors, registrants, and brand owners, this step essentially transforms “the supplier says the product is compliant” into “I have a set of documents and test data to verify whether this batch meets the agreed-upon standards.”

Why Should You Compare the COA With the Approved Specification?

Because a COA only has true audit value when clear acceptance criteria exist.

The FAO notes that Pesticide Specifications are not only used by regulatory agencies to determine whether the quality of products on the market matches that of registered products, but can also serve as part of a sales contract, providing buyers with a basis for expected quality. Specifications typically cover requirements such as active ingredient content, relevant impurities, applicable physical and chemical properties, and storage stability.

Therefore, procurement audits cannot stop at:

“The supplier provided a COA.”

The real questions to ask are:

“Which version of the Specification was used to test this COA?”

“Which production batch does it correspond to?”

“Do the test results meet the requirements of this Specification?”

“Are the testing methods comparable?”

If you are still establishing quality standards during the supplier approval phase, you may first refer to How to Develop a Pesticide Product Specification Before Supplier Approval. This step should occur before commercial batch production begins.

Specification and COA: What Is the Difference?

Understanding the roles of these two documents is the first step in the entire audit process.

Document	Primary Purpose	Typically Corresponds to
Product Specification	Defines the quality requirements the product must meet	Product
COA	Reports actual test results	Specific Batch
TDS	Describes the product’s technical characteristics	Product
SDS	Provides information on hazards, safe handling, and storage	Product / Formulation
Batch Record	Records information related to the manufacturing process	Batch
Registration Data	Supports registration in target markets	Product / Market

These can be understood as:

Specification = Standard

COA = Actual Result

For example:

Test Item	Specification	COA Result
Active Ingredient	Specified Acceptance Range	Actual Test Value
pH	Specified Range	Actual Test Value
Suspensibility	Minimum Requirement	Actual Test Value
Wet Sieve	Specified Limit	Actual Test Value

Only when these two columns can be effectively compared can the COA truly support batch review.

If you’d like to first gain a systematic understanding of what the COA, TDS, and SDS each can verify, you can refer to COA vs. TDS vs. SDS for Pesticides.

Step 1: Confirm the Exact Product Identity

Don’t jump straight to the test results as soon as you receive the COA.

First, confirm:

• Active Ingredient
• Concentration
• Formulation
• Product Name or Product Code
• Manufacturer or Source Information, where applicable
• Specification Reference

For example, if you purchased:

Lambda-Cyhalothrin 25 g/L EC

then the COA should at least clearly correspond to this specific product—not a product with a different concentration, different formulation, or a technical material.

This may seem very basic, but many document issues actually stem from this very point.

For example:

Lambda-Cyhalothrin 25 g/L EC

and

Lambda-Cyhalothrin 25% WP

Although they share the same active ingredient, they are not the same finished formulation.

Different formulation types mean:

• Different physical systems
• Different specifications
• Different QC parameters
• Different packaging
• Different registration identities

Therefore, first confirm exactly which product you are reviewing before comparing the numbers.

Step 2: Check the Specification Version

This is a step that many procurement personnel tend to overlook.

Don’t just ask:

“Do you have a specification?”

You should also confirm:

Which specification version was used for this batch?

Recommended checks:

Document control items	What needs to be confirmed
Product Name	Is it consistent?
Formulation	Is it consistent?
Specification Number	Is it consistent?
Revision	Is it an approved version?
Effective Date	Is it still valid?
Approval Reference	Is it traceable?

For example:

The purchase order was executed in accordance with Specification Rev. 02.

However, the COA provided by the supplier states that testing was conducted according to Rev. 01.

In this situation, one cannot simply look at whether the results are within specifications.

First, it is necessary to confirm whether there are any changes between Rev. 01 and Rev. 02 that affect the acceptance criteria for this batch.

This version control is particularly important for long-term, recurring purchases.

Because when a dispute arises a year later, the most troublesome issue is often not “how much of the product was tested,” but rather:

“Which set of standards did both parties actually use for the purchase at that time?”

Step 3: Match the COA to the Actual Production Batch</ h2>
Sample COAs and Commercial Batch COAs must not be confused.

If the supplier provides you with a sample-stage COA, it primarily certifies the results of the tested sample.

If the batch being prepared for export is a Commercial Batch, you must verify that the COA corresponds to the actual production batch.

At a minimum, check:

Batch Information	Key Audit Points
Batch Number	Does it match the actual shipment?
Production Date	Is it reasonable?
Test Date	Does it correspond to the testing of this batch?
Product Code	Is it consistent?
Package Coding	Is traceability possible?
Carton / Label Code	Does it correspond to the batch?

For example:

COA:

Batch A20261001

Actual goods prepared for container loading:

Batch B20261005

In this case, the COA for Batch A cannot directly serve as proof of quality for Batch B.

This does not necessarily indicate a product quality issue.

However, it does mean:

This COA has not yet verified the actual shipment batch.

For the first bulk purchase, it is recommended to link sample approval with commercial batch review. You can also refer to Pesticide Sample Testing Before a Bulk Order to learn how to link sample approval to subsequent bulk production and batch QC.

Step 4: Compare Every Required Test Item With the Specification

Only after confirming the product and batch should you proceed to the actual COA review.

It is recommended to create a simple audit table:

Test Item	Approved Specification	COA Result	Status	Comment
Active Ingredient	Approved Range	Actual Result	Pass / Hold / Fail	Compare directly
Appearance	Approved Requirement	Actual Observation	Pass / Hold / Fail	Check consistency
pH	Approved Range	Actual Result	Pass / Hold / Fail	Where applicable
Suspensibility	Approved Requirement	Actual Result	Pass / Hold / Fail	Where applicable
Wet Sieve	Approved Limit	Actual Result	Pass / Hold / Fail	Where applicable
Other Parameters	Product-specific	Actual Result	Pass / Hold / Fail	Review as required

Here is a very important principle:

Not all pesticides should undergo exactly the same COA test items.

Different formulations—such as SC, EC, WP, WDG, SL, OD, and FS—have different physical properties, so the applicable quality parameters also vary.

For example, an SC product may require a focus on suspensibility, wet sieve, viscosity, or other applicable physical properties.

Conversely, the review of an EC product may focus more on parameters such as emulsion characteristics.

So do not mechanically apply an SC COA checklist to all pesticides.

Step 5: Check the Test Method, Not Just the Number

This is the key to determining whether COAs are truly comparable.

Assumption:

Specification requirement:

Suspensibility ≥ X%

The COA shows:

Result = Y%

It seems simple.

But you should also ask:

How was the result measured?

Because factors such as:

• Sample Preparation
• Water Quality
• Temperature
• Conditioning
• Analytical Procedure
• Calculation Method
• Method Version

can all affect the test results.

The FAO/WHO pesticide specification system emphasizes the use of clear, reliable, and appropriately validated testing methods for quality evaluation; its technical documentation also specifically notes that CIPAC has long provided a large number of methods for testing the chemical and physical properties of pesticide formulations.

Therefore, a more professional audit relationship should be:

Parameter → Test Method → Acceptance Limit → Actual Result

rather than simply:

Parameter → Number

If the buyer plans to arrange for independent laboratory testing, they should also confirm in advance whether the testing methods used by both parties are comparable.

Step 6: Check the Units and Expression of Results

This is an area where misjudgments are very common in actual procurement.

For example, the Specification states:

250 g/L

While the COA states:

25%

One cannot simply assume that:

250 = 25%

and therefore conclude that the two results are completely interchangeable.

You must first confirm:

• g/L or g/kg
• w/w or w/v
• whether density is involved
• the basis for expressing the test results
• the notation used in the Registration Document
• What is the expression method required by the Specification?

For some Active Ingredients, it is also necessary to confirm which chemical expression basis is being reported, for example:

• acid equivalent
• salt
• ester
• active moiety

These expressions cannot be determined based solely on numerical values.

Therefore, if units are inconsistent, the most professional approach is not to “guess the conversion yourself.”

Rather:

First confirm the basis of expression, then perform the appropriate technical conversion and compliance assessment.

Step 7: Do Not Use a Universal Tolerance for Every Pesticide

This is a point the article must particularly emphasize.

It is often seen online:

“The content of the active ingredient in pesticides is permitted to vary by ±5%.”

This statement is not suitable for direct use as a universal procurement standard for all pesticides.

Specifications, active ingredients, formulations, reference standards, and regulatory requirements may vary across different products.

Even FAO/WHO specifications are not a uniform commercial standard that can be mechanically applied to all suppliers’ products in isolation from the specific product and its intended use. The FAO clearly distinguishes between different specification procedures and their respective bases of application.

Therefore, during audits, the following approach should be followed:

Approved Specification First → Actual Result Second

Rather than:

Internet Tolerance First → COA Second

If the purchasing parties have already established Acceptance Criteria in a contract or approved Specification, judgments should be made in accordance with the applicable formal requirements.

Step 8: Check Formulation-Specific Quality Parameters

Active Ingredient Content is important, but for the Finished Formulation, it is usually not the only factor.

Formulation	Common Audit Focus Areas
SC	Active Ingredient, Suspensibility, Wet Sieve, Viscosity, Storage-related Properties, etc.
EC	Active Ingredient, Emulsion Characteristics, Acidity/Alkalinity, etc.
SL	Active Ingredient, Solution Stability, pH, etc.
WP	Active Ingredient, Wettability, Suspensibility, Wet Sieve, etc.
WG / WDG	Active Ingredient, Dispersibility, Suspensibility, Wet Sieve, Granule Properties, etc.
OD	Active Ingredient, Dispersion Behavior, Wet Sieve, Viscosity, etc.
FS	Active Ingredient, Suspension Behavior, Viscosity, and applicable Seed Treatment Properties

These are audit guidelines; they do not constitute a mandatory, uniform testing checklist for all products.

Actual testing should still be conducted in accordance with the specific Product Specification and applicable Test Method.

If your procurement team needs to distinguish between quality control approaches for different formulation types, refer to Pesticide Formulation Types: A Buyer’s Guide.

Step 9: Review Missing Results Carefully

If you notice a missing result on the COA, do not immediately conclude:

“This product is non-compliant.”

You should first distinguish between two scenarios.

Missing Data

For example:

The Specification requires a certain test.

The COA does not report it.

In this case, you can only conclude:

The audit is incomplete.

Rather than:

The product failed.

The absence of a result does not necessarily mean the result is non-compliant.

Out-of-Specification Result

The other scenario is:

The specification clearly defines the acceptance range.

The COA provides the actual result.

The result clearly exceeds the applicable limits.

Only then does this constitute a genuine quality deviation, which requires further handling in accordance with the quality system and contractual agreements.

These two situations are entirely different.

Step 10: What Should You Do if a COA Result Is Out of Specification?

If a result does indeed fail to meet the approved specifications, it is not recommended to simply reduce the issue to:

“Just retest it.”

A more reasonable process is:

Identify → Verify → Investigate → Correct if Appropriate → Re-test Where Justified → Release or Reject

You can follow this logic:

Situation	Recommended Action
Missing Test Results	Request valid supplementary data
Unit Inconsistency	Confirm basis of expression
Different test methods	Confirm comparability of methods
Suspected data entry error	Verify source records
Confirm OOS	Initiate Deviation / Investigation
Investigation confirms the issue is correctable	Handle in a controlled manner according to the quality system
Retest after correction	Confirm that the retest has a technical basis
Still fails to meet requirements	Handle according to quality and contractual procedures

Most importantly:

Do not mark an unresolved deviation as “approved” just to meet a shipping deadline.

If rework or corrective action occurs, the product’s compliance with applicable requirements must ultimately be reconfirmed.

Step 11: Check Whether the COA Covers Every Batch in the Shipment

A single purchase order may not correspond to just one production batch.

For example, a purchase order may include:

• Batch A
• Batch B
• Batch C

In this case, you need to confirm:

How is each commercial batch tested and traced?

You can establish the following relationship:

Production Batch → Package Code → Carton → COA → Shipment

For example:

Batch	COA	Packaging Code	Shipment
A	COA-A	A	Included
B	COA-B	B	Included
C	COA-C	C	Included

This ensures that both parties can quickly identify the corresponding batch in the event of a subsequent quality complaint.

POMAIS’s existing export quality control process also emphasizes the traceability relationship between Production Batch, Packaging Code, Batch COA, and Shipment.

If you would like to learn more about the complete quality control process from production to container loading, please refer to How Pesticide Quality Is Controlled Before Export.

A Practical Pesticide COA Audit Example

The following fictional example illustrates the audit logic.

Note: The numbers below are used solely to demonstrate the audit method; they do not represent the statutory specifications of any actual pesticide product, nor are they actual COA data from POMAIS.

Assume the following product was purchased:

Example Product: 250 g/L SC

The approved specifications stipulate:

Test Item	Approved Specification
Active Ingredient	Specified Acceptance Range
pH	Specified Range
Suspensibility	Minimum Requirement
Wet Sieve	Specified Limit

Supplier-submitted COA:

Test Item	Specification	COA Result	Audit
Active Ingredient	Within approved range	Within range	Pass
pH	Within approved range	Within range	Pass
Suspensibility	Meets minimum	Meets minimum	Pass
Wet Sieve	Required	Not reported	Hold

This batch cannot be directly classified as:

Failed Product

Because what is missing is data, not proof that the test results are non-compliant.

A more accurate conclusion would be:

Hold — Additional information required before final shipment approval.

Review will continue once the supplier provides valid data.

This distinction is very important for procurement personnel.

Missing Result ≠ Failed Result

What Are the Most Common Red Flags in a Pesticide COA?

If you need to review a large number of supplier documents daily, prioritize checking the following issues.

Red Flag	Why It’s Worth Paying Attention To
No Batch Number	Unable to confirm which production batch the COA corresponds to
Wrong Product Name	Product identity may be inconsistent
Incorrect Formulation	May not be the same finished formulation
Missing Specification Version	Cannot confirm which standard was used for testing
Required Test Missing	Audit cannot be fully completed
Only “PASS” Is Shown	Cannot directly verify actual results
Unit Is Different	Direct comparison may not be possible
Test Method Is Missing	Comparability of results needs to be confirmed
COA Date Is Unclear	Cannot determine data correspondence
Sample COA Used for Bulk Batch	Cannot automatically verify the commercial batch
Different Batch on Carton	Traceability must be reconfirmed
Conflicting Documents	Technical document consistency must be verified

However, please note:

A “Red Flag” does not automatically equate to “Fraud.”

For example, if a COA does not include a batch number, it could be due to a document template issue or the supplier providing an incorrect version.

A professional procurement process should be:

Identify the Issue → Ask for Evidence → Verify → Make the Decision

Rather than:

See a Difference → Immediately Accuse the Supplier

This approach is more in line with true B2B quality management.

How Should You Decide: Pass, Hold, or Reject?

To help procurement personnel make quick decisions, three simple statuses can be used.

Status	Applicable Scenarios	Recommended Action
Pass	All applicable requirements have been verified and met	Proceed to the next step
Hold	Critical data is missing or unresolved issues exist	Do not release for now
Non-Conforming	Reliable data proves non-compliance with applicable requirements	Should not be released directly as a conforming batch

There is another important distinction here:

“Hold” is not the same as “Reject.”

If a required result is missing from the COA, you may need to submit supplementary documentation.

If the results fall outside the specification, a formal deviation investigation may be required.

Therefore, procurement personnel should not categorize all issues solely as “Acceptable” or “Rejected.”

In actual business operations, adding a Hold status can significantly reduce unnecessary disputes.

Should Buyers Request Independent Testing Before Shipment?

Not every shipment requires third-party testing.

The decision to arrange independent testing should be based on the risk associated with the order.

The following situations warrant closer consideration:

• First Order with a New Supplier
• High-Value Shipment
• Registration-Linked Product
• Government or Tender Supply
• Previous Quality Dispute
• Critical Product Specification
• Buyer Contract Requires Independent Verification

Third-party testing can cover:

• Sampling
• Active Ingredient Analysis
• Relevant Physical Parameters
• Packaging Inspection
• Quantity Verification
• Shipment Verification

However, it is important to clarify:

Independent testing serves as an additional layer of verification; it is not a substitute for the supplier’s standard QC responsibilities.

Similarly, a single passing third-party test result does not imply that all future batches from the supplier will automatically pass.

How Does the COA Audit Fit Into the Full Export Process?

The COA audit is not the entire export quality control process.

It is more like one of the key checkpoints.

The complete process can be understood as:

Product Specification

↓

Sample Approval

↓

Commercial Production

↓

Finished Batch QC

↓

Batch COA

↓

Packaging & Batch Verification

↓

Document Review

↓

Shipment Release

Therefore, if you rely solely on a single COA to evaluate the entire order, you may easily overlook:

• Incorrect Packaging
• Incorrect Label
• Incorrect Batch Coding
• Incorrect Quantity
• Document Mismatch
• Unresolved Quality Deviation

POMAIS’s existing export quality control process already links these steps together.

For procurement projects requiring a more comprehensive technical documentation system, you may also refer to Pesticide Technical Documents: What Buyers Should Request from a Supplier.

Pre-Shipment Pesticide Specification vs. COA Checklist

If you need to apply the information in this article directly to your procurement work, you can use the checklist below.

Audit Item	Buyer Check
Product Identity	Are the Active Ingredient, Concentration, and Formulation consistent?
Specification	Is the correct approved version being used?
Specification Revision	Have the Revision and Effective Date been confirmed?
Batch Number	Does the COA correspond to the actual commercial batch?
Production Date	Is traceability ensured?
Test Items	Are all items required by the Specification covered?
Test Methods	Are the test methods clearly defined and comparable?
Units	Are units such as g/L, g/kg, and % consistent or have they been correctly converted?
Active Ingredient	Do the actual results meet the applicable acceptance criteria?
Physical Properties	Do the applicable formulation-specific parameters meet requirements?
Relevant Impurities	If applicable, have the relevant audits been completed?
Missing Data	Are there any unresolved data gaps?
OOS Result	Are there any results outside the specification?
Packaging	Is the packaging consistent with the approved requirements?
Batch Coding	Do the labels, packaging, cartons, and COA match?
Shipment	Do all shipped batches have clear quality justification?
Deviations	Are there any unresolved quality issues?
Final Decision	Pass, Hold, or Non-Conforming?

The true value of this table isn’t to make buyers fill out yet another form.

Its value lies in transforming “I think this COA is fine” into:

What I checked, what the basis was, which items have passed, and which items still need confirmation.

What Should Buyers Ask the Supplier Before Shipment?

If you want to improve the efficiency of communication with suppliers, it’s not recommended to simply send:

“Please send the COA.”

Instead, you can ask directly:

Which approved product specification was used for this batch?

What is the production batch number?

Does this COA represent the actual batch prepared for shipment?

Which test methods were used for the reported results?

Are all required specification parameters included?

Are there any unresolved quality deviations?

If the shipment contains multiple batches, can you provide the corresponding COA for each batch?

These questions demonstrate a higher level of professionalism than simply asking for “the COA.”

Because what you really need is:

Traceable Quality Evidence

not just a PDF file.

How POMAIS Handles Specification and Batch Quality Discussions

POMAIS works with pesticide importers, distributors, registration companies, and crop-protection brands that need commercial products to meet defined product requirements.

For a sourcing project, the technical discussion can begin with:

• Active Ingredient
• Concentration
• Formulation
• Destination Country
• Product Specification
• Packaging
• Expected Quantity
• Registration Status
• Required Technical Documents

Depending on the product and project, the documentation package may include the Product Specification, COA, TDS, SDS/MSDS, batch-related information, and other applicable technical or registration-support documents.

The important point is not simply how many documents a supplier can send.

The more useful question is whether:

the product identity is clear, the specification has been agreed upon, the batch is traceable, and the COA can be evaluated against the correct acceptance criteria.

You can also review the current POMAIS pesticide product portfolio when comparing available active ingredients and formulations for your market.

For an actual sourcing project, buyers can provide the active ingredient, concentration, formulation, destination country, packaging requirements, and expected order quantity. This allows the technical and commercial requirements to be clarified before bulk production begins.

Frequently Asked Questions

Is a COA Enough to Approve a Pesticide Shipment?

No.

A COA provides batch-specific test information, but it should be reviewed against the applicable Product Specification and linked to the actual shipment batch.

Packaging, batch identity, labeling, and other commercial requirements may also require separate verification.

What Is the Difference Between a Pesticide Specification and a COA?

The Product Specification defines the standards the product is expected to meet.

The COA reports the actual results obtained from a particular sample or production batch.

The COA becomes much more useful when its results can be compared directly with the approved Specification.

Should the COA Include the Batch Number?

For batch-level quality verification, a clear batch or lot reference is highly important because it allows the buyer to connect the COA with the actual commercial goods.

Can I Use a Sample COA for a Bulk Shipment?

Not automatically.

A sample COA describes the sample that was tested. It should not automatically be treated as evidence that a later commercial production batch meets the same requirements.

The commercial batch must be evaluated in accordance with the approved Product Specification and appropriate batch-level quality control procedures.

What If One Required Test Result Is Missing From the COA?

Do not automatically classify the product as non-conforming.

First determine whether the test is required for the batch and whether the missing information can be legitimately provided or verified.

Until the issue is resolved, the shipment may need to remain on hold.

What If the COA Result Is Outside the Specification?

Treat it as a quality deviation requiring appropriate investigation.

Do not simply adjust the acceptance limit to make the result pass.

Depending on the situation, the result may need to be verified, the cause investigated, and corrective action or additional testing considered in accordance with the applicable quality system.

Does Every Pesticide Use the Same COA Parameters?

No.

The applicable parameters depend on the active ingredient, formulation, product specification, regulatory context, and intended use.

An SC, EC, WP, WDG, or FS product may have different physical-quality requirements.

Is There a Universal ±5% Rule for Pesticide COA Acceptance?

No.

Buyers should not apply a single universal tolerance to every pesticide.

Acceptance requirements should be derived from the applicable product specification, registration requirements, recognized technical references, and agreed-upon commercial criteria.

Should Buyers Request Third-Party Testing for Every Shipment?

Not necessarily.

Independent testing can be valuable for high-risk or high-value projects, first orders, registration-linked products, tenders, or situations where the buyer requires additional verification.

The appropriate scope should be determined based on risk.

Does a Passing COA Prove That a Pesticide Can Be Imported?

No.

Product quality and regulatory authorization are separate issues.

The buyer must still confirm destination-market registration, import requirements, labeling, packaging, and other applicable regulatory requirements.

Can a Single COA Cover Multiple Production Batches?

This should not be automatically assumed.

If a shipment contains multiple batches, the buyer should confirm how each batch is tested and how the relevant COA records correspond to the actual goods.

Final Pre-Shipment Decision

Before approving a pesticide shipment, do not ask only:

“Did the supplier send the COA?”

Ask five more useful questions:

1. Is this the exact product we approved?

2. Is this the correct version of the specifications?

3. Does the COA correspond to the actual production batch?

4. Do the reported results meet the applicable acceptance criteria using appropriate methods?

5. Are there any unresolved quality, traceability, or documentation issues?

If the answers are clear, the COA becomes useful evidence in the shipment-release process.

If one of the critical answers is unclear, the right decision is often Hold and verify, not immediate approval and not immediate rejection.

For international pesticide procurement, that small difference can prevent a technical document issue from escalating into a shipment dispute.

The goal of a COA audit is not to collect more documents. It is to establish a clear, traceable connection between the approved specification, the actual batch, the measured results, and the product being shipped.