Skip to main content
iVentureTeam
Odoo Implementation

Odoo ERP Trends for 2026 and 2027: What to Plan For and by When

Odoo ERP trends for 2026 and 2027 with real dates: AI on IAP credits, e-invoicing mandates by country, the JSON-2 API cut-off, hosting and version support.

Siddharth JambukiyaSiddharth JambukiyaOdoo Techno-Functional Consultant
November 21, 202612 min read0 views
Odoo ERP Trends for 2026 and 2027: What to Plan For and by When cover

Most "ERP trends" lists describe what vendors hope to sell. This guide does the opposite: it lists what is already decided, with dates, and what each item means for an Odoo user. Our Odoo consulting services start from exactly this kind of plan.

Related service: Odoo implementation services — fixed-scope implementations with a named senior team.

This article is for owners, CFOs and IT leads who run Odoo or plan to adopt it in the next 18 months. If you want the feature view of the new release instead, read our guide to what to know about Odoo 20.

Odoo ERP trends: What to plan for and by when

The biggest Odoo ERP trends for 2026 and 2027 are paid AI usage, mandatory e-invoicing, the move to the JSON-2 API, hosting trade-offs and tighter version support. Each one has a date and an owner in your business.

TrendKey dateWho is affectedWhat to plan
AI agents on IAP creditsOdoo 20, September 2026Teams using Odoo AIA monthly credit budget and Custom plan check
E-invoicing mandatesSeptember 2026 to October 2027Firms selling in France, Germany, Spain, Poland, UAEFormat, network and master data readiness
XML-RPC to JSON-2 APIRemoval in Odoo 22 (fall 2028)Every external integrationAn inventory of scripts and connectors
Hosting choiceAny upgrade or renewalFirms with custom modulesOnline, Odoo.sh or on-premise decision
Version supportOdoo 18 ends September 2027Databases on 18 or olderAn upgrade slot before support ends
Legacy surchargeOnce a year, per agreementDatabases older than the three newest versionsUpgrade cost compared with 25% extra fees

How will AI agents on IAP credits change Odoo budgets?

AI agents in Odoo 20 change budgets because AI is now billed by usage through IAP credits, not through your own model key. That makes AI a running cost you need to forecast, like SMS or document scanning.

The Odoo AI documentation describes agents that understand natural-language requests, use tools and run inside automated workflows. It also warns that installing the AI app on the Standard plan triggers an upsell to the Custom plan.

On the Odoo AI IAP service page, credits cost EUR 1 each, sold in packs such as EUR 10, EUR 100 and EUR 500. Odoo says credit usage varies by feature, task complexity and request size. Odoo 20 also removed the setting to use your own OpenAI or Gemini key.

What this means for planning:

  • Budget owner: give AI credits a named owner and a monthly cap, the same way you treat ad spend.
  • Plan check: confirm you are on the Custom plan (US$61.00 per user a month billed yearly in the US) before rolling AI out.
  • Pilot first: run one agent on one process for a month, then measure credits used per task.
  • Governance: decide which records an agent may read and which actions need human approval.
  • External agents: Odoo AI can also connect to an outside agent through an Odoo MCP server, which shifts cost to that tool.

For real examples of where AI pays off, see our Odoo AI use cases. For a worked monthly budget, read our Odoo 20 AI and IAP credits cost breakdown.

Which e-invoicing mandates hit in 2026 and 2027?

The e-invoicing mandates that hit in 2026 and 2027 are France, Germany, Spain, Poland and the UAE, with Belgium already in force since January 2026. If you sell in any of these countries, this is the trend with the hardest deadline.

CountryDateWho must comply
Belgium1 January 2026B2B e-invoicing in force, with a first-quarter tolerance period
Poland (KSeF)1 February 2026 / 1 April 2026 / 1 January 2027Turnover above PLN 200m, then most VAT payers, then micro firms
UAE1 July 2026 pilot, 1 January 2027Pilot group first, then revenue of AED 50m or more
France1 September 2026All firms must receive; large and mid-size firms must issue
Germany1 January 2027Issuing required above EUR 800,000 turnover (receiving since 2025)
Spain (VeriFactu)1 January 2027 / 1 July 2027Corporate income tax payers, then all other obligated taxpayers
UAE1 July 2027 / 1 October 2027Revenue below AED 50m, then in-scope government entities
France1 September 2027Small and micro firms must issue
Germany1 January 2028All remaining businesses must issue
European Union (ViDA)1 July 2030Digital reporting for intra-EU B2B sales

The UAE Ministry of Finance timeline also requires each business to appoint an Accredited Service Provider before its phase starts. Dates in other countries can still move, so recheck them each quarter.

Odoo already does much of the heavy lifting. Its e-invoicing documentation says Peppol registration is free, is available in Odoo Community, and that Odoo acts as an access point for BIS Billing 3.0, XRechnung and NLCIUS.

The work that remains is yours: clean customer VAT and registry numbers, the right format per customer and tested sending. Our comparison of Odoo e-invoice formats explains which format each country expects.

Why does the XML-RPC to JSON-2 API move need a plan now?

The XML-RPC to JSON-2 API move needs a plan now because the old endpoints are already deprecated and every integration you own must be rewritten before removal. The deadline looks far away, but integration rewrites queue behind other projects.

The Odoo external API reference says the `/xmlrpc`, `/xmlrpc/2` and `/jsonrpc` endpoints are deprecated. The `db` service was removed in Odoo 20 and Online 19.1. The `common` and `object` services are scheduled for removal in Odoo 22 (fall 2028) and Online 21.1 (winter 2027).

That last date is the one many teams miss. If your database runs on Odoo Online, your old integrations face removal about a year earlier than on Odoo.sh or on-premise.

The new JSON-2 API posts to `/json/2//`, uses API keys instead of a user ID and password, takes named arguments only, and runs each call in its own transaction. The external API is only available on Custom pricing plans.

  1. List every connection: eCommerce, shipping, bank, BI, payroll and in-house scripts.
  2. Tag the method: note which use XML-RPC or JSON-RPC and which use other routes.
  3. Ask vendors: get a JSON-2 date from each connector vendor in writing.
  4. Rewrite in-house code: move to API keys, named arguments and one call per transaction.
  5. Test on a copy: run every integration against a test database before the upgrade.

Our step-by-step guide to JSON-2 API migration covers the code changes in detail.

Which Odoo hosting choice fits the next two years?

The right Odoo hosting choice for the next two years depends on how much custom code you run and how much upgrade control you need. Each option handles these trends differently.

FactorOdoo OnlineOdoo.shOn-premise
UpgradesFrequent SaaS versions every two to three monthsYou schedule major upgradesYou schedule major upgrades
Custom modulesNot supportedSupportedSupported
Extended supportNot availableLimited versions, extra feeAny version, extra fee
API removal dateOnline 21.1 (winter 2027)Odoo 22 (fall 2028)Odoo 22 (fall 2028)
Best fitStandard processes, small IT teamCustom code with managed hostingData residency or full control

The Odoo Online documentation states that Odoo Online is incompatible with custom modules and Odoo Apps Store modules. Odoo Online versions are also not supported on Odoo.sh or on-premise, so leaving Online means moving to the next major version first.

The trend we see is a split. Standard businesses move toward Odoo Online for its steady upgrades, while firms with integrations and local compliance code stay on Odoo.sh or on-premise. Our guide to Odoo Online vs Odoo.sh vs on-premise compares cost and control.

How do Odoo version support dates and the legacy surcharge shape your upgrade calendar?

Odoo version support dates and the legacy surcharge set the outer limit of your upgrade calendar: stay inside standard support, and stay inside the three newest versions. Miss either one and you pay in risk or fees.

VersionReleasedEnd of standard support
Odoo 20September 2026September 2029 (planned)
Odoo 19September 2025September 2028 (planned)
Odoo 18October 2024September 2027 (planned)
Odoo 17November 2023September 2026 (ended)
Odoo 16October 2022September 2025 (ended)

Per the Odoo support policy, security updates are only provided during standard support. You can upgrade to any major version still under standard support, or one that left it less than six months ago.

The Odoo Enterprise Subscription Agreement defines Covered Versions as the three most recent major versions. Once a year, and no earlier than six months after a new major release, databases older than that pay an extra 25% of the annualized price.

With Odoo 20 out, the covered versions are 18, 19 and 20. By our reading, a database on Odoo 17 or older can face the surcharge from about March 2027. If Odoo keeps its once-a-year cadence, Odoo 18 drops out when the next major version arrives.

Our explainer on the Odoo legacy surcharge shows how to compare the fee with the cost of upgrading.

ERP trends in 2026 land differently by industry: exporters feel e-invoicing first, retailers feel integrations, and service firms feel AI costs. Use the table to see which trend should lead your plan.

IndustryPain or cost driverOdoo approachHow iVentureTeam helps
Manufacturing and exportE-invoice mandates in EU customer countriesPeppol access point and country formatsMap formats per customer, test sending
Wholesale and distributionEDI and shipping connectors on old APIsJSON-2 API with API keysInventory and rewrite integrations
Retail and eCommerceMarketplace and storefront sync breaking at upgradeTested connectors on a staging copyUpgrade testing and connector fixes
Professional servicesAI drafting and summaries adding credit costsOdoo AI agents on IAP creditsPilot one agent, set a credit budget
UAE and GCC tradersAED 50m threshold and ASP choiceLocalization plus provider connectionReadiness review before your phase
Multi-country groupsDifferent dates per subsidiaryOne database, country formats per companyOne calendar across all entities

What should be on your Odoo planning calendar, quarter by quarter?

Your Odoo planning calendar should put compliance first, upgrades second and AI third, because only the first two have legal or contract dates. Here is the order we suggest for most clients.

  1. Q4 2026: list every country you invoice, every integration and your current version. Run a free Odoo health check to see where your database stands.
  2. Q1 2027: finish German and Spanish e-invoicing readiness, and UAE readiness for large firms. Move any Odoo 17 or older database onto an upgrade plan.
  3. Q2 2027: prepare for the UAE second phase and the Spanish July date. Start a small AI pilot with a credit cap.
  4. Q3 2027: finish French readiness for small firms, and upgrade off Odoo 18 before its September 2027 end date.
  5. Q4 2027 to 2028: finish the JSON-2 rewrite. Odoo Online users should treat winter 2027 as their real API deadline.
Where does your Odoo stand? Check it free

iVentureTeam turns Odoo ERP trends into one dated plan, then delivers the upgrade, compliance and integration work behind it. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.

  • Trend review: your countries, integrations, version and hosting checked against every date in this guide.
  • Upgrades: our Odoo upgrade services move you to a supported version with custom modules tested.
  • E-invoicing: format setup, Peppol registration and country localization for each company.
  • API rewrites: XML-RPC and JSON-RPC integrations moved to JSON-2 with test runs.
  • AI pilots: one agent, one process, a credit budget and approval rules before wider rollout.

This is a closest-fit example, not an AI or e-invoicing project: it shows what happens when a business falls behind Odoo's support window and has to catch up. It predates Odoo 20.

EvoLogics GmbH, a German subsea technology company, ran Odoo 12 Enterprise with a large body of custom business-flow code. It was three major versions behind, cut off from newer features and current security patches.

We audited every custom module, then migrated the database and the custom code in parallel to Odoo 15 Enterprise. Full testing on the migrated database came before production. The project took 12 weeks, with less than one day of cutover downtime.

The lesson for 2027 planning is timing. A three-version jump is possible, but a planned one-version upgrade each cycle is far easier. Read the EvoLogics Odoo 12 to 15 Enterprise migration case study.

The Odoo ERP trends for 2026 and 2027 reward businesses that plan by date: e-invoicing first, supported versions second, API rewrites third and AI when the basics are stable. None of them needs to become a crisis.

The future of ERP is less about new screens and more about dated obligations. Write down your countries, integrations, version and hosting today. Match them to the dates above, and you will know which project comes first and roughly when each one must be finished.

Ready to build your 2027 Odoo plan?

Get a 2027 planning review

Turn these deadlines into a dated plan for your own database. Get a 2027 Odoo planning review, call +91-90235-15208, or email business@iventureteam.com.

Frequently Asked Questions

+

The main ERP trends for 2026 are AI agents billed by usage, mandatory e-invoicing in more countries, API modernization and shorter tolerance for old versions. For Odoo users, each of these now has a published date.

Does Odoo 20 AI cost extra?

+

Yes. Odoo 20 AI runs on Odoo AI IAP credits at EUR 1 per credit, and installing the AI app on the Standard plan triggers an upsell to the Custom plan. Usage depends on the feature and task size.

Can I still use my own OpenAI key in Odoo 20?

+

No. Odoo 20 removed the setting to use your own OpenAI or Gemini key for built-in AI features. You can still connect an outside AI agent to Odoo through an Odoo MCP server.

When will Odoo remove XML-RPC?

+

XML-RPC and JSON-RPC are deprecated in Odoo 20. The common and object services are scheduled for removal in Odoo 22 (fall 2028) and in Odoo Online 21.1 (winter 2027). Plan JSON-2 rewrites well before then.

Which countries require e-invoicing in 2027?

+

Germany (larger firms from 1 January 2027), Spain's VeriFactu (from January and July 2027), the UAE (from January 2027 in phases), Poland's micro firms and French small firms from September 2027. Recheck dates each quarter.

Does Odoo support Peppol e-invoicing?

+

Yes. Odoo acts as a Peppol access point, registration is free and available in Odoo Community, and supported formats include BIS Billing 3.0, XRechnung and NLCIUS. You still need clean customer identifiers.

When does Odoo 18 support end?

+

Odoo 18 standard support is planned to end in September 2027. After that it receives no security updates, and extended support is only offered on Odoo.sh for limited versions or on-premise, for an extra fee.

What is the Odoo legacy surcharge?

+

It is an extra fee of 25% of the annualized subscription price, charged once a year for databases older than the three most recent major versions. It applies no earlier than six months after a new major release.

Should I move to Odoo Online to stay current?

+

Only if you run standard processes without custom modules. Odoo Online upgrades often and does not support custom or Apps Store modules, so firms with integrations usually stay on Odoo.sh or on-premise.

Free Odoo upgrade plan

Planning an Odoo upgrade?

Tell us your version, edition and custom modules. We check what breaks, what it costs to fix and the safest path, before any work begins.

Free, with no obligation. A senior consultant replies within 12 business hours.

We use cookies to improve your experience

Essential cookies make the site work, and we use analytics to improve it. Choose “Only necessary” to turn analytics off. See our cookie policy.