Skip to main content
FromNine
Menu

Odoo practice

Odoo, one modular ERP from first invoice to plant floor.

We implement Odoo for MSMEs, exporters and the smaller entities of larger groups, write custom modules that survive each annual upgrade, and connect Odoo to banks, the IRP for GST e-invoices, Peppol for European buyers, online stores and the group ERP. AI is added where it takes routine work off your team.

For MSMEs, exporters and group subsidiaries in India that want one ERP without the overhead of a large programme.

Share your requirementsCompare platforms
  • OdooGold PartnerPartner status · Odoo
  • ISO/IEC 27001 certified
  • 600+ European government projects
Odoo apps on a single database and their connections. In the centre is one Odoo database holding six applications: accounting, sales and CRM, inventory, manufacturing, projects and HR. Six links lead outward to AI document capture, the IRP for GST e-invoices and Peppol for European buyers, banks and their statement files, online sales channels, the SAP core of the group, and identity.

When Odoo fits, and when another choice is better

A good fit when

  • An MSME has outgrown spreadsheets and separate accounting software and wants accounting, GST, sales, stock and HR in one system.
  • A group wants a light ERP for its smaller entities, in India or in Europe, that reports into the SAP core.
  • You want to go live with accounting and inventory first and switch on further apps later.
  • Your processes follow common practice, and the cost per user weighs heavily in the decision.
  • You want control over hosting, up to running Odoo on infrastructure you choose, with data stored where your contracts require.

Look elsewhere when

  • Consolidation across many companies, high-volume production or demanding statutory reporting call for SAP S/4HANA, with Odoo at most in the smaller entities.

    Alternative: SAP

  • Big contact centres, multi-stage service requests or large customer and dealer portals are Salesforce territory.

    Alternative: Salesforce

  • If Odoo would need deep changes to its standard behaviour, each annual upgrade turns into a project; a custom application is then often cleaner.

    Alternative: Enterprise Software & SaaS

Five types of Odoo work

Most engagements combine several of these five. They also serve as the column headings in the capability matrix.

  1. 01

    Implement

    Rollout

    We select the apps, configure them with GST and other localisation settings, migrate your data and go live in phases, so trading never stops.

    Deliverables

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

    Extend

    Custom modules

    Modules in Python and OWL that extend Odoo by inheritance, covered by automated tests so each annual upgrade stays under control; Odoo Studio for changes that need no code.

    Deliverables

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

    Integrate

    Interfaces

    Links to banks, the IRP, Peppol, online stores, logistics partners, payment gateways and the group ERP, built on Odoo’s external API with an integration layer when volumes justify it.

    Deliverables

    • Interface list
    • Monitored connectors
  4. 04

    Migrate

    Migration and upgrades

    Moves from spreadsheets, older accounting software or an earlier Odoo version, with data mapping, reconciliation and porting of custom modules to the current release.

    Deliverables

    • Migration plan
    • Reconciliation reports
  5. 05

    Operate

    Run and improve

    Hosting on Odoo.sh or infrastructure you choose, monitoring and backups, and an annual upgrade plan that keeps you on a supported version.

    Deliverables

    • Hosting set-up
    • Upgrade calendar
    • Support backlog

Capability matrix

The Odoo apps we cover and the type of work in each. Read each row across.

  • Accounting and invoicing

    Multi-company accounting, fiscal localisation including GST, bank reconciliation, and links to the IRP.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Sales, CRM and e-commerce

    Quotations, subscriptions, the Odoo website and connections to external marketplaces and shops.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Inventory and purchase

    Stock across warehouses, routes, reordering and vendor management.

    • Implement
    • Extend
    • Integrate
    • Migrate
    • Operate

  • Manufacturing and quality

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

    • Implement
    • Extend
    • Integrate
    • Operate

  • Projects, timesheets and field service

    Planning, time recording and billing of work performed.

    • Implement
    • Extend
    • Operate

  • HR and expenses

    Employee records, leave and expense claims; payroll only where a localisation supports it.

    • Implement
    • Extend
    • Operate

  • Localisation, GST and Peppol

    Charts of accounts and tax reports per country, GST set-up for India and Peppol for European buyers.

    • Implement
    • Integrate
    • Operate

  • AI features

    Digitisation of vendor bills and expenses and the AI features of newer versions, configured and governed.

    • Implement
    • Extend
    • Operate

  • Odoo.sh and self-hosting

    Hosting, staging copies, backups, monitoring and annual version upgrades.

    • Migrate
    • Operate

Odoo and AI

Standard on the platform

Odoo’s own AI targets repetitive tasks. When a vendor bill or expense receipt arrives, digitisation extracts the details and suggests an accounting entry that a person then checks. Writing assistance appears in email, documents and the website editor, and newer releases let you configure AI-filled fields and agents that work on Odoo records.

Availability varies with version, edition and hosting, and several features draw on paid credits. We check what your installation includes, and in which location documents are processed, before any plan relies on it.

Built beside the platform

Beside Odoo we build what it lacks: an assistant that answers questions on Odoo data within each user’s access rights, sorting of incoming documents such as purchase orders and GST invoices before they reach the right app, and automation of routine steps like payment matching, reminders and reorder alerts. All of it runs through Odoo’s external API and respects its access rules.

Each service has limited rights, stops for maker-checker approval before it posts an entry or releases a payment, and logs every step. A person takes any decision the service is unsure about.

Choosing the route

  1. 01

    Is the job reading vendor bills or expense receipts?

    If yes

    Start with Odoo’s digitisation and track how often your team corrects it.

    If no

    Review automated actions and your version’s AI features before any custom build.

  2. 02

    Does it rely on data or files held outside Odoo?

    If yes

    Build a separate service that talks to Odoo through its external API.

    If no

    Configure the standard features and keep the logic in Odoo.

  3. 03

    Is your Odoo hosted on Odoo Online?

    If yes

    Odoo Online does not accept custom Python modules, so any custom AI runs as a separate service.

    If no

    On Odoo.sh or your own servers, a custom module can place the AI step inside Odoo’s screens.

From scoping to a stable Odoo

  1. Step 01

    Scope

    Processes, apps, GST and other localisation needs, integrations and the hosting decision.

    • Module map
    • Hosting decision

  2. Step 02

    Configure

    Standard set-up first, built with your key users in a test database.

    • Configured database
    • Gap list

  3. Step 03

    Customise sparingly

    Custom modules only where a genuine gap remains, each with tests and upgrade notes.

    • Custom modules
    • Test suite

  4. Step 04

    Migrate data

    Opening balances, masters and open items moved and reconciled with the old books.

    • Reconciliation reports

  5. Step 05

    Go live

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

    • Cut-over checklist
    • First close

  6. Step 06

    Upgrade every year

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

    • Upgrade calendar
Illustrative example

An MSME exporter moving off spreadsheets

01Situation
An engineering goods exporter keeps orders, stock and production in spreadsheets and uses separate accounting software. It reports its B2B invoices to the IRP by hand, and two of its EU buyers now ask for invoices over Peppol.
02What we would put in place
One Odoo database for accounting, GST, sales, inventory and manufacturing, an automated link to the IRP that stores each IRN with its invoice, and Peppol exchange for the European buyers.
03Where an officer decides
The accounts team approves each invoice before it is reported to the IRP, and an authorised officer approves vendor payments above an agreed limit (maker-checker).
04How success would be measured
Days from month end to closed books, share of invoices accepted by the IRP at the first attempt, share of vendor bills posted without retyping, and effort per annual upgrade.

Odoo among your other systems

In an MSME, Odoo is the centre of everything; in a larger group, it is one entity’s ERP at the edge. Typical links go to banks, the IRP for GST e-invoices, Peppol for European buyers, online stores, logistics partners and payment gateways, and, in a group, to SAP for consolidation and intercompany invoices.

Most links can use Odoo’s external API directly. Once volumes rise, or several systems rely on the same records, an integration layer in between means one upgrade does not break the rest. The Integrations & APIs team defines those contracts.

Illustrative example

People and channels

  • Staff in Odoo
  • Online store and portal
  • Mobile and POS

Odoo

External API · integration layer

Systems and networks

  • IRP and Peppol
  • Banks and statements
  • SAP group core
  • Logistics and payments
How Odoo connects to people, systems and networks
Read the diagram as text

Left: people and channels, with staff working in Odoo, the online store and customer portal, and mobile and point-of-sale use.

Centre: Odoo, linked to the rest through its external API and, where volumes require it, an integration layer.

Right: systems and networks, with the IRP and Peppol, banks and their statement files, the SAP core of the group, and logistics partners and payment gateways.

Odoo by sector

Public sector

Government & Public Sector

Autonomous bodies, societies and publicly funded non-profits that need accounting, purchasing and projects in one system, on hosting they control and with records that stand up to audit.

600+

European government projects

  • Manufacturing & Industry

    Component makers and the smaller plants of a group running work orders, bills of materials and quality checks in Odoo, with figures passed to SAP for consolidation.

  • Healthcare & Life Sciences

    Diagnostic chains, clinics and medical distributors that track batches and expiry dates across stock, purchases and GST invoices.

India

Odoo, GST e-invoicing and European buyers

For an Indian company, the localisation that matters first is GST. GST-registered businesses above the turnover threshold report their B2B and export invoices to the Invoice Registration Portal (IRP) and receive an Invoice Reference Number (IRN) for each; since 1 April 2025, larger taxpayers cannot report invoices more than 30 days old. The invoice process in Odoo therefore needs a reliable daily link to the IRP and a clear owner for rejected invoices.

Exporters and groups with European entities meet a second set of rules. Belgium has required structured e-invoices between businesses since 1 January 2026, in practice over Peppol, and other Member States are introducing their own requirements. Each localisation is configured and tested with your actual customers and suppliers, and custom modules stay away from tax logic, so a change in the rules comes with an Odoo update instead of new development.

Questions about Odoo

How do GST e-invoicing and Peppol fit together in Odoo?

They cover different invoices. In India, a GST-registered business above the turnover threshold reports its B2B and export invoices to the Invoice Registration Portal (IRP), which returns an Invoice Reference Number (IRN) for each one. Peppol is an e-invoicing network used across Europe: invoices to buyers or subsidiaries in the EU travel over it in the Peppol BIS Billing 3.0 format where the trading partner requires it, as Belgian businesses have for domestic B2B invoices since 1 January 2026.

We check what the Indian localisation of your Odoo version and edition covers for GST and e-invoicing, set up IRP reporting and the Peppol registration, test exchanges with your main customers and suppliers, and decide how incoming invoices are matched and approved. The two processes then run side by side from the same Odoo database.

Which edition: Community or Enterprise?

Community costs nothing in licences and is open source, yet it leaves out apps that most growing companies end up needing, among them parts of accounting, localisation and the AI features. Enterprise includes those and Odoo’s upgrade service, priced per user. We hold both against your list of processes before recommending one.

Where should our Odoo run: Odoo Online, Odoo.sh or our own servers?

Odoo Online needs the least effort but does not take custom Python modules. Odoo.sh, Odoo’s managed platform, supports custom modules, staging copies and automated tests. Running it on your own servers or cloud gives you full say over location and security, and the full operational burden. Where your data must be stored, how much you customise and what your IT team can run decide it.

What does each annual upgrade cost?

Odoo brings out a new major version each year and keeps only recent versions in support. Its upgrade service converts standard data; custom modules have to be ported by the team that maintains them. So the bill is driven by the amount and style of customisation. We extend Odoo by inheritance instead of overwriting it, keep tests for each module and plan the upgrade cycle from the first phase.

Can Odoo sit beside SAP in one group?

Yes. In a two-tier set-up SAP carries consolidation and the group core, while Odoo runs the smaller companies, whether in India or in Europe. Most of the effort goes into the integration: common master data, intercompany invoices, and mapping each local chart of accounts to the group chart. Our SAP practice designs both ends together.

Can we switch from our current accounting software to Odoo without disrupting the business?

In most cases, yes, by moving in phases: accounts and masters first, then operations, while the old software stays available read-only for past records. Balances, open items and GST data are reconciled at every phase, so the change can be checked in the figures as well as on screen.

Tell us about your Odoo plans

Selecting a first ERP, repairing a heavily customised Odoo or bringing subsidiaries onto the group ledger: describe your processes and timeline, and we will propose a first phase.

Share your requirementsOur delivery model