A beer can pass through receiving, the brewhouse, fermentation, conditioning, and packaging while its records remain scattered across invoices, brew sheets, tank boards, and inventory tabs. The brewery can still struggle to explain what happened from the first ingredient receipt to the last packaged unit.
Reliable **craft brewery production** records create one quantity-and-status chain. They connect what arrived, what the recipe expected, what the team actually used, what moved between vessels, what was lost, what passed review, and what became available to sell.
This is an operational framework, not legal, tax, food-safety, or alcohol-regulatory advice. U.S. breweries should confirm the federal, state, and local requirements that apply to their operations.
Start the record before brew day
A batch cannot be traced cleanly if the starting materials are vague. When malt, hops, yeast, adjuncts, processing aids, cans, bottles, crowns, ends, labels, and kegs arrive, the receiving record should capture:
- material identity and specification;
- supplier and supplier lot when provided;
- quantity and purchasing unit;
- received date, condition, and storage location;
- internal lot or receipt reference;
- status such as available, held, rejected, or allocated.
Document unit conversions once rather than asking each brewer to improvise them. Grain may be bought by sack and issued by pound; cans may arrive by pallet and be consumed by each.
Packaging belongs in this record too: the planned format needs enough correct cans, ends, labels, cartons, or kegs.
Give the intended beer a controlled definition
Before production begins, connect the unique batch ID to the approved recipe version. The intended record should identify the product, target volume, ingredient quantities and units, planned additions, expected measurements, equipment route, expected yield, and packaging plan.
The recipe describes what should happen; the batch record preserves what did happen. Do not edit the recipe afterward to make a deviation look planned. For a permanent change, approve a new version and keep the earlier version attached to its batches. The guide to [recipe and batch management](https://resources.buildwithkerno.com/recipe-and-batch-management-for-food-and-beauty-brands/) explains why that separation matters.
Capture brew-day actuals at the point of work
Good **brewing batch tracking** records actual quantities and observations, not only a completed checkbox. For each run, capture the lots and quantities of **brewery ingredients** used, key measurements required by the process, start and finish times, equipment, operators, transfers, samples, and deviations.
The record should make three things clear:
1. What was expected? 2. What actually occurred? 3. What action was taken when the two differed?
For gravity, temperature, volume, pH, or another process value, define when it is taken, how it is measured, the expected range, and the response outside that range. The same principle applies to the [quality checks a product business documents](https://resources.buildwithkerno.com/simple-quality-checks-every-product-business-should-document/).
At the end of brew day, record the volume transferred forward and explain major variance from the target. Spillage, trub, transfer residue, an incorrect reading, or an intentional adjustment should not disappear into a single unexplained number.
Keep the batch identity through the cellar
Once wort enters fermentation, the batch should not become just “Tank 4.” Record the batch ID, tank, transfer time, volume, additions, required readings, status, and next action.
Use clear states such as active fermentation, conditioning, held, ready for packaging, transferred, or closed. Preserve the sequence after the tank board changes.
When beer moves between vessels, record both sides of the transfer: volume out, destination, volume in, date, and reason for the difference. If two batches are blended, preserve the relationship instead of creating a new number with no parent history.
Reconcile packaging rather than posting the plan
Packaging turns liquid volume into countable saleable units and can hide loss. Begin with verified volume entering the run. Record good units by format, rejects, samples, measured loss, remaining bulk, and held product.
Use a simple reconciliation:
**Volume entering packaging = good packaged output + verified loss + samples + rejects + remaining bulk**
Convert units to a common volume before comparison. This **packaging yield** check makes variance visible instead of burying it.
Suppose 930 liters enter packaging. Good packages account for 890, samples use 4, verified loss accounts for 18, and 8 remain in a vessel. The unexplained 10-liter gap deserves a note and, if repeated, review.
The broader guide to [batch production in small-scale manufacturing](https://resources.buildwithkerno.com/mastering-batch-production-in-small-scale-manufacturing/) shows why actual yield should update inventory and costing instead of the planned quantity.
Separate packaged output from available brewery inventory
Completing the packaging run should not automatically make every unit available. Finished **brewery inventory** should identify beer, batch, package format, quantity, location, and release status. Units awaiting a required review, label correction, or other decision should remain held in both the physical area and the record.
Once released, increase available inventory by the good packaged quantity—not the plan. Preserve unavailable quantities separately so a later count can be explained.
Federal brewery rules include detailed operational and recordkeeping requirements. For example, 27 CFR Part 25 addresses daily brewery records, quantities of materials received and used, beer produced and transferred for packaging, losses, and physical inventories. A useful production system should support the brewery’s verified obligations, but software alone does not establish compliance.
Run one end-to-end record test
Trace one recent beer forward from ingredient receipts to packaged stock, then backward from one keg or case to its recipe version, batch, vessel history, and material references.
Use this compact review:
- Can you identify the recipe version and actual ingredient lots used?
- Can you follow volume through each vessel transfer?
- Can you reconcile packaging output, loss, samples, rejects, and remaining bulk?
- Can you distinguish packaged, held, released, and unavailable units?
- Can another team member retrieve the same answer without relying on memory?
If a larger order is approaching, pair this trace with the [food-production volume preflight](https://resources.buildwithkerno.com/can-your-food-business-handle-a-high-volume-order-run-this-preflight-test/) to review capacity, packaging, and release readiness.
Kerno is being built to connect materials, formulas, production, costing, quality, and finished inventory. Whatever system a brewery uses, each record should make the next decision clearer.
Frequently asked questions
Does every brewery ingredient need a lot number in the production record?
Record the supplier or internal lot reference when one exists and when your requirements call for it. At minimum, the record should identify the exact receipt or stock used well enough to investigate a supplier or batch issue.
Should packaged beer enter available inventory as soon as the packaging run ends?
Not automatically. Post good output to a held or pending status when review is still required, then release only the approved quantity to available inventory.
How should a brewery record beer lost during transfers or packaging?
Record the estimated or measured quantity, stage, and reason. Use a small consistent set of loss categories, and review recurring unexplained variance instead of hiding it in yield.
Can a spreadsheet support brewing batch tracking?
Yes, if the brewery controls identifiers, units, versions, access, formulas, and backups. A spreadsheet becomes fragile when the same batch facts must be copied across separate files or only one person understands the links.
What is the first brewery record to standardize?
Start with one batch record that connects the approved recipe, actual ingredient use, vessel transfers, packaging reconciliation, quality status, and final released quantity.
Practical takeaway
Map one beer before redesigning every form. Follow its quantities and status from receiving through packaged inventory, mark every unexplained handoff, and fix the largest gap first. A dependable record is not the one with the most fields. It is the one that lets the team explain what happened and decide what happens next.
