A bottling log is one row for each run: the product and its lot, how many gallons went to the filler, the bottle size, how many bottles that should have filled, how many it did fill, how many were rejected, a few fill checks taken during the run, a cap check, a label and date-code check, and the best-by date printed on the lot. The sheet works out the good bottles and the yield. The point of it is to make two kinds of loss visible: sauce that never reached a bottle, and bottles that were filled and then thrown away. Here's a template with three runs in it.
The short version
- One row a run. Fill it in at the line, not afterwards.
- Should fill: gallons times 128, divided by the bottle's fluid ounces.
- Pull a bottle three times a run and measure the fill. Write each one.
- Count rejects and say why in the notes.
- TaroStack records the run as a batch, takes bottles, caps and labels off stock and gives the lot its date. More below.
An example: three runs of 5 oz bottles
Blue Ridge Hot Sauce is a made-up Roanoke hot sauce maker I use in these examples:
| Date | Product | Lot | Gallons | Should fill | Filled | Rejects | Good | Yield | Fill checks (oz) |
|---|---|---|---|---|---|---|---|---|---|
| Nov 5 | Original | L2611-01 | 25 | 640 | 621 | 6 | 615 | 96.1% | 5.1, 5.0, 5.1 |
| Nov 12 | Smoked habanero | L2611-02 | 20 | 512 | 498 | 3 | 495 | 96.7% | 5.0, 5.1, 5.0 |
| Nov 17 | Green chile | L2611-03 | 20 | 512 | 476 | 14 | 462 | 90.2% | 5.1, 4.8, 5.0 |
Reading the runs
Should fill is arithmetic. Twenty-five gallons is 3,200 fluid ounces, and 3,200 over 5 is 640 bottles.
The first loss: 640 to 621. Nineteen bottles' worth of sauce stayed in the kettle, the hoses and the filler bowl. That's 3%, and it's about the same on the second run (512 to 498). It's the cost of your line. It only becomes a problem when it changes.
The second loss: rejects. Six and three are ordinary: a chipped neck, a crooked cap. The green chile run had 14, and the notes say what happened. One fill check read 4.8 oz against a 5 oz label. The filler was adjusted, three underfilled bottles were pulled, and eleven crooked labels were redone and count as rejects on the sheet because they were handled twice.
Yield puts both together. Two runs at 96% and one at 90.2%. Ten percent of a batch is around 50 bottles. At $5 a bottle wholesale that's $250 gone from one run, and the log is the only place it shows.
Why fill checks get their own column
A bottle labeled 5 fl oz has to hold 5 fl oz. A fill that drifts low is a labeling problem; a fill that drifts high gives sauce away, about 2% of the batch for every tenth of an ounce on a 5 oz bottle. Three checks a run, at the start, the middle and the end, catch a drift while it can still be fixed. The rules on stated contents are in net weight labeling requirements.
The label and date check is the other one worth a column. Before the first case is sealed, read the lot and best-by on a bottle and compare it with this row. A whole run coded with yesterday's lot is a bad afternoon.
Get the template
Download the bottling log template. The log, with should fill, good bottles and yield worked out, and a read-me. It's an ordinary Excel file with no macros, and it works in Google Sheets, LibreOffice and Numbers. Scaling the batch itself is in how to make hot sauce in bulk.
Where this stops working
The log knows 621 bottles were filled. The stock sheet still thinks you have all the bottles, caps and labels you started with. And the 615 good bottles exist only on this row until someone adds them to finished stock under lot L2611-01, with the right date.
How TaroStack does it
TaroStack treats the bottling run as a batch and moves everything at once.
A bottle is a recipe. Five ounces of sauce, a bottle, a cap, a shrink band, a label. Record a run of 615 and the sauce comes off the kettle batch's lot, the packaging comes off stock, and 615 bottles go into finished stock as lot L2611-01 with their best-by date.
Your checks are on the batch record. Fill checks, cap check, label check and initials are fields of your own, and the printable form carries a sign-off.
Yield against the recipe. From your own batch history, TaroStack shows whether a recipe yields what it claims, so a filler that's wasting 10% shows up as a pattern.
Lot labels. Print lot labels with the code and date, as GS1-128 barcodes if a buyer wants them.
Which stores got the run. Each order records the lots it shipped, so one recall report lists every customer a lot reached.
| The job | Log sheet | In TaroStack |
|---|---|---|
| Bottles, caps, labels used | A separate subtraction | Come off with the batch |
| Finished stock by lot | Add it by hand | Created by the batch |
| Yield over time | Compare rows | Shown against the recipe |
| Fill and label checks | Columns | Fields on the batch record |
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.
