Fragmented integration between systems: the invisible tax of silos

Operational Gap #4 of 5 | Series: What ERP Doesn't Solve

There is one question that reveals the real state of a company's technological architecture better than any IT audit: how long does it take to know the exact number of units available of a product when a customer calls?

If the answer includes phrases such as “I have to consult it and I'll call you”, “it depends on the shift I did the counting” or “wait until I look at it in another system”, the problem of data silos is already costing money.

Medium-sized Spanish companies operate in a fragmented technological ecosystem. The ERP manages finances, the CRM manages customers, e-commerce manages online sales, the HR system manages people, the PMS manages reservations or the MES manages production. Each system has its own data model, its own updating rate and its own logic.

And neither was born to talk to others.

51% of companies recognize that integration issues prevent them from taking advantage of their data. And 99% face challenges stemming from the complexity of their system ecosystem. [1]

The real cost of data silos

Data silos are not an abstract IT architecture problem. They translate into hours lost in manual reconciliation, errors in orders and invoices due to unsynchronized data, decisions made with incomplete information and customers who receive different answers depending on the channel.

Only 53% of SMEs integrate their ERP with CRM. [2] The remaining 47% have their customers updated in one system and the business conditions in another. When sales need to validate a customer's credit before closing an order, someone has to consult the ERP, someone the CRM and, if they don't match, someone has to reconcile.

In addition, 78% of companies believe that software vendors themselves make it difficult to access data to create dependency. [3] Whether they are right or not, the result is the same: limited APIs, poorly documented, or subject to additional licenses. Native integration is the exception, not the rule.

Where does this gap become critical

Omnichannel retail and ecommerce

Multichannel retail is where data silos become most evident. 74% of B2B customers expect real-time inventory visibility. [4] But if the ERP, online store, and point of sale aren't in sync, that visibility simply doesn't exist.

A small gap — as little as 5% in data during a high-volume campaign — can result in six-figure losses. [4] And resolving integration issues can take more than 14 weeks.

Hospitality

A medium-sized hotel or chain usually operates with multiple systems: PMS for reservations, revenue management, POS for restaurants, channel manager and accounting ERP. Each with its own database. [7]

Without integration, the numbers don't add up until the monthly close. Pricing decisions are made with outdated data and purchases are not aligned with the occupancy forecast.

Industrial manufacturing

In manufacturing, critical integration follows the PLM → ERP → MES flow. Engineering changes must be reflected in the bill of materials and in production orders.

Without that connection, what is produced may not match what was designed. In regulated sectors — such as food, aeronautics or medical devices — this is not just an operational problem, but a direct compliance risk.

The composable ERP approach as a solution

The answer to this problem has a name: composable ERP. An approach in which each business function uses the best tool for its use case, while an integration layer ensures that all systems communicate without needing to replace them. [5]

76% of IT managers are already familiar with this concept and 84% plan to implement it. [6]

In practice, tools such as n8n or Make act as that integration hub: they connect the APIs of each system, synchronizing data at the pace required by the business and transforming formats when necessary. Supabase can function as a unified data layer where all systems converge.

The result is a single source of truth, without replacing existing infrastructure.

In addition, the regulatory context in Spain adds urgency. The convergence of SII [9], mandatory B2B electronic invoicing [10] and VERIFACTU requires many companies to manage multiple tax reporting formats.

Companies that solve their data silos don't just gain operational efficiency: they also simplify their regulatory compliance.

The right question for direction

System integration is often perceived as a technical problem that IT must solve. But useful reframing is economic: how much does it cost each week for systems not to talk to each other?

If several people spend hours reconciling data, the calculation is simple: hours multiplied by cost.

An integration architecture based on tools such as n8n, Make and Supabase can solve this problem in 4—6 weeks, without replacing existing systems and with a measurable return in months.

The decision is not technical. It is cost-effective.

Bibliographic references

Methodological note: The numerical citations in superscript [N] refer to the APA references listed below. All statistics have been verified in the original sources before inclusion.

[1] Panorama Consulting. (2024). ERP Report 2024. Cited in: SaasWorthy. (2024) .Top 50 ERP Statistics That Will Define 2025. SaasWorthy. https://www.saasworthy.com/blog/top-erp-statistics — 51% of companies recognize that integration issues prevent them from taking advantage of their data; 99% face data complexity challenges.

[2] Aberdeen Group. Quoted in: SaasWorthy. (2024). https://www.saasworthy.com/blog/top-erp-statistics — Only 53% of SMEs integrate their ERP with CRM. The remaining 47% manage these two data sources manually or disconnected.

[3] SaaS worthy. (2024). Top 50 ERP Statistics That Will Define 2025. SaasWorthy Blog. https://www.saasworthy.com/blog/top-erp-statistics — 78% of companies believe that software vendors intentionally complicate access to data to create dependency.

[4] APPS and Connect. (2024). ERP-eCommerce Integration: Fix Sync Failures for Retailers.appsConnect. https://www.appseconnect.com/the-fastest-way-for-us-retailers-to-fix-erp-ecommerce-sync-failures/ — 74% of B2B customers expect real-time inventory visibility; a 5% error in synchronization can result in six-figure campaign losses.

[5] Infosys Cobalt. (2023). Composable ERP — New Era of ERP. Infosys. https://blogs.infosys.com/infosys-cobalt/public-cloud/composable-erp-new-era-of-erp.html — Description of the composable ERP approach and its adoption in mid-market organizations.

[6] ERP Today. (2024). The Indispensable Link: Integration, Composable Architectures and Value Maximization. ERP Today. https://erp.today/the-indispensable-link-integration-composable-architectures-and-value-maximisation-for-modern-cfos-within-erp-systems/ — 76% of IT managers are aware of the decomposable ERP concept and 84% plan to implement it.

[7] Net Suite. (2024). 6 Business Benefits of System Integration in Hospitality.netSuite. https://www.netsuite.com/portal/resource/articles/erp/system-integration-hospitality.shtml — Analysis of hotel system silos and the operational impact of the disconnect between PMS, POS and ERP.

[8] Bizowie. (2024). Omnichannel Retail ERP: Connecting POS, eCommerce, and Warehouse. Bizowie. https://bizowie.com/omnichannel-retail-erp-connecting-pos-ecommerce-and-warehouse — Omnichannel retail requires real-time synchronization between POS, ecommerce and warehouse that standard ERPs don't offer as standard.

[9] Holded. (2024). SII: what it is, how to do it and who is obligated.Holded. https://www.holded.com/es/blog/todo-lo-que-necesitas-saber-sobre-el-sii — Description of Immediate Information Supply (SII) and its implications for medium-sized companies in Spain.

[10] Connect EDI. (2026). B2B electronic invoicing will be mandatory in 2026.Connect EDI. https://conectaedi.com/factura-electronica-b2b-obligatoria-guia-2026/ — B2B electronic invoicing becomes mandatory in Spain, affecting all companies regardless of their size.

‍