Why Systems Don't Talk (And What It Costs)

You know the feeling

An order comes in through your website. Someone in the office has to manually re-key it into your ERP because your eCommerce platform doesn't talk to it. A customer changes their delivery address. Three people have to be emailed to update the system. Stock levels are wrong because your warehouse management doesn't sync with your inventory. A despatch goes out with the wrong item because the picking system doesn't know what you actually have.

You've built a successful business. Your systems work. But they don't work together.

The frustrating part? You're not alone. This is the most common operational problem I see in print, embroidery, workwear, and promotional merchandise businesses.

The Hidden Cost

Disconnected systems don't feel like a serious problem. They're just a workaround. A bit of manual work. Extra emails. The kind of friction you've learned to live with.

But when you measure it, the numbers are staggering:

• 3–6 hours per week lost to manual re-keying between your eCommerce platform and ERP
• 2–4 hours per week spent on manual invoicing and reconciliation
• 3–5% of inbound stock at risk from inventory errors that don't sync
• 1–3% of orders affected by picking and despatch mistakes

On a £2m business, that's roughly £40k–80k per year in lost productivity and error correction alone. Not including the customer dissatisfaction when orders go wrong.

Why This Happens

Systems don't fail to talk to each other by accident. There's usually a reason:

1. They weren't chosen to work together

Your ERP was implemented 5 years ago. Your eCommerce platform was added last year because you needed to sell online. No one asked whether they could integrate. They just assumed they could.

The ERP vendor says "Yes, integration is possible." What they don't say is that it requires custom development, costs £15k, and takes 4 months.

2. The integration was too expensive or complex

You got a quote for the integration. It was £20k. Your eCommerce platform needed to be heavily customized. The timeline was uncertain. So you shelved it and accepted the manual workaround instead.

That decision made sense at the time. But the cost of the workaround has compounded every month since.

3. Your data isn't clean enough to integrate

Your ERP has 10 years of data in it, and a lot of it is messy. Duplicate products. Inconsistent naming conventions. Missing information. Before any integration can work, that data needs to be cleaned up—and that's a project in itself.

What Actually Happens

Most businesses in this situation do one of three things:

Option 1: Accept the workaround

You keep doing the manual work. It becomes the cost of doing business. You hire someone to manage it. That person stays very busy but never feels like they're catching up.

Option 2: Try to build an integration without a plan

You hire a developer or a systems integrator. They start building without a clear specification of what needs to happen. Six months in, you've spent £30k and it still doesn't work the way you expected. The project stalls.

Option 3: Replace one of the systems

You decide the eCommerce platform was a mistake. You choose a different one that has better ERP integration. By the time you've migrated data, retrained staff, and got the new system live, you've spent £60k and lost 4 months of productivity.

How to Fix It (Without Panicking)

The good news: disconnected systems can almost always be fixed. The bad news: it requires honesty about what you actually have and what integration actually means.

Step 1: Understand what you have

What systems do you actually run? What does each one do? How do they connect (or not connect) today? Who's doing the manual work, and how much time is it taking?

Step 2: Define what "integration" actually means

Integration isn't a binary thing. It's not just "connected" or "disconnected." There are degrees of integration—and different levels cost different amounts.

Does your eCommerce platform need to push every order to your ERP automatically? Or just high-value orders? Does inventory need to sync in real time, or is a twice-daily batch update enough? Does every product attribute need to match, or just SKU and price?

These are design questions, not technical ones. But they determine whether your integration costs £5k or £50k.

Step 3: Decide on the approach

Once you know what you have and what you need, you have options:

• Native integration: If both systems have built-in connectors, use them
• Middleware: A third-party platform that talks to both systems (Zapier, Make, etc.)
• Custom integration: A developer builds the connection to your exact specification
• Process redesign: Sometimes the cheapest fix is to change how the systems are used, not build an integration

The Right Starting Point

The mistake most businesses make is jumping straight to "fix the systems" without understanding what they actually have or what they actually need.

The right starting point is to sit down with someone who understands both your business and your technology, and answer three questions:

1. What's actually broken about the way things work now?
2. What would "fixed" look like?
3. What's the cheapest way to get there?

That's what an operational audit does. Not a systems audit. Not a technical review. A business-focused conversation about what's costing you money and what you should do about it.