HACCP for kombucha: the two control points that actually matter
A HACCP plan can balloon into a binder nobody reads. For kombucha, the food-safety story is refreshingly focused: two things do almost all the work — how fast you get acidic, and how much alcohol ends up in the bottle.
Kombucha is an unusually safe product when it's made well, and the reason is chemistry. A finished kombucha sits well below pH 4.2, and that acidity is a genuine barrier to foodborne pathogens. The job of a food-safety plan isn't to add ceremony — it's to prove, batch after batch, that the barrier was there. Aligned with the Kombucha Brewers International (KBi) Code of Practice, here are the control points worth your attention.
Control point 1 — acidification
The primary hurdle is low pH, reached quickly. The risk window is the first day or two of fermentation, before the culture has acidified the sweet tea. If the batch drops below roughly pH 4.2 early — commonly within about 48 hours — pathogens never get a foothold.
What drives an early, reliable drop is pitching enough mature, low-pH starter liquid — and treating that as a food-safety practice, not just a flavour choice. The 10% figure you'll sometimes see quoted is too little for a dependable early drop; pitch at least 20% by volume of well-acidified starter, and more when your starter is younger or less sour. So the things worth recording are simple: the starter you pitched, the pH at set, and the pH as it falls — held low all the way to packaging.
This is the one measurement that should drive a clear pass/fail on your batch record. Everything else supports it.
Control point 2 — alcohol
Fermentation makes a little ethanol. In most markets a drink sold as non-alcoholic must finish under 0.5% ABV (parts of the EU allow up to 1.2%). This is a regulatory line more than a safety one, but it belongs in your plan because it's a real limit on a real product. Test finished batches, record the result, and know your market's threshold.
Unlike acidification, an alcohol reading shouldn't silently block a batch in your system — it's information you act on, not an automatic gate. But it should be documented every time.
Everything else is a prerequisite
Two controls carry the safety case; a handful of prerequisite programmes keep the conditions right around them:
- Cool the tea before you pitch. Pitching into tea that's too hot stresses or kills the culture and slows acidification — the thing you most need to happen fast.
- Hold a sensible ferment temperature (commonly ~21–32 °C). Warm enough to acidify briskly, not so warm that things run away.
- Keep raw, live product cold after packaging (roughly 4–9 °C) so it stays stable and doesn't over-carbonate.
- Hot-steep your tea — a simple thermal step that starts you from a clean base.
These matter, but they're operational prerequisites, not the control points themselves. Keeping that distinction clear is what stops a plan from turning into noise.
The point of the paperwork
Documentation exists to answer one question on demand: was this batch safe, and can you show it? If a record ever conflicts with what you know happened on the floor, trust the floor and investigate — the log is there to reflect reality, not replace it. And documenting a low pH is never a substitute for a lab or a qualified assessment; it's the evidence that your process did what it should.
This article is general information, not certified food-safety, legal or regulatory advice. Follow your local regulations and the current KBi Code of Practice, and validate your own process.