Lubinpla

How to write a letter of equivalency for a chemical product

Summary

Writing a product equivalence statement takes 5 steps: name both products, define the scope, cite the evidence, list untested conditions and drop unsupported wording. A letter of equivalency can claim only the level its evidence reaches, such as the same specification, matched results in named tests, or approval for the same end use, and nothing beyond it.

  • Under a US TSCA test rule, an equivalence applicant submits each substance's chemical identity, "the basis for the applicant's belief" that it is equivalent, and any other data the rule names (US EPA, 40 CFR 790.85, 2026).

  • FAO treats two pesticides as equivalent when the impurity and toxicological profiles and the physical and chemical properties of technical materials from different manufacturers are similar (FAO, 2026).

  • A Canadian certificate of equivalency is valid until December 31 in the second year after issue and ceases if the basis for equivalence no longer applies (Pest Control Products Regulations, SOR/2006-124, s. 39(2), 2026).

  • Under the FAO/WHO pesticide specifications manual, a revision of a reference specification "may render the hitherto equivalent products non-equivalent" (FAO and WHO, 2025).

What do you need before writing a product equivalence statement?

You need four things before drafting: the exact identity of both products, the requirement the equivalence is measured against, the evidence for each claim, and a record of what was not tested. Without all four, the letter states a conclusion nobody can check.

  • Product identity: trade name, product code, maker, manufacturing site and document revision, for both the reference product and the offered product. Regulatory equivalence regimes ask for the same. Canada's equivalency review asks for the name and address of the place where each active ingredient and each formulation is manufactured (Pest Control Products Regulations, SOR/2006-124, s. 38(5), 2026).

  • The requirement: the specification and its edition, the list of test methods, or the end use that defines what "equivalent" means for this customer.

  • Evidence: certificates of analysis, test reports, technical data sheets and safety data sheets for both products, each with its date.

  • Untested conditions: temperatures, materials, contaminants or service conditions that no evidence covers.

Decide who will read the letter before you draft it. A purchasing team at the customer, a quality engineer and a manufacturer's technical team need different detail, so the reader you pick changes what goes in. The trade-offs are set out in how to write a technical report for a customer and a manufacturer.

What scope can an equivalence statement cover: specification, test results or end use?

An equivalence statement can cover one of three scopes: the same specification, matched results in named tests, or approval for the same end use. Each scope supports different wording. Together they form a ladder, where each step up needs evidence the step below does not, and a letter should name the highest level its evidence reaches, not more.

The ladder below sets which wording a draft letter of equivalency may use at each level of evidence.

Scope level

Evidence it needs

Wording it supports

Wording to avoid

Same specification

Both products meet the named specification edition, shown in current CoAs or test reports

"Both products meet the requirements of [specification, edition]"

"Equivalent in all respects"

Matched results in named tests

Side-by-side results by the same methods, with conditions

"In tests A, B and C, results were within the stated limits of the reference product"

"Performs the same in service"

Approved for the same end use

A listing or approval by the body that grants it, for that use

"Both products are listed by [approver] for [use], as of [date]"

"Approved" without naming the approver or the use

Most commercial letters belong on the first row. Both products meet the same specification edition, and that says nothing about properties the specification does not control. Regulatory equivalence, such as FAO's pesticide procedure, compares more than a specification: impurity profile, toxicological profile and physical and chemical properties (FAO, 2026).

Matched test results need the same methods, the same conditions and current samples of both products. A reference value copied from an old technical data sheet is not a side-by-side test. Approval for the same end use is the strongest claim and the hardest to support, because only the approving body can grant it.

Which evidence supports a product equivalence claim?

An equivalence claim rests on data for both products, by the same methods, tied to the requirement the letter names: certificates of analysis against the specification, side-by-side test reports, and a composition comparison where the customer's question depends on composition. Data on one product only, or by different methods, supports a description, not an equivalence.

Regulators set the pattern. Under a US TSCA test rule, the applicant submits the chemical identity of its substance, which "may include all characteristics and properties of the applicant's substance or mixture, such as boiling point, melting point, chemical analysis (including identification and amount of impurities), additives, spectral data" (US EPA, 40 CFR 790.85(a), 2026). The same section asks for "the basis for the applicant's belief" that the substance is equivalent, and may ask for a description of the manufacturing process (US EPA, 40 CFR 790.85(b) and (c), 2026).

In a commercial letter, list each claim with the document behind it: claim, document, date, method. A typical value on a technical data sheet supports a typical value, not a guaranteed limit. A certificate of analysis supports the lot it covers. If the evidence is a single test run, say so in the claim's own sentence.

Which words should a product equivalence statement avoid?

Avoid any word that claims more than the evidence shows: "equivalent in all respects", "identical", "drop-in replacement", "same performance", "fully compatible", and "approved" without a named approver. Each one implies tests and approvals the letter usually does not have.

In regulated settings, "equivalent" names a defined test, not a general likeness. The FAO and WHO manual on pesticide specifications states: "Equivalence is determined in a two-tiered approach" (FAO and WHO, 2025). Under its first tier, technical grade active ingredients from different manufacturers or processes are deemed equivalent if they meet the existing specification and pass assessments of the manufacturing process, the impurity profile and mutagenicity testing; a second tier adds toxicology data where the first is uncertain (FAO and WHO, 2025). A commercial letter that uses the bare word can be read as claiming a comparison that broad, so every word should match a document.

Safer replacements state the scope and the evidence in the same sentence:

  • Instead of "equivalent", write "meets the same requirements of [specification, edition], shown in [document, date]".

  • Instead of "drop-in replacement", write "met the reference product's limits in [named tests]; not tested in [conditions]".

  • Instead of "fully compatible", name the materials tested and the method.

A claim that your product equals a named competitor product needs the same evidence for the competitor product. Without it, describe only your own product against the specification.

How do you record conditions that were not tested in an equivalence statement?

Record untested conditions as a separate, named list in the letter: each condition, why it matters to the customer's use, and what evidence would close it. Silence about a condition reads as a claim that it was covered.

Write the list in the customer's terms, not the lab's. Useful entries name the variable and its range:

  • Temperatures outside the tested range, for example above the highest test temperature in the report.

  • Materials not tested, such as seal elastomers, coatings or metals the customer uses.

  • Mixing with the reference product during a changeover, if no compatibility test was run.

  • Contamination, dilution or service age, if all tests used fresh product.

  • Regulatory status in the customer's jurisdiction, if only one jurisdiction was checked.

End each entry with the action that would close it: a named test, a field trial with acceptance criteria, or a question to the maker.

Canada's equivalency rules show why the list matters: a certificate of equivalency ceases to be valid once "the basis on which the foreign product and the registered pest control product were determined to be equivalent no longer applies" (Pest Control Products Regulations, SOR/2006-124, s. 39(2), 2026). An equivalence covers only its basis.

When does a product equivalence statement stop being valid?

A product equivalence statement stops being valid when its basis changes: a change in either product's composition, manufacturing site or process, a new edition of the cited specification, or the end of the date the letter states. A letter without a validity line is read as permanent, which no evidence supports.

Regulated equivalence sets explicit limits. In Canada, a certificate of equivalency for a pest control product "is valid until December 31 in the second year after the year in which it is issued", and ceases earlier if the basis for equivalence no longer applies or the registered product's registration is cancelled or expires and its sale and use are no longer authorized (Pest Control Products Regulations, SOR/2006-124, s. 39(2), 2026). Under a US TSCA test rule, the equivalence data can include a description of the manufacturing process (US EPA, 40 CFR 790.85(c), 2026), which ties the finding to that process.

In a commercial letter, write the validity as one line with three parts: the composition and site the evidence covers, the specification edition, and a review date. The FAO and WHO manual notes that amending a clause of a reference specification may make hitherto equivalent products non-equivalent (FAO and WHO, 2025), so a new specification edition calls for a fresh check.

Ask the maker of each product to tell you about formulation or site changes. After any change, reissue the letter rather than extending the old one.

How do you check a letter of equivalency before it is signed?

Before a letter of equivalency is signed, test the draft against five rows: both products identified, scope stated, each claim tied to evidence, untested conditions listed, and validity tied to composition and production site. A letter that passes all five says only what its documents show.

The table below decides whether a draft letter of equivalency is ready to sign.

Check

Pass

Fail and what to do

Both products identified

Name, code, maker, site and document revision for both

Trade name only: add code, maker and site

Scope stated

One scope level named: specification, tests or end use

Scope implied by "equivalent": name the level

Each claim tied to evidence

Every claim lists a document, date and method

Claim without a document: remove it or get the data

Untested conditions listed

Named list with the action that would close each

No list: write one before signing

Validity tied to composition and site

Composition, site, specification edition and review date stated, as regulators tie validity to the basis (SOR/2006-124, s. 39(2), 2026)

No validity line: add it

The evidence row is the one most often failed. A claim without a dated document behind it should come out of the letter, not be softened.

Have someone who did not write the letter run the check, reading each claim against its document. A writer tends to read a claim the way it was meant, not the way it is worded. Lubinpla drafts an equivalence statement only from the evidence already concluded in the case, adds no new judgment of its own, and keeps open items in the document only where that document type allows them.

Frequently asked questions

Is a letter of equivalency the same as a declaration of conformity?

No. A supplier's declaration of conformity attests that an object meets specified requirements. ISO/IEC 17050-1:2004 sets general requirements for such declarations, for products, processes, management systems, persons or bodies (ISO/IEC 17050-1:2004, scope). A letter of equivalency compares two products, so it also needs evidence on the reference product.

Can a distributor sign a product equivalence statement?

A distributor can sign one, but only for what the documents in hand show. The signer should hold the evidence for each claim, name the maker's documents it relies on, and state what was not tested. If only the maker holds composition or site data, the letter should cite the maker's statement or say that point is unconfirmed.

Does an equivalence statement carry over an OEM or regulatory approval?

No. An approval belongs to the body that grants it and to the product it lists. An equivalence statement can report that both products are listed for a use, with the list and its date, but it cannot extend an approval to an unlisted product.

Related posts