Blogs
Six systems, one business: the real cost of software that does not talk
A typical food wholesaler runs orders, pricing, stock, routing, invoicing and credit control as separate systems that do not share data with each other, so someone re-enters the same information by hand between them every day. The real cost is not any one system's price - it is the labour spent moving information that should already be in one place.
What six systems actually looks like in practice
A single day's order usually passes through more separate tools than anyone in the business would list if asked directly:
- orders, arriving on WhatsApp, by phone, or written on a pad by the till
- pricing, living in a spreadsheet, or in someone's head, as its own separate thing
- stock, checked by walking round the warehouse because the ordering system does not know what is actually on the shelf
- routes, planned on paper or a whiteboard
- invoicing, raised in an accounts package once everything else has already happened, typed in again from whatever was actually delivered
- credit control, a diary and a memory for who still owes what
None of those six is wrong on its own. None of them was built to know the other five exist.
Where the real cost sits
The cost is not the software subscriptions, most of which are modest on their own. It is the person, or the half a person's time, spent moving information between the six: typing an order that arrived on WhatsApp into a system that cannot read WhatsApp, checking stock by eye because the ordering system does not know what is actually on the shelf, re-keying what was actually delivered into the accounts package because the pick sheet and the invoice live in different places and nothing connects them automatically.
One wholesaler's own four years of trading produced 47,936 messages and 197,758 individual order lines, almost all of it starting life on WhatsApp before it went anywhere else - a genuinely large amount of real business information that six disconnected systems have no way of sharing, so a meaningful share of it gets manually copied, or worse, simply not copied and left to live only in the messages themselves.
None of the six systems is wrong on its own. None of them was built knowing the other five exist.
A day in six systems, traced through
Follow one order through a business running all six separately and the pattern is obvious. A kitchen sends its order on WhatsApp at ten at night. Someone reads it in the morning and types it into an ordering spreadsheet, checking stock by walking round the warehouse because the spreadsheet has no idea what is actually on the shelf. The pricing gets looked up separately, from memory or a second sheet, because the ordering spreadsheet does not hold customer-specific rates either. A picker works from a printed sheet generated from the order, which may or may not match what actually gets loaded if something runs short. The driver delivers whatever was actually loaded, which the accounts package never sees until someone manually raises an invoice from the picking sheet rather than from the order, at which point any difference between what was ordered, what was picked and what was delivered has to be reconciled by a person who was not there for any of the three.
Every one of those handoffs is a place a mistake can enter and nobody catches it until a customer queries an invoice weeks later. None of the six systems did anything wrong. Each one did exactly the job it was bought to do. The cost is entirely in the gaps between them, and it is paid every single day, in minutes that add up, by whoever in the business ends up being the connective tissue between six tools that were never introduced to each other.
Where the errors actually come from
Every manual re-entry is a chance for the same information to become two slightly different things - a price typed correctly into the ordering spreadsheet and typed wrong into the invoice, a delivery quantity that matches the pick sheet but not what actually left the van, a customer name spelled one way in the accounts package and another way everywhere else, of which one wholesaler's own book carries 1,241 separate kitchen names for its actual customer list, purely from how differently the same business gets written down in different places. Every one of those small mismatches is a small piece of trust lost with a customer, an invoice query, or a stock figure that turns out to be wrong the day it actually matters.
What actually fixes it, and what does not
The honest fix is not a seventh system layered on top of the other six, which is how a lot of wholesale software ends up sold and how a lot of it ends up half-used. It is one system that already does the six jobs on the same data, so an order priced correctly is the same order that gets picked, routed, invoiced and chased, without anyone retyping it in between. The accounts package is the one exception worth keeping separate, because it already does its job well and a business's financial records are the last thing worth migrating for convenience - the right answer there is a system that reads and writes to it, not one that replaces it.
Plainly
What it will not do on its own
- It does not replace the accounts package already in use - it sits beside Xero or a similar system, reading and writing to it, not migrating years of financial records.
- It will not fix a business process that was genuinely broken before the software arrived - it removes the re-entry, not the underlying decision-making.
- It does not do payroll, and has no plans to.
- Bringing six systems' worth of history into one place takes real setup time at the start - it is not a same-day switch, whatever the pitch for any system promises.
Questions people ask
- Why do wholesalers end up running so many separate systems?
- Each one was usually adopted to solve a single problem, a spreadsheet for pricing, an accounts package for invoicing, a whiteboard for routes, at the point that problem became painful enough to fix. None of them was chosen with the other systems in mind, so none of them share data, and a business ends up with six or more separate tools that all need a person to keep in sync by hand.
- What is the actual cost of running disconnected wholesale systems?
- Mostly labour rather than subscription fees: the time spent re-entering the same order, price or delivery information into a second or third system by hand, and the errors that creep in every time information is typed again rather than shared automatically between systems that already have it.
- Do I have to replace my accounts package to fix this?
- No, and a system that asks you to is worth being cautious of. The accounts package is usually the one system worth keeping exactly where it is, with everything else reading from and writing to it rather than replacing it.
- How long does it take to consolidate several wholesale systems into one?
- Longer than a same-day switch, in practice, because years of pricing arrangements, customer records and history genuinely need to be brought across correctly rather than assumed. Any promise of an instant switch usually means the detail is being skipped rather than solved.
Read next
Give us one night.
Send us one evening's orders. We run the night next to you. In the morning you compare the two.