Custom Odoo development.
Your Odoo is running, and you know what it is missing: a business module, a connector, a portal, a version migration. Krafter writes that code. Two senior developers, clean and tested modules, maintained from one Odoo version to the next. No audits, no training: development.
Odoo is the base. We write the rest.
The reality
Odoo does a lot. Your business never quite fits the standard.
An approval flow specific to your business, a pricing rule that exists nowhere else, a business tool to plug in, a portal for your customers or technicians: that is where the standard stops. The usual reflex is to stack store apps that almost fit, or to work around the problem in a spreadsheet on the side.
A module written for your need 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, ORM, views, OWL, not by a configurator who codes on the side.
What we build
The code your Odoo is missing.
Custom business modules
#1New models, business rules, approval flows, calculations specific to your activity: a module that fits into Odoo as if it had always been there, with its access rights and its tests.
Talk about itConnectors and synchronization
#2Online store, logistics, banking, CRM, business software: two-way flows between Odoo and your other tools, with error recovery and logged exchanges.
Talk about itPortals and apps
#3Customer or supplier portal, a dedicated interface for field teams, an iOS and Android mobile app connected to Odoo: your data, without opening the back office.
Talk about itVersion migrations
#4Your custom modules ported to the next Odoo version: code adapted to the new framework, data migrated, tests run again. Our own modules take that road at every release.
Talk about itAutomation and reports
#5Scheduled actions, batch processing, job queues, custom PDF reports and dashboards: everything your teams still do by hand.
Talk about itTaking over existing code
#6Modules inherited from a previous provider, without documentation or tests: code review, fixes, cleanup, then long-term maintenance.
Talk about itWho it is for
You know what you want. We write it.
This service is for companies that already run Odoo in production and have a precise need: a feature, a flow, an integration. You know your business and your Odoo. What you are missing is two developers who master the framework, with no project manager between you and the code.
What you get here
- Tested Odoo modules in Python and OWL
- Connectors to your other tools
- Migration of your custom modules
- Takeover and maintenance of existing code
- People who write the code themselves
What we do not offer
- Choosing an ERP or auditing your processes
- Standard installation and configuration
- Training your teams
- Reselling Odoo licenses
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.
SaaS foundations, job queues, dashboards, roles and access rights, data import, global search: these are the building blocks we reuse on our projects. The code is open for anyone to read. It is 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, installed modules, existing custom code.
A conversation with a founder who codes, not a salesperson. 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. For small ongoing changes, time and materials remains an option.
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.
Automated tests, code review, Odoo conventions: the module must survive the next migration.
Going live
and beyondDeployment on your Odoo, then maintenance and version migrations if you wish.
Fixes, improvements, upgrades: the same code, looked after by the same developers.
Budget
How much does custom Odoo development cost?
A simple connector between Odoo and another tool starts at around €2,000 to €5,000 excl. VAT. A complex integration ranges from €5,000 to €15,000 excl. VAT. A business module is priced as a fixed fee per batch, once we have read your written need. For ongoing changes, 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.
- Business module
- Fixed price per batch, based on a written need.
- Time and materials
- €700 to €1,100 excl. VAT per day.
- Versions
- Odoo 17, 18 and 19, Community and Enterprise.
- Code
- It belongs to you, no black box.
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. If your Odoo runs an older version, the first estimate often covers migrating your custom modules.
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.
When a store app covers your need, use it: it is faster and cheaper. Custom work makes sense when an app almost fits and forces workarounds, or when several apps step on each other. We will tell you straight.
Yes. We read the code first: structure, tests, compatibility with your version. You then get a costed opinion on what to keep, what to fix and what to rewrite. Maintenance can then move to us.
Standard data is migrated with Odoo’s tools or OpenUpgrade, depending on your edition. We handle the custom code: adapting it to the new framework, migrating its data, testing on a copy of your migrated database, then going live.
You do. The code written for your Odoo belongs to you. It follows the framework’s conventions, with no black box: any Odoo developer can read it and take it over.
No. We build what Odoo does not do out of the box. To choose an ERP, configure Odoo from scratch or train your teams, a specialized integrator is better placed, and we can work alongside them on the development side.
Let’s build a product people → actually use
30 minutes on a call with a founder. Answer within 24 to 48 hours.