Bidirectional integration
A bidirectional integration transfers data in both directions between two systems: changes in system A reach system B, and changes in system B flow back to A. It needs clear rules on which system prevails in case of conflicts.
Explanation
Many integrations are one-way. Orders flow from the shop into the ERP, and that is it. Often that is not enough. The shipping status should go back to the shop, the payment status back to the CRM, changed customer addresses into both systems. Then the integration works bidirectionally.
That sounds like twice the work, but it is often more. If the same record is changed in both systems, a conflict rule is needed. It is common to define a leading system for each data object or even each field. The integration must also recognize which change it wrote itself, so that it does not run in circles and send the same change back and forth endlessly.
Example from everyday integration work
Between shop and ERP the rule is: items, prices and stock levels lead in the ERP and flow into the shop. Orders originate in the shop and flow into the ERP. Shipping status and tracking number come back from the ERP into the shop. If a customer changes their address in the shop, it is reported to the ERP as long as the order has not been shipped yet.
- Stock and price reported to the shop every 15 minutes
- Order and shipping status synchronized on change
How it differs from related terms
- Unidirectional integration: data flows in one direction only. Simpler and cheaper.
- Data mapping: is needed for both directions in bidirectional integrations.
- Webhook: helps detect changes quickly in both directions.
Relevance to our services
Whether an integration works in one or both directions is one of the most important cost drivers, see What does an integration cost? Typically bidirectional are connections between shop and ERP: shop-ERP integration.
Frequently asked questions
Do I always need a bidirectional integration?
No. If only one system generates data and the other just receives it, such as invoices for accounting, one direction is enough. That is simpler, cheaper and easier to monitor.
Related
Data mapping
Data mapping defines which field from system A flows into which field of system B and how values are converted. Explanation, example and practical tips.
Interface
A software interface connects two systems so they exchange data automatically. Definition, everyday example and how it differs from API and middleware.
Shop-ERP connection
Products, stock levels, prices and orders synced automatically between shop and ERP.
