How to Set Pesticide Product Specifications Before Supplier Approval

Approving a pesticide supplier should not begin with price, a sample, or a generic product name.

It should begin with a clear answer to one question:

What exactly must this product meet before we consider it acceptable?

For pesticide importers, distributors, registration companies, and private-label brands, a product specification creates that standard.

It connects supplier selection with sample approval, commercial production, batch testing, and future repeat orders.

A stronger procurement sequence is:

Product Requirement → Agreed Specification → Sample Testing → Supplier Approval → Bulk Production → Batch QC → COA

The key principle is simple:

Approve the specification before approving the supplier.

Why Set the Specification Before Approving the Supplier?

A quotation such as:

Azoxystrobin 250 g/L SC

does not fully define the commercial product.

Two suppliers may offer the same active ingredient, concentration, and formulation code while using different:

• Technical material sources
• Formulation systems
• Physical-quality targets
• Impurity profiles
• Storage-performance standards
• Test methods
• Internal QC requirements

If the buyer approves the supplier first and discusses quality later, the commercial relationship begins with an unclear acceptance standard.

That creates problems when:

• The sample differs from future production
• Buyer and supplier laboratories report different results
• One party uses tighter limits than the other
• A production batch falls outside the buyer’s expectations
• Registration documents no longer match the commercial product

A written specification gives both sides the same technical reference.

For supplier comparisons, see how to compare pesticide suppliers beyond price.

Start With the Exact Product Identity

Before setting individual quality parameters, define the product itself.

A basic product identity should normally include:

Item	Example
Active ingredient	Azoxystrobin
Nominal concentration	250 g/L
Formulation	SC
Commercial product identity	Finished formulation
Manufacturing/source reference	Where relevant
Destination market	Defined country/registration market
Registration relationship	Confirm where applicable

This first step sounds obvious, but document mismatches frequently begin here.

For example:

250 g/L SC

and

25% WP

are not interchangeable products simply because they contain the same active ingredient.

The formulation changes:

• Physical properties
• Testing requirements
• Packaging
• Application behavior
• Registration identity

The specification should therefore describe the exact commercial formulation being purchased.

Which Quality Parameters Should Be Included?

A pesticide product specification should contain the parameters needed to define acceptable commercial quality.

The exact list depends on the active ingredient, formulation, registration, and intended market.

Active Ingredient Content

The specification should define the nominal active ingredient content and the applicable acceptance range.

The tolerance should come from an appropriate technical basis, such as:

• Registered product requirements
• Applicable recognized specifications
• Validated internal standards
• Mutually agreed commercial requirements

Do not create a universal percentage tolerance and apply it to every pesticide.

Relevant Impurities

For technical materials and certain formulated products, relevant impurities may need to be controlled.

A technical material specification that shows only:

Active ingredient: 97%

may still be incomplete if important impurity limits are applicable.

Impurity requirements should be based on the relevant product/source and regulatory context.

Formulation-Specific Physical Properties

Finished formulations need physical-quality parameters that reflect how the formulation is designed to behave.

A good SC specification does not look the same as a good EC, WP, or WDG specification.

Storage-Related Requirements

Where applicable, specifications may also include parameters associated with:

• Accelerated storage
• Low-temperature stability
• Persistent separation
• Caking
• Redispersibility
• Other formulation-specific stability behavior

The objective is not to create the longest specification possible.

It is to define the parameters that meaningfully protect the product’s registered and commercial quality.

Which Parameters Change by Formulation Type?

Different pesticide formulations require different quality-control priorities.

Formulation	Typical Specification Areas
TC	Active ingredient content, relevant impurities, moisture or other source-specific requirements
SC	Active ingredient, appearance, pH where applicable, suspensibility, wet sieve, viscosity or pourability, storage behavior
EC	Active ingredient, appearance, emulsion characteristics, acidity or water where relevant
WP	Active ingredient, wettability, suspensibility, wet sieve, moisture, powder condition
WG / WDG	Active ingredient, dispersibility, suspensibility, wet sieve, dustiness, attrition or granule integrity, moisture
SL	Active ingredient, appearance, solution stability, pH or acidity where applicable
OD	Active ingredient, dispersion behavior, wet sieve, viscosity and storage-related properties
FS	Active ingredient, suspension behavior, viscosity and relevant seed-treatment formulation properties

These are typical specification areas, not universal mandatory limits.

A particular product may require:

• More parameters
• Fewer parameters
• Different methods
• Different acceptance ranges

The correct specification must match the exact formulation.

For a broader overview, see our pesticide formulation types buyer guide.

How Should Buyers Set Acceptance Limits?

A specification parameter becomes useful only when the buyer can determine whether a result passes or fails.

Weak specification wording includes:

• “Good suspensibility”
• “Normal pH”
• “Stable emulsion”
• “Fine powder”
• “No serious sediment”

These descriptions are subjective.

A stronger specification defines:

Parameter → Test Method → Acceptance Requirement

For example:

Parameter	Test Method	Acceptance
Active ingredient	Agreed analytical method	Defined acceptable range
Suspensibility	Agreed physical method	Defined minimum requirement
pH	Agreed method	Defined range
Wet sieve	Agreed method	Defined maximum or minimum as applicable

The purpose is not to create unnecessarily tight limits.

The purpose is to make the specification measurable and repeatable.

Why Must the Test Method Be Defined?

A number without a test method can still create disputes.

Two laboratories may test the same sample and obtain different results because they used different:

• Water quality
• Temperature
• Conditioning
• Sample preparation
• Analytical procedures
• Method versions
• Calculation methods

This is particularly relevant for formulation properties such as:

• Suspensibility
• Wettability
• Emulsion stability
• Dispersibility
• Wet sieve
• Foam
• Flowability

Where appropriate, buyer and supplier can agree on:

• CIPAC methods
• Validated manufacturer methods
• Registered analytical methods
• Other accepted laboratory procedures

For important acceptance parameters, the method should be clear enough that both parties understand how compliance will be assessed.

A specification is stronger when it tells the laboratory not only:

what to test

but also:

how the result should be generated.

FAO/WHO Specification vs Commercial Purchase Specification

FAO/WHO pesticide specifications can provide important technical references, but buyers should understand what they represent.

They should not automatically be copied into every supplier contract without confirming applicability.

A useful distinction is:

FAO/WHO or Other Recognized Reference Specification

Provides an established technical quality framework for specific pesticide products or sources under the relevant specification system.

Registered Product Requirement

Defines the product identity and quality requirements accepted under a particular registration.

Commercial Purchase Specification

Defines the quality standard the buyer and supplier agree to use for sample approval, production, and commercial acceptance.

These documents may overlap, but they are not automatically identical.

A buyer should not assume that:

“This active ingredient has an FAO specification, therefore every manufacturer’s product is automatically covered by it.”

The specification used for procurement should match the actual commercial and regulatory situation.

Specification vs TDS vs COA: What Is the Difference?

These documents are closely related but serve different purposes.

Product Specification

Defines:

What the product must meet.

TDS

Describes:

What technical product is being offered.

COA

Reports:

What was actually measured in the sample or batch.

That relationship can be summarized as:

Specification = Acceptance Standard

TDS = Product Technical Profile

COA = Actual Test Results

A COA is therefore most useful when its results can be compared directly with an approved specification.

For a detailed document comparison, see COA vs TDS vs SDS for pesticides.

You can also review our broader guide to pesticide technical documents.

Should Buyers Use the Tightest Possible Specification?

No.

A tighter specification is not automatically a better specification.

Over-specification can create:

• Unnecessary batch rejection
• Higher manufacturing cost
• Supplier disputes
• Testing complexity
• Requirements with little practical quality value
• Limits that commercial-scale production cannot consistently maintain

The objective should be:

strict enough to protect product identity and commercial quality, but technically justified and realistically measurable.

For example, a buyer should not add a physical property simply because another pesticide includes it.

The parameter should have a real technical reason to be controlled.

Likewise, do not automatically convert every “typical value” in a TDS into a contractual acceptance limit.

A typical technical value and a purchase specification serve different purposes.

Test the Specification Before Supplier Approval

Once the specification has been agreed, test a representative sample against it.

The correct sequence is:

Agreed Specification

↓

Representative Sample

↓

Laboratory Testing

↓

Compare Results With Acceptance Limits

↓

Sample Approval

↓

Supplier Technical Approval

A sample should not simply be approved because:

“It looks good.”

The stronger conclusion is:

The sample complies with the agreed product specification.

This also creates a technical bridge to future commercial production.

For a complete workflow, see pesticide sample testing before a bulk order.

Can the Supplier Meet the Specification at Commercial Scale?

This is one of the most important questions in supplier approval.

A laboratory or pilot sample may meet a specification.

But commercial sourcing requires the supplier to produce:

• 1 tonne
• 5 tonnes
• 20 tonnes
• Repeat orders

with comparable quality.

Supplier approval should therefore evaluate more than the first sample.

Ask whether normal production can consistently control:

• Active ingredient content
• Formulation properties
• Raw-material variability
• Processing conditions
• Batch QC
• Storage
• Packaging compatibility

A useful commercial specification must be achievable consistently at normal manufacturing scale.

An unusually perfect development sample has limited value if future production varies significantly from batch to batch.

Separate Product and Packaging Specifications

For private-label pesticide projects, the formulation specification and packaging specification should be linked but kept separate.

Product Specification

Covers the pesticide itself:

• Active ingredient
• Concentration
• Formulation properties
• Quality parameters
• Test methods
• Acceptance limits

Packaging Specification

May cover:

• Bottle or bag material
• Container size
• Cap
• Inner seal
• Label
• Printing
• Batch coding
• Carton
• Pallet configuration

A pesticide can meet every laboratory requirement and still create commercial problems if the package leaks or fails during transport.

For this reason:

product approval and packaging approval should be treated as two separate checkpoints.

What Changes Should Trigger Re-Approval?

Supplier approval should not mean that the product can change indefinitely without review.

Material changes may require technical reassessment.

Examples can include:

• Technical active ingredient source change
• Manufacturing site change
• Significant formulation change
• Co-formulant system change
• Major specification revision
• Relevant analytical-method change
• Packaging-material change
• Registration-related change

The exact re-approval requirement depends on the product and market.

For registration projects in particular, source and formulation changes may have regulatory consequences.

A good supplier relationship should therefore include appropriate change control.

Where a change could affect the agreed product identity, quality, or regulatory project, it should be communicated before routine commercial supply.

Use Specification Version Control

A specification should be identifiable.

Useful document-control information can include:

• Product name
• Formulation
• Specification number
• Revision/version
• Effective date
• Approval reference

This avoids future disputes such as:

“Which specification was this order produced against?”

For long-term repeat orders, version control becomes increasingly important.

The commercial order should refer to the correct approved specification version whenever practical.

Pesticide Product Specification Template

A buyer can use the following structure as a starting point.

Specification Field	What the Buyer Should Define
Product identity	Active ingredient + concentration + formulation
Product/source reference	Where technically or regulatorily relevant
Appearance	Clear measurable description
Active ingredient content	Nominal value + applicable acceptance range
Relevant impurities	Where applicable
pH / acidity	Where technically relevant
Formulation physical properties	According to SC, WP, WG, EC, SL, OD, FS, etc.
Storage-related requirements	Where applicable
Test method	CIPAC, validated, registered or otherwise agreed method
Acceptance limit	Clear pass/fail requirement
COA parameters	Which results should appear on batch documentation
Revision	Version / date
Additional notes	Product-specific requirements

This template should be adapted to the actual pesticide.

Do not mechanically apply every row to every formulation.

Weak Specification vs Better Specification

Consider a simplified example.

Weak Specification

Imidacloprid 200 g/L SL

• Active ingredient: 200 g/L
• Appearance: Good
• pH: Normal
• Stability: Good

The problem is that:

• “Good” is subjective
• “Normal” is undefined
• Test methods are missing
• Acceptance limits are unclear

Better Specification Structure

Imidacloprid 200 g/L SL

Define:

• Exact product identity
• Active ingredient acceptance range
• Relevant appearance requirement
• pH requirement where applicable
• Solution/stability parameters where relevant
• Test methods
• Clear acceptance criteria
• Specification revision

The second format can support:

• Sample testing
• Supplier approval
• Batch QC
• Dispute resolution
• Repeat purchasing

That is the practical purpose of a commercial specification.

Supplier Approval Checklist

Before approving a pesticide supplier, confirm:

Check	Buyer Question
Product identity	Is the exact AI, concentration and formulation defined?
Regulatory fit	Does the specification match the intended registered/commercial product?
Active ingredient	Is an appropriate acceptance range defined?
Relevant impurities	Are applicable impurity limits addressed?
Physical properties	Are the correct formulation-specific parameters included?
Test methods	Can buyer and supplier produce comparable results?
Acceptance limits	Is pass/fail measurable?
Sample	Has a representative sample been tested?
Commercial scale	Can normal production consistently meet the specification?
COA	Will future batch results be reported against the agreed parameters?
Change control	Will material product/source changes be communicated?
Version control	Is the approved specification clearly identified?
Packaging	Has a separate packaging specification been approved where required?

Supplier approval should come after these technical questions are sufficiently resolved.

Frequently Asked Questions

Is a Pesticide Specification the Same as a COA?

No.

The specification defines the required quality standard.

The COA reports actual test results for a particular sample or production batch.

Who Should Set the Pesticide Product Specification?

The buyer and supplier should agree on it.

The final requirements should be informed by the applicable registration, recognized technical references, validated methods, and commercial quality needs.

Can I Copy an FAO/WHO Specification for Any Supplier?

Not automatically.

FAO/WHO specifications can be valuable references, but applicability to a particular manufacturing source and product must be confirmed.

Should Every Formulation Use the Same Specification?

No.

SC, EC, WP, WG/WDG, SL, OD, FS and other formulations have different physical-quality characteristics and therefore different specification needs.

Does a Tighter Specification Always Mean Better Quality?

No.

Limits should be technically justified, measurable, and realistic for consistent commercial production.

Overly restrictive specifications can create unnecessary cost and rejection without improving practical product quality.

Should the Test Method Be Included in the Specification?

For important measurable parameters, it is highly useful to define or reference the agreed test method where applicable.

This improves comparability between supplier and buyer laboratories.

Can a Sample Pass While the Supplier Still Fails Approval?

Yes.

A passing sample does not automatically prove the supplier can maintain commercial-scale batch consistency, documentation, source stability, and supply reliability.

Does Meeting the Specification Prove Field Efficacy?

No.

Product specification confirms defined chemical and physical quality characteristics.

Biological efficacy depends on separate factors such as target organism, crop, use rate, timing, local conditions, and registered claims.

Should Packaging Be Included in the Product Specification?

It is usually clearer to keep the formulation specification and packaging specification separate but linked within the same purchasing project.

Can the Specification Change After Supplier Approval?

Yes, but material changes should be evaluated through an appropriate change-control process, especially when they affect registered product identity, manufacturing source, formulation, or commercial quality.

Set the Standard Before Approving the Supplier

Pesticide supplier approval is stronger when both parties know exactly what product is being approved.

The right sequence is:

Define → Agree → Test → Approve → Produce → Verify

At POMAIS, commercial sourcing projects can be discussed around the exact active ingredient, concentration, formulation, destination market, product specification, packaging, and expected order quantity before bulk production.

This gives the buyer a clear technical basis for:

• Supplier comparison
• Sample approval
• Batch QC
• COA review
• Repeat-order consistency

The objective is not to create unnecessary specification complexity.

It is to make sure that the product approved before the first order is the same quality standard used for future commercial production.