What changes force a new filing
Updated
On this page6
A scheduled process covers one product, made one way, in one container. Knowing what invalidates it is what keeps a growing range compliant.
The rule
If it changes the product, the process or the container, the scheduled process may no longer apply. The process filing itself is per product, per process and per container size, which is the clearest statement of scope you will get.
Always
A new product, including a new flavor, because a process must be developed and validated for every product variation.
A new container size, because cooling and equilibration depend on volume and geometry.
A change of acid or acid level.
A change in process: hot fill to cold fill, a different cook, a different hold.
The ones people think are safe
A pepper substitution. Different varieties differ in pH and in how readily acid penetrates them, and a formulation validated on one is not automatically valid on another.
Changing the particle size. A chunkier sauce takes longer to reach equilibrium, which is one of the factors the process specifies.
Adding a vegetable. Carrot, onion and fruit all bring their own pH and their own buffering.
A different closure. The container closure is part of what was evaluated.
Scaling the batch, because cooling rate and hold time change with volume.
Building it in
Keep a written record of which scheduled process covers which product and container, with its filing reference, and attach it to the product record rather than filing it separately.
Then make "does this need a new process" a required question in any change. The failure mode is never a decision to skip it; it is a series of small reasonable changes after which nothing being made matches anything that was filed.
