Why spreadsheets stop working for a growing winery — and how to tell when you have crossed the line

Nearly half of small US wineries still run production on spreadsheets and paper — and that is not a scandal, it is a rational choice. At 1,000 cases with one winemaker, a well-kept workbook beats most software: free, flexible, and exactly as complicated as you make it. The problem is that a winery does not outgrow Excel gradually. It works, and works, and then one harvest it fails in five places at once. This article is about seeing the line before you cross it.

Where winery spreadsheets actually break

• One editor at a time: the cellar workbook lives on one laptop. During harvest, the person receiving fruit, the person running the press and the person doing additions all need to write — so two of them keep notes on paper "to enter later". Later is where data goes to die.
• No memory of change: a cell overwritten is a fact destroyed. When a tank volume looks wrong in March, there is no way to see who changed it, when, or what it said before.
• Formula rot: the workbook is a program nobody tests. A sort that breaks row alignment, a copied formula that misses a row, a volume summed in gallons into a litre total — silent errors that surface months later in a report.
• The blend problem: spreadsheets are flat, wine is not. Lot 12 is 60% of what became lot 19, which was split across three tanks and two bottlings. Modelling that composition history in rows and columns is exactly the kind of graph problem spreadsheets are worst at.
• Reporting by reconstruction: TTB Form 5120.17 wants beginning inventory, additions, removals and losses that reconcile. From a workbook, that is a weekend of forensic accounting every reporting period — from records designed for it, it is a query.

The five tipping points

In practice the move is triggered by events, not case counts. Any one of these is the signal:

• A second person needs to write production data — the single-editor model is broken from that day.
• You run a mock recall (or a buyer asks for one) and tracing a lot from vineyard to shipped cases takes hours. FSMA 204 and trade customers are making this a routine request, not an emergency drill.
• A TTB report or excise return takes more than an afternoon, or an auditor asks how a number was derived and the honest answer is "it was in the spreadsheet".
• You catch a real error — a lost addition, a wrong tank, a double-counted volume — that made it into wine or into a filing.
• Growth math: above roughly 5,000 cases, the hours spent maintaining and reconciling workbooks reliably exceed the cost of software that does it structurally.

What to look for when you replace it

The goal is not "Excel in the cloud" — it is structure: lots, vessels, operations and inventory as first-class records that reference each other, so composition and history are facts you query rather than stories you reconstruct. Evaluate software on:

• Lot-level traceability both directions: from a block of fruit to every bottle it ended up in, and from a bottled lot back to every input — in minutes, exportable, audit-ready.
• Multi-user with an audit trail: everyone writes from the cellar floor (phone or tablet, mid-punch-down), and every change keeps its author and timestamp.
• Atomic inventory: additions, transfers and bottlings that update stock as one operation, so the tank board always reconciles with reality.
• Reporting from records, not alongside them: TTB-oriented summaries derived from the same operations you logged anyway — not a separate workbook to maintain.
• Transparent pricing you can start on alone: if the price is a sales call and onboarding is a project, it was built for a different size of winery than yours.

And keep spreadsheets for what they remain great at: one-off analysis, budgeting, scenario math. The line is simple — Excel for thinking, structured records for the system of record.