Testing & Stability
Support performance with the right evidence

Testing should answer the questions that matter for the product, the formula and the intended communication. Plan it early so evidence can support development and launch decisions.

Formula stability

Microbiology

Packaging compatibility

Performance evidence

Plan the evidence path

Match the testing plan to the product risk, format, packaging and claims.

Confirm the stability questions for the formula and pack

List the formula, microbiological, packaging and performance risks first.
Match each risk to an appropriate test, sample condition and acceptance criterion.
Plan the evidence path early enough for results to influence development decisions.

Identify microbiological and preservation checks where applicable

List the formula, microbiological, packaging and performance risks first.
Match each risk to an appropriate test, sample condition and acceptance criterion.
Plan the evidence path early enough for results to influence development decisions.

Review packaging compatibility and dispensing performance

List the formula, microbiological, packaging and performance risks first.
Match each risk to an appropriate test, sample condition and acceptance criterion.
Plan the evidence path early enough for results to influence development decisions.

Define what product performance needs to be demonstrated

List the formula, microbiological, packaging and performance risks first.
Match each risk to an appropriate test, sample condition and acceptance criterion.
Plan the evidence path early enough for results to influence development decisions.

Use testing to improve the product

Evidence is not only a final gate; it can help the team make better decisions during development.

Use stability observations to guide formula and pack refinement

Use test observations to refine the formula, package or intended use.
Keep sample versions, test conditions and decisions linked for traceability.
Separate internal development findings from the claims that can be used publicly.

Track changes between samples so the final direction is clear

Use test observations to refine the formula, package or intended use.
Keep sample versions, test conditions and decisions linked for traceability.
Separate internal development findings from the claims that can be used publicly.

Keep test methods and acceptance criteria documented

Use test observations to refine the formula, package or intended use.
Keep sample versions, test conditions and decisions linked for traceability.
Separate internal development findings from the claims that can be used publicly.

Separate internal development observations from consumer-facing claims

Use test observations to refine the formula, package or intended use.
Keep sample versions, test conditions and decisions linked for traceability.
Separate internal development findings from the claims that can be used publicly.

Make the next development conversation more useful

The most useful testing plan is built around real product questions and the evidence needed for intended use.

Questions to answer

What could change during the product life?
Which stability or compatibility risks need early attention?
What performance statement needs support?

Useful outputs

Risk-to-test matrix
Sample and acceptance record
Organized evidence file

Before you move to the next stage

Use this short check to keep the product direction clear and ready for the next conversation with your team or manufacturing partner.

List the key product risks
Map each risk to an evidence source
Confirm sample and packaging conditions
Keep reports organized for the launch file