Last Updated: August 17th, 20262761 words13.8 min read

Pesticide Technical Documents: What Buyers Should Request from a Supplier

When evaluating a pesticide supplier, asking “Do you have the documents?” is not enough. Buyers need to know which document describes the product, which one defines quality, which one belongs to a specific batch, and which information is required for registration in the destination market.

For pesticide importers, distributors, registration companies, and private-label brands, the technical file usually starts with the product specification, Certificate of Analysis (COA), Safety Data Sheet (SDS/MSDS), and Technical Data Sheet (TDS). Depending on the project, buyers may also need label information, stability data, batch traceability, manufacturing information, and registration-support materials.

These documents are not interchangeable. Each answers a different procurement question.

What Technical Documents Should a Pesticide Supplier Provide?

The exact document package depends on the pesticide, formulation, destination country, registration status, and purchasing stage.

The following table provides a practical starting point.

Document Main Purpose Typical Level
Product Specification Defines the required quality standard Product
Certificate of Analysis (COA) Reports actual test results Batch
Safety Data Sheet (SDS/MSDS) Describes hazards, handling and safety information Product/Formulation
Technical Data Sheet (TDS) Summarizes the technical product profile Product
Label Information Supports market and regulatory review Product/Market
Stability Information Supports assessment of product behavior during storage Product/Formulation
Batch Identification Supports traceability Batch
Registration-Support Information Supports regulatory evaluation Product/Market

The most important point for buyers is that all relevant technical documents should refer to the same active ingredient, concentration, formulation and product identity.

Commercial documents such as the invoice, packing list, certificate of origin and bill of lading are also important for international trade, but they serve a different purpose from the technical product file.

Start with the Product Specification

Many buyers request a COA first.

In practice, the product specification should come first, because it defines what the supplier is expected to manufacture.

The specification establishes the acceptance criteria for the product.

For example, a suspension concentrate may include parameters such as:

  • Active ingredient content
  • Appearance
  • pH
  • Suspensibility
  • Wet-sieve performance
  • Viscosity
  • Storage-related physical properties

An EC, WP, WDG or OD will normally require a different set of formulation-specific parameters.

This is why one generic pesticide specification cannot be applied to every formulation type.

Why the Specification Comes Before the COA

The relationship is straightforward:

Product Specification → Production → Batch Testing → COA

The specification defines the target.

The COA reports the actual results obtained for a production batch.

Without an agreed specification, a buyer may receive a COA showing numbers without knowing whether those results meet the required commercial standard.

For new sourcing projects, confirm the specification before approving the sample or placing the first bulk order.

What Should a Pesticide COA Prove?

A Certificate of Analysis is one of the most important documents in pesticide procurement.

However, a COA should do more than display the active ingredient percentage.

A useful COA helps the buyer verify whether a specific batch meets the agreed product specification.

Specification and Result Are Not the Same Thing

For example:

Test Item Specification Result
Active ingredient 39.0–41.0% 40.2%
pH 5.0–8.0 6.6
Suspensibility ≥ 90% 95%

The specification shows the acceptable range or requirement.

The result shows what was actually measured.

These two columns serve different purposes.

Why the Batch Number Matters

A COA should be connected to the production batch being evaluated or shipped.

Useful information may include:

  • Product name
  • Active ingredient
  • Concentration
  • Formulation
  • Batch number
  • Manufacturing or test date
  • Test items
  • Specification limits
  • Actual results
  • QC approval

A generic COA used repeatedly without a clear batch relationship provides less value for shipment verification.

When working with a new supplier, ask:

Does this COA represent the actual production batch, or is it only a sample document?

That question can prevent misunderstandings later.

What Does an SDS Tell a Pesticide Buyer?

An SDS, also called MSDS in many commercial discussions, focuses on hazards, handling, storage and safety information.

It is not a quality certificate.

A typical SDS may address areas such as:

  • Product and supplier identification
  • Hazard identification
  • Composition information
  • First-aid measures
  • Fire-fighting measures
  • Accidental release
  • Handling and storage
  • Exposure control
  • Physical and chemical properties
  • Stability and reactivity
  • Toxicological information
  • Ecological information
  • Disposal
  • Transport-related information

For buyers, one of the most important checks is whether the SDS actually matches the formulation being supplied.

An SDS for one concentration or formulation should not automatically be treated as suitable for a different product.

SDS Does Not Replace the COA

The distinction is important:

COA = batch quality

SDS = safety and hazard communication

A supplier providing an SDS has not yet demonstrated that the commercial batch meets your required specification.

You still need the appropriate quality documents.

What Should a Pesticide TDS Contain?

A Technical Data Sheet provides a concise technical overview of the product.

Depending on the supplier and project, it may include:

  • Product name
  • Active ingredient
  • Concentration
  • Formulation
  • Physical description
  • Key technical characteristics
  • General storage information
  • Packaging information
  • Product positioning
  • Other relevant technical notes

The TDS is generally a product-level document, rather than a certificate created separately for each production batch.

TDS Is Not the Same as a COA

A TDS tells the buyer:

What product is this?

A COA tells the buyer:

What were the test results for this batch?

That difference should remain clear when reviewing supplier files.

The product specification, TDS and COA should also remain technically consistent with each other.

If one document identifies a product as 50% WP and another identifies the same product as 50% WDG, the technical file needs clarification before the order proceeds.

Why Should Buyers Review Label Information Early?

For private-label pesticide projects, label work should begin before commercial production—not after the product has already been packed.

Label review may involve information such as:

  • Active ingredient
  • Concentration
  • Formulation
  • Product name
  • Net contents
  • Batch information
  • Manufacturer or importer information
  • Hazard statements
  • Storage instructions
  • Registered uses
  • Directions for use
  • Required legal or regulatory text

The supplier can support artwork preparation and technical product information, but the importer or local registration partner should confirm the final regulatory content required in the destination market.

POMAIS supports custom pesticide packaging and multilingual label development for international distributors and private-label brands.

A practical workflow is:

Product Confirmation → Technical Information → Label Draft → Local Review → Artwork Approval → Printing → Production

This reduces the risk of discovering label problems after packaging materials have already been printed.

When Should Buyers Ask for Stability Information?

Stability information becomes particularly important when a product will be:

  • Registered in a new market
  • Stored for long periods
  • Shipped through hot or cold climates
  • Packed in a new container
  • Manufactured in a technically sensitive formulation
  • Evaluated for repeat commercial supply

Different formulations can have different stability concerns.

For example:

An SC may need attention to suspension stability, viscosity, sedimentation and redispersibility.

An EC may require attention to solubility, crystallization and emulsion behavior.

A WDG may require evaluation of granule integrity, dispersibility and moisture sensitivity.

An OD may require evaluation of dispersion stability and storage behavior.

The amount and type of stability documentation required depends on the product and project.

Buyers should therefore ask a more precise question:

What stability information is available for this exact formulation and specification?

rather than simply asking:

Do you have a stability test?

Which Pesticide Documents Should Be Batch-Specific?

Not every technical document needs to be recreated for every batch.

Understanding the difference between product-level and batch-level documentation makes procurement more efficient.

Document Typical Relationship
Product Specification Product-level
TDS Product-level
SDS/MSDS Product/formulation-level
COA Batch-level
Batch identification Batch-level
QC release information Batch-level
Stability information Product/formulation-level
Registration dossier/data Product/market-level

The COA is especially important because it should normally reflect the actual batch being supplied.

By contrast, a TDS or SDS does not usually change simply because the next batch has a different batch number, unless the underlying product formulation or relevant information has changed.

Why This Matters for Repeat Orders

For repeat procurement, buyers do not need to restart the entire technical review every time.

A practical approach is to retain approved product-level documents and review the new batch-specific information for each shipment.

This can include:

  • New batch number
  • New COA
  • Production date
  • Packaging confirmation
  • Shipment traceability

This makes repeat-order quality management much more efficient.

What Does Pesticide Registration Support Actually Include?

“Registration support” is one of the most misunderstood phrases in international pesticide sourcing.

A supplier may have useful technical information and supporting documents, but that does not mean one document package will automatically satisfy every country.

Registration requirements can vary by:

  • Destination country
  • Product type
  • Active ingredient
  • Concentration
  • Formulation
  • Intended use
  • Crops
  • Target pests, weeds or diseases
  • Registration route
  • Local regulatory authority

Depending on the project, registration-related discussions may involve:

  • Product identity
  • Composition
  • Product specification
  • Manufacturing information
  • Analytical information
  • Physical and chemical data
  • Stability information
  • Safety data
  • Existing studies
  • Label information
  • Other regulatory materials

Supplier Support Is Not the Same as Regulatory Approval

Buyers should distinguish between two questions:

What can the supplier provide?

and:

What does my regulatory authority require?

These are not the same question.

A supplier may have extensive technical files while the destination authority still requires additional studies, local data or specific documentation.

For this reason, avoid relying on statements such as:

“We provide a complete registration package for every country.”

A more professional process is:

  1. Confirm the destination country.
  2. Confirm the exact active ingredient, concentration and formulation.
  3. Obtain the local registration requirements.
  4. Compare those requirements with available supplier data.
  5. Identify any gaps before starting the registration project.

This approach reduces regulatory uncertainty.

How Should Buyers Check Technical Document Consistency?

A professional technical file should tell one consistent product story.

The following information should be checked across relevant documents:

Technical Field What to Check
Active ingredient Same chemical identity
Concentration Same declared content
Formulation Same formulation code
Product name Consistent where applicable
Manufacturer/source Clearly identified
Specification Same approved quality requirements
Batch number Correct on batch-related files
Packaging Consistent where included
Label information Matches the intended product

For example, imagine the supplier provides:

TDS: Chlorothalonil 75% WP
COA: Chlorothalonil 75% WDG
Label: Chlorothalonil 720 g/L SC

Even though the active ingredient is the same, these are three different commercial products.

The documents should not be approved until the supplier clarifies which product is actually being supplied.

Technical consistency is more important than simply receiving a large number of files.

When Should Buyers Request Each Document?

Requesting documents at the correct procurement stage can save time for both buyer and supplier.

Procurement Stage Recommended Technical Review
Initial supplier screening Basic specification, TDS, SDS
Product comparison Detailed product specification
Sample evaluation Sample COA, specification, TDS
Registration planning Registration-support information required for the market
Private-label development Product data and label information
Order confirmation Final approved specification
Before shipment Actual batch COA and relevant batch information
Repeat order New batch COA and consistency check

This process also prevents one common mistake: requesting a complete regulatory dossier before the buyer has even confirmed the exact formulation or destination market.

Document depth should increase as the project becomes more serious.

Red Flags in Pesticide Supplier Documents

Technical documents can reveal supplier risks before a commercial problem occurs.

The following issues deserve further investigation.

The COA Has No Clear Batch Identity

A batch certificate should be traceable to the product or batch it represents.

The Formulation Changes Between Documents

If the TDS states SC but the COA states EC, the supplier should explain the inconsistency before approval.

Concentration Is Not Consistent

A 200 g/L product and a 20% product should not automatically be assumed identical without technical confirmation.

One Generic SDS Is Used for Different Products

Different active ingredients, concentrations or formulations may require different safety information.

The Supplier Cannot Explain the Product Specification

A supplier should know which acceptance criteria are used for the commercial product.

The COA Only Shows Active Ingredient Content

For many formulated products, active ingredient content alone may not provide enough information to evaluate physical formulation quality.

“Registration Support” Is Identical for Every Country

Destination-market requirements can differ significantly.

Generic promises should be verified against the actual registration requirements.

Product-Level and Batch-Level Documents Are Confused

The supplier should understand why a TDS and a batch COA serve different purposes.

Technical Documents Arrive Only After Production

Important product specifications, registration information and label requirements should be reviewed before production wherever possible.

This reduces the risk of producing goods that do not match the buyer’s intended market.

Technical Document Review Checklist

Before approving a new pesticide supplier or product, use the following review framework.

Check Buyer Question
Product identity Do all documents describe the same active ingredient, concentration and formulation?
Specification Is the commercial quality standard clearly defined?
COA Does it report actual results against the agreed specification?
Batch traceability Is the COA connected to the actual production batch?
SDS Does the safety document match the exact product supplied?
TDS Does it accurately describe the commercial formulation?
Stability Is suitable information available when required?
Label Has technical and regulatory content been checked early?
Registration What can the supplier provide for this specific market?
Consistency Do all technical files match one another?
Repeat orders Can new batches be compared with the approved product standard?

A supplier does not become reliable simply because it sends many PDF files.

The real test is whether the documentation is product-specific, technically consistent, traceable and useful for the buyer’s actual procurement or registration decision.

How POMAIS Supports Technical Documentation

POMAIS works with pesticide importers, distributors, registration companies and private-label brands sourcing crop protection products for international markets.

Our technical and commercial support can include product specifications, COA, SDS/MSDS, TDS, packaging information, label support and project-specific registration materials where available and applicable.

We recommend confirming the exact product before building the document package.

That means identifying:

  • Active ingredient
  • Concentration
  • Formulation
  • Destination country
  • Registration status
  • Packaging
  • Estimated order volume
  • Required technical documents

This allows the technical file to be aligned with the actual product rather than sending unrelated generic documents.

Buyers evaluating a new supplier can also review our guide on how to choose a pesticide manufacturer in China and our pesticide production and quality-control process before moving to sample or bulk-order evaluation.

Frequently Asked Questions

What Documents Should a Pesticide Supplier Provide Before Sample Approval?

At the sample stage, buyers usually benefit from reviewing the basic product specification, TDS, SDS and a representative COA.

Additional documents depend on the product and destination market.

The objective is to confirm what product is being evaluated and which specification the sample represents.

Is a COA the Same as a Product Specification?

No.

The product specification defines the required quality limits.

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

A useful COA should therefore be interpreted against the approved specification.

What Is the Difference Between COA, SDS and TDS?

A COA focuses on product or batch test results.

An SDS focuses on hazards, safety, handling and storage.

A TDS provides a technical overview of the product.

They serve different functions and should not be treated as substitutes for one another.

Does Every Pesticide Batch Need a New COA?

For commercial quality verification, each production batch should normally be associated with its own batch-specific testing information.

The exact documentation practice depends on the supplier and project, but buyers should be able to connect the COA to the batch being supplied.

Does Every Batch Need a New SDS?

Normally, an SDS is associated with the product or formulation rather than being recreated solely because a new batch number is produced.

However, the SDS should remain current and correctly match the product being supplied.

Can a Supplier Provide a Complete Pesticide Registration Dossier?

A supplier may have substantial technical and registration-support data, but whether it is “complete” depends on the destination country and regulatory pathway.

Buyers should first obtain the local authority’s requirements and then compare them with the information available from the supplier.

When Should I Request Registration Documents?

Begin registration discussions after confirming the destination country and the exact active ingredient, concentration and formulation.

This avoids reviewing documents for a product that does not fit the intended registration route.

What Should I Do If Supplier Documents Do Not Match?

Do not assume the difference is only a formatting error.

Ask the supplier to confirm the correct active ingredient, concentration, formulation, specification and batch identity before approving the sample, label or commercial order.

Need Technical Documents for a Pesticide Sourcing Project?

Send POMAIS your:

  • Active ingredient
  • Concentration
  • Formulation
  • Destination country
  • Registration status
  • Required packaging
  • Estimated quantity
  • Document checklist from your technical or regulatory team

We can review the product requirements and confirm which technical documents and registration-support materials are available before you move to sample evaluation or commercial production.

Discuss your pesticide sourcing and documentation requirements with POMAIS.

Share to: