Turning a recipe into a product
Updated
On this page6
What has to become a number
- Finished equilibrium pH, measured on a settled jar.
- Fill temperature, as a minimum rather than a target.
- Net weight into the jar.
- The proportion of low-acid ingredients, by weight.
- Process time, from your filed process, adjusted for altitude.
Why the proportion matters more here than in most crafts
The published guidance on salsa and sauces is explicit that changing the ratio of low-acid ingredients -- more onion, more pepper, more garlic -- changes the safety of a tested recipe, not just its flavor. Vegetables are the low-acid part. "A bit more garlic" is a formulation change and it is the single most common way a maker leaves the process their recipe was built on.
That is the hard part of turning a recipe into a product: the thing cooks adjust by instinct is the thing you now cannot adjust without going back to the process authority.
Weigh everything
By weight, never by volume. A cup of chopped onion is not a repeatable quantity and two people will not produce the same one. The ratio is the product, and a ratio measured in cups is a ratio you do not actually know.
Write it as a specification, not as a method
The test is whether somebody else could hit it without asking you what you meant. If the document says "cook until thick", it is still a recipe. If it says a target soluble solids or a hold time at temperature, it is a specification and you can run a business from it.
The specification is what a co-packer buys
If you ever hand production to somebody else, the specification is the entire transaction: they make what it says and nothing else. A maker with only a recipe and a feel for it cannot hand it over, and finds that out at the point they most need to. Writing it down early costs an afternoon and is the difference between a business that can grow past your own hands and one that cannot.