| Criterion | Store app | Odoo Studio | Custom module |
|---|---|---|---|
| What it is | A ready-to-install module written by a vendor | Odoo’s toolbox to customize without coding: fields, views, automations, PDF reports | Python and OWL code written for your need, in a separate module |
| The right choice when | The app covers your need without workarounds | You need a field, a view or a simple rule | The need touches business logic, calculations or flows between tools |
| The limit | You depend on its vendor for every fix | Customizations pile up and become hard to track | It takes developers who know the framework |
| At migration time | The vendor has to release the next version | Each customization must be checked, and weighs on the price | The code follows the conventions and is ported methodically |
Custom Odoo development.
Your company runs Odoo, or has just chosen it, and it is missing code: a business module, a connector, a version migration, the takeover of existing work. Krafter writes it. Two senior partners, Odoo developers who design and code themselves, on Community and Enterprise alike.
Odoo is the base. We write the rest.
Definition
What is custom Odoo development?
It means writing the code Odoo does not include out of the box: a Python and OWL module that adds your models, rules and screens, a connector to your other tools, or porting your modules to a new version. A well-written module follows the framework’s conventions: it respects access rights, stays readable by any Odoo developer and survives migrations.
- For whom
- Companies running Odoo, or that have chosen it, with a precise development need.
- Editions
- Odoo Community and Enterprise.
- Hosting
- Odoo.sh or a server you control. Odoo Online does not accept custom Python modules.
- Who codes
- Two senior partners, helped by AI, who review and test every line.
- Price
- Connectors from €2,000, migrations from €8,000 to €30,000 excl. VAT, modules at a fixed price.
- Code
- It belongs to you.
The reality
Odoo does a lot. Your business never quite fits the standard.
An approval flow specific to your business, a unique pricing rule, a store to synchronize: that is where the standard stops. The usual reflex is to stack store apps that almost fit, or to pile up Studio customizations.
A custom Odoo module does better. It builds on Odoo’s data model, fits into its screens and access rights, and survives version migrations. On one condition: it must be written by developers who know the framework from the inside, from the ORM to OWL components.
What we build
The code your Odoo is missing.
Custom business modules
#1New models, business rules, approval flows, calculations, PDF reports: a module that fits into Odoo as if it had always been there, with its access rights and its tests.
Learn more
Connectors and synchronization
#2Online store, payments, accounting, CRM, reporting: flows between Odoo and your other tools, with error recovery and logged exchanges.
Learn more
Version migrations
#3Your custom modules and Studio customizations ported to the next version: code adapted, data migrated, tests run again on a copy of your database.
Learn more
Taking over existing code
#4Modules inherited from another provider, without documentation or tests: audit, costed plan, cleanup, then maintenance.
Learn more
Odoo connected to Claude or ChatGPT
#5An MCP server gives an AI assistant access to Odoo, limited to the rights of the connected account: query your data and act in plain language.
Learn more
Portals and mobile apps
#6Customer or supplier portal, iOS and Android app for field teams: your Odoo data without opening the back office.
Learn moreCommon needs
The details, need by need.
Three topics come up in almost every request. Each one has its own page: price, method and frequent questions.
01
Odoo migration
Moving from 16 to 17, 17 to 18 or 18 to 19 with your custom modules and Studio customizations. What drives the price, and the method step by step.
€8,000 to €30,000 excl. VAT
Plan my migration02
Odoo connectors
Shopify, PrestaShop, WooCommerce, Sage, HubSpot, Power BI, or Claude and ChatGPT: when a store app is enough, and when you need custom work.
€2,000 to €15,000 excl. VAT
See the connectors03
Odoo in Lyon
A studio based in Morancé, near Lyon, working over video calls with companies in the region and across France.
Studio in the Beaujolais
The studio near LyonWho it is for
You know what is missing. We write it.
This service is for companies that run Odoo, or have just chosen it, and need development: a feature, a flow, a migration, code to take over. You know your business. What you are missing is Odoo developers, with no project manager between you and the code.
An Odoo developer, without hiring
Hiring a senior Odoo developer takes time, and a single profile rarely covers Python, OWL, PostgreSQL and migrations. Krafter gives you two senior partners, at a fixed price per batch or on time and materials, with no team to manage.
Conviction
“The real test of an Odoo module is not delivery day. It is the next migration. A module that follows the framework moves from one version to the next without drama. A module that works around it gets rewritten every time.”
François Pluchino
Co-founder & CTO, Krafter
Proof in the code
Our own Odoo modules, open source.
Pyper brings together 41 Odoo modules published by Krafter under the LGPL-3 license, maintained side by side on Odoo 17, 18 and 19.
Krafter started as an Odoo integrator before expanding to SaaS and mobile apps. Pyper gathers the building blocks we reuse: SaaS foundations, job queues, dashboards, roles and access rights, data import, global search. The code is open for anyone to read: the best way to judge our work before trusting us with yours.
How it works
A written need, a fixed price, tested code.
No six-month scoping phase: your need is already clear, so the work starts with the code.
01 / 04
The need
30 min callYou describe what is missing. We look at your Odoo: version, edition, hosting, installed modules, existing custom code.
A conversation with a founder who codes. If a store app is enough, we will tell you.
The estimate
fixed priceA fixed price per batch, stating what is included and what is not.
Each batch is a usable feature. Time and materials remains an option for small changes.
Development
on a copy of your databaseThe code is written and tested on a test database, a copy of yours. You approve each batch before it goes live.
AI writes a large share of the code. Every line is reviewed and tested by a senior partner, following Odoo conventions.
Going live
and beyondDeployment on your Odoo, then maintenance and version migrations if you wish.
The same code, looked after by the same developers.
Comparison
Store app, Studio or custom module?
Custom work is not always the right answer. Here is how to decide.
Budget
How much does Odoo development cost?
A simple connector between Odoo and another tool costs €2,000 to €5,000 excl. VAT, a complex integration €5,000 to €15,000 excl. VAT. A version migration ranges from €8,000 to €30,000 excl. VAT. A business module is priced as a fixed fee per batch, after scoping. Time and materials is billed €700 to €1,100 excl. VAT per day.
- Simple connector
- €2,000 to €5,000 excl. VAT.
- Complex integration
- €5,000 to €15,000 excl. VAT.
- Version migration
- €8,000 to €30,000 excl. VAT.
- Business module
- Fixed price per batch, after scoping.
- Audit before takeover
- 1 to 3 days, €700 to €3,300 excl. VAT.
- Time and materials
- €700 to €1,100 excl. VAT per day.
- Maintenance
- 8 to 12% of the development budget per year, changes on top.
Odoo maintenance
Odoo maintenance and support, by people who know the code.
Application maintenance keeps your Odoo code working after go-live: fixes, changes, compatibility with updates, preparing the next migration.
Keeping the code in working order is budgeted at 8 to 12% of the development cost per year. Changes are then billed on time spent, €700 to €1,100 excl. VAT per day, or as prepaid time credit. Your support requests go straight to the two partners.
Code written by another provider? A 1 to 3 day audit comes first: written report, costed plan, debrief on a video call.
Not to be confused with Odoo’s Maintenance app, which tracks your equipment: here, it is your code that is maintained.
Our scope
What we do not do.
- Choosing an ERP and consulting on your processes
- Full functional configuration of Odoo from scratch
- Training your teams
- Reselling Odoo licenses
Krafter develops, and sticks to it. Consulting, configuration and training are trades of their own, with their own specialists.
Your project also needs configuration or training? Krafter works alongside your functional integrator: they configure and train, we develop.
FAQ
A precise Odoo need? Describe it in a few lines: version, modules involved, what is missing. A founder will reply within 24 to 48 hours.
Describe my needBefore you hand over your Odoo.
Yes, on both editions. Our own open source modules are maintained for Odoo 17, 18 and 19. On an older version, the first project is often the migration.
Odoo Online, Odoo’s SaaS offer, does not accept custom Python modules: custom development requires Odoo.sh or hosting you control. We work with both. We do not sell hosting, but we can install and configure the server of your choice.
It is priced as a fixed fee per batch, after scoping your written need. Each batch is a usable feature, stating what is included and what is not. For ongoing changes, time and materials is billed €700 to €1,100 excl. VAT per day.
Between €8,000 and €30,000 excl. VAT, depending on the number of installed addons, the data volume, the amount of Studio customization and the number of versions to climb. Standard data goes through Odoo’s tools or OpenUpgrade, depending on your edition. We handle the custom code.
Yes. It starts with a 1 to 3 day audit, €700 to €3,300 excl. VAT: written report, costed plan, debrief on a video call. Maintenance can then move to us.
Yes. Keeping the code in working order costs 8 to 12% of the development budget per year, then changes are billed on time spent or as prepaid time credit. Your requests go to the developers who know your code.
Yes, through an MCP server. The Model Context Protocol is an open protocol that lets an assistant like Claude act inside software through declared tools. The assistant queries Odoo and acts in plain language, with the rights of the connected account. Since Odoo 20, Odoo offers one with standard tools; a custom server makes sense on earlier versions or for your custom modules. Kascade and Smashr, two Krafter products being launched, each expose an MCP server.
Yes. AI writes a large share of the code, and every line is reviewed and tested by a senior partner before it reaches your Odoo.
You do. It follows the framework’s conventions, with no black box: any Odoo developer can read it and take it over.
No. To choose an ERP, configure Odoo from scratch or train your teams, a functional integrator is better placed. We can work alongside them on the development side.
No, Krafter is not listed in the Odoo partner directory. The studio started as an Odoo integrator before expanding to SaaS and mobile apps. To judge our level, read our code: 41 modules published as open source.
Let’s build a product people → actually use
30 minutes on a call with a founder. Answer within 24 to 48 hours.