What buyers should know first
A COA/TDS request should name the product, target grade, application, review stage, document type, and QA priorities. Buyers should clarify whether they need a TDS, representative COA, sample COA, or lot-specific COA.
Buyer Template
COA/TDS Request Email Template
A good COA/TDS request email should tell the supplier what document is needed, which product or grade is under review, and whether the buyer is screening, sampling, qualifying a supplier, or preparing a first purchase. Many delays happen because buyers ask for a COA without explaining whether a representative COA, sample-specific COA, or lot-specific COA is required. This template helps procurement, QA, and product development teams request the right technical files for botanical extracts, mushroom extracts, fruit powders, and other botanical ingredients without turning the first message into a vague document request.
What to do next
Use this note to define the review stage, product grade, application, document need, and commercial assumptions before asking suppliers for price, COA/TDS, or samples. That keeps procurement, QA, and product development aligned around the same material path.
Start with the review stage, not only the ingredient name
A good COA/TDS request email should tell the supplier what document is needed, which product or grade is under review, and whether the buyer is screening, sampling, qualifying a supplier, or preparing a first purchase. Many delays happen because buyers ask for a COA without explaining whether a representative COA, sample-specific COA, or lot-specific COA is required. This template helps procurement, QA, and product development teams request the right technical files for botanical extracts, mushroom extracts, fruit powders, and other botanical ingredients without turning the first message into a vague document request.
For U.S. B2B buyers, the first useful supplier response usually depends on five details: target specification, intended application, sample or document stage, expected quantity, and destination. When those details are missing, suppliers can only respond with broad availability language, and procurement may end up comparing offers that are not actually equivalent.
Compare the grade before comparing price
| Representative COA | Use for early screening when the buyer wants to understand typical test categories, specification limits, and document format before sampling. |
|---|---|
| Sample COA | Use when QA is reviewing the material connected to a specific sample path or formulation test. |
| Lot-specific COA | Use when a purchase order, shipment, or supplier qualification step requires the document tied to a defined batch or lot. |
| TDS | Use to understand product identity, target specification, physical profile, carrier, storage, handling, and application fit before deeper QA review. |
| Request context | State product, grade, application, review stage, destination, and internal QA limits so the supplier can route useful files. |
Application fit
This template works for supplement brands, contract manufacturers, functional beverage teams, food formulation groups, personal-care developers, and distributors comparing botanical ingredient suppliers. It is most useful when the buyer needs COA/TDS files before sample approval, supplier qualification, or first commercial order planning.
A supplier can give a better recommendation when the buyer names the dosage form or finished product format. Capsules, tablets, gummies, stick packs, beverages, powders, foods, and personal-care applications can put different pressure on solubility, color, taste, carrier, microbiology, and document review.
When the application is still uncertain, the buyer should say so directly. A good supplier response can then separate what is already known from what needs sample work, formula review, or QA confirmation. This is especially useful for teams that are comparing several botanical ingredients for the same launch window.
Quality documents to request
Ask for the TDS first when the product or grade still needs screening. Ask for a representative COA when QA wants to preview analytical categories. Ask for a sample-specific or lot-specific COA only when the material path is specific enough to support that request. If the team has internal limits for microbiology, heavy metals, residual solvents, pesticides, allergens, or country-of-origin review, include those details in the first message.
The cleanest request names whether the file is needed for screening, sample approval, internal QA comparison, first purchase planning, or ongoing supplier qualification. That context helps avoid sending a file that does not answer the buyer's actual question.
For early screening, ask whether a TDS and representative COA path can be discussed. For sample or first purchase review, ask how documents connect to the material path under evaluation. This distinction keeps procurement, QA, and product development from treating unrelated files as if they represent the same grade.
Use the same criteria for every supplier reply
| Identity and grade | Confirm the exact Botanical Extracts name, botanical or material identity, target grade, assay or ratio language, and any carrier or excipient expectations. |
|---|---|
| Application fit | State the dosage form or product format so the supplier can flag solubility, sensory, color, taste, carrier, handling, or compliance concerns before sampling. |
| Document path | Ask whether TDS, representative COA, sample COA, and lot-specific COA support are available for the review stage under discussion. |
| Commercial assumptions | Compare sample quantity, MOQ, lead time, replenishment path, destination, packing, and whether U.S. warehouse support is relevant. |
| Supplier response quality | Prefer replies that connect specification, documents, sample route, MOQ, lead time, and missing buyer details in one answer. |
Details to include in the first message
A concise RFQ brief helps suppliers answer with usable technical and commercial context instead of a generic price line. Buyers can adapt this structure before requesting COA/TDS, samples, or first purchase support.
- Product: Botanical Extracts
- Target specification or grade: [fill in marker, ratio, extract type, or custom requirement]
- Application: [capsule, tablet, powder blend, beverage, functional food, cosmetic, or other]
- Review stage: [early screening, sample request, QA review, first purchase, or replenishment]
- Documents requested: COA/TDS first; note any internal QA limits or additional files needed
- Quantity and timing: [sample quantity, first order estimate, annual forecast if known, target date]
- Destination and packing: [ship-to region, packing preference, warehouse or direct-shipment need]
Supplier response benchmark
A strong supplier reply should not only quote a price. It should confirm the grade being discussed, explain the available specification path, identify the next document or sample step, and ask for any missing details that affect commercial fit. If the reply does not connect specification, sample, documents, MOQ, and lead time, the buyer may need another clarification round before the offer is usable.
How to use this note
Use this page before sending the first message and again when comparing supplier replies. The goal is not to overcomplicate the RFQ. The goal is to give the supplier enough context to answer like a technical sourcing partner: which grade fits, which documents can be routed, what sample path makes sense, and what commercial assumptions should be confirmed before a purchase order.
Copy-ready template
Use this text before contacting suppliers
Adapt the bracketed fields before sending. The goal is to give procurement, QA, and product development enough context to receive a useful first reply.
COA/TDS request email
Short document request
Risk control
Sourcing risks to resolve before sample review
Most delays happen because the buyer and supplier are not discussing the same grade, document stage, or application. Resolve these points early so samples and quotes arrive with usable context.
Common risks
- Requesting a lot-specific COA before a lot or shipment path exists.
- Using a representative COA as final approval evidence for a future shipment.
- Leaving out target specification, application, or review stage.
- Asking for documents without naming internal QA limits or test priorities.
- Treating document availability as a substitute for QA review of method language and limits.
Questions to ask supplier
- Is the buyer asking for a TDS, representative COA, sample COA, or lot-specific COA?
- Which product name, grade, active marker, extract ratio, or carrier should the document match?
- Is the request for screening, sample approval, supplier onboarding, or first purchase review?
- Which microbiology, heavy metals, residual solvent, pesticide, allergen, or origin questions matter?
- Should the supplier also clarify sample availability, MOQ, lead time, and packing?
RFQ details to include
- Product name and target specification.
- Application and dosage form.
- Sample quantity, first order volume, and annual estimate if known.
- Destination, packing preference, and target timing.
- COA/TDS or additional QA files needed for the review stage.
Related products and tools
Continue the buyer review
Use these related pages to connect the insight note to product specifications, QA documents, RFQ preparation, and application planning.
Quality and document review pathContinue the sourcing review with this related page.
COA vs TDS buyer guideContinue the sourcing review with this related page.
COA/TDS request checklistContinue the sourcing review with this related page.
Request COA/TDS from Essence SourceContinue the sourcing review with this related page.
Back to Buyer GuidesBrowse more notes in this insight track.
Regulatory and research sources used for this guide
These external references are included to support the sourcing and compliance framework in this article. They do not replace legal, regulatory, or finished-product claim review, but they give procurement and QA teams a more reliable starting point than supplier sales language alone.
- 21 CFR Part 111 - The eCFR text provides the dietary supplement CGMP structure relevant to specifications and quality control review.
- 21 CFR 111.70 specifications - This section supports the template's emphasis on established specifications before document approval.
- FDA dietary supplement labeling guide - FDA guidance helps buyers keep technical document review separate from finished-product labeling decisions.
- FTC Health Products Compliance Guidance - FTC guidance supports avoiding unsupported health-product claims in supplier and finished-product language.