We set up hosting in your name: Odoo.sh, your cloud or on premise. Odoo.sh is the simplest for Enterprise. Larger or regulated deployments go on your own AWS or Azure account, where Codeeo is an AWS partner.

Services · Odoo and ERP implementation

Odoo scoped to what you will actually use.

Q: Can you migrate our data?

Yes, and we reconcile it against the old system. Customers, products, stock levels, open invoices and history are mapped, cleaned and imported into a test database first. Nothing goes live until finance has checked the balances.

Q: Will customisation break upgrades?

Not if it is done the Odoo way. We build customisations as proper modules that inherit rather than overwrite, so a version upgrade carries them forward. Modifications made directly to core are how upgrades become rewrites.

Q: What about training and support?

Role based training at each go-live, and a retainer after. Finance, warehouse and sales each get training on their part, recorded for new starters. Most clients keep a monthly block of hours for the questions and tweaks that follow.

Odoo does almost everything, which is exactly why implementations stall. We scope the modules you will genuinely use, migrate the data properly, and leave the rest switched off until you need it.

Sales, inventory, manufacturing, accounting, purchasing and point of sale, implemented in the order the business needs them.

Get in touch See our work

Built for: Companies with stock, manufacturing or several entities that have outgrown separate tools.
Typical timeline: A first module such as sales or inventory in six to ten weeks. A full suite over six to twelve months.
What you own: Your Odoo subscription and database, hosted in your name on Odoo.sh or your own cloud.
Rated: 4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

What you get

The Odoo modules, in the order a business turns them on.

Each one is a project with its own data, training and go-live. We run them one at a time. We deliver Odoo implementation in the UK with Odoo ERP modules for sales, inventory, accounting and manufacturing, configured before anything is customised.

Explain your project

Odoo developers
Custom modules and modifications done the Odoo way, so upgrades still work.
Your customisations survive the next Odoo upgrade instead of blocking it.
Odoo implementation
Scoping, configuration, data migration, training and go-live, module by module.
You go live module by module, with the business running the whole time.
Odoo migration
Version upgrades and moves from other ERPs, with the data reconciled on the way.
You switch over with the data reconciled, so nobody is checking two systems for a month.
Inventory management
Multi-warehouse, lots, serials and reordering rules that match how stock really moves.
Stock on screen matches stock on the shelf, across every warehouse.
Manufacturing module
Bills of materials, work orders and costing for companies that make things.
You know what each unit cost to make, not just what it sold for.
Odoo accounting
Chart of accounts, VAT and multi-entity set up to the standard your auditor expects.
Your auditor gets the books in the shape they expect, VAT and entities included.
Purchase management
Suppliers, RFQs and approvals, connected to stock so you order what you will sell.
You order what stock says you need, with approvals in the system rather than in email.
Point of sale
Retail and hospitality POS that shares stock and customers with the back office.
A sale at the till updates stock and the customer record in the back office at once.
Odoo customisation
Fields, flows and reports changed to fit the business, without forking the product.
The system fits how you work, without a fork you have to maintain forever.
ERP consulting
An honest view on whether Odoo fits, and what to switch on first if it does.
You find out whether Odoo fits before you spend on licences and migration.

Who this is for

Three reasons Odoo projects land on our desk.

Odoo does almost everything, which is why implementations stall. Three reasons they land on our desk, and the sequence that gets them finished. An Odoo migration is a chance to remove customisation that Odoo ERP now does as standard.

A previous implementation stalled

Too many modules turned on at once, data half migrated, the team back on spreadsheets. We find what is salvageable and restart one module at a time.

Restarted one module at a time.

The business has outgrown separate tools

Stock in one place, invoices in another, customers in a third. One system with one customer record is the point of an ERP.

One customer record is the point of an ERP.

You need manufacturing or multi-warehouse stock

The place where generic tools give up. Odoo handles both well when the data model is set up properly from the start.

Where generic tools give up.

Four phases, one module at a time.

01DiscoverWhich processes hurt most, in which order, and what data exists for each. The output is a module sequence and a list of what stays switched off for now.
02DesignChart of accounts, warehouses, product structure and user roles designed on paper and agreed with finance before anything is configured.
03BuildEach module is configured, loaded with real migrated data and tested by the people who will use it before it goes live. The next module starts only when the last one is trusted.
04MeasureReconciliation against the old system for the first month, then adoption: what is still being done outside Odoo, and why.

Selected work

Where this service has already shipped.

Two or three of the companies this lane has built for. The full list is on the work page.

Retail and eCommerce

THE GORGEOUS FLOWER

A Dubai florist with free same day delivery on orders by 5 PM, and a delivery date and window chosen at checkout.

Same day florists live or die on the cut-off. The Gorgeous Flower Co checkout asks for a delivery date and one of three windows with the current UAE time shown, pins the recipient on a map and carries a gift message on every bouquet, with loyalty points and subscriptions to bring customers back.

View case

How we work together

Three ways to buy an Odoo implementation.

Odoo's own licensing is per user and transparent. Our fee is for the implementation, migration, customisation and training. Whether it is a new Odoo implementation in the UK or an Odoo migration from an older version, the scope and timeline are written down first.

Fixed scope

A defined build with a deadline

We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.

Written scope and acceptance criteria
Fixed price and delivery date
Weekly build on a URL you can open
30 days of fixes after launch

Get in touch

Dedicated team

A product that keeps evolving

Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.

Senior engineers, not a rotating bench
Your tools, your repo, your process
Monthly, cancel with 30 days notice
A lead who answers for the team

Get in touch

Retainer

Something live that needs looking after

A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.

Agreed response times
Monitoring and dependency updates
A monthly report of what changed and why
Priority access to the same team that built it

Get in touch

Technology

What we build this with.

Chosen to fit the problem and the team who will own it afterwards.

01Business platforms

Microsoft Dynamics 365
Business Central
Power Platform
Odoo

02Data and cloud

PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker

Questions people ask before implementing Odoo.

Odoo Community or Enterprise?

Enterprise for most businesses. Community when the budget is the constraint and the needs are simple.

Enterprise includes accounting, manufacturing and the mobile apps, plus hosting on Odoo.sh. Community is free to licence but you host and maintain it, and several modules are missing. We will tell you which fits.

How long does it take?

Can you migrate our data?

Will customisation break upgrades?

Do you host it?

What about training and support?

Services that usually go with this one.

Microsoft Dynamics 365 and CRMDynamics 365 and Business Central set up so sales actually use them.Custom software and business systemsThe system that replaces the spreadsheet nobody dares change.Web development and eCommerceSites and stores tuned for the checkout and the search terms that bring buyers.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews

Odoo scoped to what you will actually use.

The Odoo modules, in the order a business turns them on.

Odoo developers

Odoo implementation

Odoo migration

Inventory management

Manufacturing module

Odoo accounting

Purchase management

Point of sale

Odoo customisation

ERP consulting

Three reasons Odoo projects land on our desk.

A previous implementation stalled

The business has outgrown separate tools

You need manufacturing or multi-warehouse stock

Four phases, one module at a time.

Where this service has already shipped.

THE GORGEOUS FLOWER

Three ways to buy an Odoo implementation.

Fixed scope

Dedicated team

Retainer

What we build this with.

Questions people ask before implementing Odoo.

Services that usually go with this one.

Tell us what the business needs. We will tell you what to build first.