Skip to main content
FromNine
Menu

Enterprise platform · Odoo

Odoo, one modular system for the whole business.

We implement Odoo for growing organisations and subsidiaries, write custom modules that survive the yearly upgrade, and connect Odoo to banks, Peppol, e-commerce and the group ERP. AI comes in where it removes routine work.

For growing organisations and group subsidiaries across Europe that need one system without enterprise overhead.

Discuss your platform needsCompare the platforms
  • OdooGold PartnerPartner status · Odoo
  • ISO/IEC 27001 certified
  • 600+ European government projects
Odoo modules on one database and the systems around them. At the centre sits one Odoo database with six modules side by side: accounting, inventory, manufacturing, sales and CRM, projects, and HR. Six connections lead out: AI document capture, the Peppol network, banks with CODA statements, e-commerce, the SAP group core, and identity.

Where Odoo fits, and where it does not

Fits well when

  • A mid-sized organisation wants finance, sales, stock, projects and HR in one database instead of a patchwork of tools.
  • Subsidiaries of a larger group need their own ERP, connected to the group core.
  • You want to start with a few modules and add more as the organisation grows.
  • Processes are close to common practice and licence cost matters.
  • Control over hosting matters, up to running Odoo yourself in an EU data centre.

Consider alternatives when

  • Group finance across many legal entities, manufacturing at scale or heavy statutory reporting. SAP S/4HANA is built for that, with Odoo possibly in the subsidiaries.

    Alternative: SAP

  • Large contact centres, complex case management or extensive citizen portals. Salesforce is stronger there.

    Alternative: Salesforce

  • You expect to change Odoo’s core behaviour substantially. Every yearly upgrade then becomes a project, and a custom application may be the cleaner choice.

    Alternative: Enterprise Software & SaaS

What we deliver on Odoo

Five kinds of work, usually combined. They also label the columns of the capability matrix below.

  1. 01

    Implement

    Implementation

    Module selection, configuration, fiscal localisation and data migration, delivered in phases so the business keeps running.

    Outputs

    • Module map
    • Configured database
    • Key-user training
  2. 02

    Extend

    Custom modules

    Python and OWL modules that inherit rather than overwrite, with automated tests, so the yearly upgrade stays manageable. Odoo Studio where a no-code change is enough.

    Outputs

    • Custom modules
    • Automated tests
    • Upgrade notes
  3. 03

    Integrate

    Integration

    Banks, Peppol e-invoicing, e-commerce, carriers and payment providers, and the group ERP, through Odoo’s external API and an integration layer where volumes call for one.

    Outputs

    • Interface list
    • Monitored connectors
  4. 04

    Migrate

    Migration and upgrades

    From spreadsheets, a legacy ERP or an older Odoo version: data mapping, reconciliation, and moving custom modules to the new release.

    Outputs

    • Migration plan
    • Reconciliation reports
  5. 05

    Operate

    Managed evolution

    Hosting on Odoo.sh or your own infrastructure, monitoring and backups, and a yearly upgrade plan so you never fall out of support.

    Outputs

    • Hosting set-up
    • Upgrade calendar
    • Support backlog

Capability matrix

Odoo applications we work with, and the kind of work we do in each. Read a row from left to right.

  • Accounting and invoicing

    Multi-company accounting, fiscal localisations, bank reconciliation and e-invoicing.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Sales, CRM and e-commerce

    Quotations, subscriptions, the Odoo website and links to external shops.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Inventory and purchase

    Multi-warehouse stock, routes, replenishment and supplier management.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Manufacturing and quality

    Bills of materials, work orders, maintenance and quality checks.

    • Implement
    • Extend
    • Integrate
    • Operate

  • Projects, timesheets and field service

    Project planning, time tracking and invoicing of work done.

    • Implement
    • Extend
    • Operate

  • HR and expenses

    Employees, leave and expenses; payroll where a country localisation exists.

    • Implement
    • Extend
    • Operate

  • Fiscal localisation and Peppol

    Country charts of accounts, tax reports, Peppol and national e-invoicing formats.

    • Implement
    • Integrate
    • Operate

  • AI features

    Bill and expense digitisation and the AI features of recent versions, configured and governed.

    • Implement
    • Extend
    • Operate

  • Odoo.sh and self-hosting

    Hosting, staging databases, backups, monitoring and version upgrades.

    • Migrate
    • Operate

AI on Odoo

Native on the platform

Odoo includes AI features aimed at routine work. Digitisation of supplier bills and expense receipts reads the document and proposes the entry for review, and AI-assisted writing is available in emails, documents and the website builder. Recent versions add configurable AI features, such as fields filled by AI and agents that act on Odoo records.

What is available depends on version, edition and hosting, and some features consume paid credits. We confirm what your version offers, and where documents are processed, before planning around it.

Built around the platform

Around Odoo we build what it does not do natively: assistants that answer questions over Odoo data with access rights applied, classification of incoming documents before they reach the right application, and automation of routine back-office steps such as matching, reminders and stock alerts. These services use Odoo’s external API and respect its access rights.

They work with bounded permissions, wait for approval before posting or paying, and keep a full log. When a result is uncertain, a person decides.

Which route fits

  1. 01

    Is the task capturing supplier bills or expenses?

    If yes

    Use Odoo’s digitisation first and measure how often people correct it.

    If no

    Look at automated actions and the AI features of your version before building anything.

  2. 02

    Does the task need data or documents from outside Odoo?

    If yes

    Build a service around Odoo that uses its external API.

    If no

    Configure the native features and keep the logic inside Odoo.

  3. 03

    Do you run on Odoo Online?

    If yes

    Custom Python modules are not available there, so custom AI runs as an external service.

    If no

    On Odoo.sh or self-hosted, a custom module can bring the AI step into the Odoo screens.

The path to a working Odoo

  1. Step 01

    Scope

    Processes, applications, localisation needs, integrations and the hosting choice.

    • Module map
    • Hosting decision

  2. Step 02

    Configure

    Standard configuration first, with your key users, in a test database.

    • Configured database
    • Gap list

  3. Step 03

    Customise sparingly

    Custom modules only for real gaps, with tests and upgrade notes.

    • Custom modules
    • Test suite

  4. Step 04

    Migrate data

    Opening balances, master data and open items, reconciled against the old system.

    • Reconciliation reports

  5. Step 05

    Go live

    Training, cut-over and close support through the first period end.

    • Cutover checklist
    • First close

  6. Step 06

    Upgrade yearly

    A planned upgrade rhythm, so you stay on a supported version.

    • Upgrade calendar
Illustrative example

Subsidiaries on Odoo, group on SAP

01Situation
A group runs SAP at headquarters, while its smaller subsidiaries in Belgium and Germany work in spreadsheets and an end-of-life local package. Both countries now require structured e-invoices.
02What we build
One Odoo template with the Belgian and German localisations, Peppol and XRechnung exchange, and an integration that sends trial balances and intercompany invoices to the SAP group core each period.
03Human control
Local finance teams approve incoming e-invoices before posting; group controllers approve the mapping of local accounts to the group chart.
04What we would measure
Days from period end to group reporting, share of supplier invoices posted without retyping, and effort per yearly upgrade.

Odoo in the wider landscape

Odoo sits at the centre of a smaller organisation and at the edge of a larger one. We connect it to banks, the Peppol network, e-commerce, carriers and payment providers, and in groups to the SAP core for consolidation and intercompany flows.

Odoo’s external API handles most links directly. When volumes grow, or several systems share the same data, we put an integration layer in between so that upgrading one system does not break the others. Our integration and API practice designs those contracts.

Illustrative example

People and channels

  • Staff in Odoo
  • Webshop and customer portal
  • Mobile and point of sale

Odoo

External API · integration layer

Systems and networks

  • Peppol network
  • Banks and CODA statements
  • SAP group core
  • Carriers and payment providers
Odoo among the systems and networks it serves
Read the diagram as text

On the left, people and channels: staff in Odoo, the webshop and customer portal, and mobile and point of sale.

In the middle, Odoo, connected to everything else through its external API and, where volumes call for it, an integration layer.

On the right, systems and networks: the Peppol network, banks with CODA statements, the SAP group core, and carriers and payment providers.

Odoo in your sector

Public sector

Public Sector & Government

Agencies, inter-municipal bodies and publicly funded non-profits that need accounting, purchasing and projects with Peppol e-invoicing to and from public administrations, on hosting they control.

600+

European government projects

  • Manufacturing & Industry

    Smaller plants and subsidiaries: bills of materials, work orders and quality, linked to the group’s SAP core for consolidation.

  • Healthcare & Life Sciences

    Care organisations and medical suppliers managing stock, purchasing and invoicing with lot traceability.

International

Odoo across European markets

Odoo’s fiscal localisations are where country rules show up first. Belgium made Peppol e-invoicing between businesses mandatory in 2026. Germany requires businesses to receive e-invoices in XRechnung or ZUGFeRD formats and is phasing in issuing. France is rolling out its reform through approved platforms, and Spain is introducing Verifactu requirements for invoicing software.

We configure each localisation, test it with real trading partners and keep custom modules clear of the tax logic, so a rule change arrives with the next Odoo update instead of a rebuild.

Odoo questions we hear often

How does Odoo handle Belgian e-invoicing over Peppol?

Since 1 January 2026, Belgian VAT-registered businesses have to send and receive structured electronic invoices for domestic B2B transactions, in practice over the Peppol network. Odoo’s Belgian localisation supports sending and receiving through Peppol.

We set up the registration, test exchanges with your main customers and suppliers, check that invoices meet the Peppol BIS Billing 3.0 format, and decide how incoming invoices are matched and approved.

Community or Enterprise edition?

Community is open source and has no licence fee, but lacks applications and features many organisations need, including several accounting, localisation and AI features. Enterprise adds those, along with Odoo’s upgrade service, for a per-user subscription. We compare the two against your actual process list, not a feature brochure.

Odoo Online, Odoo.sh or our own hosting?

Odoo Online is the simplest but allows no custom Python modules. Odoo.sh is Odoo’s platform service with custom modules, staging and automated tests. Self-hosting gives full control over location and security, and full responsibility for operations. Sovereignty requirements, customisation needs and your own operations capacity decide.

What does the yearly upgrade cost us?

Odoo releases a major version every year and supports only recent versions. Standard data is upgraded through Odoo’s upgrade service; custom modules have to be migrated by whoever maintains them. The cost depends almost entirely on how much was customised and how, which is why we inherit rather than overwrite, keep tests, and plan the upgrade from the start.

Can Odoo run next to SAP in a group?

Yes, as a two-tier ERP: SAP for the group core and consolidation, Odoo in smaller subsidiaries. The work is in the integration: shared master data, intercompany flows and the mapping of local charts of accounts to the group. Our SAP practice designs both sides together.

Can we move from our old ERP to Odoo without stopping the business?

Usually, with a phased plan: finance and master data first, operations next, with the old system kept read-only for history. We reconcile balances and open items at each step, so the move is visible in the numbers, not just in the screens.

Talk to us about Odoo

Whether you are choosing an ERP, rescuing an over-customised Odoo or connecting subsidiaries to a group core, start with a conversation about your processes and your timeline.

Discuss your platform needsExplore our approach