Integration mission · Odoo
Odoo, and the tool Odoo doesn't do.
You run Odoo. You also run something else for the part Odoo doesn't cover: the planning tool, the lab system, the webshop, the field app. They don't talk, so someone re-types, and the answer you got was that it's out of scope.
Book a 30-minute callWhat we do here.
We connect the other tool to Odoo through Odoo's documented external API, from the outside. We don't write custom modules inside your Odoo. That's not a preference, it's the reason the connection survives: Odoo ships a major version every year, and everything built inside has to be migrated with it. A connection built beside it, through the interface Odoo publishes, keeps working. Your Odoo stays standard, which is what Odoo itself tells its customers to aim for.
The plan decides the part that matters more than the plumbing: which system owns the customer, the product, the price and the stock level; what happens when both change the same record; what an invoice created through the API does to your accounting if it skips Odoo's own workflow; what runs at 3 a.m. when one side is down. You get those decisions in writing before anything is built.
When your process changes, the connection changes in days, not as a new project. When Odoo upgrades, it keeps working.
What you get.
-
A connection that runs on your side, in your accounts
-
An alert when something didn't sync, before month-end finds it
-
Tests around it, so a change doesn't break it
-
Documentation someone else can pick up
-
Upkeep priced in from day one, so "it follows your business" stays true
How it runs.
1
The plan, two days
We sit with the people who use both systems, then write the plan: what connects to what, which system owns which data, what happens on conflict, on failure, on deletion, and what it will cost to build.
2
The build, quoted in the plan
A block of days. Tests around the connection, monitoring, documentation, code running on your side.
3
It runs, and we watch it
The first weeks monitored by us. After that, the bucket of days for changes.
Proof
Twinbooks · ten days
From a command-line tool to a product their clients use themselves
The migration tool worked; everything around it was manual. We built the customer-facing layer around it in ten days and left the tool untouched, on purpose.
Read the caseThree questions.
- We have an Odoo partner. Do they need to be involved?
- Only if you want them to be. We don't modify what they maintain; we connect to it through the API. Nobody steps on anybody's work.
- Can you do it inside Odoo instead?
- We can, and we'll tell you if a case needs it. It's rare, and it puts the connection on Odoo's upgrade treadmill. The default is outside.
- What if the other tool has no API?
- We'll know in the first call. Sometimes there's an export we can build on; sometimes the honest answer is that the tool is the problem. Either way you hear it before you pay for a plan.
Price.
Integration plan.
Two days, €1,500 excl. VAT. The plan is yours. Build it with us, or with anyone.
Build.
Quoted in the plan, as a block of days, monitoring for the first weeks included. Most connections land between €4,000 and €9,000. Changes afterwards from the bucket of days.
Not for.
- A tool with no interface at all. We'll tell you in the first call, and what the alternatives are.
- A one-off data migration. Different job; ask us anyway.
- Anyone who wants the system of record customised from the inside.
Tell us about Odoo.
Lean builders. We deliver.