Odoo

Odoo implementation by people who also keep the books

Most Odoo projects are run by developers who have never closed a month, or by accountants who cannot write a module. The work goes wrong in the gap between the two. We do both, and the accounting is set up to be audited, not just to look finished.

What the work covers

No.ScopeWhat it means in practice

01ConfigurationSales, purchasing, inventory, manufacturing, POS, accounting. We configure what you will actually use and leave the rest switched off, because an Odoo nobody can navigate is worse than the spreadsheet it replaced.

02Custom modulesWhen the standard module stops short, we write the module. Python, XML views, ORM, proper migrations. Not studio hacks that break at the next version.

03Data migrationChart of accounts, opening balances, customers, suppliers, products, stock, open invoices. Reconciled against the old system before anybody is asked to trust it.

04Hosting and deploymentSelf-hosted on your own server with Docker, or Odoo.sh, or Odoo Online. You hold the credentials and the database either way.

05UpgradesVersion upgrades, including the custom modules that usually make upgrades frightening. We have taken live systems across major versions without losing a day of trading.

What we have actually built on it

No.SystemWhat it does

01A publisher we run it forA publishing business runs its orders, invoicing, inventory, costing and courier dispatch in Odoo. Every order placed on its website becomes an invoice and moves stock. We are not recommending a system we have not run ourselves.

02Odoo 19 for a publisherSelf-hosted on Docker with a custom module, running in daily use.

03HR, payroll and tasksEmployee records, payroll runs and task tracking moved off spreadsheets and onto Odoo.

04A multi-tenant ERP of our ownMERPP: accounting, POS, manufacturing and tax filing, built from scratch on PostgreSQL. It is why we know what Odoo is doing underneath, and when it is the wrong answer.

How it runs

We map the processes first and write them down. You get that map whether or not you hire us. Then configuration and migration run in phases against a staging database, with a parallel run before anything is switched over. Nobody is asked to learn a new system and close a month in the same week.

If Odoo is the wrong fit, we say so at the mapping stage. It is a poor fit for some manufacturing and for businesses whose process is their product. That conversation is cheaper before the licence is bought.

Book a friction audit

hello@inertiaautomate.com