Buyer guide

COA and TDS Request Checklist for Botanical Ingredients

Use this checklist before asking for documentation so your QA, procurement, and product teams can review the same ingredient path without avoidable back-and-forth.

Request COA/TDS Review quality path
Quality document review setting for botanical ingredient COA and TDS requests

What to include in the first document request

A useful COA or TDS request starts with the exact ingredient identity, target specification, intended application, and review stage. Asking for "all documents" without context often slows the process because the right file depends on product grade, lot path, and whether the team is screening, sampling, or preparing an RFQ.

  • Product name, botanical name, and part used.
  • Target marker, assay, extract ratio, or grade language.
  • Intended use: supplement, food, beverage, cosmetic, or other B2B application.
  • Whether the request supports screening, sample approval, or purchase planning.
  • Any internal QA limits your team must check before sample review.

How COA and TDS usually differ

A COA is typically lot-oriented and helps reviewers understand test results for a specific material path. A TDS is typically product-oriented and summarizes specification, identity, usage, handling, and technical reference details. Buyers often need both, but they answer different questions.

  • Use COA review to check lot-specific analytical values.
  • Use TDS review to compare product-level specification fit.
  • Ask whether additional testing files are available for the review stage.
  • Confirm whether documents are sample-specific, stock-specific, or representative.
Procurement note

Best first message for COA/TDS routing

Send the product name, desired specification, estimated annual or first-order volume, application, destination country, and the internal question your QA team is trying to answer. That gives the supplier enough context to route the correct COA/TDS path instead of sending generic files that may not match the buyer's decision.

Screening stage

Ask for the TDS, target specification, available grade options, and whether representative COA review can be routed once the product appears to fit. This keeps early screening light while still giving QA enough structure to compare suppliers.

Sample stage

Ask whether the COA path can align with the sample or material path under review. Also confirm sample quantity, packing format, shipping destination, and whether the sample is for formulation, analytical review, or commercial evaluation.

First PO stage

Ask how documents will be handled for the purchase order, which quality attributes need confirmation before release, and whether the supplier needs any buyer-side specification sheet before preparing final commercial details.

Ready to request documentation?

Include the product page URL, target grade, and whether your team needs screening documents or sample-review files.

Request COA/TDS

Copy-ready COA/TDS request template

Hello Essence Source team, we are reviewing [ingredient name] for [supplement / beverage / food / cosmetic / other B2B application]. Our target specification is [marker, ratio, or grade], with an estimated first order of [quantity] and possible annual volume of [quantity]. Please route the appropriate TDS and available COA path for [screening / sample review / RFQ / first PO planning]. Destination is [city, state/country], and our QA team is especially checking [identity, assay, microbiology, heavy metals, carrier, solubility, or other limit].

Common mistakes that slow document review

  • Requesting every document before naming the grade or application.
  • Comparing COAs from different specifications as if they are the same material.
  • Asking for lot-level files before confirming whether the product is a fit.
  • Leaving out internal QA limits that determine whether the product can move forward.
  • Separating document review from sample, quote, and destination details.
Related paths

Connect documentation review to sourcing decisions

COA and TDS review works best when it is connected to the product page, quality workflow, and RFQ checklist instead of handled as a separate file request.

Quality Review PathHow documentation supports supplier screening and sample review Bulk RFQ ChecklistTurn document review into a cleaner quote request Product CatalogFind the ingredient page before sending a document request Contact Essence SourceSend the product, specification, quantity, and QA question