- Home
- Consulting
- Integrations
Frictionless systems integration.
ERP, CRM, e-commerce, marketplaces and legacy systems connected so orders, inventory, pricing and tax data flow in real time, through APIs, events, iPaaS or dedicated connectors.
We integrate with
- SAP
- Salesforce
- MuleSoft
- VTEX
- TOTVS Protheus
- Kafka
Integration is the invisible layer where a digital project lives or dies. Every connector is built with idempotency, retry, a dead-letter queue and reconciliation from day one, not patched in later.
Three ways to integrate, and when to use each
We choose the right model for the scenario, with no silver bullet. Many operations combine all three.
Point-to-point, via API
One system talks directly to another. Simple and inexpensive for a few stable integrations, but it turns into a tangle as systems multiply.
- Fast to deliver
- Ideal for one or two integrations
- Dedicated connectors
Middleware and iPaaS
A central layer orchestrates the exchanges with reusable APIs, governance and observability. Suited to meshes with many systems and several teams consuming the same APIs.
- Reusable, layered APIs
- Centralized governance and security
- Scales across teams
Event-driven
Systems exchange asynchronous messages via Kafka or RabbitMQ, each at its own pace, with idempotency and a dead-letter queue.
- Resilience and decoupling
- High volume, multiple consumers
- Auditable event log
One hub at the center, each system at its own pace
ERP, CRM and legacy systems publish through the hub; e-commerce, marketplaces, payments and logistics consume with idempotency, retry and reconciliation.
- ERPSAP, Protheus, Bling, Tiny
- Legacy systemsDedicated connectors
- CRMSalesforce, HubSpot
- APIs and webhooksVersioned contracts
- Integration hubiPaaS or events
- E-commerceVTEX, Salesforce, Shopify
- MarketplacesCatalog, orders, inventory
- PaymentsGateway, fraud prevention, PIX
- LogisticsWMS, tracking, fulfillment
- Analytics and BIEvents and reports
- WhatsAppCCX Messages
Illustrative architecture. The actual design comes from the systems map built during discovery.
Integrations CCX delivers end to end
Each practice has a page with a reference architecture and frequently asked questions.
SAP and e-commerce integration
SAP S/4HANA and Commerce Cloud integrated with VTEX, Shopify, Salesforce and marketplaces via SAP CPI, BTP and events.
Protheus and e-commerce integration
TOTVS Protheus connected to e-commerce and marketplaces for orders, inventory, pricing, tax and logistics, with no stuck queues.
MuleSoft consulting
API-led architecture with MuleSoft Anypoint: reusable APIs, governance, security and observability for enterprise integration.
Salesforce Data Cloud
Data from every channel unified in Data Cloud to activate audiences across marketing, commerce and customer service.
How we run an integration project
- 1
Discovery
Systems map, master data, business events and the source of truth for each piece of data.
- 2
Architecture
Integration model, whether events, iPaaS or connectors, and versioned API contracts.
- 3
Build and go-live
Automated tests, isolated environments and a cutover with a parallel run and a rollback plan.
- 4
Support
Continuous monitoring, reconciliation and evolution of the mesh for new channels.
Enterprise systems integration: 2026 guide
What systems integration is, and why it decides the outcome of a digital project
It is the discipline of connecting software that was never designed to talk to each other, such as ERP, CRM, e-commerce, marketplaces, WMS, marketing and legacy systems, so that orders, inventory, prices, customers and tax invoices move between them consistently. A good-looking storefront that doesn't sync inventory with the ERP delivers a poor experience, even if everything else is flawless.
The project starts by mapping systems, master data and business events, and by defining who owns each piece of data: which system is the source of truth for inventory, and which for price.
ERP and e-commerce: SAP, Protheus, Bling and Tiny
It is the most common and most critical scenario in Brazilian digital retail. Orders that never reach the ERP, stale inventory, prices that diverge across channels and NF-e invoices that fail to issue all share the same cause: poorly architected integration.
The pattern that prevents overselling combines near-real-time sync with periodic reconciliation. For tax documents (NF-e, NFC-e and CT-e), the integration follows each state's rules and the correct issuing sequence.
Event-driven architecture: Kafka, RabbitMQ, idempotency and DLQ
Instead of the e-commerce waiting for the ERP to respond, it publishes an order-created event and moves on; ERP, WMS and CRM consume it at their own pace. One system going down doesn't take the others with it, multiple consumers work in parallel and the event log becomes the source of truth.
The pillars are idempotency, retry with exponential backoff, a dead-letter queue and event versioning, with the Outbox pattern so no event is lost between the database and the broker. It is the same engineering that runs CCX Messages and NexLog OS.
MuleSoft and iPaaS: when middleware pays for itself
The question isn't whether MuleSoft is good, but how many integrations you have and how much reuse and governance you need. For a few stable integrations, dedicated connectors are simpler. For dozens of systems and several teams consuming the same APIs, API-led architecture, in system, process and experience layers, pays for itself: each new integration reuses what already exists.
We implement MuleSoft when it is justified and dedicated connectors when it isn't, without pushing a license the operation doesn't need.
How to recognize a well-built integration
It shows in what doesn't happen: inventory doesn't oversell, orders don't disappear, tax issuing doesn't stall. And a new channel or marketplace comes in by reusing the existing mesh, instead of rebuilding everything from scratch.
Frequently asked questions
What is systems integration?
Connecting systems that don't talk to each other, such as ERP, CRM, e-commerce, marketplaces, WMS and legacy systems, so that order, inventory, price, customer and tax data flow in real time and consistently. CCX integrates through APIs, events, iPaaS and dedicated connectors.
How do you integrate an ERP with e-commerce without overselling stock?
With event-driven architecture, idempotency, retry and a dead-letter queue: each order or inventory event is processed only once and reconciled periodically. CCX connects SAP, Protheus, Bling and Tiny to VTEX, Shopify, Salesforce and marketplaces.
How much does a systems integration project cost?
It depends on the number of systems, the volume of events and how critical the tax and financial flows are. We start with a free assessment and estimate the project by phase, alongside the cost of operating with disconnected systems: manual rework, inventory errors and hours of reconciliation.
Is MuleSoft worth it, or can you integrate without an iPaaS?
It depends on the number of integrations and the governance you need. For a few integrations, dedicated connectors are enough. For dozens of systems with API reuse and governance, an iPaaS like MuleSoft pays for itself. CCX runs the assessment and implements both models.
What is event-driven architecture, and when should you use it?
Integrating through asynchronous events, with Kafka or RabbitMQ, instead of coupled synchronous calls. It brings resilience, auditability and scale, and fits high-volume operations with multiple consumers.
Does CCX integrate WhatsApp and CRM with the ERP?
Yes. With CCX Messages and CRM connectors such as Salesforce, HubSpot and Zendesk, we connect customer service, abandoned cart, OTP and after-sales to the ERP and the e-commerce, with signed webhooks and per-client rate limits.
Have systems that don't talk to each other?
Thirty minutes with a CCX engineer, at no cost, to map your systems and the right integration model for your operation.