The Wine Inventory Spreadsheet, Done Right (and When to Retire It)

Let's be honest: most wineries start on a spreadsheet, and a well-built one can carry a small cellar for a while. The problem is that almost nobody builds it well. They open a blank sheet, type "Wine" in column A and "Qty" in column B, and eighteen months later it's a 40-column monster that only one person understands.

This guide gives you the structure that actually works if you're staying on a spreadsheet for now, and then tells you the honest truth about where the ceiling is.

The columns your wine inventory sheet actually needs

Keep one row per SKU per location. That rule alone prevents most spreadsheet disasters. Then use these columns:

• SKU / Wine name. One consistent naming convention: varietal, vintage, bottle size. "Merlot 2023 750ml", not "merlot new batch (2)".
• Vintage. A separate column, even though it's in the name. You'll want to filter and sort by it.
• Category. Finished bottles, unlabeled bottles, bulk wine, empty bottles, packaging, bag-in-box, dry goods. Mixing categories in one count is how you end up "discovering" 2,000 bottles that were actually empties.
• Location. One row per location. If the same wine lives in the cellar and the warehouse, that's two rows. Never a note in a comment.
• Quantity + unit. Bottles, cases, liters. Pick the unit per category and never mix. A "12" that means cases in one row and bottles in the next is a silent disaster.
• Last updated + by whom. The closest a spreadsheet gets to an audit trail. If a count looks wrong, this tells you who to ask.
• Reorder threshold. A simple conditional-format rule that turns the row red below a minimum. This is your only early warning.

Three rules that keep the sheet honest

• One person owns it. Not "everyone edits it," one person reconciles all changes. Shared editing without ownership is how numbers drift.
• Log movements, don't overwrite. Keep a second tab where every movement is a new row: date, SKU, from, to, quantity, reason. Then the inventory tab is calculated, not typed. Overwritten numbers have no history; when something doesn't add up, you have nothing to check.
• Count physically every month. The spreadsheet will drift from reality. A monthly physical count is the correction. Put it in the calendar or it won't happen.

The ceiling: when the spreadsheet stops working

Even a perfectly built sheet has a ceiling, and it arrives sooner than people expect. You've hit it when any of these are true:

• More than one location. The moment wine moves between sites, spreadsheet updates depend on someone remembering to log the transfer. They won't, every time.
• More than two people touching inventory. Concurrent edits, overwrites, and "I thought you updated it" conversations.
• Bottling runs. A bottling run touches bulk wine, empty bottles, labels, capsules, and finished stock in one event. Updating five rows by hand after a 12-hour bottling day is where errors are born.
• Anyone selling from the field. A rep at a restaurant table can't check a spreadsheet on your office desktop. They quote from memory.
• Compliance questions. If a HACCP auditor or distributor asks you to trace a batch, a cell that was overwritten 14 times has no answer.

What replacing it looks like

The upgrade isn't "a better spreadsheet." It's moving the movement log, the calculated inventory, and the audit trail into a system that updates itself: scan a pallet and the location changes, run a bottling and every category adjusts, let a rep check live stock from a phone. We've written up the full Excel-vs-software break-even analysis if you want the honest cost comparison.

Oenova's free plan covers 5 SKUs, 2 locations, and 2 seats, which is exactly the size of cellar that's about to outgrow its spreadsheet. Import your sheet, keep it as backup, and see which one your crew reaches for after a week. No credit card required, and your data exports back to CSV any time.