GoKawiilWhat sounds like a small API task is usually a full integration problem: sequencing, sync vs async, edge cases, and an old system nobody fully trusts.
Four words show up in almost every eCommerce project we take on here at Neuralab: “Just connect it to our ERP.“ They usually drop near the end of a kickoff call, tossed out as casually as asking for the Wi-Fi password.
The word doing all the heavy lifting (and all the damage) there is just. It’s the word that turns a monolithic beast of a legacy system that nobody in the room fully understands into a neat little line item some project manager expects to close in a two-week sprint.
I want to make an argument that sounds painfully obvious once you say it out loud, yet gets completely ignored on most projects: building a new store and connecting it to the systems already running the business are not the same sport. Heck, they’re barely the same project!
A new storefront is greenfield. Clear ground with no legacy baggage. You plan the architecture and data model upfront and mostly hold to the plan. An integration with an existing ERP or CRM is brownfield by default. It’s an archaeological dig into an old system you didn’t build, that’s poorly structured, still running, and troublesome in ways nobody ever bothered to write down. Treat the second like the first and you get an integration that works beautifully in the demo and completely shits the bed the first time a real order does something unexpected.
There is a fix, and it comes down to timing more than technique. I’ll get to it, but first you need to see what you’re actually up against.
The integration layer breaks because no one owns the handoffs between systems
Let’s start with what the integration layer actually is. The storefront takes the order – the gateway authorizes the cash – the tax engine figures out the state’s cut – the ERP opens a sales order and reserves stock – accounting generates an invoice – the warehouse picks and packs – the CRM logs it all so customer support has something to stare at next week.
Every single one of those systems has an owner. But the handoff between them has no real owner at all. That’s what the integration layer is: the unowned seams. And seams are exactly where the fabric tears, because it’s the one place where two systems that were designed in total isolation have to agree on something in real-time, having never formally met.
Sometimes system takes the money a beat before the order exists
... continue reading