A brand adds a marketplace, then a 3PL, then a returns platform, then a PIM. Each connection gets built by whoever was nearest the problem that month, and each one works. Five years later there are a dozen people who understand one connection well and nobody who can draw the whole thing.
This isn’t a failure of any individual decision. Every connection got made for a reason, usually a good one, usually under time pressure. The gap sits above the individual integrations, in the space nobody was asked to own.
Three parties, three versions of how it currently works
The cost appears when more than one party has to touch the same systems at once. An internal team is mid-build while a new platform is being onboarded. A consultant arrives to fix something specific and gets briefed by whoever happens to be free that week. Everyone is working from their own understanding of the current state, because no diagram exists that anyone has agreed is accurate.
You can test this in about ten minutes. Ask three people who know the stack to draw it on a whiteboard separately, then compare. The disagreements are never about the big boxes. They’re about direction of travel, what happens on failure, and which connection is still live.
The question that stops the room
Ask a brand which system owns the price for a given SKU and you’ll usually get an answer. Ask what happens when two systems disagree about it, and the answer gets slower. Ask the same about stock, about product status, about the tax code, and at some point somebody says they’ll need to check with the person who built it.
Field-level ownership is where undocumented estates actually hurt. Not in the connections themselves, which tend to be fine, but in the overlaps: two systems both writing to the same field, in different formats, on different schedules, with a last-write-wins rule nobody chose deliberately. That’s the bug you find at 4pm on a Friday during peak, and it’s the one that takes three days to trace because the trace has to be rebuilt from scratch every time.
Why it never gets written down
Mapping has no natural owner. It isn’t a sprint goal, it doesn’t close a ticket, and it belongs to no single team. The person who understood the last integration best has usually moved on to the next one, or moved on entirely.
It’s also the first thing cut. When a project runs late, documentation is the line item that can be dropped without anything visibly breaking that quarter. The cost lands eighteen months later, on someone else, in a different budget. That’s a structural incentive problem rather than a discipline problem, which is why telling teams to document more has never worked.
What a usable map contains
Most estates have some form of diagram somewhere. The reason it doesn’t help is that it stops at the boxes and arrows, which is the part everyone already knows.
A map that earns its place covers:
Every live connection, including the ones built for a project that ended
Direction of travel per field, and which system wins a conflict
Sync frequency and what queues up behind a failure
Who owns the credentials, and what expires when
Which environment the connection exists in, and whether the sandbox matches production
That last one gets skipped more than any other. Sandbox and test environments that are current, rather than merely present, are the cheapest way to find out where the picture is wrong before production tells you.
The map matters most when something is about to change
A replatform, a migration, an ERP swap, a new marketplace. These are the moments several parties need to agree on how the system behaves now before anyone can safely change it. Discovery on a replatform is largely the cost of rebuilding a map that should already have existed, and it gets paid at consultancy day rates by a brand that already knew the answers somewhere in the building.
The same applies to a new hire. Someone senior joining an ecommerce or systems team spends their first two months asking five people the same question and reconciling the answers themselves. Handing them an accurate map turns that into a week.
A map nobody maintains is worse than none at all
Here’s the uncomfortable part. A diagram last updated in 2023 is actively dangerous, because people trust it. They plan against it, scope against it, and brief vendors from it. An absent map makes everyone check. A stale one makes everyone confident.
So the maintenance question has to be answered at the same time as the mapping question. Someone owns it, it gets reviewed when a connection changes rather than annually, and it lives where the people who need it already work. A map maintained in a tool only one person has a licence for has already started rotting.
Why we’re the ones saying this
Commerce Thinking shares co-founders with HighCohesion, an iPaaS platform built off years of hands-on integration work. Integrations aren’t an add-on service for us, they’re where the firm started. We’ve built this picture for 30+ brands, across most platform combinations you’d expect to meet.
If nobody internally has the time or the remit to own the mapping, that’s the work we do, and it’s usually faster than the internal version because we’ve seen the same shapes before.
Every new system and every new consultant is a chance to add to a shared map or to quietly work around the absence of one. The first costs a little time now. The second costs considerably more later, usually to someone who wasn’t in the room when the original decision got made.