Custom modules
Processes Odoo doesn't include, such as a commission calculation with your rules or your own approval workflow. Each module comes with its documentation and its tests.
First we check whether Odoo already does it or whether configuration solves it. If development is needed, the module is tested separately and reaches production after review by a second person.
Custom developments are often born in a hurry: a change made directly on the server, untested and undocumented. They work until it's time to upgrade or the person who built them leaves.
And often they weren't needed. Odoo covers more out of the box than it seems, and each version covers more.
Always in this order: standard, configuration and, if there's no other way, code.
Processes Odoo doesn't include, such as a commission calculation with your rules or your own approval workflow. Each module comes with its documentation and its tests.
Odoo connected to your bank, to another Odoo instance or to other programs in your company. With a log of what is synchronised and an alert when something doesn't add up.
Quotes, delivery notes and invoices in your company's format. And reports that come straight out of Odoo, without going through a spreadsheet first.
A new field or a different view doesn't need a module. They're handled with Studio and saved along with the rest of the configuration.
When a new version of Odoo comes out, we review your modules against it and adapt them. We've already done this with custom modules for Odoo 20.
What the development has to do and how to check that it does it. With that, we give you the scope and the price before starting.
There are no copies of your database on the team's laptops. Development is done on a sample database with the same configuration as yours.
The change is installed first in a test environment, separate from production. That's where you check it before giving the go-ahead.
Only what has passed testing and been reviewed by another member of the team reaches production. Nobody changes code in production by hand.
You have a set period to check it in real use, once it's in production. Anything that doesn't meet what was agreed is fixed at no cost.
Each company handled its IT its own way. Now the group has a single point of contact for the ERP, Microsoft 365 and the monitoring of its computers
Production applications on a monitored server with backups. Project planning inside Odoo. And a single support team.
The group's consolidated accounts came from a spreadsheet built by hand. We are moving them into Odoo, with every figure traceable to its source.
Functional design process by process, written acceptance criteria, a fixed price and support through go-live.
Odoo Private SaaS: your Odoo on a dedicated server in the European Union, with backups, updates and monitoring.
A help desk for your Odoo: questions, bugs and small changes, with measured response times.
You get a perpetual licence to use and modify it in your company and your group, including with another provider. SolveIT holds the ownership and can reuse parts in other projects without using your information. If you need ownership or exclusivity, it's agreed in the proposal.
Yes, after reviewing them. We look at the code and how it's deployed, and tell you what can be maintained as it is and what would be cheaper to rebuild.
They have to be adapted for each version; nobody can avoid that. What changes is the cost: a module that has tests and doesn't touch Odoo's core is adapted much faster than one built in a hurry.
No. Custom modules work on Community and on Enterprise. What doesn't accept them is Odoo Online, the vendor's cloud service. Studio does require Enterprise.
It depends on the requirement. Small changes can be covered by the support contract. Anything else is quoted with a scope and a fixed price before a line of code is written.
Tell us which process is left out. We'll tell you whether configuration solves it or development is needed.