Processes start to bypass the system
Part of the work goes back to Excel, email or extra files, because the current process in Odoo no longer matches how the company actually works.
Odoo maintenance and development for manufacturers
We take over the care of a running Odoo, fix technical problems and develop the system as the company changes. We work on modules, processes, integrations and custom Odoo extensions.
- Odoo takeover
- Modules and processes
- Integrations
- Fixes and errors
- Upgrades
- Custom modules
Odoo works, but the company does not stand still
Going live does not end the work on Odoo.
A manufacturer introduces new products, changes how production is planned, opens another warehouse, grows B2B sales, changes purchasing rules or connects new systems. A process that was simple at implementation can look completely different two years later.
The problem starts when Odoo stops keeping up with those changes.
Let's check what limits your system todayMore and more exceptions appear
A new order type, an extra warehouse, unusual production or another customer group each lead to further manual workarounds.
Integrations need changes
An ERP does not work in isolation. Changing the e‑commerce platform, the WMS, the courier system or the way data is exchanged can mean rebuilding an existing integration.
An Odoo upgrade becomes a project
The more custom modules and modifications there are, the more important it is to check their compatibility with the next Odoo version before the production environment is upgraded. Odoo's official process also assumes a separate upgrade test and adapting custom modules to the target version.
What does Odoo maintenance and development cover?
The scope depends on how the company uses Odoo and which processes have already been adapted to its needs.
We do not start from a list of random changes. First we establish which parts of the system affect the team's daily work, and where errors, manual operations and limitations arise.
Areas of work
- Fixing errors
- We diagnose problems in how Odoo works, in its configuration, in custom modules and in the data flow between systems.
- Developing existing processes
- We modify working solutions when the way the company sells, buys, stores, manufactures or serves customers changes.
- Developing custom modules
- We extend Odoo where its standard features do not match the company's process and the chosen environment allows custom code modules. Odoo Online does not support such modules, so the development options there differ from Odoo.sh or a self-hosted environment.
- Integrations
- We develop and fix how Odoo communicates with the e‑commerce platform, WMS, PIM, marketplaces, logistics systems and the other tools used in the organisation.
- Work automation
- We look for manual operations that can move into an Odoo workflow or be automated between modules and systems.
- Updates and upgrades
- We prepare the system, data, integrations and custom modules for the move to the next Odoo version, and check the key processes before changes go to production.
- Tidying up the existing solution
- If Odoo has been developed over several years or by different providers, we tidy up the code, the configuration and the dependencies between modules.
- Analysing new needs
- Before a larger change we check whether the problem should be solved by configuring standard Odoo, changing the process, extending an existing module or building a custom solution.
Important: The maintenance and development scope depends on the Odoo version, edition, installed apps and hosting model. Community and Enterprise differ in the features available, and Odoo Online does not allow custom code modules. So before work starts we check not only the processes and the code, but also the variant of the system the company uses.
Taking over Odoo from a previous provider
Changing the company responsible for Odoo should not start with the first ticket to fix. First you have to establish what actually works in the system. We start every Odoo maintenance and development engagement the same way.
- 01
We get to know the current environment
We establish the Odoo version and edition, the hosting model, the subscription plan (if applicable), the apps in use, additional modules and the key dependencies.
- 02
We analyse the modifications
We separate standard features, configuration and solutions written specifically for the company. We review the code of custom modules and the places that need tidying up.
- 03
We review the integrations
We establish which systems exchange data with Odoo, in which direction the information flows and where synchronisation errors are handled.
- 04
We identify the critical processes
We check which parts of Odoo are critical for sales, inventory, purchasing and manufacturing, and point out the processes whose problems directly affect the team's work.
- 05
We split the scope and set priorities
We separate problems that need fixing and technical debt from development driven by business needs. Critical items come first; then we plan development in line with the company's processes and goals.
Only then can further changes be planned responsibly.
We develop Odoo together with the manufacturer's processes
Odoo covers far more than sales and CRM. The platform has areas for inventory, purchasing, manufacturing, quality, maintenance, sales and accounting, among others.
Which features are available depends on the edition and the installed apps, though. So we do not assume that every Community and Enterprise installation offers the same scope. That is why developing the system at a manufacturer can touch several connected processes.
Manufacturing
Changes to BOMs, manufacturing orders and the way production is planned and, depending on the edition and apps in use, to operations, work centres and more advanced production execution.
Inventory
New warehouses and locations, replenishment rules, lots, serial numbers and the flow of materials and finished products.
Purchasing
Developing the procurement process, reordering rules, cooperation with suppliers and the link between purchasing and the needs of inventory or production.
Quality
In Odoo Enterprise the scope can include the Quality app, which creates control points and quality checks tied to manufacturing and inventory operations. With Odoo Community we assess quality handling separately, depending on the process and the extensions available.
Maintenance
Equipment, service requests and preventive and corrective work can be linked to Odoo's manufacturing processes. The exact scope depends on the version, the installed apps and the environment's configuration.
B2B and D2C sales
Changes to customer handling, quoting, price lists, orders and the flow of information between Odoo and the sales channels.
This does not mean every company should use every module. The scope should follow the processes that are genuinely worth running in one environment.
A change in one area affects the next
At a manufacturer, Odoo can sit between sales, inventory, purchasing and manufacturing. So when we develop the system, we look beyond the screen where a user reported the problem.
We check the whole flow
- product
- material purchasing
- inventory
- manufacturing
- sales
- order fulfilment
- financial data
Only then can we decide where the change belongs and which systems it really has to cover.
See Odoo for manufacturingMaintenance and development are two different kinds of work
A running system needs both.
Maintenance
It is about what already works and should keep working correctly.
It covers, among other things:
- diagnosing and fixing errors
- problems with existing modules
- integration errors
- configuration fixes
- problems that appear after changes
- preparing for updates
Development
It is about changes driven by the company's new needs.
It can cover:
- new features
- further modules
- workflow changes
- new automations
- new integrations
- growing B2B or D2C sales
- changes to inventory processes
- changes to manufacturing
- custom Odoo modules
With this split, outages and day-to-day problems do not compete directly with the planned development of the system.
Developing Odoo should not mean piling on more exceptions
Not every business need is worth solving with a new module. Sometimes configuring an existing process is enough. Sometimes the problem is that responsibility was assigned to the wrong system. And sometimes a custom extension really is justified. Before a larger change we check three options:
- 01
Standard Odoo
Can the process be handled with features the system already has?
- 02
Configuration and process change
Can the need be met without writing custom code?
- 03
Custom development
Does the company's specific situation really require a custom module or an extension of an existing solution?
Custom code gives flexibility, but it has to be maintained and adapted with every new Odoo version. So customisation should solve a specific problem, not replace analysing the process.
An Odoo upgrade that keeps your own modifications
Moving to the next Odoo version is not just a matter of running an update. Especially when the system has custom modules, integrations or modified processes.
Odoo states that for databases with custom modules the code has to be adapted to the target version and tested before production is upgraded. The official upgrade process for customised databases includes, among other things, preparing the modules for the new version, working on an upgraded test database, testing, and a rehearsal of the whole process before the production switch.
The scope of such an upgrade also depends on hosting. Odoo Online does not allow custom Python modules, so the upgrade scenario differs from Odoo.sh and on-premise installations.
Before changing the version we check
- the modules in use
- custom extensions
- integrations with external systems
- automated actions
- flows between apps
- data that needs migrating
- the company's critical processes
Then we prepare a test environment and scenarios for the processes that have to be checked before the new version goes live in production.
Odoo remains part of the company's wider system
Maintaining Odoo also covers the places where data passes between systems.
Odoo provides mechanisms for integrating the platform's data and functions with external applications. Odoo 19 also offers the External JSON-2 API.
Access to the external API depends on the Odoo variant, though. In Odoo's current subscription offer the External API is available on the Custom plan, not on One App Free or Standard. Odoo Community is not one of those subscription plans, so for Community installations and self-hosting we check what a given connection can do separately.
Odoo can communicate with, among others:
- an e‑commerce platform
- a PIM system
- a WMS
- marketplaces
- logistics systems
- finance tools
- supplier systems
- in-house solutions
When one element changes, we check its effect on the whole data flow
- 01
A changed product field
It can affect what the store shows.
- 02
A new order status
It may require a change to an integration.
- 03
A different way of running inventory
It can change the information passed to the sales channels.
That is why we develop not just a single Odoo feature, but also its place in the whole process.
See Odoo integrationsWhen is it worth taking over or developing an existing Odoo?
Most often when:
- the current provider is not developing the system at the pace you need
- the company has no permanent team responsible for Odoo
- some processes are moving back to Excel
- the number of manual operations is growing
- the modifications in place are hard to develop further
- integrations regularly need manual intervention
- an Odoo upgrade is planned
- a new warehouse, market or sales channel is coming
- the way you manufacture or plan is changing
- the company wants to roll out further areas of Odoo
- before every change it is hard to judge its effect on other processes
Not every such case calls for rebuilding the system. The first step is to establish where the real limitation lies. If it turns out a new environment or a change of ERP is needed, the right scope is Odoo implementation. You will find the full list of work on the system in our Odoo services.
Show us how your Odoo works todayFAQ: Odoo maintenance and development
Takeover, custom modules, integrations, upgrades and Odoo editions.
Yes. We start a takeover by getting to know the current environment, the modules in use, custom modifications, integrations and the key business processes. On that basis we set the scope of work needed before regular development begins.
Yes, if the environment in use allows custom code modules. If Odoo's standard features and configuration are not enough for a justified business process, the scope can include building or developing a custom module. Odoo Online does not support custom code modules, so such development needs a different hosting model.
No. First we check whether the need can be met with standard Odoo features or a configuration change. We add custom code when it is genuinely needed.
Yes. The scope can include analysing the existing integration, data mappings, sync directions, error handling and the changes needed on one or both sides. We describe how we design connections on the Odoo integrations page.
No. The scope of integration is not limited to one specific e‑commerce platform. The technical way of connecting depends, however, on what both systems can do and on the Odoo variant. In Odoo's subscription plans, access to the External API is provided on the Custom plan, so before designing an integration we check the edition, plan, hosting and available interfaces of the specific installation.
Yes. The scope can include analysing the current installation, preparing custom modules, a test upgrade, verifying integrations and key processes, and preparing the move to the production version.
Custom modules have to be verified and, if needed, adapted to the target Odoo version. Odoo's official documentation states that the code of custom modules must be compatible with the target version before the database is upgraded.
It can. Odoo has areas for manufacturing, inventory, purchasing, quality and maintenance, among others, so development can also cover processes typical of a manufacturer. Which features are available depends on the edition and the installed apps. For example, the standard Quality app belongs to Odoo Enterprise. We describe this in more detail on the Odoo for manufacturing page.
We always start by checking the specific installation. Community and Enterprise differ in features and licensing, and on top of that the options depend on hosting and installed modules. So before a takeover or development work we confirm what is available in the current variant and whether the planned changes need Enterprise, an additional module or a different environment.
With gathering information about the current installation and processes. Above all we need the Odoo version and edition, the hosting model, the subscription plan (if applicable), the list of modules in use, and information about custom extensions, integrations and the problems that currently make work hardest.
Let us take responsibility for developing your Odoo
Describe how your company uses Odoo today, which areas have been modified and what currently needs improving.
On that basis we will decide whether the first step should be taking over maintenance, tidying up the existing solution, fixing an integration, an upgrade or developing another process.
[email protected]ul. Jana Henryka Dąbrowskiego 28, 15-872 Białystok, Poland
What is worth preparing?
- the Odoo version and edition
- the hosting model and subscription plan, if applicable
- the list of modules in use
- information about custom extensions and integrations
- the problems that make work hardest today
Enquiry sent
Thank you, we'll get back to you within 1 business day.
The enquiry has not been sent
We have marked the fields that need filling in or correcting.