出荷前に農薬仕様書を分析証明書（COA）と照合して監査する方法

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.

注意事項： COA自体は仕様書ではありません。

A Specification answers the question:

「この製品はどのような基準を満たさなければならないのか？」

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.”

本当に問うべき質問は次のとおりです。

“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 供給業者の承認前に農薬製品仕様書を作成する方法. 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.

ドキュメント	主な目的	Typically Corresponds to
製品仕様書	Defines the quality requirements the product must meet	製品
COA	実際のテスト結果を報告する	Specific Batch
TDS	Describes the product’s technical characteristics	製品
SDS	Provides information on hazards, safe handling, and storage	Product / Formulation
バッチレコード	Records information related to the manufacturing process	バッチ
登録データ	対象市場での登録をサポートします	Product / Market

These can be understood as:

Specification = Standard

COA = Actual Result

具体的な例を挙げますと、以下の通りです。

テスト項目	製品仕様	COA結果
有効成分	Specified Acceptance Range	実際のテスト値
pH	指定範囲	実際のテスト値
感受性	最小要件	実際のテスト値
湿式ふるい	指定制限	実際のテスト値

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、TDS、SDSの比較.

Step 1: Confirm the Exact Product Identity

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

まず、以下を確認してください。

• 有効成分
• 集中
• 製剤
• 製品名または製品コード
• Manufacturer or Source Information, where applicable
• 仕様参照

For example, if you purchased:

ラムダシハロトリン 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.

具体的な例を挙げますと、以下の通りです。

ラムダシハロトリン 25 g/L EC

(NAIST) と

ラムダシハロトリン25%WP

有効成分は同じだが、最終的な製剤は同じではない。

Different formulation types mean:

• Different physical systems
• 異なる仕様
• Different QC parameters
• 異なるパッケージ
• 異なる登録ID

したがって、 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?”

以下の点も確認してください。

このバッチではどの仕様バージョンが使用されましたか？

推奨されるチェック:

Document control items	確認すべき事項
製品名	一貫性はありますか?
製剤	一貫性はありますか?
仕様番号	一貫性はありますか?
リビジョン	Is it an approved version?
発効日	Is it still valid?
承認参照番号	追跡可能ですか？

具体的な例を挙げますと、以下の通りです。

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.

なぜなら、1年後に紛争が発生した場合、最も厄介な問題は「製品のどの部分が検査されたか」ではなく、むしろ次の点であることが多いからです。

「当時、両当事者は実際にどの基準に基づいて購入を行ったのか？」

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.

輸出用に準備されているバッチが商用バッチである場合は、COAが実際の製造バッチと一致していることを確認する必要があります。

At a minimum, check:

バッチ情報	主要な監査ポイント
バッチ番号	Does it match the actual shipment?
製造日	Is it reasonable?
試験日	Does it correspond to the testing of this batch?
製品コード	一貫性はありますか?
パッケージコーディング	Is traceability possible?
Carton / Label Code	Does it correspond to the batch?

具体的な例を挙げますと、以下の通りです。

COA：

バッチA20261001

Actual goods prepared for container loading:

バッチ番号 B20261005

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

これは必ずしも製品の品質問題を示すものではありません。

しかし、それは次のことを意味します。

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.

ステップ4：すべての必須テスト項目を仕様書と比較する

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

It is recommended to create a simple audit table:

テスト項目	承認済み仕様書	COA結果	ステータス	コメント
有効成分	Approved Range	実結果	Pass / Hold / Fail	直接比較する
外観	承認された要件	実際の観察	Pass / Hold / Fail	一貫性をチェックする
pH	Approved Range	実結果	Pass / Hold / Fail	該当する場合
感受性	承認された要件	実結果	Pass / Hold / Fail	該当する場合
湿式ふるい	Approved Limit	実結果	Pass / Hold / Fail	該当する場合
その他のパラメータ	製品固有	実結果	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.

したがって、SC COAチェックリストをすべての農薬に機械的に適用しないでください。

ステップ5：数値だけでなく、試験方法も確認する

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

仮定：

仕様要件：

Suspensibility ≥ X%

COAには以下が記載されています。

Result = Y%

簡単そうです。

But you should also ask:

How was the result measured?

次のような要因があるためです。

• サンプルの準備
• 水質
• 温度
• コンディショニング
• 分析手順
• 計算方法
• 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

単に：

パラメータ → 数値

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

これは、実際の調達において判断ミスが非常に多く発生する分野である。

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.

まず確認する必要があります：

• g/Lまたはg/kg
• w/w or w/v
• 密度が関係しているかどうか
• the basis for expressing the test results
• the notation used in the Registration Document
• 仕様書で要求されている表現方法は何ですか？

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

• acid equivalent
• 塩
• エステル
• active moiety

These expressions cannot be determined based solely on numerical values.

したがって、単位が一致しない場合は、「自分で換算値を推測する」のではなく、別の方法をとるのが最もプロフェッショナルなアプローチです。

それよりも：

まず表現の根拠を確認し、次に適切な技術変換と適合性評価を実施する。

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%.”

この記述は、すべての農薬に対する普遍的な調達基準として直接使用するには適していません。

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:

承認された仕様が先 → 実際の結果が後

のではなく：

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.

製剤	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	有効成分、濡れ性、懸濁性、湿式ふるいなど
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

これらは 監査ガイドラインであり、義務的な統一テストチェックリストを構成するものではありません。 すべての製品に適用されます。

実際の試験は、製品仕様書および該当する試験方法に従って実施する必要があります。

If your procurement team needs to distinguish between quality control approaches for different formulation types, refer to 農薬製剤の種類：購入ガイド.

Step 9: Review Missing Results Carefully

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

“This product is non-compliant.”

まず、2つのシナリオを区別する必要があります。

データがありません

具体的な例を挙げますと、以下の通りです。

仕様書では、特定の試験が要求されている。

COAはそれを報告していない。

In this case, you can only conclude:

The audit is incomplete.

のではなく：

製品は故障しました。

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

仕様外の結果

もう一つのシナリオは次のとおりです。

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.

ステップ10：COAの結果が規格外だった場合はどうすればよいですか？

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

この論理に従うことができます。

状況	推奨される行動
Missing Test Results	Request valid supplementary data
単位の不一致	Confirm basis of expression
さまざまな試験方法	方法の比較可能性を確認する
Suspected data entry error	Verify source records
在庫切れを確認する	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

最も重要なこと：

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.

ステップ11：COAが出荷品のすべてのバッチをカバーしているかどうかを確認する

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

For example, a purchase order may include:

• バッチA
• バッチB
• バッチ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

具体的な例を挙げますと、以下の通りです。

バッチ	COA	パッケージコード	出荷
A	COA-A	A	同梱
B	COA-B	B	同梱
C	COA-C	C	同梱

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 輸出前に農薬の品質管理はどのように行われるのか.

A Practical Pesticide COA Audit Example

以下 fictional example 監査ロジックを示しています。

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:

テスト項目	承認済み仕様書
有効成分	Specified Acceptance Range
pH	指定範囲
感受性	最小要件
湿式ふるい	指定制限

Supplier-submitted COA:

テスト項目	製品仕様	COA結果	監査委員会
有効成分	Within approved range	範囲内	合格
pH	Within approved range	範囲内	合格
感受性	最低限の要件を満たす	最低限の要件を満たす	合格
湿式ふるい	必須	報告されていません	ホールド

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.

赤旗	注目する価値がある理由
バッチ番号なし	Unable to confirm which production batch the COA corresponds to
商品名が間違っています	製品の同一性に一貫性がない場合があります
Incorrect Formulation	May not be the same finished formulation
Missing Specification Version	どの規格が試験に使用されたかは確認できません。
Required Test Missing	Audit cannot be fully completed
「合格」のみが表示されます	実際の結果を直接検証することはできません
Unit Is Different	Direct comparison may not be possible
テストメソッドがありません	Comparability of results needs to be confirmed
COA Date Is Unclear	Cannot determine data correspondence
バルクバッチに使用されるサンプルCOA	Cannot automatically verify the commercial batch
Different Batch on Carton	Traceability must be reconfirmed
Conflicting Documents	Technical document consistency must be verified

ただし、以下の点にご注意ください。

「危険信号」は必ずしも「詐欺」を意味するものではありません。

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

のではなく：

違いが分かったら、すぐに供給業者を非難してください。

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

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

調達担当者が迅速な意思決定を行えるよう、3つのシンプルなステータスを使用することができます。

ステータス	該当するシナリオ	推奨される行動
合格	All applicable requirements have been verified and met	Proceed to the next step
ホールド	重要なデータが欠落しているか、未解決の問題が存在する	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.”

実際のビジネス運営では、 ホールド 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
• 政府または入札による供給
• 過去の品質紛争
• Critical Product Specification
• Buyer Contract Requires Independent Verification

第三者機関によるテストでは、以下の項目が対象となります。

• サンプリング
• 有効成分分析
• Relevant Physical Parameters
• 梱包検査
• 数量検証
• 出荷確認

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:

製品仕様書

↓

サンプル承認

↓

商業生産

↓

Finished Batch QC

↓

バッチCOA

↓

Packaging & Batch Verification

↓

文書レビュー

↓

出荷リリース

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

• 不適切な梱包
• ラベルが間違っています
• Incorrect Batch Coding
• 数量が間違っています
• 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 農薬技術文書：購入者が供給業者に要求すべき事項.

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.

監査項目	購入者チェック
プロダクトアイデンティティ	Are the Active Ingredient, Concentration, and Formulation consistent?
製品仕様	Is the correct approved version being used?
Specification Revision	Have the Revision and Effective Date been confirmed?
バッチ番号	Does the COA correspond to the actual commercial batch?
製造日	Is traceability ensured?
試験項目	Are all items required by the Specification covered?
試験方法	Are the test methods clearly defined and comparable?
我が軍の部隊数	Are units such as g/L, g/kg, and % consistent or have they been correctly converted?
有効成分	Do the actual results meet the applicable acceptance criteria?
物理的特性	Do the applicable formulation-specific parameters meet requirements?
関連する不純物	If applicable, have the relevant audits been completed?
データがありません	Are there any unresolved data gaps?
OOS Result	Are there any results outside the specification?
パッケージング	Is the packaging consistent with the approved requirements?
バッチコーディング	Do the labels, packaging, cartons, and COA match?
出荷	出荷されたすべてのロットには、明確な品質上の根拠がありますか？
偏差	未解決の品質問題はありますか？
最終決定	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 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.

POMAISは仕様およびバッチ品質に関する議論をどのように処理するか

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:

• 有効成分
• 集中
• 製剤
• 仕向国
• 製品仕様書
• パッケージング
• 予想数量
• 登録状況
• 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 市場向けに利用可能な有効成分や製剤を比較する際には、これらの点を考慮する必要があります。

実際の調達プロジェクトにおいては、バイヤーは有効成分、濃度、配合、仕向国、包装要件、および予想注文数量を提供することができます。これにより、量産開始前に技術的および商業的な要件を明確にすることができます。

よくある質問

農薬の出荷承認には、分析証明書（COA）だけで十分ですか？

いいえ。

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?

自動的には行われません。

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.

COAに必要な検査結果が1つでも欠けている場合はどうなりますか？

製品を不適合品として自動的に分類しないでください。

まず、その検査が当該バッチに対して必要かどうか、そして不足している情報が正当に提供または検証可能かどうかを判断します。

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?

いいえ。

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?

いいえ。

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?

必ずしも。

独立した試験は、リスクの高いプロジェクトや高額なプロジェクト、初回注文、登録関連製品、入札、または購入者が追加の検証を必要とする状況において、非常に有益となる。

The appropriate scope should be determined based on risk.

分析証明書（COA）に合格すれば、農薬を輸入できることが証明されるのか？

いいえ。

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.

1つの分析証明書で複数の製造バッチをカバーできますか？

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 保留して確認, not immediate approval and not immediate rejection.

国際的な農薬調達においては、そのわずかな違いが、技術文書の問題が出荷紛争に発展するのを防ぐことができる。

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.