Routing, ordering and accounts are the unglamorous core of food distribution — and the spreadsheets and legacy tools holding them together have a hard ceiling. The question is whether you hit it before or after it costs you a customer.

UK food distribution is a high-volume, low-margin business that runs on coordination. A distributor might serve a few hundred venues across a region, each with different order patterns, delivery windows and credit terms, all fulfilled from one warehouse by a handful of vans on tight morning routes. The work is operational, not clever — but the coordination it demands is genuinely hard, and most distributors are doing it with tools that were never built for it.

Distribution is an operations problem

The instinct, when a distributor outgrows pen and paper, is to reach for accounting software. That’s a category error. Accounting tells you what happened after the fact; distribution lives or dies on what’s happening right now — which orders are in, what’s on each van, whether the 6am route accounts for the customer who moved their delivery window yesterday.

Treating distribution as an accounting problem is how you end up with a finance system bolted to a wall of spreadsheets, each one a workaround for something the finance system can’t see.

The spreadsheet ceiling

Spreadsheets are a genuine achievement. A good operations manager can run a surprisingly large distributor on a few well-built sheets, and many do. But there’s a ceiling, and it’s predictable.

It arrives when the business depends on a spreadsheet that only one person fully understands; when two people edit the same file and the routes diverge; when an order change at 5pm doesn’t reach the warehouse because it lived in an email, not a system. The spreadsheet didn’t fail — it simply ran out of the one thing it can’t provide: a single, shared, live source of truth.

What a distributor’s stack actually needs

The core is narrower than enterprise vendors would have you believe. A distributor doesn’t need everything — it needs these things to work together:

  • Ordering that customers can use directly, with their pricing and their products, instead of phone and email.
  • Routing that turns the day’s orders into sane van runs and adapts when they change.
  • Account management — credit terms, statements, pricing tiers — connected to the orders, not living in a separate ledger.
  • A warehouse view that reflects what’s actually been picked and loaded, in real time.

Get those four sharing one data model and most of the daily firefighting disappears, because the thing everyone was reconciling by hand is now just true by default.

Off-the-shelf vs built-for-you

There are generic ERPs that technically cover this. The problem is fit. A distributor’s edge is in the specifics — how it routes, how it prices, how it handles the regular who calls to add a tray of tomatoes after cut-off. Generic systems force those specifics into a shape that suits the software, and the operation bends to the tool instead of the other way around.

That’s the case for a stack built around how distribution actually works, by people who’ve spent time in the warehouse and the van rather than just the boardroom.

Where we’re pointing this

We’re building Estia for exactly this: a food distribution platform bringing routing, ordering and account management into one system built for the warehouse and the van. As a venture studio, we build and operate it ourselves — in active build with launch partners — because the only way to get distribution software right is alongside people running real routes.

If your distribution business is approaching the spreadsheet ceiling — or already past it — we’d like to hear about it.