Odoo implementation

Odoo, in phases you can check.

When the assessment says replace, we implement Odoo for the order, the stock and the books first, and add the next app once that phase is live. The dates come out of discovery. The gates below don't move.

Talk to us See the method

First phase

The order, the stock and the books.

Sales, purchasing, inventory and accounting on one Odoo database. Customers, products and accounts are defined once, so adding the next app later is not a new integration project.

In the first phase

  • Quotes and sales orders, with your pricing and credit rules.
  • Purchasing and goods receipts.
  • Stock on hand, locations and valuation.
  • Invoicing, bills, bank reconciliation and GST reporting from the same records.
  • The connections to systems that stay, such as a Shopify store or a carrier.

Later, each quoted on its own

  • Manufacturing, field service, helpdesk or projects, where they fit.
  • Point of sale and a shared loyalty programme.
  • A trade portal or an Odoo shop, where the Shopify rule says so.
  • Payroll only when it is scoped in writing. It is not part of "the books" by default.

The method

Six gates, in order.

Each gate has a written output. We don't start the next one until the last one is signed off.

Discovery

We map order-to-cash, procure-to-pay and record-to-report with the people who do the work, and name the systems that stay before anyone writes a connector.

  • Process map and app map
  • Written scope and quote
  • The scope is yours to take elsewhere

Configure

Standard Odoo first, then settings, then Studio, then a small module, and an integration last. All of it on a staging copy, never on the live database.

  • Configuration log
  • Every customisation named and justified

Migrate

Customers, suppliers, products, open orders, open receivables and payables, and stock on hand, moved in trial runs until they come across clean.

  • Opening balances reconciled with your accountant
  • Stock valuation that matches

Train

People practise in staging on their own data: their orders, their suppliers, their exceptions. Not a demo company.

  • Role-by-role run-throughs
  • Written procedures for each exception

Cut over

At a period boundary. The old system becomes read-only for history. Nothing goes live until balances match and the people using it have signed off.

  • Cut-over plan and rollback point
  • Go / no-go sign-off

Support

The same people on the first month-end, the fixes and the upgrades. The next app starts only when the first phase is stable.

  • First month-end closed together
  • Upgrade plan for each Odoo release

Standard before custom

Less custom code, cheaper upgrades.

Why it matters

Odoo releases a new version each year. Every Studio change and every custom module has to be retested when you upgrade. The more of your process that runs on standard Odoo, the smaller that bill, every year.

What we do about it

We try a setting before Studio, and Studio before code. When custom work is the right answer, it is named in the scope with the reason, and it is on the upgrade checklist from day one.

What you pay for

Two bills, kept apart.

Odoo bills Odoo

Odoo licences are priced per user by Odoo and billed by Odoo separately, under Odoo's terms. So are Odoo's hosting plans and any AI credits you choose to use. We name them in the scope so there are no surprises, but they are not on our invoice.

We quote the work

Discovery, configuration, migration, training, cut-over and support are quoted in writing from the agreed scope. We don't publish a starting price, because it would not survive contact with your data.

Get started

Start with discovery.

Tell us what runs your orders, stock and invoicing today. We'll tell you whether Odoo is the right answer before anyone quotes an implementation.

Talk to us Keep, modernise or replace