Ask a cider maker which apples went into last October's semi-dry and you'll usually get a good answer. Ask which tank it fermented in, what the gravity read on day nine, which bottling run it ended up in, and how many cases of that run are still sitting in the back of the tasting room, and the answer starts to depend on whose handwriting is in the notebook. That gap matters more every year. Wholesale buyers want lot numbers on invoices, the federal tax return wants gallons that reconcile, and a single bad batch can turn into a phone call you'd rather answer in ten minutes than in ten days. This piece is for the people pressing and pouring: what a batch record really needs to hold, where the paperwork pressure comes from, and how to tell when a notebook has done its job and it's time for something sturdier.
The Notebook Works Until Someone Asks a Question
Most small cideries in the valley run on some mix of a cellar log, a shared spreadsheet, a whiteboard on the tank room wall, and the point-of-sale system in the tasting room. None of those are wrong. A cellar log written by the person who actually took the reading is often more honest than any software screen, and plenty of excellent cider has been made with nothing fancier than a clipboard.
The trouble isn't the tools. It's that each one answers a different question, and none of them talk to each other. The cellar log knows the fermentation. The spreadsheet knows what got bottled. The POS knows what sold on Saturday. When a distributor calls to say a customer found a hazy bottle, you need all three at once, and you need them tied together by one number.
That number is the lot. If you take one thing from this article, make it a habit of assigning a lot code at the press and carrying it forward through every step. A workable batch record follows that code and captures, at minimum:
- Fruit in: the orchard block or grower, variety, pick or delivery date, and weight. If you buy apples, the grower's name and the date they arrived.
- Pressing: the press date, juice volume, starting gravity, and any sulfite or yeast additions.
- Fermentation: the tank or barrel, the yeast, temperature notes, and the gravity readings that tell you when it finished.
- Blending: which lots went into which blend, in what proportions. This is where most paper trails quietly fall apart.
- Packaging: the bottling or canning run date, the finished volume, the package format, and the lot printed on the label or case.
- Out the door: which accounts received which lot, and how much went across your own bar.
You can keep all of that in a well-built spreadsheet. Many cideries do. The question is how many people touch it, how many blends you run, and how fast you can answer "where did lot 24-07 go?"
What a Production System Actually Tracks
The jump from notebooks to a production system isn't really about software. It's about who holds the connections between steps. In a spreadsheet, a person does: someone has to remember that Blend C used half of tank 3 and all of barrel 11, then type that into the right row. In a manufacturing system, the connection is part of the record itself, because a blend or a bottling run can't be logged without naming the lots that went into it.
That's what manufacturing modules in ERP software are built to do. You define a recipe (a bill of materials, in their language) for each product, so a case of your dry cider "consumes" a set volume of finished cider, bottles, caps, labels, and cartons. When you record a bottling run, the system draws down those inputs, creates finished goods carrying their own lot number, and remembers which upstream lots fed into them. Trace forward from a grower's delivery and you see every case it touched. Trace backward from a single account's invoice and you land on the press date.
For a small producer, the useful part is often less glamorous than traceability. It's knowing you have 400 labels left for a SKU that needs 600 next week, or that the tasting room has been pulling cases without anyone moving them out of warehouse inventory. Guides on odoo for food & beverage manufacturing walk through this kind of setup in practical terms: lot and expiry tracking, recipes with yield loss, and stock that moves between a production space and a retail floor. Odoo is one option among several; the specific product matters less than whether it models the way cider actually gets made.
And cider is awkward to model. Yields change with every harvest. A tank of juice can sit for months before anyone decides what it becomes. Blends get adjusted by taste, not by formula. Any system you look at should handle these realities:
- Partial lots, so half a tank can go to one blend and half to another without losing either history.
- Volume conversions between gallons in tank, liters in the bottle, and cases on the pallet.
- Lots that stay open for weeks or months, rather than a factory-style job that starts and ends in a shift.
- A clean split between what moves through the tasting room and what ships to wholesale accounts.
If a vendor demo can't show you those four things with your own numbers, it's built for a different kind of factory.
Where the Paperwork Pressure Comes From
Even if you never buy a piece of software, the records still have to exist, because several outside parties expect them.
Start with federal tax. Hard cider has its own tax class, and the eligibility rules are specific. Under 27 CFR 24.331, cider qualifies for the hard cider rate only if it contains at least 0.5 percent and less than 8.5 percent alcohol by volume, is made primarily from apples or pears, contains no other fruit, and stays under a carbonation limit of 0.64 gram of carbon dioxide per 100 milliliters. Push a batch past 8.5 percent, add a few quarts of black currant, or carbonate it harder, and it lands in a different, higher-taxed class. That means your production records need to show ABV, ingredients, and carbonation per lot. "We think it came in around eight and a half" isn't a figure you want to defend.
State licensing adds its own layer. New York's farm cidery law, signed in October 2013 according to state legislative and governor's office releases at the time, requires licensees to make their hard cider from apples grown in New York and caps production at 150,000 gallons a year. Albany's Nine Pin Cider Works became the first licensee in early 2014. If you hold that license, the source of every bin of fruit is a compliance question as well as a flavor one, which is one more reason to write down the grower at the press.
Then there's food safety. The FDA's Food Traceability Rule, written under section 204 of the Food Safety Modernization Act, requires covered businesses to keep specific records at each step a listed food moves through and to hand those records to the FDA in an electronic, sortable spreadsheet within 24 hours of a request. The rule applies to foods on the agency's Food Traceability List, and enforcement now starts on July 20, 2028. Check with your own regulator whether anything you make or sell falls under it. Even if your cider doesn't, the 24-hour, sortable-spreadsheet standard is a good picture of where buyers and distributors are heading. They'll ask the same question in the same tone.
Distributors and larger retail accounts are the most immediate pressure. Many want lot codes on invoices, and some will want to know you can pull every case of a lot from the market in a day. That's a fair ask, and it's much easier to say yes when the lot code has been riding along since the press.
When You Don't Need a System Yet
Here's the honest part: a lot of Hudson Valley cideries don't need ERP software, and some never will. Software costs money, setup time, and patience, and a badly configured system is worse than a clean spreadsheet because people stop trusting it and go back to the whiteboard anyway.
A spreadsheet and disciplined lot codes are probably enough if:
- You sell most of what you make across your own bar or at farmers' markets.
- You run a handful of products and blend rarely.
- One or two people do all the production record-keeping.
- You can answer "where did this lot go?" in under an hour, today, without calling anyone.
It's worth looking at a production system when the answers flip. Signs that you've outgrown the notebook:
- You have several wholesale accounts or a distributor, and they ask for lot codes.
- You blend across tanks, barrels, and vintages regularly.
- Inventory counts in the tasting room and the cellar don't match, and nobody's sure why.
- Your TTB operations report takes a full day of reconciling three sources.
- Seasonal staff log production, and their records don't look like yours.
If you're in between, start with the cheapest fix: one lot code format, assigned at the press, written on every tank tag, blend sheet, case, and invoice. That habit costs nothing and makes any future system dramatically easier to set up, because the data you'd be importing already makes sense.
Start With the Lot Code, Then Decide
Tracking every batch isn't really about software. It's about whether you can follow one bin of apples all the way to one customer's glass and back again. Three things to do this season:
- Assign a lot code at pressing and carry it onto every tank tag, blend sheet, and case.
- Record ABV, ingredients, and carbonation per lot so your tax class is never a guess.
- Time how long a mock recall takes. If it's more than an hour, that number tells you whether a production system has earned its place.
