The green tea / EGCG question: what an extract restriction means for your formulas

Green tea extract is a useful case study in a problem the whole industry faces: a popular botanical whose safety question lands not on the herb but on a single constituent. The EGCG dossier under EU assessment could lead to strict limits, or even a ban, on EGCG-rich extracts — and a manufacturer using green tea extract needs to know, precisely, how much EGCG each of its products delivers. That is a constituent-level question, and it exposes whether your formulas are modelled deeply enough to answer it. Here is the discipline that makes a restriction survivable.

The restriction is on the constituent, not the ingredient

A limit on EGCG is not a limit on "green tea extract" as a line item — it is a limit on a compound inside that extract, whose concentration varies by extract specification. Two green tea extracts can carry very different EGCG loads. So compliance depends on a number most formulas never record: the EGCG content of the specific extract used, multiplied by the amount in the product. A formula that stores green tea extract as a single opaque ingredient cannot answer the regulator's question; a formula that stores the extract's key constituents can.

Modelling extracts by their actives

Serious botanical formulation records an extract's standardized constituents as data: the marker compounds, their percentages, the extract ratio. For green tea that means the catechin and EGCG content; for other botanicals it is their own actives. With constituents stored on the ingredient, the delivered amount of any compound per serving is a calculation, not a guess — and a constituent-level limit becomes a number you can check across every product instantly.

Finding your exposure across the catalog

When the limit lands, the manufacturer needs the list: every product containing green tea extract, with the EGCG delivered per daily dose, sorted against the new ceiling. Products under the line are fine; products over it need reformulation — a lower-EGCG extract specification, a reduced dose, or a different botanical. A system that computes delivered constituent per serving across all formulas produces that triage list in one pass.

Reformulating to a constituent target

Bringing a product under an EGCG ceiling usually means switching to an extract with a lower standardized EGCG content, which changes the whole profile — the marker compounds the claim relies on, the cost, possibly the efficacy story. Handling the switch as a tracked version, with the new extract's full constituent profile flowing into the panel and claims, keeps the reformulation honest rather than a quiet substitution that breaks a claim no one rechecked.

The principle generalizes

Green tea is the example of the week; the pattern is permanent. Berberine, fennel, hydroxycitric acid and other botanicals move through assessment, and each decision can land on a constituent. The manufacturers who treat botanical extracts as constituent-bearing data — not opaque line items — are ready for whichever botanical is next.

Because botanical assessments and any resulting limits are still developing, confirm the current EU requirements for your specific extracts and products rather than relying on a general summary.

Where Lemoniq fits

Lemoniq models botanical extracts by their standardized constituents — markers, percentages, extract ratios — so delivered EGCG or any other compound per serving is a live calculation. Finding which products exceed a constituent limit is one query, and reformulating to a new extract specification runs as a tracked, documented version.

The takeaway

A botanical restriction that targets a constituent can only be managed by formulas that record constituents. Model your extracts by their actives, and the EGCG question — and the next one like it — becomes a query and a controlled reformulation instead of a catalog-wide unknown.

Lemoniq stores extract constituents as data, making constituent-level restrictions a query and a tracked reformulation. We solve this exact problem. See how it works