What this exists to fix
Point-to-point scripts between Odoo and surrounding systems break silently at every upgrade.
An Odoo instance exchanging orders and stock with a webshop and a 3PL through cron scripts written by someone who has left. Nobody knows a sync failed until a customer asks where their order is. These connectors queue, retry, and surface the record that failed.
What it does
REST and XML-RPC connectors with retry and dead-letter handling
Field mapping maintained as configuration, not code edits
Sync run history with per-record error visibility
Upgrade-tested against supported Odoo versions
Versions, dependencies, and licensing
| Verified Odoo compatibility | Confirmed per deployment. Tell us your Odoo version and edition. |
|---|---|
| Depends on | base; credentials for the system being connected |
| Installation model | Addon plus per-integration configuration. Which endpoints and field mappings you need is a scoping conversation, not a checkbox |
| Licence | Contact Sales |
| Implementation | Quoted separately from the licence |
| Annual support | Contact Sales |
| Upgrades | Contact Sales |
We list an Odoo version and edition here only once that exact combination has been tested. Rather than claim breadth we have not verified, tell us what you run and you will get a straight answer.
Public documentation for this application is not published yet. Ask for it with a demo and we will walk the configuration with you.
What this usually goes in with
See Integration Connectors against your process
A demo on your workflow rather than ours, and an honest answer on whether this application fits or needs extending.