Which ERP to choose: the method for making the right decision in 2026

An ERP (Enterprise Resource Planning) is a single software system that centralizes a company's data and processes: purchasing, inventory, production, sales, accounting, and invoicing. Choosing an ERP involves weighing three families of solutions: modular open-source suites like Odoo, legacy mid-market vendors like Sage, and platforms for large corporations like SAP.

The right choice isn't found in a ranking. It depends on four measurable variables: the complexity of business processes, the volume of transactions processed, the ability to integrate with the rest of the information system, and the budget actually available over five years. The global ERP software market will reach $106.22 billion in 2026and 83% of deployments are now cloud-based or hybrid (Fortune Business Insights). The question is no longer whether you need an ERP, but which one to choose, and above all, how to integrate it with your sales channels.

ERP: definition, modules, and actual scope

An ERP is built on a single database fed by modules that share the same product, customer, and third-party repository. In practical terms, entering an order automatically triggers stock reservation, the generation of a picking slip, the accounting entry, and the invoice. This continuity of data flow is what distinguishes an integrated management software suite from a collection of business applications linked together by Excel exports.

The exact scope varies by vendor, but the logic remains the same: a financial and logistics core, with optional modules activated as the company grows. The difficulty does not lie in the number of available modules, but in the scope the company decides to cover in the first year. Overly ambitious functional requirements prolong the project and dilute team adoption.

A classic trap: confusing functional coverage with business coverage. A standard sales management module handles quotes and orders, but it does not manage contractual price lists per customer, personalized catalogs, or self-service ordering. These needs fall under a specialized commerce layer, which should be connected to the ERP rather than developed within it.

Odoo, Sage, or SAP: which ERP for which profile

Three vendors account for the majority of ERP projects in France for the SME and mid-market segments. The comparison below is based on their actual positioning, pricing models, and integrator ecosystems, rather than a global rating that is meaningless outside of a specific business context. The deciding factor remains the alignment between process complexity and solution weight: over-equipping a 40-employee SME with a platform designed for multinational groups leads to low adoption rates and an unsustainable total cost of ownership.

Profile/ERP mapping table

‍

Odoo, modularity at the lowest entry cost

Odoo claims 15 million users, over 430 million euros in revenue, and a 7-billion-euro valuation (La Libre, September 2025). Its appeal lies in its granularity: a company can activate accounting and inventory, then add production or maintenance without changing the foundation. The free plan, limited to one application, allows you to test the configuration before making any commitments.

The trade-off lies in integration. The quality of the deployment depends almost entirely on the chosen partner, and over-customizing the code makes version upgrades painful. A simple rule: require the integrator to provide a list of planned custom developments and reject anything that can be solved through standard configuration. For sales flows, there is a native connector between Odoo and a sales management copilot that synchronizes catalogs, negotiated prices, stock, and customer accounts without custom development.

Sage, the reliable choice for the French mid-market

Sage has 6.1 million customers worldwide and 2.5 billion pounds sterling in revenue for its 2025 fiscal year. In France, its strength is not technological, but structural: a dense network of integrators and accountants who are familiar with its product lines, charts of accounts, and regulatory reporting requirements. For an industrial or trading SME looking primarily for accounting reliability and sales management, the project risk is low.

A key point of caution concerns sales channels. E-commerce and catalog management modules remain basic when faced with B2B requirements: contract-based pricing grids, packaging units, and volume discounts. The best practice is to keep Sage as the master system for financial data and connect a dedicated stock management layer on top, such as retail inventory management, and for online sales.

SAP: functional depth for complex organizations

SAP remains the default choice for mid-market companies and large multi-site accounts, with coverage ranging from industrial planning to multi-currency financial consolidation. One deadline is currently shaping all decisions: standard maintenance for SAP ECC (versions EHP 6 to 8) ends at the end of 2027, with paid extended maintenance available until the end of 2030. Thousands of companies must therefore decide between migrating to S/4HANA or switching vendors.

This decision-making process is a strategic window of opportunity. Rather than simply renewing the status quo, the method involves mapping existing custom developments, classifying each as "standardizable," "to be outsourced," or "to be kept," and then moving everything related to customer experience outside the ERP scope. On this point, it is often faster to modernize B2B commerce using the existing ERP than to wait for the end of a three-year migration.

4 criteria that determine the choice of an ERP

Most selection grids compare lists of features. This is the best way to choose an oversized solution. Four criteria explain most successes and failures: actual functional coverage, integration capability, total cost of ownership, and regulatory compliance. Each can be measured, documented, and challenged with vendors during the consultation phase. Other frequently cited criteria, such as usability, product roadmap, and brand reputation, are tie-breakers, not filters.

Functional coverage and business-specific needs

The mistake is to validate coverage based on a sales demonstration. The reliable method consists of one exercise: submit three real-world scenarios from your business to the vendors, such as a multi-delivery address order, a partial return with a credit note, or a tiered volume-based contract price. The demonstration must be performed using these scenarios with the company's own data. A vendor that dodges these use cases will not cover the business once in production.

Integration capability and available connectors

A high-performance but closed ERP costs more than an average, well-connected one. Three questions to ask in writing: which APIs are publicly documented, what volume limits apply, and what standard connectors exist for sales, payment, and shipping platforms. An order flow that updates in real-time avoids double entry in sales administration. This is also what allows you to digitize the B2B product catalog without duplicating the master data.

Total cost of ownership over 5 years

The license price represents only a fraction of the budget. You must add integration, data migration, training, hosting, annual maintenance, and version upgrades. A useful scoping rule: ask each vendor for a five-year cost estimate, including hosting and support, based on a 30% growth assumption in the number of users. The choice between SaaS or IaaS significantly alters the cost structure and the level of in-house expertise required.

Compliance and electronic invoicing

In France, the requirement to receive electronic invoices has applied to all businesses since September 1, 2026, and the obligation to issue them extends to mid-sized companies, SMEs, and micro-businesses on September 1, 2027. Your ERP must therefore be connected to a partner dematerialization platform (PDP). A direct question to ask: is the connection to a PDP native, a paid add-on, or something that requires custom development? This also affects upstream workflows, particularly e-procurement and B2B payments.

ERP budget: the true 5-year cost

The cost quoted during the sales phase is almost always just the license fee. However, integration, data migration, and change management are structurally much heavier expenses. The 2026 Panorama Consulting report indicates that more than a quarter of organizations exceed their ERP project budget, with underestimated technological requirements being the primary cause. The solution is simple: build the budget line by line rather than relying on a global quote, and explicitly set aside a contingency reserve.

The second most underestimated item is data migration. Cleaning up a product catalog of 40,000 items, de-duplicating a customer database, and reconstructing pricing history often represents several man-months of work. This must be done before configuration, never during. A company that migrates dirty data into a new ERP will simply end up with a dirty ERP.

The calculation should conclude with a single metric to present to management: the average annual cost per active user, including all expenses. This is the only figure that allows you to compare two offers with different structures.

5 mistakes that derail ERP projects

ERP project failures follow repetitive patterns, regardless of the vendor chosen. They rarely stem from the technology itself and almost always from governance, scope, and data quality. Identifying these errors before launch takes a few days of workshops. Correcting them after go-live costs months of delays and a lasting loss of trust from operational teams.

Pre-launch checklist

• Undefined scope. A validated document must list the processes covered in version 1 and those deferred. Any request outside this scope requires formal committee arbitration, not verbal agreements made during workshops.
• Over-customization of the standard. Every specific development must be justified in writing, with its 5-year maintenance cost calculated. Scoping goal: less than 15% customization in the initial scope.
• Lack of an internal project lead. A company-side project manager, available at least 50% of the time, with the authority to make decisions. A project managed solely by the integrator will inevitably drift toward the integrator's interests.
• Unprepared data. Cleaning up product, pricing, and customer master data must begin at least three months before go-live, with target completion rates measured weekly.
• Training treated as an afterthought. Key users must be trained on the testing environment, not the week of launch. Appoint department leads responsible for cascading information and reporting pain points.

A weekly review of these five points, led by the internal project manager, is enough to detect most issues before they become structural.

‍

Beyond the ERP: connecting the foundation to B2B commerce

An ERP is designed to execute and record, not to sell. It manages inventory, accounting entries, and manufacturing orders. It was never intended to offer professional customers a personalized catalog, online contract pricing, or self-service order tracking. This is why companies that try to turn their ERP into a sales channel end up accumulating custom developments and losing the benefits of the standard software.

The architecture that works separates roles. The ERP remains the master system for financial data, inventory, and master records. A commerce layer, connected via API, handles the customer experience, order entry, and automation of incoming workflows.

What the ERP does poorly and should be outsourced

Four functions resist ERP integration: customer-specific enriched catalogs, complex contract pricing, multi-channel order entry, and customer self-service. A concrete example: an order received by email as a photo or PDF currently requires a sales admin employee to re-enter the data. Automating this flow and pushing it into the ERP significantly reduces administrative burden, with a measurable return on investment within a few months. Automated replenishment follows the same logic.

The 3-layer target architecture

The reference model consists of three levels: the ERP as the management system, an API integration layer that synchronizes products, prices, inventory, and accounts, and a commerce layer that presents the offering to professional customers, distributors, or a B2B marketplace. This decoupling allows the sales experience to evolve without touching the management core. It also facilitates migrations: changing ERPs no longer requires rebuilding the digital channel. To frame this second choice, the B2B platform comparison and the criteria for choosing the right B2B e-commerce platform provide a directly reusable framework.