ERP 2026: the uncomfortable truth

Not a marketing ranking. A reading of the forces that really matter for French SMEs, mid-sized companies and large accounts, at a time when the market is moving faster than it has in ten years.

This article starts from a base you may know: the overview published by foxeet.fr — Logiciel ERP: Top 13 most used in France (2026). The work is serious, the market positions are up to date, the tone is honest. We build on it to enrich it, correct it on a few factual points — notably Odoo pricing, which floats around like a lost duck —, detail the real strengths and weaknesses of each player, and offer a reading that diverges on one central point: the base article reserves Odoo for very small businesses and SMEs. Our field experience shows that this positioning is now as dated as a fax in a Teams meeting.

First, what an ERP is — and why this choice commits your company for ten years

An ERP (Enterprise Resource Planning) is the central software that drives all of a company's operations: sales, purchasing, inventory, manufacturing, accounting, payroll, human resources, sometimes e-commerce and after-sales service. It is the organization's “nervous system”. Well chosen, it streamlines work, makes data reliable and frees up time. Poorly chosen, it becomes a permanent burden, slows teams down, and costs far more than planned — often at the precise moment when cash flow really did not need that.

Choosing an ERP is not comparing features in an Excel table. It is committing for 7 to 10 years to a vendor, an integration partner, and a technical trajectory. At that scale, bad choices are not fixed — they are lived with. This article aims to give you the keys to assess this choice with clear eyes.

The landscape has changed in twelve months

Four forces are reshaping the French ERP market right now, and none of them was top of the agenda two years ago.

Mandatory electronic invoicing. From September 1, 2026, all French companies will have to receive their supplier invoices in a standardized electronic format. Large companies and mid-sized companies will also have to issue them in this format on the same date. SMEs and micro-enterprises join the issuing obligation on September 1, 2027. Penalties apply: €500 from the first offense, up to €15,000 per year. Every French company must also appoint an official platform that will act as the intermediary with the tax authorities (called an “Accredited Platform”). It is an ERP topic before it is a tax topic — the software must know how to produce, receive and transmit these invoices in the right format.

Artificial intelligence enters the ERP. In 2026, AI is no longer limited to an assistant that helps draft an email (which, on reflection, was already a modest use case for a technology described as revolutionary). It executes tasks: validating a supplier invoice, triggering a replenishment order, classifying an expense report. Microsoft announced in April 2026 the rollout of these “autonomous agents” in its Business Central ERP. Odoo has integrated AI into all its modules since version 19 and is preparing a ramp-up in 20. It is a structural change: the ERP stops being a data-entry tool and becomes an assistant that acts.

Costs are rising everywhere. Annual increase of 3 to 7% at Odoo, +10% per year at NetSuite (Oracle's ERP, true to its reputation), a special 25% surcharge introduced by Odoo in April 2026 for customers who remain on versions more than three years old — a polite way of reminding them to upgrade. The historic promise of open-source software — almost zero license cost — is eroding. But in the field, Odoo remains two to four times cheaper than its direct competitors.

Integration partners are consolidating. The market of firms that install Microsoft Dynamics set a record for mergers and acquisitions in 2025, and the pace is accelerating in 2026. On the Odoo side, several leading integrators report growth above 50% over the year, attracting the interest of investment funds. For the IT director or the executive choosing a partner in 2026, the risk is no longer the quality of the service at the start. It is the stability of the team two to three years from now.

The architecture argument: why Odoo's engine is ahead

Before comparing the players one by one, a point that the foxeet article does not cover and yet weighs heavily on ten years of total cost: the technical quality of each ERP's “engine”. Imagine a car. You can judge its bodywork, its dashboard, its equipment — but it is the engine, its reliability and its modernity, that determines how it behaves over ten years. For an ERP it is the same: behind the screens used by teams, there is a software engine. And on this engine, the gap between Odoo and the rest of the market has become structural.

A modern and open programming language

Odoo is built with Python, the most widely used programming language in the world since 2022. It is also the reference language of artificial intelligence (tools like ChatGPT, forecasting models and image recognition systems are almost all written in Python). It is the language most taught in engineering schools and bootcamps. Concrete consequence: finding a Python developer is much easier than finding a developer in the proprietary languages used by other ERPs — some of which have become so rare that they are recruited almost through obituaries.

Let's compare the daily cost of an expert developer (TJM = Taux Journalier Moyen, the average daily rate billed per day of work):

• Experienced Odoo developer in France: €600 to €900 depending on experience. Nearshore (Maghreb, French-speaking Africa) drops to €250-400.
• AL developer (Microsoft Business Central's proprietary language): €700 to €1,100. Chronic shortage.
• ABAP developer (SAP's proprietary language): €900 to €1,500. Tight market, few young people trained. In ten years, it will be a living museum.
• 4GL developer (Sage X3's proprietary language): €700 to €1,000. Small population, long training, and wondering every year whether they would do better to retrain.

On a mid-sized company project with 100 days of custom development, the gap between Odoo and a proprietary ERP represents €30,000 to €60,000 on the initial investment — and as much at every major change over 7 to 10 years. With an Odoo nearshore team (which most serious integrators use), the gap doubles.

The other consequence, less visible today but structural tomorrow: Odoo can natively integrate any artificial intelligence technology. Connecting Odoo to an AI assistant, a document recognition tool, a sales forecasting engine — it is simple and fast. Proprietary ERPs do not have this ease, because their internal languages were designed when AI was still called “expert system” and fit on a floppy disk.

A powerful and free database

Odoo stores its data in PostgreSQL, considered the best open-source database on the market. Adopted by all the major cloud players (Amazon, Microsoft, Google), it is free, high-performing, and geared to modern uses (large volumes, fast search, AI capabilities).

Quick comparison:

• Sage X3: uses Microsoft SQL Server or Oracle Database (additional license of €8,000 to €30,000).
• Cegid XRP: SQL Server.
• Microsoft Business Central: SQL Server.
• NetSuite: Oracle Database (included in the overall price, but subject to Oracle's 10% annual increase).

Over 5 to 10 years, the cumulative database license cost can represent €30,000 to €150,000 that you do not pay with Odoo.

A modern architecture, not a patchwork of stacked versions

Odoo was designed as a single block, with overall consistency. When a developer creates an extension for the accounting module, it works with the same logic as for the sales or HR module. Everything is designed so that you extend the standard without ever rewriting the core of the software — which is exactly what allows you to upgrade Odoo versions without breaking everything.

In contrast, many of its competitors look like family homes: a veranda was added in the 90s, the kitchen redone in 2010, and a heat pump stuck on last summer. Everything works, but the whole is not exactly coherent.

• Sage X3 relies on an engine dating from the 90s, over which a modern interface has been laid. Two generations of technology coexist, with the complications that implies.
• Microsoft Business Central is in the middle of a transition between its old language (C/AL) and its new language (AL). Many existing installations mix the two, which complicates changes and delights consultants who specialize in debugging.
• Cegid XRP comes from several successive acquisitions (Talentsoft for HR, Meta4 for international payroll). The building blocks are not yet fully unified — people sometimes speak of a “patchwork”, a term that salespeople prefer to rephrase as “modular platform”.
• NetSuite uses a proprietary language (SuiteScript), poorly standardized, with a small community (mostly North American).

Practical consequence: a well-written Odoo module that follows the conventions migrates quickly from version 17 to version 19. No migration is completely automatic, but modern AI tools significantly speed up developers' work and reduce bugs.

Ergonomics designed for the end user

The point rarely cited in comparisons, but which determines real adoption in teams: Odoo has the best ergonomics in the ERP market. Clear interface, consistent navigation from one module to another, responsive behavior on mobile, universal search. A new employee gets going in a few hours, where Sage X3, NetSuite or the others require several days of training — training that is partly forgotten by the following weekend.

This is an economic matter, not a cosmetic detail: an ERP that is not used, or that is bypassed through Excel (because it is still the fastest way to get a correct report), destroys the value of the investment. The real adoption rate after go-live is one of the most important indicators to track, and one of the most rarely audited six months after go-live.

Open source: not just a price advantage

Odoo's source code is public (for the Community version) or accessible to customers under contract (for the Enterprise version). Concretely, this means you are never a prisoner of your vendor. If you change integrator, you keep control. If you want to audit security, you can. If you want to take the project over in-house, it is possible.

Conversely, on a proprietary ERP (Microsoft, Oracle, SAP, Sage, Cegid), the code is closed and dependence on the vendor is total. This argument grows in importance with the consolidation of integrators: if your partner firm disappears or is acquired, the Odoo customer keeps control of their project.

The French market: six serious players, no more

Odoo

The Belgian vendor is leading the race in the French SME–mid-market segment. Valuation of €8.6 billion in February 2026, up 72% in fifteen months. 2025 revenue of €650 million, growth above 40%. 7,000 employees, target of 10,000 in 2026. France has become Odoo's second-largest market, with 13,000 customers under contract.

The structuring event: Odoo opens its French subsidiary in Lyon in May 2026, in the Part-Dieu district. Joséphine Vander Linden takes charge. 100 hires targeted by the end of 2026, up to 800 over five years.

Reference price in 2026: €29.90/user/month on an annual subscription on the Custom plan (€37.40 monthly). This plan includes all Odoo Enterprise modules — accounting, sales, purchasing, inventory, manufacturing, CRM, HR, project, helpdesk, e-commerce, point of sale — with hosting by Odoo, the possibility of self-hosting, connection to third-party systems, multi-company management, and access to third-party developed modules. This is the price to compare with those of Cegid, Sage and Microsoft: with equivalent features, Odoo remains two to four times cheaper.

Strengths

• Modern technical architecture (Python, PostgreSQL) — 5 to 10 years ahead of legacy ERPs.
• The best ergonomics in the ERP market, high adoption rate in teams.
• Broad functional coverage: sales, purchasing, inventory, manufacturing, CRM, HR, native Belgian payroll, e-commerce, POS, project, helpdesk, accounting, more than 50 native modules.
• Complete and standalone French accounting: electronic invoicing, FEC (Fichier des Écritures Comptables), DSN (Déclaration Sociale Nominative), VAT, and now standard generation of the tax return package (liasse fiscale) in the latest versions. An SME or mid-sized company can keep all of its accounting in Odoo, without third-party software.
• Very powerful multi-axis analytic accounting, included as standard. Where SAP, Sage X3 or NetSuite charge for a dedicated module (CO at SAP) or require heavy configuration, Odoo natively offers tracking by project, by cost center, by activity, by vehicle, cross-referenced on several axes simultaneously. It is one of the points where Odoo functionally surpasses Cegid and Sage X3 for everyday needs.
• Open source: no locked-in dependence on the vendor, accessible code, audit possible.
• Unbeatable total cost: license + integration + development 30 to 50% below proprietary competitors with equal features.
• Native multi-country: 50+ local adaptations maintained, particularly strong in Europe and French-speaking Africa.
• Gradual deployment possible: modules are activated in phases, no need for a “big bang” project.
• Very broad ecosystem of add-on modules developed by the community or partners.
• Fast roadmap: one major version per year, AI features rolled out across all modules since version 19.

Weaknesses

• No native French payroll in Odoo. It is a real limitation that the vendor does not address (French payroll remains one of the most complex in the world, with 200+ collective agreements and a shifting regulatory framework). Going through a connector to a specialized solution is the market standard. ANOR has developed a native Odoo ↔ OpenPaye connector that effectively erases this limitation: payroll is outsourced to OpenPaye, a specialized French provider, and accounting entries, DSN filings and payslips flow back automatically into Odoo. For the customer, the experience is that of an “all-in-one” ERP at an overall cost lower than Cegid or Sage payroll.
• Heavy manufacturing industry (automotive, aerospace, large chemical processes) remains better covered by specialized ERPs.

Cegid

Third-largest French ERP vendor, founded in Lyon in 1983, 3.5 million payslips processed per month. Four main solutions: XRP Flex for SMEs (50 to 500 employees), XRP Sprint for SMEs with specific needs, XRP Ultimate for mid-sized companies, Orli for fashion and luxury. Observed prices: €70 to €110/user/month for XRP Flex, €120 to €180 for Ultimate.

Strengths

• Native French regulatory compliance, continuously updated (tax returns, social declarations, international accounting standards, electronic invoicing).
• Solid functional depth in multi-country payroll via the Meta4 solution and in accountant workflows — ground where Cegid retains specific expertise.
• Native French hosting, sovereign data.
• Dense network of partner accountants who ease data takeover and support.
• Dedicated sector coverage (Orli for fashion, specialized retail modules).

Weaknesses

• Proprietary technical architecture (.NET, SQL Server), uncertain longevity over ten years.
• Post-acquisition accumulation effect (Talentsoft, Meta4): modules not yet unified, uneven user experience from one module to another.
• Weak supply chain and manufacturing coverage compared with Sage X3 or Odoo — unsuited to industry.
• Implementation cost and hourly development cost among the highest in the French market: a Cegid project typically costs 40 to 70% more than an Odoo project with equivalent features.
• Rigid custom development: going through proprietary configurators, strong dependence on the vendor or a certified firm, long delivery times.
• User ergonomics lagging (dense forms, clunky navigation), adoption sometimes difficult.
• No clear calendar of major versions, the product trajectory is less readable than that of Odoo or Microsoft.

Sage

Sage 100 and Sage X3 form the densest installed base in the French SME market. Sage 100 remains the standard for very small businesses/SMEs in accounting and sales management; Sage X3 targets structured industrial SMEs. Sage X3 prices: €80 to €120/user/month in the cloud, €200,000 to €800,000 for a perpetual license.

Strengths

• Historic functional depth in heavy industry and complex trading (production management, fine traceability), the legacy of 25 years of specialization.
• Massive installed base: finding an accountant who knows Sage 100 or an ERP manager who knows Sage X3 is easy.
• Quality support in France, with plenty of staff.
• Structured e-invoicing ecosystem (Sage Network accredited platform, connectors, supplier invoice dematerialization).
• Sage 100 remains unbeatable for accounting-centric very small businesses up to 20 users.

Weaknesses

• Sage X3: aging technical engine, modern interface laid over an old core, visible technical debt.
• Ergonomics 10 years behind Odoo and Microsoft.
• High total cost of ownership: Sage X3 implementation typically 50 to 100% more expensive than an equivalent Odoo project, particularly on multi-site deployments with customization.
• Rigid custom development: old proprietary language (4GL), no modern extension framework, long ramp-up for developers, stretched delivery times on changes.
• Small and aging community of specialized developers, foreseeable scarcity.
• Sage X3 cloud strategy still being stabilized.
• Technical documentation partly closed, slow ramp-up for a new integrator.

Microsoft Dynamics 365 Business Central

Business Central won over 4,200 French companies in 2025 according to Microsoft France. Essentials price around €70/user/month, Premium at €100.

Strengths

• Native integration with Microsoft 365 (Outlook, Excel, Teams, SharePoint, Power BI) — a decisive argument if the company already lives in that universe.
• Agentic AI ahead: the April 2026 update industrializes autonomous agents (expense reports, accounts payable, logistics execution).
• Extension tools (Power Platform) that make it possible to build connected applications without touching the core of the ERP.
• Azure hosting in France available.
• Financial strength of the vendor, clear and predictable version calendar.

Weaknesses

• High implementation cost: a typical mid-sized company Business Central project typically comes out 60 to 100% more expensive than an Odoo project with equivalent features, because of the complexity of the ecosystem (Power Platform, AL, partner certifications).
• Rigid custom development: proprietary AL language, developer shortage, high hourly cost, extension process constrained by the Microsoft architecture.
• Strong dependence on the Microsoft ecosystem: if the company leaves Microsoft 365, the value of Business Central collapses.
• Ergonomics improving but not at Odoo's level, particularly on large data-entry screens.
• Microsoft product priorities aligned with very large accounts, sometimes far from the needs of French mid-sized companies.

Divalto Infinity

A French vendor specialized in the industrial SME–mid-market segment, Divalto Infinity costs between €50 and €90/user/month.

Strengths

• Complete functional coverage of production management, job management, field after-sales service.
• Native French hosting, French vendor.
• Strong industrial expertise in the integrator network.
• Decent ergonomics, modernization under way.
• Good value for money in the industrial mid-market segment.

Weaknesses

• Small integrator network, few options in case of disagreement with the historic partner.
• E-commerce, retail and services coverage lagging behind Odoo.
• Limited technical community, few add-on modules, which makes custom development more rigid and more expensive than with Odoo.
• Implementation cost higher than Odoo for an equivalent scope, due to the scarcity of integrators and the shallower depth of the third-party module ecosystem.
• Less ambitious functional roadmap, no strong AI positioning.
• Low commercial visibility outside industry: a non-industrial executive never hears about Divalto.

NetSuite (Oracle)

NetSuite remains relevant for mid-market groups with strong international exposure, multi-currency, multi-jurisdiction, with complex financial consolidation.

Strengths

• Global reference on complex financial consolidation and international accounting standards.
• Deep multi-country, multi-currency, multi-jurisdiction handled natively.
• Platform stability, huge international installed base.
• Advanced customization for those who master the environment.

Weaknesses

• Annual license increase of ~10%, structural.
• Very high implementation cost: a typical mid-sized company NetSuite project typically comes out two to three times more expensive than an equivalent Odoo project, due to American specificities to adapt, localization costs and the pricing of Oracle-certified integrators.
• French adaptation to be completed with third-party modules or developments.
• Rigid custom development: proprietary SuiteScript, small community outside the USA, extension process constrained by the vendor, stretched delivery times.
• Oversized and out of budget for a single-entity French SME.
• Historically aging ergonomics, modernization under way but not finished.
• Oracle lock-in: changing platform away from NetSuite is a multi-million project.

Three underlying trends to understand

The cloud has won — except for Odoo, which maintains self-hosting

72% of new ERP projects in France are in the cloud (IDC study, 2025). Self-hosting (“on-premise”, i.e. installing the software on the company's own servers or with a dedicated host) remains massively used in defense, nuclear, healthcare and organizations with strong sovereignty or cybersecurity constraints.

On this front, beware of a trap: for most proprietary ERPs (Sage, Cegid, Business Central, NetSuite), self-hosting has become a degraded mode — research and development budgets go to the cloud, and self-hosted versions live in survival mode. Odoo is the exception: self-hosting is maintained at functional parity with the Odoo.sh cloud. It is a fully supported option, chosen every year by a significant share of new French mid-sized and large-account customers.

What is at stake behind the cloud shift is the end of the traditional perpetual license model. No more usage rights to amortize over five years, no more massive provisions. Instead, a monthly subscription that weighs on profitability year after year. It is a change of financial model that should be discussed at the executive committee before being decided by the IT department.

AI in the ERP: between promise and real value

Every vendor sticks an AI assistant on their product and sells it as revolutionary — it has become a mandatory part of the sales pitch, much like “our solution is cloud-native” five years ago. In production, in 2026, the only use cases that really work are demand forecasting, accounting anomaly detection and supplier assessment. What is useful, measurable, with a clear return on investment.

The 2026 turning point is AI that executes. An agent no longer suggests, it acts — it validates a supplier invoice, triggers a replenishment order, classifies and allocates an expense report. Microsoft is the first to industrialize this approach in Business Central. Odoo is heading in the same direction with version 20, with a significant structural advantage: being written in Python, Odoo is technically the simplest to connect to current and future AI models. The question for the IT director is no longer “does this ERP have AI?” (they all do, more or less well), it becomes “what scope of action do I delegate to an agent, and with what governance?”.

Sovereignty becomes a criterion again

35% of public tenders now require French hosting. This was outside the top 10 criteria three years ago. The European Data Act adopted in 2025 has accelerated the movement, and general management teams now take the question seriously — not just IT directors.

On this front, the analysis deserves to be more nuanced than “French vendor = sovereign, others = not sovereign”. The real sovereignty of an ERP is measured by six criteria: nationality of the vendor, location where data is hosted, access to the source code, ability to retrieve your data in an open format, ability to change provider easily, and resistance to extraterritorial laws (notably the US Cloud Act, which can compel an American company to provide its customers' data to US authorities, even if the servers are in France).

What Odoo enables in terms of sovereignty — and which is not nuanced in the foxeet article:

• Free choice of hosting. The customer chooses where their data lives. Odoo.sh, Odoo's official cloud, currently runs on Google Cloud Platform — like the vast majority of cloud ERPs on the market that rely on American hyperscalers (Microsoft Azure for Business Central, Oracle Cloud for NetSuite, AWS/Azure for Sage Cloud). At this level, Odoo is not at a disadvantage compared with its competitors. The real difference is that Odoo on the Custom plan also allows self-hosting with OVHcloud, Scaleway, Outscale, or directly on the company's own servers. This flexibility is unique in the ERP market: it is the only solution that allows an organization with sovereignty concerns to switch to a 100% French, SecNumCloud-qualified infrastructure without changing ERP. Sage X3, Cegid, Business Central and NetSuite impose their proprietary cloud infrastructures, with no equivalent sovereign option.
• Accessible and auditable source code. Odoo Community is under a free license (entirely public). Odoo Enterprise is accessible to customers under contract. For an organization with security concerns, this allows an independent audit — a possibility technically nonexistent at Microsoft, Oracle, Sage or Cegid.
• Data recoverable at any time in an open format. Odoo stores data in PostgreSQL, an open and standard format. At any time, the customer can download all of their data, restore it elsewhere, import it into another tool. By contrast, NetSuite, Business Central and Sage X3 use proprietary formats that are much harder to extract.
• Simple contractual reversibility. The Odoo customer who changes integrator takes back their sources, their database, their settings, and continues with another partner. The SAP, NetSuite or Business Central customer who changes integrator discovers that technical mobility is never that simple, and that the vendor remains an unavoidable gatekeeper.
• Compatibility with very-high-security hosts. For organizations subject to high cybersecurity constraints (healthcare, defense, operators of vital importance), self-hosted Odoo can be deployed on State-qualified infrastructures (SecNumCloud label at OVHcloud, Outscale). No proprietary cloud ERP allows this today without giving up its foundation.
• Independence from foreign laws. Odoo SA is Belgian, subject to European law and the GDPR. Compare with Microsoft, Oracle and Salesforce, American vendors subject to the Cloud Act, which can compel the transmission of data to American authorities even if the servers are in Paris. For an organization with sovereignty concerns, self-hosting Odoo with a French provider (OVHcloud, Outscale) totally closes the door to any foreign jurisdiction — an option that proprietary ERPs simply do not offer.

Position of the other players:

• Cegid, Divalto, EBP: French vendors, French hosting, but proprietary code and captive cloud.
• Sage: British vendor, European hosting, proprietary code.
• Microsoft, Oracle (NetSuite): American vendors, Paris data centers available, but subject to the Cloud Act.

For an organization that takes sovereignty seriously — beyond the simplistic geographic argument — Odoo is today the most complete option in the ERP market, ahead of the French vendors themselves on the criteria of portability, reversibility and access to the code.

Electronic invoicing: an ERP topic before a tax topic

The calendar is now firm: from September 1, 2026, all French companies must be able to receive electronic invoices in the standardized format via the network of Accredited Platforms. On the same date, large companies and mid-sized companies must issue them. SMEs and micro-enterprises join the issuing obligation on September 1, 2027.

Three actions are mandatory for every company:

• Appoint an Accredited Platform (the technical intermediary between your ERP and the tax authorities).
• Issue and receive invoices in a standardized electronic format (Factur-X, UBL or CII — these are technical standards that structure the invoice so that it can be read automatically).
• Transmit additional transaction data (B2C, international, payments received) to the authorities.

Penalties are graduated: €500 for the first offense, +€1,000 every three months if it persists, €15 per non-compliant invoice, €250 per data transmission failure, with an annual cap of €15,000.

Position of ERP vendors on Accredited Platform status:

• Odoo obtained its accreditation on April 22, 2026. Free integrated module, no extra cost for customers on the Custom plan.
• Sage operates Sage Network as an Accredited Platform, complemented by connectors to Sage 100 and supplier invoice dematerialization.
• Cegid obtained its accreditation and offers native integration in XRP Flex and Ultimate.
• Microsoft Dynamics 365 Business Central relies on third-party partners (Docaposte, Generix, Esker), with no Microsoft accredited platform of its own.
• NetSuite: integration via third-party modules, no Oracle accredited platform in France.
• Divalto: connectors to the main platforms, native integration under way.

Our take: an ERP with an integrated and free accredited platform — like Odoo — provides a simpler compliance path than an ERP that goes through a separately billed third-party connector. Over 5 years, the difference amounts to tens of thousands of euros for a standard SME or mid-sized company.

The ISO certifications that now matter

Three international standards (“ISO”) have become structuring for the choice of an ERP in 2026, particularly in tenders and in mergers and acquisitions.

ISO 27001 (information security): the reference standard to qualify the cybersecurity maturity of a vendor or a host. Systematically requested in public tenders and large private tenders.

• Odoo SA: ISO 27001 certified at the level of the organization and procedures. The Odoo.sh infrastructure relies on Google Cloud Platform, itself certified ISO 27001, 27017, 27018.
• Microsoft Azure: full certifications (ISO 27001, 27017, 27018, 27701).
• Oracle (NetSuite): ISO 27001 across all cloud data centers.
• OVHcloud (Odoo self-hosting option): ISO 27001, HDS healthcare label, SecNumCloud very-high-security label on dedicated offers.
• Cegid: ISO 27001 on its French cloud data centers.
• Sage: ISO 27001 on Sage Cloud.

ISO 9001 (quality management): not an ERP product certification in the strict sense, but a signal about the vendor's and the integrator's processes. Particularly relevant for choosing the integrator — an ISO 9001 certified firm guarantees formalized specifications, acceptance test reports and maintenance processes.

ISO 20022 (structured banking exchanges): the new global standard for interbank payments (SEPA instant transfers, international SWIFT transfers). The ERP must be able to generate transfer order files (“pain.001”) and read structured bank statements (“camt.053 / camt.054”). All major ERPs support ISO 20022 in 2026, but the quality of implementation varies — Odoo and Cegid cover standard and extended SEPA flows natively, whereas Sage X3 and Business Central often require a dedicated bank connector billed on top.

For a mid-sized company planning a five-year deployment, requiring concrete evidence on these three certifications from the tender stage has become good practice. It is also a quick filter to rule out vendors or integrators that lack the required operational maturity.

Why we recommend Odoo for mid-sized companies and large accounts too

This is where we frankly diverge from the foxeet article. Foxeet places Odoo in the “very small business / SME / Startup” category and even states that in international and multi-entity accounting consolidation, “Sage X3 and Cegid keep the advantage”. This positioning is outdated. Here is why.

Odoo is no longer an SME ERP. The vendor has explicitly changed its commercial target over the last twelve months. The Partena Professional partnership in Belgium — announced as “10 times bigger than the largest current customer” — puts Odoo on large-account ground. The Odoo 20 roadmap announcements — industry-specific versions for Hospitality, Construction, Care homes — target segments where vertical ERPs cost a great deal and where Odoo arrives with an aggressive value proposition. The Partena partnership covers 920,000 payslips. It is not an SME case, it is an industry case.

Multi-entity and international accounting is no longer a blocker in 2026. Multi-company management is included in the Custom plan. Financial consolidation works natively on version 19, and version 20 strengthens consolidated reporting capabilities. On international accounting standards (IFRS), what remained of the limits in 2022-2023 has been closed by a mix of native features, certified modules and custom developments that are quick to set up. On the French side, the tax return package (liasse fiscale) is now generated natively by Odoo in the latest versions, whereas until recently it required a third-party module or an export to specialized software. And multi-axis analytic accounting is included as standard — a point that many competing vendors bill as an extra module or require heavy configuration for. We observe it on real projects: a group of 5 to 15 entities with IFRS consolidation runs on Odoo painlessly, provided the integrator knows their accounting subject.

Multi-country has become a strength. Local charts of accounts, specific VAT rates, customs duties, collective agreements — Odoo natively covers more than 50 countries with local adaptation modules maintained by the vendor or the community. For a mid-sized group established in Europe, French-speaking Africa or the Maghreb, deploying Odoo is today faster than an equivalent NetSuite deployment — for a total cost two to three times lower.

The total cost remains unbeatable, even at 200 users. On a 100-user project deployed over three years, the total cost of Odoo Custom comes out around €470,000 (licenses ~€108,000, hosting ~€10,000, integration ~€150,000, custom development ~€80,000, data migration and training ~€50,000, maintenance over 3 years ~€70,000). The same project over the same period on Sage X3 or Cegid XRP Ultimate exceeds €800,000. On NetSuite or Business Central with customizations, it frequently crosses the million-euro mark over the same window. The gap does not come only from the price of licenses — it comes above all from the implementation cost (implementations on Sage X3, Business Central and NetSuite typically require 50 to 100% more person-days with equivalent features) and from the rigidity of custom development (the competitors' proprietary languages — AL, ABAP, 4GL, SuiteScript — are slower to evolve, require partner certifications, and limit extension possibilities). With Odoo, a business feature is added in a few days where it takes several weeks elsewhere.

Gradual deployment is an operational asset. A mid-sized company does not launch an ERP project as a “big bang” (starting up the whole system at once). Odoo deployment is done by scope — sales management first, then production, then after-sales service, then HR. Each step can be delivered independently. It is the opposite of the model imposed by the large ERPs, which require 12 to 18 months of upstream preparation before any go-live. For a mid-sized company under growth pressure or acquiring subsidiaries, this stepwise deployment is an operational advantage, not just a budgetary one.

The technical advantage becomes a strategic advantage over 10 years. Python, PostgreSQL, modern architecture — while competitors drag along old technologies (proprietary languages, costly databases, building blocks stacked through acquisitions), Odoo capitalizes on the most dynamic technical stack of the moment. For a mid-sized company thinking 10 years ahead, this is the argument that should weigh the most: technological longevity, availability of talent, the ability to integrate future waves of innovation (AI, edge computing, vector search).

The real limit, which must be named honestly, is very-high-complexity heavy manufacturing industry — automotive, aerospace, large chemical processes. In these sectors, specialized ERPs keep a functional lead that Odoo will not close for several versions. Outside this scope, Odoo is today a credible option up to mid-sized companies with 500 or 1,000 users, and beyond for large accounts that are willing to structure their project differently from a legacy vendor.

Our take

The right ERP is not the most powerful, nor the cheapest, nor the most fashionable. It is the one that matches the company's business reality at the time of the choice, and whose product trajectory stays aligned with the company's over the next five to ten years. Everything else is communication.

And then, whichever ERP is chosen, there is a truth that no vendor will put in their brochure: the quality of the integrator matters as much as that of the product. A poor Odoo configuration gives a project as disappointing as a poor SAP configuration — for about a tenth of the price, which is meager consolation. The rule applies to all vendors: Cegid, Sage, Microsoft, Oracle do not deliver “plug-and-play” ERPs, and a good integrator turns an average product into a successful project, where a bad one destroys the value of the best product. In a market where firms get bought out by funds every six months, choosing a stable, experienced and independent partner has become a real contact sport.

For the majority of French SMEs and mid-sized companies in trading, retail, services and industry, Odoo on the Custom plan remains today the best functional and economic compromise — including for organizations with several hundred users or several legal entities, which the foxeet article does not acknowledge.

For mid-sized companies highly exposed to specific French regulatory constraints (complex multi-country payroll, an appointed Cegid accountant, precise sector constraints) or to heavy manufacturing industry, Cegid or Sage X3 may remain relevant. But on general functional depth, what we observe on recent projects contradicts the received wisdom: Odoo now covers at parity — or better — the majority of mid-sized company cases where Cegid and Sage were historically positioned as the default. For organizations fully committed to the Microsoft ecosystem seeking execution AI without changing their office stack, Business Central remains the logical choice (and a costly one, but you can't have everything).

The real ERP debate in 2026 is no longer “which one to choose”. It is “how to avoid signing for five years with a product or a partner whose trajectory diverges from ours”. And this question is not addressed by any online comparison — it is addressed in a consulting firm, by looking at the financial statements, the roadmaps and the contracts.

A serious integration partner does not just install the standard — it invests to fill the product's blind spots where its customers need it. For example, we invested in developing a native Odoo ↔ OpenPaye connector to deliver quality French payroll without weighing on the customer's budget, in dedicated business modules (winery tank management, sector platform integration, ERP-EDI connectors), and in accounting audit and version migration tools that reduce risk on mid-sized company projects. It is this upstream work — rarely visible in sales demonstrations, which prefer blue-gradient screens — that makes the difference between an ERP project that keeps its promises and one that disappoints.

This is exactly the work we do at ANOR ahead of every integration decision: asking the right questions about the business, the organization, the ten-year trajectory, before even talking about a vendor or a module. Because at this stage, the question is never technical. It is always business.