Nobody plans to run a distribution business on spreadsheets. It happens gradually: the accounts package handles the invoices, a workbook handles the routes, another one handles the price lists, and for years the combination genuinely works. The awkward truth about having outgrown spreadsheets is that there is no alarm for it — the tools do not break, they just start charging more and more hours to do the same job. What follows are seven signs that the charge has become real, why each one happens, and what the ceiling looks like from the other side. The count matters less than the severity: one sign that touches cash or continuity can outweigh three that merely annoy.
1. The same order is typed more than once
An order arrives by phone or email, goes into the day’s sheet, gets copied to a pick list, and is typed a third time into the accounts package as an invoice. Every retype is a chance for a wrong quantity, a wrong price or a missed line — and the errors surface at the worst possible point, as a dispute after delivery. The tell: someone in the office can describe their morning as “getting yesterday into the system”.
2. Nobody fully trusts the stock figure
The warehouse count, the spreadsheet and the accounts package each hold a stock number, and they drift apart between counts because sales, returns, transfers and write-offs post to them at different times — or not at all. Once the figure is doubted, people compensate: extra safety stock, a walk to the racking to check before confirming an order, a monthly count that eats a weekend. Doubt is expensive even when the number turns out right.
3. Customer-specific pricing lives in people’s heads
Contract prices, volume deals and “what we agreed with him in March” sit in a sheet only one person really understands, so quoting depends on that person being in the room. Invoice queries multiply because the price charged and the price agreed drift apart, and every query costs a credit note and a little trust.
4. Invoices go out days after the goods did
When invoicing is a back-office typing job, it queues behind everything else. The gap between delivery and invoice quietly stretches payment terms — the clock most customers pay on starts at the invoice, not the drop — and it multiplies disputes, because queries land when nobody quite remembers the delivery. Watching the invoicing backlog grow across the week is watching working capital leak.
5. “Where’s the van?” takes phone calls to answer
The route plan is a printout, so once vehicles leave the yard the plan stops being information and becomes hope. Delivery confirmations arrive as paper at day end; a customer asking for an ETA triggers a call to the driver; a signature that would settle a dispute is in a cab, a folder, or gone. The office spends its afternoon reconstructing a day it could have been watching.
6. The end of day is a marathon
Cash counted against a sheet, cheques matched to invoices, returns booked by hand, van stock guessed until the next count — in a cash-heavy operation the day-end can easily run to hours, and it lands on the most senior person in the room because only they can arbitrate the discrepancies. (If this sign is the one that stings, the day-end deserves its own diagnosis — the variance usually has traceable sources.)
7. One person is the system
The formulas, the file locations, the workarounds, which sheet is the “real” one — it all lives with one person, and their holiday is an operational risk. Spreadsheets rarely enforce an end-to-end operational process on their own; mostly they memorialise one person’s process. Growth means more people touching the files, which means versions, and versions mean the Monday argument about whose copy is right. And behind the versions sits the control problem. Modern spreadsheet platforms can offer sharing controls and version history — but spreadsheet-led operations typically lack what the operating record actually needs: enforced workflow (nothing stops an edit going straight to consequences), role-based operational permissions (who may change a price versus who may view it), and a single auditable process that survives the file being emailed, downloaded and copied. Spreadsheet error is a well-documented risk in its own right — the European Spreadsheet Risk Interest Group’s research has spent years cataloguing how it happens — and the common thread is exactly this: important numbers, weak controls around them.
Have you outgrown spreadsheets? The self-assessment
Put a baseline on it before changing anything
Whichever signs bite, measure them for a fortnight before touching a system. Six numbers are enough: hours spent re-keying per week; average days from delivery to invoice; the number and value of stock adjustments at the last count; day-end duration; order errors reaching customers per week; and how many live copies of the “master” spreadsheet exist. The baseline turns the migration case from a feeling into arithmetic — and it is what you will measure the new system against six months later.
What the other side of the ceiling looks like
The fix for a back office that has outgrown spreadsheets is not a better spreadsheet — and it is usually not a bigger system swallowing everything either. It helps to be precise about the three roles in play: the accounting ledger (invoices, payments, the books — a job the accounts package can often keep doing well); the operational record (orders, stock, pricing, routes, deliveries — the part currently scattered across workbooks, and the part that needs a real system); and any genuine specialist systems a business already relies on, which should integrate rather than be forcibly replaced. The spreadsheets are what goes; the ledger’s role is a choice, not a casualty. The fix, concretely, is putting the operational record somewhere that shares one spine with the ledger. On RouteMagic, an order is captured once — by telesales, a rep in the field, or the customer themselves — with the right price list and credit limit enforced at capture, then flows through pick, load, delivery and invoice as one record: the heart of joined-up order management. Stock moves post as they happen, so the inventory figure is the live one, not last count plus guesswork. Drivers capture proof of delivery and can invoice at the doorstep, so the causes behind sign 4 and sign 5 shrink together — the invoice no longer queues behind the office, and the delivery evidence exists the moment the drop completes. And the accounts package can stay, continuing as the financial ledger where that is the right architecture: approved invoices, credit notes and payments synchronise through two-way accounting integrations with the packages distributors already run — Xero, Sage 50, QuickBooks and others — so the ledger keeps its role without anyone retyping into it.
The scale of the reclaimed time is operation-specific, but it is real enough to be published: in RouteMagic’s published Bits ’N’ Bobs case study, the convenience-store products supplier reports 2–3 hours of admin time saved per day — one operation’s result, not a promise, but a fair indication of what sign 1 and sign 6 cost when nobody is counting.
Conclusion
The tipping point is not “how advanced is the spreadsheet?” — clever workbooks are usually evidence for the ceiling, not against it. The real question is how much operational dependency, delay and risk now sits around the files: hours re-keying, days between delivery and invoice, stock figures nobody quite trusts, a day-end that eats the most senior person in the room, and a system that lives in one head. That is why the baseline matters more than the sign count — measure the six numbers for a fortnight and the case stops being a feeling. And keep the roles straight when acting on it: the spreadsheets are what goes; the accounting ledger can often continue as the ledger while a proper operational record takes over orders, stock, routes and deliveries. If one sign materially touches cash, stock or continuity, quantify it now — before it becomes the next workaround that someone has to remember.
