Point-to-point integrations
One development per pair of systems. Change one and three break.
Module 01 · Integrafy Platform · The connection layer
ConnectWithout Connect, data does not move. With Connect, it moves in real time.
Bidirectional connectors between ERP, eCommerce, CRM and logistics. Event-driven sync, every piece of data once and in under five seconds.
The challenge
Every system speaks its own language. And someone acts as translator.
In most industrial and distribution companies, the ERP and the store understand each other through nightly files, scripts nobody documented or a person who copies and pastes.
Data arrives late
Stock updates once a day. In between, the store sells what is not there.
Silent failures
An order that never reaches the ERP makes no noise. It is discovered when the customer calls.
The ERP nobody touches
A twenty-year-old system that works. And that nobody wants to modify to connect it.
The cost is not in the connector. It is in what happens when data arrives late, duplicated or not at all.
What really matters
Connecting is not moving a file. It is every piece of data arriving once, on time and without duplicates.
Anyone can copy data from one system to another. The hard part is guaranteeing an order is not created twice, a stock level is not lost and, if something fails, someone finds out before the customer.
Integrafy Connect
The layer that joins your systems.
Connect abstracts communication with each system through specific adapters and normalises data into a unified model. Everything else in the platform (Data, Flow, KnowOS, Agents) works on that model.
It syncs by events, not by nightly processes: when something changes in one system, the rest know within seconds.
In one sentenceWithout Connect, data does not move.
Where Connect sits in Integrafy Platform
Connect is the entry point for structured data: ERP, eCommerce, CRM and WMS write to and read from the operational database through it.
Why a layer and not more integrations
Six systems, fifteen integrations to maintain. Or six connections.
Every point-to-point integration is a development, a maintenance job and a place where something can fail. With Connect, each system connects once to the unified model.
Both ways
What the ERP knows reaches the store. What happens in the store goes back to the ERP.
ERP → eCommerce
StockCataloguePrices and price listsOrder statuses
→ERPThe operational source of truth
ConnectUnified data modelIdempotency · retriesUnder 5 s per event
eCommerceWhere the customer buys
←
OrdersCustomersReturns
eCommerce → ERPStep by step
What happens when stock changes in the ERP.
ERP source
Connect adapter · queue
Unified model operational data
eCommerce destination
1 The stock of a reference changes: an event is emitted
2 The adapter translates the data into the unified model
3 Checks whether that event was already processed (idempotency)
4 Updates the operational data
5 Publishes the new stock in the store
6 The store confirms receipt
7 If it fails: retry with backoff and, finally, dead-letter queue
Under 5 seconds · end to end (p99) · every step is logged in Observe
Reliability
Designed for the day something fails.
An integration is judged when it fails. These are the three guarantees that keep a failure from becoming a lost or duplicated order.
Every event, exactly once
Reprocessing an event does not duplicate orders or stock movements. The result is the same even if it arrives twice.
Retry queues
If a system does not respond, the event waits and is retried with exponential backoff. Nothing gets lost on the way.
Error queue and alerts
What cannot be processed is set aside with its reason, and the owner is notified by email or webhook.
< 5 sper event in production (p99)
0duplicates from reprocessing
24/7monitoring in Observe
Native connectors
Over 100 pre-built connectors. Each with its protocol.
And if your system is not on the list, it connects anyway: REST, SOAP, XML-RPC, JSON-RPC, OData, flat files, CSV, EDI, SQL, DB2 or webhooks.
ERP
SAP Business OneService Layer · DI API
SAP R/3RFC · BAPI
OdooXML-RPC
Business CentralOData
SageCOM · SQL
AS/400DB2
eCommerce
PrestaShopAPI · webhooks
ShopifyAPI · webhooks
MagentoREST API
WooCommerceREST API
CRM · WMS
HubSpot · SalesforceAPI
Dynamics 365 · ZohoAPI
Mecalux · GenerixAPI · files
OpenBravoAPI
Legacy systems
And the twenty-year-old ERP? It connects without touching it.
The most common case in industry: an AS/400 or a custom ERP that works and that nobody wants to modify.
Connect reads and writes wherever the system already allows: DB2 database, flat files over FTP or staging tables. The legacy stays the same; the store stops being an island.
DB2Flat filesFTP / SFTPStaging tables
Comparison
A custom script, or a connection layer.
Many integrations start as a one-off development. The challenge appears the day the ERP changes, a second channel arrives or an order fails.
Maintenance Custom point-to-point developmentEvery integration is different code, often undocumented. Integrafy ConnectPre-built adapters on a common model, maintained by us.
Sync Custom point-to-point developmentNightly processes or every few hours. Integrafy ConnectEvent-driven, in under 5 seconds.
Duplicates Custom point-to-point developmentA reprocess can create the same order twice. Integrafy ConnectIdempotency: every event is processed exactly once.
Errors Custom point-to-point developmentDiscovered when the customer complains. Integrafy ConnectRetries, dead-letter queue and alert to the owner.
New channel or ERP Custom point-to-point developmentAnother development from scratch. Integrafy ConnectOne more connector on the same model.
Traceability Custom point-to-point developmentScattered logs, if any. Integrafy ConnectEvery event logged in Observe, searchable by order or reference.
Results in production
What changes when data flows on its own.
Orders were typed in by hand
“Online orders were entered by hand. Stock took 24 h to update.”
−80% manual work · +40% online ordersWrong per-customer prices
“Per-customer prices correct in the ERP, wrong in the store.”
0 price errorsThe store was an island
“20-year-old ERP untouched. The online store was an island.”
Synced with no changes to the ERPHow it is contracted
Connect is not bought separately. It comes with every product.
It is the foundation of Integrafy Platform: standard connectors are included in Data, Flow and KnowOS. You only pay for what goes beyond.
Standard connectors
PrestaShop, Shopify and the pre-built ERPs and CRMs included in each plan.
IncludedAdditional ERP connector
A second ERP, a second company or a legacy system. One-off setup.
from €1,200Custom integrations
Systems without a standard connector, via API, file or database.
€520 / dayPrices exclude VAT. Full details in the Integrafy Platform price list.
See the full price list →Frequently asked questions about Integrafy Connect
What does bidirectional sync mean?
Data flows in both directions: from the ERP to the eCommerce and from the eCommerce back to the ERP. An order in PrestaShop creates a Sales Order in SAP. A stock change in SAP is reflected in PrestaShop in under 5 seconds.
How long does it take to sync a change?
Events are processed in real time. Propagation time is under 5 seconds (p99) for stock and statuses. Bulk catalogue syncs depend on volume, but 80,000 references are updated in less than 1 hour.
What happens if the ERP fails or goes offline?
Connect has queues with automatic retries and exponential backoff. If the ERP does not respond, events wait and are processed in order when it comes back, with no duplicates thanks to idempotency. What cannot be processed goes to the dead-letter queue and the owner is alerted.
Do I need custom development for each connector?
No. Connectors are pre-built: you only set up credentials and field mappings. If your ERP has custom fields, they are mapped without code. Systems without a standard connector are integrated via API, file or database at €520 per day.
Does it work with legacy ERPs like AS/400?
Yes. Connect reads and writes wherever the system already allows: DB2, flat files over FTP/SFTP, EDI or staging tables, without modifying the original system. It is one of the few middleware platforms that supports legacy systems over 20 years old.
Is Connect contracted separately?
No. Standard connectors are included in every Data, Flow and KnowOS plan. Only an additional ERP connector (from €1,200) or custom integrations are quoted separately.
No-obligation diagnosis
Tell us which systems you have. We tell you how they connect.
A 30-minute session on your real system map: which connector exists, what needs adapting and what it costs to get it running.
Request a diagnosis