Heavy metals and contaminant limits for US supplements (USP)

Behind the Prop 65 headlines sits a more fundamental question every US supplement maker has to answer: how much of a contaminant is acceptable in my product, and how do I know I am under it? Heavy metals and other contaminants are governed by a web of standards — USP, FDA expectations, state limits — and managing them starts with the data on your ingredients.

Why contaminants matter

Supplements draw on botanicals, minerals, and other natural materials that can carry contaminants — heavy metals like lead, arsenic, cadmium, and mercury, plus microbiological and other impurities. These are not added; they come with the raw materials. But the finished product still has to be safe and within accepted limits, which makes contaminant control a core part of quality.

The role of USP

The United States Pharmacopeia (USP) publishes standards widely used in the supplement industry, including limits and methods for elemental impurities such as heavy metals. While USP standards are not always mandatory for supplements in the way they are for drugs, they are an influential benchmark that manufacturers, buyers, and testing labs frequently work to.

For many manufacturers, meeting recognised USP-style limits is how they demonstrate that contaminant levels are controlled.

The overlapping web of limits

Contaminant limits for a US supplement can come from several directions at once: USP standards, FDA expectations and any applicable limits, and state requirements such as California's Prop 65 safe-harbor levels. These do not always align, and the effective limit for a product is often the strictest one that applies to where and how it is sold.

Managing this means knowing not just one limit but the set of limits relevant to the product and its markets.

Limits apply to the finished product — built from ingredients

The crucial mechanical point is that the contaminant level of a finished product is built up from its ingredients. Each raw material contributes its own contaminant load, and the finished product's level is the result of combining them at their inclusion rates. A single high-contaminant ingredient, even at a modest inclusion level, can push a product toward a limit.

This is why contaminant control is an ingredient-data exercise as much as a finished-product testing one: testing confirms the result, but the ingredient data lets you anticipate it.

Identity and testing under cGMP

Contaminant control connects to the cGMP requirement to set and verify specifications. A manufacturer establishes contaminant specifications for ingredients and finished products, and verifies them through testing. The specification says what is acceptable; the testing confirms a batch met it — and both rest on knowing the contaminant profile of what goes in.

Because contaminant standards and limits vary by source, market, and over time, confirm the current applicable limits for your specific product rather than relying on a general summary.

Tracking contaminants from the formula

The robust approach is to hold each ingredient's contaminant data in its record and roll it up across the formula, so the finished product's expected contaminant picture is visible as it is built — and can be compared against the relevant limits. When the data travels with the ingredients, choosing a cleaner source or adjusting an inclusion level becomes an informed decision rather than a post-test surprise.

The takeaway

Heavy-metal and contaminant control for US supplements runs through overlapping standards — USP, FDA, state limits — and the effective limit is usually the strictest that applies. The finished product's contaminant level is built from its ingredients, so managing it well means holding ingredient contaminant data and rolling it up against the relevant limits, with testing to confirm. Anticipation beats discovery.

Lemoniq holds contaminant data with each ingredient and rolls it up across the formula, so you can compare a product's expected contaminant levels against the relevant limits as you build it. We solve this exact problem. See how it works