There's a version of this story that plays out in almost every wine and spirits operation past a certain size. It starts with a shared spreadsheet — reasonable, practical, gets the job done. Then someone adds a tab to reconcile data from a second system. Then a third. The file gets passed around, names get typed differently across teams, keys don't match. Someone creates a second spreadsheet to check the first one. And eventually, you have a project manager whose main responsibility is to verify that what the spreadsheet says is actually true.
At that point, the spreadsheet stopped being a tool. It became the problem.
Knowing when you've crossed that line isn't always obvious while you're living it. Here are five signs that tell you the spreadsheet system has reached its limit.
You're building a spreadsheet to manage your spreadsheet
When a live shared file becomes the coordination layer across multiple systems — pulling inventory data from one source, order history from another, shipment tracking from a third — the first thing that breaks is consistency. Product names are spelled differently. SKU codes don't match. The same distributor appears under three slightly different variations of the same name.
The fix is usually another tab, or another file, or a weekly reconciliation ritual where someone manually cross-references two versions of what should be the same data. Research from the University of Hawaii found that 88% of spreadsheets in active business use contain errors — not because the people using them are careless, but because manual data entry and cross-system stitching are structurally error-prone at scale [1]. The reconciliation work doesn't fix the problem. It just manages the symptoms.
Your seasonal planning relies more on memory than data
Ask most Distribution Managers how they set safety stock for the rosé season and the answer involves last year's numbers plus an adjustment based on what they remember happening. That's a reasonable starting point. It becomes a real problem when the route-to-market has changed, a new retail account came on board, or a competitor's supply disruption shifted demand patterns in ways that don't show up in last year's file.
A spreadsheet records what happened. It doesn't surface what's changed. The teams that get caught with too little rosé in June, or too much Champagne in January, are usually the ones whose planning process looks backward rather than forward.
You needed to hire someone to manage the coordination, not the operations
This is the sign that's hardest to see when you're inside it, because the hire makes sense at the time. You have a complex, multi-partner supply chain. Someone needs to keep the information flowing between systems and teams. So you bring someone in — or more likely, you promote someone internally — to maintain the spreadsheet ecosystem.
What that person is actually doing is acting as a human integration layer between systems that don't talk to each other. Their job exists because the data infrastructure can't do it automatically. And because their job involves constant manual intervention, any disruption — a sick day, a handover, a version control mistake — creates a gap in the information chain.
Your partners are working from different versions of the truth
When your importer runs their numbers and your own inventory file tells a different story, someone has to make a call about which one to trust. That conversation — the "let me check my sheet against yours" call — is a tax on every planning decision. It slows down response times. It creates hesitation exactly when speed matters most.
In multi-partner wine supply chains, this problem multiplies. Each tier runs its own systems with its own data. The distributor doesn't know what the retailer is actually selling. The importer doesn't know what's sitting in the distributor's warehouse. Everyone is planning from incomplete information and reconciling the gaps manually.
You can't answer "where is my inventory right now?" in under five minutes
Not the system-of-record answer. The real answer — what's in transit, what's at each partner node, what's committed to upcoming orders. If getting to that answer requires opening three tabs, making two calls, and waiting for someone to get back to you, you've already lost the response window that supply chain disruptions require.
A platform doesn't eliminate complexity. But it does mean that question has a single, live answer — one that doesn't depend on everyone's spreadsheet being current at the same moment.
If you're running a small operation with a handful of SKUs and one or two partners, a well-maintained spreadsheet will serve you fine. But if signs one, three, and five feel familiar — if the reconciliation workarounds, the coordination headcount, and the delayed visibility are just a normal part of how your week runs — the question isn't whether you've outgrown the spreadsheet. It's how much it's already costing you to stay in it.
References
[1] Raymond Panko, "What We Know About Spreadsheet Errors," University of Hawaii. Published in the Journal of End User Computing and reviewed in subsequent meta-analyses of operational spreadsheet error rates. ResearchGate