You may have read our Odoo 18 vs Business Central comparison and drawn up a shortlist. Since then, Odoo 19 has shipped, Microsoft has delivered its 2026 update waves, and France’s e-invoicing reform took effect on 1 September 2026. What you have in mind is no longer entirely accurate.
This article does not redo the full comparison. It covers the delta: what moved, what did not, and what it means for a manufacturing SME with 50 to 500 employees. For the philosophies of the two products, payroll, the AppSource ecosystem and e-commerce, the Odoo 18 article still holds.
What has changed since the Odoo 18 comparison
Odoo 19: manufacturing, planning, purchasing, AI
The official Odoo 19 release notes list changes that hit the shop floor directly:
- Manufacturing: Gantt view of manufacturing orders, several serial or lot numbers per order, operation costs computed on real time or at a fixed cost, work center labor cost reflected in product valuation (AVCO and FIFO methods), subcontracting receipts integrated into the standard inventory flow.
- Planning: the Master Production Scheduler computes forecast demand from history, and reordering rules gain a horizon and a deadline.
- Purchasing: forecast-based purchasing, and alternative requests for quotation created in parallel with a currency specific to each vendor.
- Inventory: multiple routes on one sales order line (combining “make to order” and “buy”), packages inside packages.
- AI: agents that query the database in natural language, natural-language search, automatic field completion, ChatGPT and Gemini integration. The public pricing page reserves Studio and agentic AI for the Custom plan.
For an industrial SME, the notable point is valuation. Building actual operation and labor costs into product cost was until now one of the gaps finance directors held against Odoo compared with a heavier production-management ERP. On paper, it is closed. Verify it in a demo on your own routings.
For the other new features and the migration timeline, see our Odoo 19 guide.
Business Central: two waves a year, a heading toward agents
Business Central updates twice a year. Version 29, part of the 2026 release wave 2, is announced for October 2026. To be precise about what we could verify: Microsoft’s wave 2 release plan page was not accessible at the time of writing, so we will not detail manufacturing features from that wave. Public direction focuses on agents (payables, sales orders) and on extending the E-Document framework. Check the release plan on Microsoft Learn before signing, especially if you expect a production improvement.
The verified facts that matter to you lie elsewhere: pricing (see below) and French e-invoicing, which reached general availability on 3 August 2026 according to Microsoft Learn.
What has not changed
- Odoo remains open source for the Community edition, with an Enterprise edition that concentrates AI and the most strategic functions.
- Business Central remains locked into the Microsoft ecosystem, with manufacturing reserved for the Premium plan.
- The gap in business model is still the first decision variable.
Comparison table: what matters for the shop floor and finance
| Criterion | Odoo 19 | Business Central (2026 waves) |
|---|---|---|
| Manufacturing / MRP | Bills of materials, Gantt, operation costing, subcontracting, MPS with history-based forecast | Production orders and routings, Premium only (Microsoft pricing) |
| Shop floor | Shop floor interface, “light” user at €7.90/month for the shop floor station | Less native depth, to be completed with a partner add-on |
| Finance | Full accounting, bank reconciliation, duplicate invoice detection | Solid accounting, multi-entity consolidation, native Power BI |
| Purchasing / inventory | Forecast-based purchasing, multi-currency alternative RFQs | Solid standard, Copilot-assisted forecasts |
| Quality | Quality control points, alerts, failure location | Quality through partner modules as needed |
| AI | Agents, natural-language search, ChatGPT/Gemini (Custom plan for agentic AI) | Copilot, payables and sales order agents, Copilot credits billed on top |
| French localization | FEC, VAT, Factur-X, approved platform status stated in documentation | FEC, Peppol BIS3 and Factur-X, through a third-party PDP |
| Extensibility | Modifiable Python code, Apps Store, OCA | AL extensions, AppSource, no core modification |
| Hosting | Odoo Online, Odoo.sh or on-premises (depending on plan) | Microsoft cloud, enforced updates |
This table mixes official documentation with field observations. The “quality” and “shop floor” cells for Business Central reflect the absence of a documented native function, not an impossibility: many partners fill those gaps.
Costs: licensing model and 5-year TCO
Public prices, as published
According to the Odoo pricing page, the Standard plan is listed at €19.90 per user per month, the Custom plan at €35.90, and a light user at €7.90. One detail the Odoo 18 article missed: Standard exists only on Odoo Online. For Odoo.sh, on-premises, Studio, multi-company and the external API, you must price the Custom plan.
According to the Business Central pricing page, Essentials is $80 per user per month, Premium $110, Team Members $8, with annual billing. Manufacturing belongs to Premium.
Simulation at list price: 30 users, 5 years, licenses only
| Scenario | Calculation | Total |
|---|---|---|
| Odoo Standard (Online) | 30 x €19.90 x 60 months | €35,820 |
| Odoo Custom (Studio, hosting of your choice) | 30 x €35.90 x 60 months | €64,620 |
| Business Central Premium | 30 x $110 x 60 months | $198,000 |
These figures are calculations on public list prices, with no partner discount, no exchange rate and no taxes. They include neither light users (shop floor) nor Team Members licenses, which lower the bill on both sides for operators who enter little data.
The variables that really move TCO
The catalog price is not the total cost. Here is what moves the bill, in order of impact:
- The scope of custom development. With Odoo, a quote where custom work weighs heavily signals that standard does not cover the need. With Business Central, it is the cost of AL extensions and AppSource apps that climbs.
- Add-on licenses. Copilot credits at Microsoft, the Custom plan at Odoo as soon as you want Studio or agentic AI.
- Version migration. Odoo publishes one major version a year and supports only the last three, see the official support policy. Plan an upgrade every 18 to 24 months. Microsoft enforces two waves a year, which your partner must test against your extensions.
- The integrator’s day rate and project length. For Odoo project cost ranges in France, see our Odoo pricing analysis. We do not publish an overall range for Business Central: no reliable primary source exists, so ask for three quotes.
Ecosystem and integrators in France and Europe
Odoo relies on a broad, highly competitive partner network. The official directory listed 139 partners in France when we checked in October 2026, 15 of them Gold. The upside: choice and negotiable rates. The risk: wide variation in quality, with some partners more at ease in services and retail than in manufacturing.
Business Central has a tighter, more uniform network, backed by the Microsoft partner program. According to MSDynamicsWorld, the product passed 55,000 customers in April 2026. The upside: integrators experienced in industry and Microsoft environments. The risk: fewer partners genuinely specialized in SME manufacturing in France, hence less negotiating power.
The question that matters is not network size but the number of projects comparable to your shop floor that the integrator has taken to completion. Insist on speaking by phone to two references.
To compare offers, our integrator scoring framework gives 12 objective criteria.
E-invoicing in France: where each solution stands
Since 1 September 2026, all companies established in France must be able to receive electronic invoices, and large companies and mid-caps must also issue them. Other companies issue from 1 September 2027, as the Odoo France documentation reminds us. For the full framework, see our France e-invoicing and ERP compliance guide.
Odoo: the official documentation states that Odoo is certified as an “approved platform” on the e-invoicing network. It receives Factur-X, UBL and CII formats but sends only in UBL. In practice: if one of your customers requires a specific format on issuance, check before signing. A Peppol link module with Chorus Pro exists for public procurement. A word of caution: approval status is assessed on the signing date against the administration’s official list, not on a documentation page.
Business Central: Microsoft does not present itself as an approved platform. According to the Microsoft Learn page, companies use the existing E-Document connectors to exchange invoices and lifecycle statuses through a certified PDP. The localization app enables Peppol BIS3 and Factur-X formats, handles issuing and receiving, and produces transaction e-reporting. General availability was 3 August 2026. In practice: you contract with a third-party platform on top, and its subscription adds to your TCO.
Both routes are compliant. Odoo simplifies the contract (one supplier), while Business Central lets you choose the platform. Either way, ask to see an issued invoice and a full status cycle in your test environment, not a slide screenshot.
When to choose Odoo, when to choose Business Central, when to choose neither
Choose Odoo 19 if…
- Your core value is manufacturing (routings, subcontracting, lots, MPS) and you want the most native functions out of the box.
- Your license budget is tight and you accept regular version upgrades.
- You want the ability to fine-tune the ERP, including through code.
- Limits to declare: highly variable integrator quality, third-party modules to audit at every upgrade, agentic AI reserved for the Custom plan, e-invoice issuance in UBL only.
Choose Business Central if…
- Your company lives in Microsoft 365 and Power BI, and management expects unified steering.
- Your production is simple (assembly, light subcontracting) or you insist on consolidated multi-entity financial reporting.
- You want a single vendor for infrastructure, with guaranteed updates.
- Limits to declare: manufacturing reserved for Premium (and shop floor supervision to be added), licenses markedly more expensive than the Odoo catalog, customization limited to extensions, enforced twice-yearly updates, an e-invoicing platform to contract separately.
When neither fits
- Highly complex or regulated production (pharmaceutical traceability, aerospace, heavy configure-to-order): look at a specialized ERP or a dedicated MES layer before forcing either one.
- More than 500 users with tightly integrated multi-site processes: higher-tier ERPs become competitive.
- No internal resources to carry the project: neither compensates for the lack of a client-side project manager. See our manufacturing ERP guide.
Five questions to ask in the demo
Build on our ERP demo evaluation guide and scoring grid, then impose these five questions on every vendor or integrator:
- “Show me one of my real manufacturing orders, with subcontracting and scrap, from release to product cost.” Use your data, not the standard scenario.
- “What is the total 5-year cost, line by line, for 30 users, 10 of them on the shop floor?” Demand licenses, hosting, the invoicing platform, AI and version upgrades.
- “What in this quote is custom work?” Get the percentage of custom development and the associated maintenance cost.
- “Show me issuing and receiving an electronic invoice with lifecycle statuses.” In the test environment, with the real platform.
- “What happens at the next major version?” Who tests my extensions or modules, who pays, and within what timeframe.
To move from shortlist to decision, download our ERP evaluation grid: 30 criteria scored out of 100 to compare two or three solutions side by side. To frame the choice upstream, also read our complete guide to choosing an ERP.
