| Factor | Closer to a simple connector | Closer to a complex integration |
|---|---|---|
| Direction of flows | One way: Odoo sends or receives | Both ways, with conflict rules |
| Synced objects | One or two: orders, contacts | Orders, products, stock, invoices and payments |
| API on the other side | Documented, stable, with a test environment | Poorly documented, rate limited, or files only |
| Transformation rules | Direct field mapping | Taxes, variants, currencies, multi-company |
| History | New data only | Historical data loaded at start |
| Error handling | Exchange log and alert | Automatic retry, queue, monitoring screen |
Custom Odoo connectors.
Your online store, accounting software or CRM doesn’t talk to Odoo, so your team types everything twice. Krafter writes the missing connector: reliable flows, both ways, with error recovery. And to run Odoo from Claude or ChatGPT, an MCP server.
Enter it once. Sync it everywhere.
Definition
What is an Odoo connector?
An Odoo connector syncs data automatically between Odoo and another piece of software: orders, customers, stock, invoices, payments. It replaces double entry and manual exports. A store app is enough when it covers your case; custom work takes over when your rules, your software or your volumes fall outside it.
- For whom
- Companies running Odoo, or that have chosen it, with software to plug in.
- Common software
- Shopify, PrestaShop, WooCommerce, Stripe, Sage, HubSpot, Power BI, in-house APIs.
- Price
- Simple connector: €2,000 to €5,000 excl. VAT. Complex integration: €5,000 to €15,000 excl. VAT.
- Editions
- Odoo Community and Enterprise, on Odoo.sh or a server you control.
- AI
- MCP server to query and run Odoo from Claude or ChatGPT.
- Proof
- Pyper: 41 open source Odoo modules, maintained on Odoo 17, 18 and 19.
Store or custom
A store app is often enough. Not always.
The Odoo store offers connectors for most widely used software. When one covers your case and follows your Odoo version, take it: it is faster and cheaper. Our first call checks exactly that.
The store is enough when
- The other software is widely used
- Flows are standard: orders, customers, products
- Your business rules are classic
- The app is maintained for your Odoo version
Custom work makes sense when
- Your software is niche or built in-house
- Your rules go beyond the standard: pricing, taxes, multi-company
- The app almost fits and forces workarounds
- Every exchange must be traced and retried on error
Common cases
The most requested connections.
Online store
#1Shopify, PrestaShop, WooCommerce: orders and customers into Odoo, stock and prices back to the store. Variants, taxes, discounts and returns are settled during scoping.
Discuss itPayment
#2To get paid on your Odoo website, the standard Stripe integration is enough. Custom work helps when Stripe collects elsewhere: subscriptions, an external platform, reconciliation with invoices.
Discuss itAccounting
#3Odoo for operations, Sage for accounting: invoices, payments and entries sent with the right account mapping. Through an API or files, depending on the Sage version.
Discuss itCRM
#4HubSpot for prospecting, Odoo for quotes and invoicing: contacts, companies and won deals in sync, with a clear rule on which system is the source of truth.
Discuss itReporting
#5Power BI or a data warehouse fed from Odoo on a schedule: sales, margins, stock, with no manual export.
Discuss itBusiness software and APIs
#6Carrier, logistics, production, partner platform: any software that exposes an API, or files, can exchange data with Odoo.
Discuss itTwo systems to connect without Odoo, or an API to open to your customers? See our custom API integrations.
Odoo and AI
Connect Claude or ChatGPT to Odoo.
MCP, the Model Context Protocol, is an open protocol that lets an assistant like Claude act inside software through declared tools. Claude and ChatGPT both support it. Plugged into Odoo, it lets you query and act in plain language.
What you can ask
- “Which invoices are more than 30 days overdue at our ten biggest customers?”
- “Create the quote for this customer with these three lines.”
- “Add the missing VAT number on this company record.”
Odoo 20 has its own MCP server
Since Odoo 20, released in September 2026, the Odoo AI app includes an MCP server. By default it exposes read tools; tools that change data are enabled one by one. If you run Odoo 20 and these tools are enough, start there.
When custom work takes over
- Your Odoo runs version 17, 18 or 19: the Odoo MCP server arrived with version 20.
- Your custom modules need business tools, such as “validate a job” or “compute a price”, rather than raw field writes.
- You want a dedicated account, tools limited to your use and a log of every action.
On Odoo 20, our tools extend the Odoo MCP server, shipped in a module. On earlier versions, we write the whole server. Expect €5,000 to €10,000 excl. VAT at a fixed price, based on the number of tools and the rules they carry.
The rights of the connected account
Every call uses the API key of an Odoo user and respects their rights. For lasting use, a dedicated account with minimal rights, as Odoo recommends.
An action log
Every tool call is recorded: who, which tool, which records, at what time.
Approval before writing
Read tools run directly. Tools that create or change data ask for your approval in the assistant.
Keys that expire
An Odoo API key lasts three months at most. Its renewal is planned from day one.
We build MCP servers for our own software: Kascade and Smashr, both launching, each expose one. The same method applies to your Odoo.
Under the hood
A connector lives inside Odoo, or next to it.
Most of the time, the connector is an Odoo module. It relies on Odoo’s access rights and scheduled actions, and follows upgrades with the rest of your code. Odoo Online does not accept custom Python modules: you need Odoo.sh or a server you control. We work with both.
Sometimes an external service calls the Odoo API. On an Odoo subscription, the external API is reserved for the Custom plan: the One App Free and Standard plans have no access to it.
Since Odoo 19, the JSON-2 API replaces the older XML-RPC and JSON-RPC APIs. Odoo has scheduled their removal with Odoo 22, in fall 2028, and earlier on Odoo Online. A connector built on the older APIs will have to be ported before then.
How it works
From the flow map to production.
A connector holds or breaks on details: a VAT rate, a variant, a duplicate customer. So the work starts with the flow map.
01 / 04
The flow map
30-min call, then a documentWhich objects move, in which direction, how often, and which system is the source of truth for each piece of data.
The API on the other side is checked too: documentation, rate limits, notifications.
The quote
fixed priceA fixed price per connector or per batch of flows, stating what is included and what is not.
Development
on a copy of your databaseThe connector is written and tested on a copy of your Odoo, against the test environment of the other software.
Automated tests on edge cases: duplicates, empty fields, network cuts, rejected calls.
Go-live
then over timeGo-live, close watch over the first days, then maintenance.
Budget
How much does an Odoo connector cost?
A simple connector costs €2,000 to €5,000 excl. VAT: one or two flows, a documented API, clear rules. A complex integration ranges from €5,000 to €15,000 excl. VAT: two-way flows, business rules, high volumes, historical data. Upkeep then runs at 8 to 12% of the development cost per year.
- Simple connector
- €2,000 to €5,000 excl. VAT.
- Complex integration
- €5,000 to €15,000 excl. VAT.
- MCP server (Claude, ChatGPT)
- €5,000 to €10,000 excl. VAT, based on the number of tools.
- Model
- Fixed price per connector, quoted from the flow map.
- Upkeep
- 8 to 12% of the development cost per year.
- Changes
- Time spent, €700 to €1,100 excl. VAT per day, or prepaid hours.
Where you stand
Simple or complex: what makes the difference.
A connector depends on two systems that evolve at their own pace. Its upkeep falls under our application maintenance.
FAQ
A connector to build? Describe both systems, the data that must flow and your Odoo version. A founder replies within 24/48h.
Describe my connectorBefore plugging into your Odoo.
A program that syncs data between Odoo and another piece of software: orders, customers, stock, invoices, payments. It can be a store app, a custom module installed in Odoo, or an external service that calls the Odoo API.
If a store app covers your flows and follows your Odoo version, take it. Custom work makes sense when the other software has no app, when your rules force workarounds, or when every exchange must be traced. We check the store with you before quoting.
€2,000 to €5,000 excl. VAT for a simple connector, €5,000 to €15,000 excl. VAT for a complex integration. The price depends on the direction of the flows, the number of objects, the API on the other side, the transformation rules and whether history must be loaded.
Yes, and to Sage, HubSpot or Power BI too. Every store has its own variants, taxes, discounts and returns. The connector is written for your case, not pulled from a generic module.
Not as a module: Odoo Online does not accept custom Python modules. An external service calling the Odoo API remains possible, but the external API is only available on the Custom plan. Odoo.sh or a server you control opens every option.
Yes, through an MCP server. Since Odoo 20, the Odoo AI app includes one, with standard tools. Krafter steps in on earlier versions, for tools specific to your custom modules, or for a tighter setup.
No. It acts with the rights of the connected Odoo account, never beyond. Tools that write ask for approval in the assistant, and every call is logged.
A connector written as a module follows the migration with the rest of your code. Connectors using the XML-RPC or JSON-RPC APIs will have to move to the JSON-2 API: Odoo has scheduled their removal with Odoo 22, in fall 2028.
Let’s build a product people → actually use
A 30-minute call with a founder. Answer within 24/48h.