The most expensive testing mistake a manufacturer can make is building the testing program after the product is already in production. By that point, the formulation is locked, the packaging is printed, and the launch date is set. If testing reveals a problem — a contaminant, a potency shortfall, a stability failure — the options are limited and costly.
A testing program built before launch, designed around the product’s specific regulatory and quality requirements, is a different animal entirely. It gives you time to identify and fix problems, validate your methods, and build the documentation infrastructure you’ll need for regulatory compliance and quality defense. Here’s how to build one.
Before you write a single specification or contact a single laboratory, you need to know which regulations apply to your product. This sounds obvious, but the answer isn’t always straightforward. A supplement with a structure/function claim is regulated under 21 CFR Part 111. A product that crosses into drug territory — even inadvertently, through a disease claim — falls under a different regulatory framework entirely. A cosmetic with certain active ingredients may be subject to OTC drug monograph requirements.
The regulatory framework determines your testing obligations. Under 21 CFR Part 111, dietary supplement manufacturers must test for identity, purity, strength, and composition. Under 21 CFR Part 117 (food), the requirements are different. Under FDA’s Modernization of Cosmetics Regulation Act (MoCRA) implementation, cosmetic manufacturers face new safety substantiation requirements that are still being defined.
Get clarity on the regulatory framework before you design the testing program. If you’re uncertain, consult a regulatory expert before proceeding. The cost of that consultation is trivial compared to the cost of building a testing program against the wrong regulatory standard.
Specifications define what you’re testing against. They should be developed before you select test methods, not after. A specification answers the question: “What does this product need to be?” The test method answers: “How do we verify it is what it needs to be?”
For a finished dietary supplement, specifications typically cover:
Specifications should be based on safety data, regulatory requirements, and label claims — not on what a particular lab can test. If your specification says “lead ≤ 10 ppm” because that’s what the lab’s standard panel reports, you’ve built your specification around the lab’s capabilities rather than around safety and regulatory requirements. USP <232> and FDA guidance documents provide reference points for elemental impurity limits; use those as your starting point.
Once specifications are defined, map each specification element to a test method. This mapping becomes the core of your testing program document. For each specification element, you need:
Some specification elements can be verified through certificate review from a qualified supplier rather than direct testing — but only if you’ve established a qualified supplier program with documented evidence of the supplier’s testing reliability. Under 21 CFR Part 111, this requires more than just receiving a COA; it requires documented supplier qualification.
With a test map in hand, you can now select laboratories based on what you actually need. This is more efficient than the common approach of picking a lab first and then asking what they can test.
For each test on your map, identify laboratories that hold ISO 17025 accreditation for that specific test and matrix. Verify accreditation scope directly through A2LA, NVLAP, or PJLA. For FDA-regulated products, confirm the lab has experience with your product category and understands the documentation requirements.
If your testing program requires multiple test types — nutritional analysis, microbiology, heavy metals, pesticides — you may need more than one laboratory. Most manufacturers work with 2–3 primary testing labs, each with specific expertise. Managing multiple lab relationships adds complexity, but it’s often better than relying on a single lab that does everything adequately but nothing exceptionally.
Method validation — or at minimum, method verification for published methods — should happen before you start release testing. A method that works well for one matrix may perform differently in yours. High-fat products can interfere with certain microbial methods. Botanical matrices can create interferences in HPLC potency assays. Encapsulation materials can affect dissolution testing.
Work with your laboratory to confirm that the methods you’ve selected perform reliably in your specific product matrix. For published methods (USP, AOAC), this is typically a verification exercise — confirming the method performs within the published parameters in your matrix. For novel methods or unusual matrices, more extensive validation may be required.
Document the method verification or validation results. This documentation becomes part of your quality system and may be requested during an FDA inspection.
Stability testing is often treated as an afterthought — something to start after launch. That’s a mistake. Stability data supports your expiration date, and without it, your expiration date is an estimate rather than a supported claim.
A stability protocol should be designed before launch and initiated at the same time as the first production batch. ICH Q1A(R2) provides the international framework for stability testing; FDA’s guidance documents for specific product categories provide additional direction. For dietary supplements, there’s no single mandatory stability protocol, but FDA expects manufacturers to have a basis for their expiration dates, and stability data is the most defensible basis.
At minimum, a stability program for a new dietary supplement should include accelerated stability testing (40°C/75% RH for 6 months) and long-term stability testing (25°C/60% RH for the full shelf life period). The specific protocol depends on the product form, packaging, and intended storage conditions.
Before releasing a new product, confirm:
Building a testing program this way takes more time upfront. It also means you launch with confidence rather than hope. At Aurora TIC, we’ve helped manufacturers across product categories build testing programs that hold up under FDA scrutiny and scale as product lines grow. The framework above is the starting point — the specifics will depend on your product, your regulatory context, and your quality system maturity.