Skip to main content
FromNine
Menu

Business platform · Odoo

Odoo, a single system in modules for the whole business.

We roll out Odoo for growing businesses and group subsidiaries, write custom modules that come through the annual upgrade intact, and connect Odoo to your bank, to e-invoicing, to online sales and to the group ERP. AI is added where it takes routine work off people’s desks.

For owner-managed businesses, growing Irish companies and group subsidiaries that want one system without the weight of a large ERP.

Talk to us about your projectSee the three side by side
  • OdooGold PartnerPartner status · Odoo
  • ISO/IEC 27001 certified
  • 600+ European government projects
Odoo modules sharing one database, and the systems around them. In the middle is a single Odoo database holding six modules next to each other: accounting, inventory, manufacturing, sales and CRM, projects, and HR. Six links run outwards: to AI capture of documents, to the Peppol network, to bank feeds, to online sales, to an SAP core at group level, and to identity.

When Odoo is the right choice, and when it is not

A good fit when

  • A mid-sized or owner-managed business wants finance, sales, stock, projects and HR in a single database rather than a collection of separate tools.
  • Subsidiaries of a bigger group need an ERP of their own that reports into the group core.
  • You would like to begin with a handful of modules and add others as the business grows.
  • Your processes are close to common practice and the licence bill matters.
  • You want a say over hosting, up to running Odoo yourself in a data centre in the EU.

Look elsewhere when

  • Group finance across a large number of legal entities, production at scale or heavy statutory reporting. SAP S/4HANA is made for that, perhaps with Odoo in the subsidiaries.

    Alternative: SAP

  • Big contact centres, complex case handling or large portals for the public. Salesforce does that better.

    Alternative: Salesforce

  • You plan to change how Odoo’s core behaves in a big way. Each annual upgrade then turns into a project, and a bespoke application may be the tidier option.

    Alternative: Enterprise Software & SaaS

Our Odoo work

Five types of work, which usually go together. The same five head the columns of the capability matrix further down.

  1. 01

    Implement

    Implementation

    Choosing modules, configuration, Irish fiscal localisation and data migration, rolled out in phases so trading carries on.

    What you get

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

    Extend

    Custom modules

    Python and OWL modules that extend by inheritance instead of overwriting, with automated tests, so the annual upgrade stays under control. Odoo Studio when a no-code change will do.

    What you get

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

    Integrate

    Integration

    Banks, e-invoicing over Peppol and other channels, web shops, couriers, payment providers and the group ERP, through Odoo’s external API and an integration layer when volumes need one.

    What you get

    • Interface list
    • Monitored connectors
  4. 04

    Migrate

    Migration and upgrades

    Off spreadsheets, an older ERP or an earlier Odoo version: data mapping, reconciliation and bringing custom modules onto the new release.

    What you get

    • Migration plan
    • Reconciliation reports
  5. 05

    Operate

    Ongoing improvement

    Hosting on Odoo.sh or on your own infrastructure, monitoring and backups, and an upgrade plan for each year so you stay on a supported version.

    What you get

    • Hosting set-up
    • Upgrade calendar
    • Support backlog

Capability matrix

The Odoo applications we work with and what we do in each one. Each row reads from left to right.

  • Accounting and invoicing

    Accounting for several companies, fiscal localisations, bank reconciliation and EN 16931 e-invoices.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Sales, CRM and e-commerce

    Quotes, subscriptions, the Odoo website and connections to other web shops.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Inventory and purchase

    Stock over several warehouses, routes, reordering and supplier management.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Manufacturing and quality

    Bills of materials, work orders, maintenance and quality control points.

    • Implement
    • Extend
    • Integrate
    • Operate

  • Projects, timesheets and field service

    Planning projects, recording time and billing the work that was done.

    • Implement
    • Extend
    • Operate

  • HR and expenses

    Staff records, leave and expenses; payroll only where Odoo has a localisation for the country.

    • Implement
    • Extend
    • Operate

  • Fiscal localisation and Peppol

    Charts of accounts and VAT returns by country, Peppol and the e-invoice formats each country requires.

    • Implement
    • Integrate
    • Operate

  • AI features

    Reading bills and receipts and the AI options in newer releases, set up and governed.

    • Implement
    • Extend
    • Operate

  • Odoo.sh and self-hosting

    Hosting, staging databases, backups, monitoring and moves to new versions.

    • Migrate
    • Operate

AI on Odoo

Built into the platform

Odoo’s AI features target routine tasks. It reads supplier bills and expense receipts and suggests the entry for someone to check, and it can help draft text in emails, documents and the website builder. Newer releases add AI features you can configure, such as fields that AI fills in and agents that work on Odoo records.

What you get varies with the version, the edition and the hosting, and some features use paid credits. We check what your version provides, and where your documents are processed, before any plan depends on it.

Built alongside the platform

Around Odoo we build what it does not offer out of the box: assistants that answer questions on Odoo data while respecting access rights, sorting of incoming documents before they land in the right application, and automation of routine back-office steps such as matching, payment reminders and stock alerts. These services work through Odoo’s external API and stay within its access rights.

Their permissions are narrow, they wait for sign-off before anything is posted or paid, and every step is logged. Where a result is unclear, a person makes the call.

Choosing a route

  1. 01

    Is the job about capturing supplier bills or expense receipts?

    If yes

    Start with Odoo’s own digitisation and track how often staff have to correct it.

    If no

    Check automated actions and the AI features of your release before you build anything.

  2. 02

    Does the job rely on data or documents held outside Odoo?

    If yes

    Build a service alongside Odoo that works through its external API.

    If no

    Set up the native features and keep the logic in Odoo.

  3. 03

    Are you on Odoo Online?

    If yes

    Odoo Online does not allow custom Python modules, so any custom AI has to run as a separate service.

    If no

    With Odoo.sh or your own hosting, a custom module can put the AI step straight into the Odoo screens.

Getting to an Odoo that works

  1. Step 01

    Scope

    Processes, applications, Irish VAT and e-invoicing needs, integrations and where Odoo will be hosted.

    • Module map
    • Hosting decision

  2. Step 02

    Configure

    Standard configuration before anything else, worked through with your key users in a test database.

    • Configured database
    • Gap list

  3. Step 03

    Customise with restraint

    Custom modules only where there is a genuine gap, each with tests and notes for the next upgrade.

    • Custom modules
    • Test suite

  4. Step 04

    Migrate data

    Opening balances, master data and open items, checked against the old system until they agree.

    • Reconciliation reports

  5. Step 05

    Go live

    Training, cut-over and close support until the first month-end or period-end is closed.

    • Cutover checklist
    • First close

  6. Step 06

    Upgrade every year

    A planned upgrade rhythm that keeps you on a version Odoo still supports.

    • Upgrade calendar
Illustrative example

An owner-managed distributor getting ready to receive e-invoices

01The situation
An owner-managed distributor of electrical components runs its accounts in an end-of-life package and its stock in spreadsheets. From November 2028, on Revenue’s planned timeline, it must be able to receive e-invoices from large suppliers, and some of its customers are public buyers that work with Peppol.
02What we would put in place
Odoo for accounting, purchasing, inventory and sales, set up for Irish VAT, with incoming EN 16931 e-invoices captured and matched to purchase orders, and outgoing e-invoices to public buyers sent over Peppol.
03Where staff decide
The finance manager approves supplier e-invoices that do not match a purchase order before they are posted, and signs off each payment run.
04How we would judge it
Share of supplier invoices posted without retyping, days to close the month, and effort per annual upgrade.

How Odoo fits with your other systems

In a smaller business Odoo is at the centre; in a larger group it sits at the edge. We link it to banks, e-invoicing and the Peppol network, web shops, couriers and payment providers, and within a group to the SAP core for consolidation and intercompany trading.

Most links run directly through Odoo’s external API. Once volumes rise, or several systems rely on the same data, we place an integration layer in the middle, so an upgrade to one system does not break the rest. Our integration and API team designs those contracts.

Illustrative example

People and channels

  • Staff in Odoo
  • Web shop and customer portal
  • Mobile and point of sale

Odoo

External API · integration layer

Systems and networks

  • Peppol network
  • Bank feeds and statements
  • SAP at group level
  • Couriers and payment providers
Odoo and the systems and networks it works with
Read the diagram as text

Left: people and channels, meaning staff working in Odoo, the web shop and customer portal, and mobile and point of sale.

Centre: Odoo, joined to every other system through its external API and, where volumes justify it, an integration layer.

Right: systems and networks, meaning the Peppol network, bank feeds, an SAP core at group level, and couriers and payment providers.

Odoo by sector

Public service

Public Service & Government

Smaller State agencies and publicly funded charities that need accounting, purchasing and projects, with EN 16931 e-invoices exchanged with public buyers over Peppol, on hosting they control.

600+

European government projects

  • Manufacturing & Industry

    Smaller plants and subsidiaries, for example in electronics or medtech components: bills of materials, work orders and quality, linked to the group’s SAP core for consolidation.

  • Healthcare & Life Sciences

    Care providers and medical suppliers that manage stock, purchasing and invoicing with lot traceability.

Ireland

Odoo and Irish e-invoicing

Country rules reach an Odoo system first through its fiscal localisation, and in Ireland the big change is VAT modernisation. On Revenue’s published timeline, every business must be able to receive EN 16931 e-invoices from 1 November 2028, large corporates issue them for domestic B2B trade from the same day, and businesses trading within the EU follow from 1 November 2029. Contracting authorities already accept EN 16931 e-invoices over Peppol under S.I. No. 258 of 2019, which matters if you sell to public buyers.

We configure the localisation, test the exchange with your real trading partners and keep custom modules away from the VAT logic, so a rule change comes with the next Odoo update rather than forcing a rebuild.

Odoo questions we are often asked

Will Odoo be ready for Irish VAT modernisation and e-invoicing?

Under Revenue’s published timeline, every business must be able to receive EN 16931 e-invoices from 1 November 2028, and VAT-registered large corporates must issue them for domestic B2B trade from that date and report the data to Revenue; a PDF will not count. From 1 November 2029 the plan extends issuing to businesses trading within the EU. The legal basis is in Finance Bill (No. 2) 2026, which has not yet been enacted, so dates and details may still move. Separately, public buyers already receive EN 16931 e-invoices over Peppol under S.I. No. 258 of 2019.

Most Odoo users in Ireland will need to receive first and issue later. We check what your Odoo version and edition support for these rules, set up the exchange, test it with your main customers and suppliers, check the output against EN 16931, and agree how incoming e-invoices are matched and approved.

Should we use Community or Enterprise?

Community is open source with no licence fee, but it is missing applications and features most businesses need, among them several accounting, localisation and AI features. Enterprise has them, plus Odoo’s upgrade service, for a subscription per user. We weigh the two against the list of processes you actually run rather than a brochure.

Odoo Online, Odoo.sh or hosting it ourselves?

Odoo Online is the easiest option but does not allow custom Python modules. Odoo.sh is Odoo’s platform service, with custom modules, staging and automated tests. Hosting it yourself gives you complete control over location and security, along with complete responsibility for running it. The decision comes down to your sovereignty requirements, how much you need to customise and the operations capacity you have in house.

How much will the annual upgrade cost?

Odoo brings out a major version each year and supports only the latest few. Odoo’s upgrade service handles standard data; custom modules must be migrated by whoever looks after them. Cost depends almost entirely on how much was customised and in what way. That is why we extend by inheritance instead of overwriting, keep tests in place, and plan for upgrades from the first day.

Can Odoo work alongside SAP within a group?

Yes, in a two-tier ERP model: SAP as the group core for consolidation, Odoo in the smaller subsidiaries. The effort goes into the integration: master data both sides share, intercompany trading, and mapping local charts of accounts onto the group chart. Our SAP team designs the two sides together.

Can we switch from our current ERP to Odoo and keep trading?

In most cases, yes, with a phased plan: finance and master data first, then operations, while the old system stays available read-only for history. Balances and open items are reconciled at each step, so you can see the move in the figures and not only on screen.

Let’s talk about Odoo

Picking an ERP, rescuing an Odoo that has been customised too far, or connecting subsidiaries to a group core: we begin with a conversation about your processes and your timeline, including the 2028 e-invoicing date.

Talk to us about your projectHow we work