It is not acid enough
Updated
On this page5
Two questions wearing the same words
A customer saying it needs more bite is talking about flavor, which the recipe can address. A maker reading a high pH has a product that is not what its process assumed, and no amount of adjusting the next batch changes the status of this one.
They do not track each other reliably, which is the whole reason the measurement exists. Sweetness masks acidity, and a sauce can taste sharp and read high or taste mild and read fine.
The usual causes
- Vinegar of unknown or lower strength than the recipe assumed.
- More low-acid ingredient than the formulation allows for.
- Dilution from a late addition nobody counted.
- Measuring the kettle rather than the finished settled product.
What to do with the batch
If the finished product is out of specification it is not shelf stable. Refrigerate it and sell it as a short-life product, or discard it. Do not take a second reading until one comes out right, and do not reason that it is probably fine because the last ten were.
The commercial consequence
This is the one failure on this property with a reach beyond the batch. Everything else here costs a day or a customer; an under-acid product that shipped as shelf stable is a recall conversation. That is why the reading is logged against the batch rather than noted and forgotten.
It is also the reason to pay a process authority rather than work from a published recipe. The figure you measure against should have been established for your formulation by somebody qualified to establish it, not inferred from a recipe written for a different sauce in a different jar.
Measure before you fill as well as after. A check in the kettle will not replace the finished reading, but it stops you filling eighty jars of something that was never going to pass.