Skip to main content
FromNine
Menu

Enterprise platform · Odoo

Odoo: a single system, built from modules, for the whole company.

We implement Odoo for growing businesses and group subsidiaries, build custom modules that survive each annual upgrade, and link Odoo to banks, MyInvois, Peppol, online shops and the group ERP. We add AI where it takes routine work off people’s desks.

For growing Malaysian businesses and group subsidiaries that need one system for the whole company without the weight of a large ERP.

Arrange a discussionPlatform comparison
  • OdooGold PartnerPartner status · Odoo
  • ISO/IEC 27001 certified
  • 600+ European government projects
One Odoo database, its modules and the systems connected to it. In the middle is one Odoo database with six modules side by side: HR, projects, CRM and sales, manufacturing, inventory and accounting. Six links run outwards: to AI document capture, MyInvois and Peppol, bank statement feeds, e-commerce, identity and the group’s SAP core.

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

A good fit when

  • A mid-sized business wants its finance, sales, inventory, projects and HR on one database instead of a scattering of separate tools.
  • Each subsidiary of a bigger group needs its own ERP, connected to the group core.
  • You would rather start small with some modules and switch on more as you grow.
  • Your processes follow common practice and licence cost is a real factor.
  • You want control over hosting, up to running Odoo on infrastructure you choose, with the location agreed and written into the contract.

Look elsewhere when

  • Consolidation over many legal entities, production at large scale or demanding statutory reporting. That is the territory of SAP S/4HANA, possibly with Odoo in the subsidiaries.

    Alternative: SAP

  • Big contact centres, intricate case handling or wide-ranging public portals. Salesforce handles those better.

    Alternative: Salesforce

  • You intend to alter the behaviour of the Odoo core substantially. Every annual upgrade would then become a project, and building your own application might be the tidier path.

    Alternative: Enterprise Software & SaaS

Our Odoo work

Five types of work, normally combined. They also serve as column headings in the capability matrix further down.

  1. 01

    Implement

    Implementation

    Module selection, set-up, fiscal localisation with e-Invoice and the transfer of data, rolled out in stages while daily operations continue.

    Deliverables

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

    Extend

    Custom modules

    Modules written in Python and OWL that extend Odoo by inheritance rather than by overwriting it, covered by automated tests so the annual upgrade stays manageable. For small changes that need no code, Odoo Studio.

    Deliverables

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

    Integrate

    Integration

    Connections to MyInvois, Peppol, banks, online shops, couriers, payment services and the group ERP, over the Odoo external API and an integration layer when volumes call for it.

    Deliverables

    • Interface list
    • Monitored connectors
  4. 04

    Migrate

    Migration and upgrades

    Moves from spreadsheets, an older ERP or an earlier Odoo release, with mapping and reconciliation of data and custom modules brought onto the new version.

    Deliverables

    • Migration plan
    • Reconciliation reports
  5. 05

    Operate

    Managed evolution

    Odoo.sh or your own infrastructure for hosting, monitoring and backups, and a yearly upgrade plan that keeps your version supported.

    Deliverables

    • Hosting set-up
    • Upgrade calendar
    • Support backlog

Capability matrix

The Odoo applications we cover and the kinds of work we take on in each, shown row by row.

  • Accounting and invoicing

    Multi-entity accounting, tax localisations, matching of bank statements and e-Invoice.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • CRM, sales and online selling

    Quotes, recurring subscriptions, the Odoo website builder and links to outside web shops.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Inventory and purchase

    Supplier management, replenishment, stock routes and multiple warehouses.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Manufacturing and quality

    Quality checks, maintenance, work orders and bills of materials.

    • Implement
    • Extend
    • Integrate
    • Operate

  • Projects, time recording and field service

    Planning of projects, recording of time and billing of the work done.

    • Implement
    • Extend
    • Operate

  • HR and expenses

    Employees, leave and expense claims, and payroll where Odoo offers a localisation for the country.

    • Implement
    • Extend
    • Operate

  • Fiscal localisation and Peppol

    Charts of accounts and tax reports per country, e-Invoice submission to MyInvois, and Peppol exchange.

    • Implement
    • Integrate
    • Operate

  • AI features

    Configuration and governance of bill and receipt digitisation and of the AI in newer releases.

    • Implement
    • Extend
    • Operate

  • Odoo.sh or own hosting

    Staging and production databases, hosting, backups, monitoring and version moves.

    • Migrate
    • Operate

AI on Odoo

Built into the platform

Odoo comes with AI aimed at repetitive tasks. Its digitisation feature reads supplier bills and expense receipts and suggests an entry for a person to check, and writing help is built into email, documents and the website builder. Newer releases let you configure AI further, for example fields that AI fills in and agents that work on Odoo records.

What you get varies with version, edition and hosting, and certain features draw on paid credits. Before anything is planned around them, we check what your version includes and where the documents would be processed.

Built alongside the platform

Where Odoo stops, we add services of our own: assistants that answer questions on Odoo data while honouring each user’s access rights, sorting of incoming documents so they land in the right application, and automated back-office routines such as matching, payment reminders and stock alerts. All of them work through the Odoo external API and keep to its access rights.

Their permissions are narrow, nothing is posted or paid without approval, and every action is logged. Doubtful results go to a person to decide.

Choosing the route

  1. 01

    Is the task about capturing supplier bills or expense receipts?

    If yes

    Start with the Odoo digitisation feature and track how often people correct its proposals.

    If no

    Before building anything, look at automated actions and at the AI your version already includes.

  2. 02

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

    If yes

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

    If no

    Configure what Odoo offers as standard and leave the logic in Odoo.

  3. 03

    Are you on Odoo Online?

    If yes

    Online cannot run custom Python modules, so any custom AI has to sit in an external service.

    If no

    With Odoo.sh or self-hosting, a custom module can place the AI step directly in the screens people use.

Towards an Odoo that works for the business

  1. Step 01

    Scope

    Processes, applications, localisation needs including e-Invoice, interfaces and the choice of hosting.

    • Module map
    • Hosting decision

  2. Step 02

    Configure

    Standard settings before anything else, agreed with key users on a test database.

    • Configured database
    • Gap list

  3. Step 03

    Customise sparingly

    Custom modules only for genuine gaps, each delivered with tests and notes for later upgrades.

    • Custom modules
    • Test suite

  4. Step 04

    Migrate data

    Master data, open items and opening balances, all reconciled against the system being replaced.

    • Reconciliation reports

  5. Step 05

    Go live

    Training, the switch-over and hands-on support until the first month-end close is done.

    • Cutover checklist
    • First close

  6. Step 06

    Upgrade yearly

    A planned annual upgrade, so you always run a version that Odoo supports.

    • Upgrade calendar
Illustrative example

A professional services firm in the 2026 e-Invoice phase

01Situation
A professional services firm with annual revenue between RM3 million and RM5 million could have entered the e-Invoice phase that began on 1 January 2026 while still billing from spreadsheets and an accounting package that has reached end of life.
02What we would deliver
Odoo with accounting, projects and timesheets on one database, invoices drawn from approved timesheets, a connection to MyInvois that submits each e-Invoice and records the validation result, and a Peppol route for clients in the EU.
03Decisions that stay with people
Engagement managers approve each invoice before it is submitted; finance staff review every rejected validation and every incoming e-Invoice before posting.
04How results would be tracked
Days from month end until invoices go out, share of e-Invoices accepted at the first attempt, share of supplier invoices booked with no manual keying, and effort for each annual upgrade.

Odoo among your other systems

Odoo is the hub of a smaller business and an outpost of a larger group. We connect it to banks, MyInvois, the Peppol network, online shops, couriers and payment providers, and in a group to the SAP core, which receives consolidation data and intercompany transactions.

Most connections run straight over the Odoo external API. When volumes grow or the same data is shared by several systems, an integration layer goes in between, so upgrading one system leaves the others working. Our integration specialists design those contracts.

Illustrative example

People and channels

  • Employees in Odoo
  • Online shop and customer portal
  • Point of sale and mobile

Odoo

External API · integration layer

Systems and networks

  • MyInvois and Peppol
  • Banks and statement feeds
  • SAP group core
  • Couriers and payment services
Odoo and the networks and systems linked to it
Read the diagram as text

Left side, people and channels: Odoo users on staff, the online shop with its customer portal, and point-of-sale and mobile use.

Centre, Odoo, which reaches the other systems over its external API, with an integration layer added when volumes require it.

Right side, systems and networks: MyInvois and Peppol, bank statement feeds, the group’s SAP core, and couriers and payment services.

Odoo by sector

Public sector

Public Sector & Government

Publicly funded foundations, professional bodies and non-profit organisations wanting one system for their accounts, purchasing and projects, with invoicing that meets e-Invoice rules where they apply, on hosting under their own control.

600+

European government projects

  • Manufacturing & Industry

    For smaller factories and subsidiaries: production with work orders, bills of materials and quality checks, linked to the SAP core of the group for consolidation.

  • Healthcare & Life Sciences

    Clinics and medical suppliers tracking stock by lot through purchasing, storage and invoicing.

Malaysia

Odoo and e-Invoice in Malaysia

For a business in Malaysia, the e-Invoice rules are where fiscal localisation matters first. The Inland Revenue Board of Malaysia (IRBM) made e-Invoice mandatory in four phases by annual turnover or revenue: 1 August 2024 above RM100 million, 1 January 2025 above RM25 million, 1 July 2025 above RM5 million, and 1 January 2026 up to RM5 million, with an exemption below RM3,000,000. Each e-Invoice is validated through MyInvois. Malaysia Digital Economy Corporation (MDEC) is the Peppol Authority for Malaysia, and Malaysia PINT is the national specification.

We configure the localisation, test it with the customers and suppliers you actually trade with, and keep custom modules apart from tax logic. When a rule changes, the fix then comes with a standard Odoo update and nothing has to be rebuilt.

Common questions about Odoo

How does Odoo deal with e-Invoice through MyInvois and with Peppol?

Since 1 January 2026, the fourth phase of mandatory e-Invoice covers taxpayers with annual turnover or revenue up to RM5 million, while those below RM3,000,000 are exempt. The Inland Revenue Board of Malaysia (IRBM) validates each e-Invoice through the MyInvois Portal or API, and also recognises submission through a Peppol service provider using Malaysia PINT.

Odoo support for Malaysia differs between versions, so we first check what the Malaysian localisation of your version covers. We then connect Odoo to MyInvois or to a Peppol service provider, test submissions and validation results with real invoices, and agree how rejected and incoming invoices are corrected and approved. For buyers in the EU, the same invoice data can be sent over Peppol using Peppol BIS Billing 3.0.

Should we choose the Community or the Enterprise edition?

The Community edition is open source and free of licence fees, yet it is missing applications and functions many businesses rely on, among them several for accounting, localisation and AI. Enterprise includes them, plus the Odoo upgrade service, against a subscription charged per user. We weigh the two against the processes you actually run, not against a brochure.

Which hosting option suits us: Online, Odoo.sh or our own servers?

Odoo Online is the simplest, but custom Python modules cannot run on it. Odoo.sh, the Odoo platform service, supports custom modules with staging and automated testing. Running Odoo on your own infrastructure gives you full say over location and security, and full responsibility for keeping it running. The decision turns on your data location requirements, the customisation you need and the operations team you have.

What will the annual upgrade cost us?

A new major Odoo version appears every year, and only recent versions stay supported. Standard data moves through the Odoo upgrade service, while custom modules have to be migrated by the team that looks after them. Cost is driven mainly by the amount and style of customisation. So we extend Odoo by inheritance instead of overwriting it, keep tests running and plan each upgrade from the start.

Can Odoo sit alongside SAP within a group?

Yes, in a two-tier set-up: SAP handles the group core and consolidation, while Odoo runs the smaller subsidiaries. The effort goes into the integration, meaning common master data, intercompany flows and a mapping of each subsidiary’s accounts onto the group chart. Our SAP team designs both sides as one.

Can we leave our old ERP for Odoo without halting operations?

Usually yes, by moving in phases. Finance and master data go first and operations follow, while the old system stays available read-only for its history. At each step we reconcile balances and open items, so the change is proven in the figures, not merely visible on screen.

Let us look at your Odoo plans together

Whether you are selecting an ERP, recovering an Odoo that has been over-customised or linking subsidiaries with the group core, begin with a discussion of your processes and the dates you are working to.

Arrange a discussionOur delivery approach