Maintenance
Lessons from sauce projects that went wrong
The failure patterns that repeat in small sauce businesses, why each one happens, and the cheap controls that would have caught it before it reached a customer.
What to take away
- Most failures are process failures, not recipe failures. The sauce was fine and the system around it was not.
- The expensive mistakes cluster at scale up, at packaging changes and at ingredient substitutions.
- Safety mistakes are a separate class. They are rarer, and they end businesses.
- Every control that would have caught these is cheap. Records, a retained sample and a written change rule cover most of them.
The failure patterns that repeat
| Pattern | What actually happened | Cheap control |
|---|---|---|
| Scaled by multiplying | Heat transfer changed, texture and safety assumptions did not hold | Re-establish the process at the new volume |
| Quiet substitution | A supplier swapped an ingredient form, nobody revalidated | Written change rule with sign off |
| Seal failures | Cap or torque changed, discovered by customers weeks later | Closure check on every run |
| Label drift | Formula changed, artwork did not | Formula version on the artwork file |
| No lot codes | A complaint could not be traced to a run | Code every jar from day one |
| Over ordering packaging | Cash tied up in a design that changed | Order to a tested forecast, not a hope |
Two of those rows are one failure seen from opposite ends, since a formula version on the artwork file only helps if the label is treated as a controlled deliverable with an owner and a date.
The safety class, treated separately
A quality mistake costs money. A safety mistake can cause harm. Shelf stable acidified sauces, low acid vegetable bases, and garlic or chilli held in oil are the formulas where an error is not recoverable by tasting. The process that makes such a product safe has to be established and documented by a qualified process authority for your formula and your container, and it has to be re-established when the formula, the container or the batch size changes.
Do not read a number from a book and apply it to your own product. That is the mistake behind most serious incidents in small food production, and it is entirely avoidable. The quality equivalent is a borrowed shelf life, and a figure that did not come from your own product in your own container is a guess with a date printed on it.
Why teaching matters more than blaming
The businesses that recover from a bad run are the ones that treat it as a training problem. Written procedures, a short induction, and a refresher after any change do more than any amount of care. The National Agricultural Library's collection of nutrition and food safety education resources gathers lesson plans, tools and educator material from USDA and partner organizations, which is useful if you are building training for people who did not come from a food background.
Planning for the disruption, not just the error
Some failures arrive from outside: a supplier collapses, equipment fails, a facility becomes unavailable. NIST's Manufacturing Extension Partnership describes business continuity planning as preparing for the impact of a broad range of threats including natural disasters, disease outbreaks, accidents and technology failures such as equipment or software breakdown, and its centers help companies build a plan. For a one product sauce business, the plan can be a single page. Not having one is the mistake.
What to do after a bad run
Stop, hold the stock, and find the cause before you decide anything. Then write down what changed and what control would have caught it. The production walkthrough sets out the records that make this possible, and the development gates explain where a change should have been caught before it reached production.
Common questions
What is the single most common mistake? Changing something without revalidating, usually an ingredient or a container.
Can I sell a batch that is only cosmetically off? Decide against a written specification, not in the moment. Cosmetic drift often signals a process change.
How long should I keep records? At least through the shelf life of the product, and longer if a customer might come back.
Is a recall survivable? Frequently yes, if you can trace lots quickly and communicate clearly. Both depend on work done beforehand.
