Stop Putting BHT in Supplement Facts! The Complete Excipient Compliance Guide

A U.S. brand once shipped 120,000 units of turmeric-and-biotin capsules — then recalled every bottle after its label audit flagged the same line twice. In the Supplement Facts panel, Polyvinyl Alcohol appeared as an "ingredient" with a blank amount. In the Other Ingredients section, the same polymer was correctly listed as a film coating. The FDA did not care that the formula was safe. Under 21 CFR 101.9 and 21 CFR 101.36, a declared panel row with no numeric amount is a misbranding trigger, and the coating had no business being a panel row at all.

This is not a rare horror story. It is the single most common reason compliance officers (RA Managers), formulators, and QA leads burn hours on false-positive errors — and it is almost always one of four predictable traps.

1. The Legal Boundary: Dietary Ingredients vs Functional Excipients

The first step to never confusing them again is to internalize that the FDA treats the two sides of a dietary supplement label under different legal frameworks.

1.1 Two panels, two rulebooks

21 CFR 101.4(g) — "Ingredients not present in the finished dietary supplement as dietary ingredients... shall be listed after the dietary ingredients in descending order of predominance."

21 CFR 101.36(b) — A dietary ingredient in the panel must be declared by its common or usual name and, where required, its quantitative amount by weight and its %DV.

1.2 One chemical, two identities — the classic case

• Calcium Carbonate in the panel = a source form of the dietary ingredient Calcium, declared as "Calcium (as Calcium Carbonate) 260 mg."
• Calcium Carbonate in Other Ingredients = an antacid/anti-caking excipient, listed with no amount.

• Ascorbic Acid in the panel = the source form of Vitamin C.
• Ascorbic Acid in Other Ingredients = an antioxidant preserving the blend.

The moment a compliance engine treats every ingredient as if it needs an amount, it fires a 21 CFR 101.9 false positive on the very excipients that legally must not have amounts.

2. The 4 Fatal Traps That Burn Compliance Officers

2.1 Trap #1 — Excipients leaking into the Supplement Facts panel

The most damaging trap. A filler (Maltodextrin), a disintegrant (Crospovidone), a coating (Polyvinyl Alcohol), or a color (FD&C Red No. 40 Lake) gets pulled into the panel. The software or the auditor then demands: "why is there no amount and no %DV?" — exactly the false 21 CFR 101.9 blocker described above.

21 CFR 101.9(g) — A label is misbranded if it fails to state the quantity of a food in a manner that is not misleading. Blank declared amounts inside a panel are a red flag to the agency.

2.2 Trap #2 — Missing botanical part and form (21 CFR 101.4(h))

Herbal and plant-derived ingredients have an extra legal requirement the chemical excipients do not: you must identify the plant part and, usually, the Latin binomial and the extraction form.

• ✅ Ashwagandha (Withania somnifera) Root Extract
• ✅ Ginkgo (Ginkgo biloba) Leaf Extract
• ❌ Ashwagandha Extract (no part, no latin name)
• ❌ Ginkgo (ambiguous)

21 CFR 101.4(h) — Where an ingredient is a plant or botanical, its common or usual name shall be the name of the plant part (e.g., root, leaf, seed) and the specific name of the plant.

This is also exactly where naive substring matching fails: a system that sees the string "Alcohol" or "PVA" and guesses "plant-derived" will mislabel a synthetic polymer as a botanical.

2.3 Trap #3 — Commercial nicknames instead of the official CFR name

Using vendor shorthand breaks the chain of custody an FDA reviewer expects:

A compliant label must carry the official name, not the lab's nickname.

2.4 Trap #4 — Hidden allergens in excipients

Excipients are the #1 hiding place for undeclared allergens. Soy Lecithin as a coating, wheat starch as a binder, or milk proteins as a flavor carrier all demand a Contains: declaration. Miss it and you expose sensitive consumers to real harm — and your brand to a Warning Letter.

21 CFR 101.4(g)(2) — When the source of an ingredient is a major food allergen, the specific source name must be declared (e.g., "soy lecithin").

3. From Eyeballing to Self-Healing: Building an Industrial-Grade Compliance Defense

No human — and no naive script — can reliably hold 100+ excipients, source forms, and botanical naming rules in mind across every revision. Modern label-compliance software must replace that with a four-layer architecture. Here is how ReguSift actually solves it:

3.1 Layer 1 — Physical Section Partitioning

At the extraction layer, the system physically separates two data streams before any rule engine touches them:

• Panel ingredients (with Amount / %DV) → enter the compliance rulebase with numeric non-empty validation.
• Other Ingredients / excipients (listed as text) → carry no amount_required semantics and are hard-blocked from the panel.

This is not a cosmetic layout trick — it is a structural guarantee that an excipient can never be asked for an amount.

3.2 Layer 2 — An Authoritative Excipient Taxonomy (100+)

A first-class dictionary covers the excipients that cause the most confusion: PVA (Polyvinyl Alcohol), Crospovidone, BHT / BHA / TBHQ, Lake color series, acidulants, binders, lubricants, disintegrants, and film formers. Each entry carries its canonical name, aliases used in OCR, allowed regions, and the governing citation (e.g., 21 CFR 101.4(g)). Recognition is seconds-fast and exact, including Crospovidone aliases like Kollidon CL.

3.3 Layer 3 — Positive Structural Evidence for Botanicals

Instead of substring guesses, a botanical is only classified as such when it carries positive structural evidence:

1. Latin binomial (Withania somnifera), and/or
2. A plant part token (root / leaf / seed / rhizome), and/or
3. An extraction-form token (extract / powder / standardized to).

This single rule eliminates the absurd case of classifying Polyvinyl Alcohol or BHT as a "herb" just because the name smells botanical.

3.4 Layer 4 — Propagation-Independent Compliance Exemption

Finally, the compliance validator exempts any ingredient that is fdaGroup === 'excipient' or physically in the other_ingredients region — and, as a third, propagation-independent fallback, re-checks the authoritative excipient dictionary directly. This is what drives false 21 CFR 101.9 blockers to exactly zero, even when classification metadata is lost in a data branch.

4. The RA Officer's 5-Step Self-Check Checklist

Save this checklist. It is the fastest way to catch the four traps before artwork goes to print.

1. Segment first. Is every ingredient on the correct side of the panel / Other Ingredients boundary? If it has no %DV semantics, it does not belong in the panel.
2. Name it officially. Replace every vendor nickname with the CFR-recognized name (e.g., Crospovidone, not PVP-K30; FD&C Red No. 40 Lake, not Red 40).
3. Prove the botanicals. For every plant ingredient, confirm the Latin binomial + plant part + extraction form are present (21 CFR 101.4(h)).
4. Hunt hidden allergens. Check each excipient's source — soy, wheat, milk, egg, tree nut, fish, shellfish, peanut.
5. Validate amounts only where they belong. Ensure no excipient row carries a false "missing amount" blocker, and every real panel nutrient has its amount and %DV.

FAQ

Q: Do excipients in Other Ingredients need to show a Daily Value (%DV)?

No. Under 21 CFR 101.36, only dietary ingredients declared in the Supplement Facts panel carry amounts and %DV. Excipients in the Other Ingredients section are listed by name and descending order of predominance under 21 CFR 101.4(g) — they carry no amount_required semantics, and no numeric non-empty validation applies.

Q: Can the same chemical be both a dietary ingredient and an excipient?

Yes. The legal identity depends on the label section, not the molecule. Calcium Carbonate is the source form of Calcium in the panel but an anti-caking excipient in Other Ingredients. Always classify by section context first, then by the molecule.

Q: Why does my label software throw "OCR did not extract a value" on excipients?

Because the validator is running 21 CFR 101.9 numeric checks against the full ingredient array without filtering excipients. The fix is a compliance exemption: any ingredient classified as an excipient, or physically in the other_ingredients region, must be excluded from the numeric non-empty validation — otherwise you get dozens of false Blocking Issues that are pure noise.

Q: When does a botanical require a plant part on the label?

Under 21 CFR 101.4(h), whenever the ingredient is a plant or botanical, the common or usual name must include the plant part (root, leaf, seed, etc.) and, typically, the Latin binomial and extraction form — e.g., "Withania somnifera Root Extract."

---

Don't let the four traps eat another workday. If you want to stop hand-checking 100+ excipients and physically separate your panel from your Other Ingredients section in seconds, ReguSift's authoritative excipient dictionary and section-partitioning engine do the heavy lifting — upload a PDF and catch compliance landmines before your auditor does.