Blog
How to scope an Odoo implementation
A practical way to bound the first Odoo release: processes, edition, custom work, data, and the people who accept it.
By Alfatih Ridho NT2 min read
- implementation
- scope
Blog
A practical way to bound the first Odoo release: processes, edition, custom work, data, and the people who accept it.
By Alfatih Ridho NT2 min read
A useful scope tells your team where the first release stops. It names the processes that move into Odoo, the processes that stay outside, and what done means.
List the work as the company performs it. How is an order promised? How is stock reserved? How is a bill approved? How is a payment matched? The Odoo app menu is a catalog. It becomes a design only after those steps are written down with the people who do them.
Bring the person who will live with the daily exception, along with the person who sponsors the project. Exceptions are where an implementation grows without anyone deciding that it should.
Odoo 20, released in September 2026, is the current major version. A supported earlier version is still a sound target when the upgrade is its own project. Community and Enterprise are different products. The difference shows up in the license, the applications, the hosting options, and the upgrade path. Confirm the application list for the chosen version against Odoo’s edition comparison before the scope is treated as fixed.
Hosting belongs in the same decision. A system on your own servers, on a host you already use, or on Odoo’s platform changes who applies updates and who is called when the database is unreachable.
Configuration is a setting Odoo already offers. Customization is code, or a view change, that your team will carry into the next version. Integration is a conversation with another system, including what happens when that system is down.
Write these in three lists. A scope that only says “Sales and Inventory” cannot be estimated honestly until that split exists. The lists also protect the upgrade. Custom code that stays small and outside the Odoo core can move forward. Custom code that rewrites a standard flow becomes the project you repeat next year.
The first day needs products, partners, a chart of accounts, open orders, stock on hand, and opening balances. It rarely needs every historical transaction inside Odoo. Say which records are in the first load, who owns the cleanup, and which figures must be reconciled before anyone posts a live invoice.
Deferred work is part of the scope. A second warehouse, a customer portal, or a shop-floor terminal can wait, and the scope should say why. Work that is described only as “later” tends to return to the first release the moment someone asks for it.
Name the people who will try the configured system and say whether it matches the scope. Acceptance is a comparison with the written boundary. Give the meeting an agenda: the processes in the first release, tried with realistic data, by the roles that will use them.
When that group is unnamed, go-live becomes a negotiation. Naming them early is one of the cheaper decisions in the project.