Integration

The eCommerce Integration Trap

Connecting your website to your ERP sounds simple. Here's why it goes wrong â€” and how to avoid the common pitfalls.

Craig Blackman·10 May 2026·5 min read

You need to sell online. So you look at eCommerce platforms. Shopify looks simple. WooCommerce looks cheap. BigCommerce looks powerful. You pick one, set it up, and launch.

Then the first 10 orders come in and you realise: your eCommerce platform doesn't understand your business.

The Problem: You're Not a Generic Retailer

Standard eCommerce platforms are built for businesses that sell finished products. You pick an item, you add to cart, you check out. The system assumes inventory is simple: you have X units, you ship them to the customer, you have X-1 units left.

Your business is different. You don't just sell a product. You sell an idea with customisation. An order isn't "1 x T-shirt." It's:

Blank garment (choose size, colour, fit)
Decoration design (upload art, approve proof, revisions)
Decoration method (embroidery vs print vs sublimation)
Delivery location (multiple locations if it's a corporate order)
Special packaging or instructions

A standard eCommerce platform can handle steps 1 and 4. It can sort of handle step 5. But steps 2 and 3 break it completely.

Where eCommerce fulfilment breaks down for decorated goods businesses

The Customisation Problem

Your customer uploads artwork. The system can't validate it (is it the right format? High enough resolution? Will it work for embroidery?). So you have to manually review every single order before you can start production. That's not efficiency. That's a manual workaround that defeats the purpose of having a website.

The Inventory Problem

Your blanks inventory is in your ERP. Your eCommerce platform doesn't know about it. So a customer orders a size-M red t-shirt and the system says it's in stock. Two hours later, your warehouse tells you you're actually out. You have to email the customer and apologise.

Even if you manually update inventory twice a day, you still have the 12-hour window where the system lies.

The Workflow Problem

An order comes in. Your eCommerce system confirms payment and sends an order confirmation to the customer. But your production system hasn't seen it yet because the eCommerce platform doesn't talk to your ERP. So you have to manually log into the eCommerce system, find the order, and email it to your production team.

If you're efficient, this adds 2-3 minutes per order. On 50 orders a day, that's 2-3 hours of manual work every day.

This is not an eCommerce fulfilment problem — it is a systems integration problem that shows up at fulfilment. The eCommerce platform captures the order. The ERP or MIS needs to execute it. When those two systems are not connected, a person in the middle is the integration.

The Reporting Problem

You want to know: "How many orders came through the website this month, versus from the phone?" Your eCommerce system has part of the answer. Your ERP has the rest. They don't talk to each other, so you manually piece together reports from both systems.

The false promise: eCommerce integration will fix the fulfilment problem

When you realise the eCommerce platform doesn't work as-is, you think: "I just need to integrate it with my ERP."

You ask the eCommerce vendor: "Can you integrate with our ERP?" They say yes. You ask for a quote. It's £20k–50k. The timeline is 3–6 months. By now, you've already launched the website and your customers are experiencing the broken workflow.

And here's the thing: even after the integration is built, the customisation problem isn't solved. Your system still can't validate artwork or understand your production workflow. The integration just passes data between two systems that weren't designed for your business.

How to avoid the eCommerce fulfilment trap

This doesn't mean you shouldn't have an eCommerce platform. It means you should have chosen differently.

1. Start with your workflow, not the platform

Map out your actual order process. From the moment a customer starts thinking about ordering, all the way through to delivery and invoice. What information do you need to collect? What decisions happen at each step? Where does customisation happen?

Once you know your workflow, you can evaluate whether a platform supports it. Most don't.

2. Look for platforms built for your industry

There are eCommerce platforms specifically built for print, embroidery, and decorated apparel. They understand artwork upload. They understand customisation. They integrate with production systems out of the box.

They're not as trendy as Shopify. But they're cheaper to implement, they work faster, and they don't require a £40k integration project to talk to your ERP.

B2B order management is another area where generic platforms fall short. If you have wholesale customers placing repeat orders, a B2B portal with account pricing, order history, and direct-to-production routing is what makes that relationship scalable — not a Shopify store with a wholesale password.

3. Require integration as a starting point, not an afterthought

Before you buy any eCommerce platform, ask: "How does this integrate with our ERP?" And don't accept "it can integrate." Get specifics. What data syncs? How often? What's the cost? What happens if there's an error?

If You've Already Made This Mistake

You're not alone. This is one of the most expensive mistakes I see in this sector. The good news: it's fixable.

The options are:

Build the integration: Accept the cost and timeline. This is the "push through" approach.
Change the eCommerce platform: Switch to a platform designed for your industry. This has migration costs and pain, but it might be cheaper than the integration.
Optimise your current process: Live with the manual workflow, but make it more efficient. This isn't a solution—it's a temporary survival strategy while you plan for option 1 or 2.

Plain English. No jargon. No vendor agenda.

A Clarity Audit maps your actual operations, identifies the changes that will make the biggest difference, and gives you a plan you can act on. No reports you'll never read. No recommendations you can't implement.

See Clarity