Extract ratio and standardized extract are two different ways suppliers describe botanical ingredients, and buyers should not compare them as if they mean the same thing. An extract ratio such as 4:1 or 10:1 usually describes a relationship between starting plant material and finished extract, but it does not by itself confirm a level of active or marker compound. A standardized extract is usually positioned around a defined marker, assay language, or specification target. For procurement and QA teams, the practical question is not which term sounds stronger; it is whether the supplier can explain identity, marker language, method, carrier, COA/TDS path, sample relevance, and application fit before the quote is treated as comparable.
An extract ratio describes concentration language, while a standardized extract should identify a target marker or specification. Buyers should compare the TDS, COA path, marker method, carrier, and application fit before treating two quotes as equivalent.
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.
Extract ratio and standardized extract are two different ways suppliers describe botanical ingredients, and buyers should not compare them as if they mean the same thing. An extract ratio such as 4:1 or 10:1 usually describes a relationship between starting plant material and finished extract, but it does not by itself confirm a level of active or marker compound. A standardized extract is usually positioned around a defined marker, assay language, or specification target. For procurement and QA teams, the practical question is not which term sounds stronger; it is whether the supplier can explain identity, marker language, method, carrier, COA/TDS path, sample relevance, and application fit before the quote is treated as comparable.
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.
| Extract ratio | Ratio language can describe input-to-output concentration, but buyers should ask what plant part, extraction path, carrier, and document support sit behind the ratio. |
|---|---|
| Standardized extract | Standardized language should name the target marker or specification, method language when available, and whether the COA/TDS can support that grade. |
| Assay marker | A marker such as chlorogenic acids, withanolides, OPC, polysaccharides, or beta-glucans should be reviewed with method and application context, not only a percentage. |
| Comparable quote | Two offers are comparable only when identity, grade type, application, document stage, sample path, MOQ, lead time, and destination are aligned. |
Ratio extracts may fit projects where the buyer mainly needs a broad botanical identity, traditional extract positioning, or a cost-sensitive formulation path. Standardized extracts may fit programs that need tighter marker language, QA comparison, label positioning, or repeatability expectations. Capsules and tablets often need cleaner COA review. Powders, beverages, gummies, and functional foods may also need taste, color, solubility, carrier, and processing discussion before the grade is accepted.
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.
Ask for the TDS first to understand whether the supplier is describing a ratio extract, a standardized marker grade, or a custom specification. Then request the COA path that matches the review stage. A representative COA may help early screening, but a sample or lot review should clarify whether the document belongs to the actual material path being considered. Buyers should also ask whether the assay method, carrier, plant part, country of origin, microbiology, heavy metals, and residual solvent expectations can be discussed.
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.
| 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. |
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.
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.
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.
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.
Use these related pages to connect the insight note to product specifications, QA documents, RFQ preparation, and application planning.
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.