This is a framework designed to build connectors with external systems, usually called Backends in the documentation.
Documentation:
It features:
- A jobs queue > In which the connectors can push functions (synchronization tasks) > to be executed later.
- An event pattern > The connectors can subscribe listener functions on the events, > executed when the events are fired.
- Connector base classes > Called ConnectorUnit. > > Include base classes for the use in connectors, ready to be > extended: > > - Synchronizer: flow of an import or export > - Mapper: transform a record according to mapping rules > - Binder: link external IDs with local IDS > - BackendAdapter: adapter interface for the exchanges with the > backend > - But ConnectorUnit can be extended to accomplish any task
- A multi-backend support > Each ConnectorUnit can be registered amongst a backend type (eg. > Magento) and a backend version (allow to have a different Mapper > for each backend's version for instance)
It is used for example used to connect Magento and Prestashop, but also used with Solr, CMIS, ...
auto_awesome What this module does
AI-generated from the code · Odoo 19.0This module is a technical framework that other modules use to build connections with external systems (like e-commerce platforms or accounting software). It provides the building blocks for synchronizing data, but does not add any user-facing features by itself.
This module is a foundation for developers to create connectors to external systems. It does not provide any direct user functionality on its own; instead, it offers a set of tools and base classes that other modules use to build specific connectors.
When installed, it adds a 'Connectors' menu under a new top-level menu, visible only to users in the 'Connector Manager' group. It also adds a 'Connectors' tab to the partner form, but this tab is hidden by default and is meant to be used by submodules.
The module introduces several technical models and components, such as connector.backend, external.binding, and various components for mapping, binding, and synchronizing data. These are used by developers to define how data is exchanged with external systems.
It also extends the queue.job model to add a related action that can open the original record from a binding, and it provides security groups to control access to connector features.
In summary, this module is a toolkit for building connectors, not a ready-to-use connector itself. It enables other modules to handle data synchronization, but end users will only see its effects through those specific connectors.
Depends on
Required by other modules
Menus it adds
Models and fields (20)
- queue.job · extends an existing model
- base.binder · new model
- base.mapper · new model
- base.deleter · new model
- base.exporter · new model
- base.importer · new model
- base.connector · new model
- base.map.child · new model
- external.binding · new modelsync_date (Last synchronization date)
- generic.exporter · new model
- base.synchronizer · new model
- connector.backend · new model
- base.export.mapper · new model
- base.import.mapper · new model
- base.record.locker · new model
- base.backend.adapter · new model
- base.map.child.export · new model
- base.map.child.import · new model
- base.connector.listener · new model
- base.backend.adapter.crud · new model
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. The module is very large and only part of the code was read. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 8 confirmed, 1 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/connector.
terminal Installation and usage
OCA documentation · Odoo 19.0Usage
Source · Odoo 19.0This module does nothing on its own. It is a ground for developing advanced connector modules. For further information, please go on:
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.