A kombucha brew log has one row for each batch, and it follows the batch from the day the tea is brewed to the day the bottles are filled. It records what went in (the tea lot, the sugar lot, and which earlier batch the starter came from), what happened (the pH and temperature at the start, the pH on the way down, the finish date and finish pH), and what came out (the flavor, the bottle count and the bottles' lot code). The starter column matters more than it looks: it's the only thing that links one batch to the next. Below are the columns, four batches including a slow one, and a file.
The short version
- One row a batch, started on brew day.
- Record lots for tea, sugar and flavoring, and the batch the starter came from.
- pH at the start, on the way, and at the finish.
- Compare the finish pH with your own limit before bottling.
- Count the bottles and give them a lot code that leads back to the row.
- TaroStack records each batch with its lots and holds it until you release it. More below.
What to record, and why
| Column | Why |
|---|---|
| Brew date, batch, tank, gallons | Which batch, where, how big |
| Tea lot, sugar lot | If an ingredient is the problem, these find the other batches |
| Starter from batch | A problem in one culture travels down this chain |
| Start pH and temperature | The starter should pull the pH down at once; a warm, acidic start ferments cleanly |
| Day 3 and day 7 pH | The curve. A flat one is an early warning |
| Finish date, finish pH, days | When it was ready, and how long that took |
| pH check | The finish pH against your limit |
| Flavor and its lot | Juice and fruit are ingredients too |
| Bottles, bottle lot | What was made, and the code on it |
Four batches
A made-up brewery with two 100-gallon tanks. Its own limit for the finish pH is 3.5.
| Batch | Brewed | Tank | Starter from | Start pH | Day 3 | Day 7 | Finished | Finish pH | Days | Bottles |
|---|---|---|---|---|---|---|---|---|---|---|
| K-201 | Oct 27 | 1 | K-199 | 4.1 | 3.7 | 3.3 | Nov 5 | 3.1 | 9 | 768 |
| K-202 | Oct 30 | 2 | K-200 | 4.2 | 3.8 | 3.4 | Nov 9 | 3.2 | 10 | 720 |
| K-203 | Nov 6 | 1 | K-201 | 4.2 | 4.0 | 3.9 | Nov 19 | 3.3 | 13 | 768 |
| K-204 | Nov 10 | 2 | K-202 | 4.1 | 3.7 | 3.4 | In the tank |
K-201 and K-203 were flavored with ginger juice, a fluid ounce a bottle, which is why they filled 768 bottles and the plain batch 720.
What the log shows
K-203 was slow, and the log says why. Its start temperature was 70°F, not 78°F, and by day 7 the pH had only reached 3.9. The note explains it: the tank room heater failed. It finished at 3.3 after 13 days. Without the temperature column, that's a mystery batch. With it, it's a heater.
The starter chain. K-203's starter came from K-201, and K-201's from K-199. If a tank's culture goes off, this column shows which later batches were seeded from it.
Days against the plan. Three batches at 9, 10 and 13 days. Tank time is this brewery's limit on how much it can sell, so a 13-day batch pushed the next one back.
The limit is yours
The example's 3.5 is this brewery's own figure. Your limit, and when to measure it, come from your own process and whoever reviewed it. The reasoning is in kombucha HACCP plan. A meter that hasn't been calibrated gives a number, not a reading: calibrate before each day's readings and write that down too.
Sizing a batch is in kombucha batch calculator, and the steps from tea to bottle in kombucha production process.
Get the log
Download the kombucha brew log. One row a batch; Days works itself out, and pH check says HOLD when the finish pH is above the limit you type on the Limits sheet. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. If you'd sooner log every reading as its own row, use the fermentation log sheet.
Where this stops working
The log knows K-203 used tea lot T-1021. It doesn't know which stores got K-203, how many bottles are left in the cooler, or which of them go out of date first. Those answers are in the delivery book and the cooler, and joining them to the log is a job for a bad day.
How TaroStack does it
TaroStack keeps the batch, its bottles and where they went as one record.
Each brew is a batch. Record it and the tea, sugar and starter are taken from the lots you used and noted on the batch record automatically. The starter is an ingredient like any other, so the chain from batch to batch is kept without a column for it.
Your readings are fields. Start pH, day 3, day 7, finish pH and temperature go on the batch-record form, with initials.
On hold until it passes. A batch on hold is out of what you can sell until someone enters the finish pH and releases it.
Bottles carry a lot and a date. They go into stock with their lot code and best-by date, and the soonest to expire sells first.
Where it went. Orders record the lot shipped. One report lists the customers who got K-203 and what's still in your cooler.
| The job | Brew log | In TaroStack |
|---|---|---|
| Lots of tea and sugar | Written on the row | Noted on the batch automatically |
| Starter chain | A column | Each batch's ingredients |
| Not yet checked | Looks like any other batch | On hold |
| Who got K-203 | The delivery book | One report |
TaroStack doesn't set your pH limit or measure anything. Recipes, batches, lots and recalls are on every plan, from $9.99 a month (5 recipes) or $39 a month (50 recipes). The first 14 days are free, with no credit card. If you'd like a hand setting up, ask, and we'll do it with you.
