Spreadsheets are not the problem
Spreadsheets are one of the most useful tools ever built for running a business. The problem is not that they exist. The problem is that they do not tell you when they have stopped being the right tool for what you are trying to do.
Most distribution businesses that are struggling with operations do not describe their problem as "we use spreadsheets." They describe it as "everything takes longer than it should," or "we are always chasing people for updates," or "I cannot trust the numbers without checking them myself first." Spreadsheets are often the underlying cause but they rarely show up as the named problem.
Here are seven patterns that indicate the operational coordination cost has crossed the line where spreadsheets are actively working against the business.
1. One person carries the knowledge
There is a person in your business, often the operations manager, the logistics lead, or a long-tenured account manager, who knows how the spreadsheets work. They know which tab is current, which formulas to trust, and which columns are updated inconsistently.
When that person is on holiday, ill, or simply leaves the business, the operation degrades until someone else figures it out. The spreadsheet works because of the person, not despite them.
This is key-person dependency at the system level. It is a different problem from key-person dependency in relationships or expertise. A system that requires a specific person to function reliably is not a system.
2. Answering a basic question requires an investigation
A customer asks how much stock you have of a product. You know it is in the spreadsheet somewhere. Finding the current number requires opening the right file, checking the date it was last updated, cross-referencing it against recent orders, and doing a mental calculation to account for what has shipped since the last update.
If answering a question about your own stock requires significant manual work, the data is not actually giving you operational visibility. It is a record of what happened, not a live picture of where things stand.
A well-run distribution operation should be able to answer inventory, order status, and margin questions in under a minute without routing them through a single person.
3. You do data reconciliation before you trust your own numbers
Before the weekly review, someone in the team spends time cross-checking figures. Orders from one sheet against invoices from another. Inventory figures against what was physically counted. Purchase orders against what was confirmed by suppliers.
Reconciliation is often treated as a normal part of operations. In a spreadsheet environment it is. But it is also a fixed cost that a business is paying every week to compensate for the fact that the same data exists in multiple places and gets updated independently.
When the business scale is small enough, this cost is manageable. When the volume of transactions increases, the reconciliation cost scales with it. Eventually it consumes meaningful headcount just to maintain baseline accuracy.
4. You have multiple versions of the same file
"Supplier Quotes Q1 2026," "Supplier Quotes Q1 2026 FINAL," "Supplier Quotes Q1 2026 FINAL v2," "Supplier Quotes Q1 2026 updated March." If any of these names look familiar, the business is running on a versioning problem.
Multiple versions of the same spreadsheet exist because the original was sent to someone, they edited their copy, and now there are two or more parallel versions of what should be a single source of truth. Merging them requires someone to go through both manually.
At low volume this is an annoyance. At high volume it is an error generator. Decisions get made using the wrong version. Data entered into one file does not appear in another.
5. Errors are discovered downstream, not at the point of entry
A pricing error on a quote gets caught when the customer queries the invoice. A stock discrepancy is discovered when a driver arrives to collect goods that are not there. A supplier delivery is missed because it was logged in the wrong tab and nobody saw it.
In a spreadsheet environment, there are few guardrails at the point of data entry. A cell can accept any value. A formula can be accidentally overwritten. A row can be deleted with no audit trail.
The implication is that catching mistakes happens later in the process, often after the error has created a customer-facing problem. The further downstream an error is caught, the more it costs to fix.
6. Automation has been bolted onto the spreadsheets
Macros that run on open. Zapier workflows triggered when a row is added. Power Automate flows that send emails when a column changes. These were built one at a time to solve specific friction points, and they work until something changes in the spreadsheet structure and breaks them.
This is one of the clearest signals that the business has grown past what spreadsheets were designed to do. When you are engineering automations around a spreadsheet to make it behave like a database, the right solution is usually an actual database with an interface built for your workflow, not a more complex spreadsheet with more scripts attached.
7. Onboarding a new team member takes weeks because of the spreadsheets
New operations hires need to be shown "the way we do it." There is no documentation that captures how the spreadsheet system works because it evolved organically over time and nobody ever wrote it down. The existing team members explain it verbally and the new hire learns by making mistakes.
A system that cannot be onboarded efficiently is a system that creates permanent dependency on people who already know it. It also means that growth requires institutional knowledge transfer, which slows hiring velocity at exactly the moment when the business wants to move fast.
What to do if several of these apply
Recognising the signals is straightforward. Knowing exactly which one to address first, and what the right solution looks like for your specific operation, requires looking at the actual workflow rather than assuming.
Most distribution businesses that have outgrown spreadsheets do not need an off-the-shelf ERP. They need a purpose-built internal tool that reflects how their operation actually works, without the complexity of a system designed for a business ten times their size.
The right starting point is a clear picture of where coordination is breaking down and what fixing it is actually worth. That is what a Workflow Audit produces.
