Odoo 20 is available, and Maxcode has already adapted its Croatian add-ons to the new version and installed them in a development environment. If you are considering an implementation or upgrade, you can now compare the concrete updates with your business processes. Availability of the new version and readiness of the add-ons are an important start, while moving an existing business database requires separate preparation and verification.
This overview was updated on 24 September 2026 using the official release notes, the current Odoo price list for Croatia and documented Maxcode adaptation work. It is intended for companies that want to connect accounting, CRM, sales, purchasing, inventory, manufacturing, projects and automation.
What does Odoo 20 bring to business users?
The official Odoo 20 release notes were published for September 2026. Practical updates include reviewing sales results alongside quotations, creating projects from sales opportunities, comparing bills of materials and suggestions for minimum and maximum inventory levels based on demand history. In purchasing, comparison of alternative quotations is improved, while accounting connects a vendor bill more clearly with a purchase order.
These changes should be considered through your own business. If sales promises a delivery date without checking materials, a demonstration should cover the quotation, reservation, purchasing and delivery. If a project manager cannot see expected profit, verify how planned and actual costs are recorded. A list of new functions alone does not answer these questions.
Before deciding, choose one regular task and one exception. An exception can be a partial delivery, a supplier price change or a goods return. Ask to see the entire flow in the system, with documents and responsible people.
What has Maxcode already adapted for the Croatian market?
I have already adapted Croatian localisation and related business add-ons for Odoo 20. Adapted modules are installed in a development environment, and focused checks of accounting, sales, purchasing, inventory and other connected flows have been carried out.
The adaptation covers accounting and tax flows, fiscalisation add-ons, advance payments, bank statements, payroll and JOPPD, as well as links between operational documents. Croatian translations of selected accounting and HR menus have also been checked in the development environment. The exact set included in an individual project is determined by the company's way of working, the Odoo edition and agreed integrations.
This confirms adaptation of the add-ons and checks in a development environment, not production go-live or every special payroll scenario. An existing company still needs to verify its data, open invoices, inventory, payroll calculations and links to external systems. Production certificates, information-intermediary services and accounting procedures require particular checks and acceptance by the responsible person and accountant.
Croatian localisation is not only translation of menus. What matters is what happens when a user issues an invoice, receives goods, calculates an advance payment, imports a statement or prepares a report. Preparation therefore starts with real documents, with sensitive data removed where it is not needed. The broader scope is explained on the Odoo accounting in Croatia page.
How should you read current Odoo prices?
On the date of verification, the official Croatian price list in EUR displays Standard at €11.90 and Custom at €22.90 per user per month with annual billing and an introductory discount. The displayed regular prices for that billing model are €14.90 and €27.90. The discount applies for 12 months to users ordered initially. Check current amounts and conditions in the official Odoo price list.
The subscription is one project item. Implementation, Croatian add-ons according to scope, migration, integrations and training must be considered separately. Odoo.sh hosting and maintenance of adapted code are also estimated separately. A final proposal should clearly state tax treatment and the total amount for your company.
If you introduce your own modules, hosting choice is particularly important. Odoo Online does not accept arbitrary custom modules. The choice between Standard and Custom should therefore be tied to planned configuration and the way you work, not only to the lower displayed amount. For the structure of total cost, see Odoo pricing and implementation.
Does Light User change user planning?
Odoo now also lists a Light User licence at €4.90. It has a limited scope and is not a substitute for a full user in sales, purchasing, projects or accounting. Employee roles should therefore be listed before calculating the subscription, including people who use only limited actions or exist as an HR record.
For every role, write down which documents the person opens, what they may confirm and where they only need to see data. Then verify that matrix with the licence provider. Do not automatically assume that every employee is a full user, but do not assume that an employee without a login necessarily has no effect on the new licence either.
What should you check about AI capabilities?
Odoo 20 extends AI agents to creating and updating records, working with files and calling them through automated actions. The official notes state that AI functions require IAP credits. The cost of their use should therefore be included alongside the subscription.
The business question is who verifies the result. An agent that prepares a purchase-order proposal does not carry the same responsibility as a process that confirms it automatically. Before enabling it, define allowed actions, limits, human confirmation and a way to verify outcomes afterwards. The first trial should have a small scope and a known expected result.
Should you upgrade an existing Odoo immediately?
The release date alone is not sufficient for a production upgrade. First make a backup and a test migration. Compare open documents, opening balances, calculations and key reports, then run the same business scenarios you use in daily work.
Also check less visible parts: user roles, automated actions, printing, email, statement imports and integration errors. If data exchange stops, it must be clear how the delay is found and who resolves it. This is part of system acceptance, not an addition after go-live.
Migration of historical data is agreed separately. A new version is not a reason to change old postings or business results at the same time. What is transferred and how it is verified should be decided before production work.
What should you prepare for a conversation about Odoo 20?
Prepare a short list of processes you want to connect, user roles, the current version and systems that remain in use. Add an example of a document that currently requires re-entry and a case in which an error occurs most often.
If you already use Odoo, list additional modules and integrations. If you are only choosing an ERP, describe the work in your own words. You do not need to know application names or decide in advance which version or licence you need.
If you want to assess Odoo 20 for your company, send a description of the process and existing system. I will check whether the new version suits your scope, which Croatian adaptations you need and what needs to be proven before work begins.
