Skip to content

FIG 01 · Odoo Development

Odoo implementation planned for the next upgrade, not just go-live

Discovery, configuration, custom modules, integrations and data migration, with the version and hosting chosen first and customisations written so the next upgrade is routine, not a rebuild.

See how it works
Business software developer at a laptop with a grid of app modules in a furniture workshop office

FIG 02 · Quick answer

What do Odoo implementation services include?

Elgrith provides Odoo implementation services and custom Odoo development: discovery, configuration, custom modules, integrations and data migration. We choose the version and hosting first, since Odoo supports its last three major versions and Odoo 20 shipped in September 2026, and we write customisations that survive upgrades. We hold no Odoo partner tier, so advice stays independent.

Odoo versions we plan new builds around
18–20
Projects delivered since 2015
1,000+
Clients across the USA, UK and India
250+
Your code, configuration and IP
100%

FIG 03 · Why it matters

Odoo 20 is out. Every version has a support window.

From Odoo’s release notes and supported-versions documentation, read on 23 Oct 2026.

FIG 04 · Version check

Which Odoo version in 2026: 18, 19 or 20?

Pick the version before anything else: it decides which apps and community modules are ready, and when you upgrade next. For most new builds the answer is the newest version your required modules support.

Odoo versions and support, checked 23 Oct 2026
VersionReleasedEnd of supportOur view
Odoo 20September 2026Supported (newest)Default for new builds, if the modules and localisation you need are ready
Odoo 19Previous major versionSupportedSound choice when a module you rely on isn’t ported to 20 yet
Odoo 18October 2024October 2027 (planned)Supported, but plan the next upgrade into your budget
Odoo 17November 2023October 2026 (planned)Upgrade now
Odoo 16 and older2022 and earlierEnded (16: October 2025, planned)Out of support: upgrade or re-implement

Sources: the Odoo 20 release notes and Odoo’s supported-versions documentation (the edition that lists 17.0 and 18.0 dates; the newest edition’s table did not render when we checked), read 23 Oct 2026. Odoo supports its last three major versions, so we recheck this table before every project starts.

Weighing Odoo against NetSuite? Read Odoo vs NetSuite in 2026

FIG 05 · What you get

Odoo development company services

Odoo is a set of apps (Accounting, Inventory, Manufacturing, CRM, eCommerce, POS and more) on one database. We configure the standard apps first, then build custom modules in Python, XML and OWL only where the standard flow doesn’t fit.

Oak tray of modular blocks with one blue block lifted out, in front of a laptop grid of app tiles
Odoo Development · built in-house

01

Discovery and fit-gap

Your processes mapped against standard Odoo apps, so every customisation has a written business reason.

02

Configuration

Companies, chart of accounts, taxes, warehouses, routes, price lists and access rights set up and documented.

03

Custom modules

Python models on the Odoo ORM, XML views and OWL components, in your Git repository with tests.

04

Odoo Studio

Fields, views and simple automations in Studio where code isn’t needed, kept tidy so upgrades stay easy.

05

External API

Integrations over Odoo’s External API (XML-RPC and JSON-RPC) with your store, payments, logistics and BI.

06

Data migration

Customers, products, stock, open invoices and balances moved from QuickBooks, Tally, spreadsheets or another ERP.

07

Version upgrades

Databases and custom modules moved to a supported version, tested on a copy before production.

08

Reports and documents

Invoices, delivery slips and management reports laid out the way your customers and finance team expect.

Deliverables

11

deliverables, in writing

Included in every build, written into your fixed quote before work starts.

FIG 06 · Migrate and connect

Data migration and integrations

Most Odoo projects replace one system and connect to several others. We plan both before configuration starts, because the data model decides how clean the migration and the integrations will be.

  • QuickBooks
  • Tally
  • Spreadsheets
  • Shopify
  • Payments
  • BI and reports
  • From QuickBooks or Xero

    Move
    Customers, vendors, products, open items and balances
    Check
    Trial balance matched at the cut-over date
  • From Tally

    Move
    Ledgers, stock items, GST details and open bills
    Check
    GSTIN and HSN data validated before import
  • Shopify and other stores

    Sync
    Orders, stock, prices and customers
    Or
    Odoo eCommerce as the store itself
    E-commerce Development
  • Payments

    Connect
    Payment providers to invoices and the online store
    Reconcile
    Payouts matched to bank statements
  • Localisation

    India
    GST and e-invoicing set up with your IRP flow
    UK
    VAT returns under Making Tax Digital
    Accounting Software Integration
  • Data pipelines

    Feed
    Odoo data into your warehouse and dashboards
    Keep
    Odoo as the system of record
    Data Engineering

FIG 07 · Implement

Odoo implementation services, discovery to go-live

Standard first, customise with a business reason. Each phase ends with something you can test, not a slide deck.

06principles

  • Discovery

    Workshops with each team, a process map and a fit-gap list against standard Odoo apps.

  • Version and hosting

    Odoo 18, 19 or 20, on Odoo Online, Odoo.sh or on-premise, chosen with you and written into the scope.

  • Configuration sprints

    Apps configured in a staging database, demoed every week and signed off by the people who will use them.

  • Test migrations

    At least one full test migration, reconciled, before the real one.

  • Training

    Role-based sessions and short how-to notes for each team.

  • Go-live

    A planned cut-over with the old system kept read-only until sign-off.

FIG 08 · Customise

Odoo customization services that survive upgrades

Every customisation is code someone has to port at the next major version. We keep the count low and write what remains so it ports cleanly.

06principles

  • Separate modules, no core edits

    Changes live in your own modules that inherit standard models and views; we never edit Odoo’s source.

  • Python on the ORM

    Business logic on the Odoo ORM, with automated tests that run on each upgrade.

    Python development
  • Git and staging

    Every module in your Git repository, tested on a staging copy of your data before production.

  • Apps Store modules, checked

    Third-party modules from the Odoo Apps Store reviewed for version support and code quality before you depend on them.

  • Access rights

    Groups and access rights reviewed, especially on Odoo 20, where record rules move into each access right’s own domain.

  • Upgrade notes

    A list of every customisation and what it does, so the next upgrade starts with a map.

FIG 09 · After go-live

Odoo consultant support after go-live

The first months after go-live decide whether people trust the system. An Odoo consultant stays on hand to fix, tune and extend, on terms agreed in your written scope.

06principles

  • Hyper-care

    A period of close support right after go-live, with fixes prioritised with your team.

  • Backlog and improvements

    New reports, automations and small modules planned in a shared backlog.

  • Upgrade planning

    A dated plan to move to the next supported version before yours reaches end of support.

  • Odoo AI agents

    Odoo 20’s AI agents set up where they help, with scheduled triggers and human review.

  • New integrations

    More systems connected as you grow.

    API integration
  • Training new staff

    Refresher sessions and updated how-to notes as your team changes.

FIG 10 · Process · 6 steps

Pick the version first, build second

A free call, a discovery and a fixed written quote, then configuration and custom modules in sprints with weekly demos. You own the modules, configuration and documentation.

  1. Step 01

    Free call

    Tell us what you run today, which Odoo apps you are considering and by when you need them. We ask about companies, users, data, localisation and integrations.

  2. Step 02

    Assessment

    Discovery workshops, a fit-gap list, and the version and hosting decision, with every proposed customisation given a business reason.

  3. Step 03

    Fixed written quote

    A written scope, a fixed quote and the plan for data migration, testing and hand-over, before any work starts.

  4. Step 04

    Sprints with weekly demos

    Configuration and custom modules in sprints on a staging database, demoed every week, with test migrations reconciled against your old system.

  5. Step 05

    Launch

    A planned cut-over after a full rehearsal, with the old system kept read-only until sign-off.

  6. Step 06

    Support

    Fixes, improvements and version upgrades on terms agreed in your written scope.

FIG 11 · What you get

Everything included

Written into your fixed quote, so you know exactly what you are paying for before work starts.

11items

  • Written scope and fixed quote
  • Process map and fit-gap list
  • Version and hosting decision, in writing
  • Configured Odoo database
  • Custom modules in your Git repository, with tests
  • Reconciled data migration and cut-over plan
  • Integrations with logging and error alerts
  • Reports and document layouts
  • Role-based training and how-to notes
  • Customisation register for future upgrades
  • Hand-over: modules, configuration and documentation are yours

FIG 12 · Tech & tools

The tools behind the work

Proven, well-supported tools, chosen for your project and set up in accounts your business owns.

  • Odoo 20
  • Odoo 19
  • Odoo 18
  • Odoo Community
  • Odoo Enterprise
  • Odoo Online
  • Odoo.sh
  • Odoo Studio
  • Python
  • PostgreSQL
  • OWL
  • XML-RPC
  • JSON-RPC
  • Docker
  • Git
  • Shopify

FIG 13 · Who it’s for

Odoo for manufacturers, distributors, retailers and service firms.

The same rules everywhere: standard first, version chosen up front, your database and your IP.

3 audiences

US teams

Odoo for growing US companies.

US projects run through our New York client partner, with engineering at our New Delhi HQ. Typical work: inventory and manufacturing on Odoo, with accounting, ecommerce and shipping integrations.

  • New York client partner
  • Inventory and manufacturing
  • Store and shipping links
  • Fixed written quote

FIG 14 · Working with us from the USA and UK

Built in New Delhi. Run on your hours.

Every project gets a point of contact in New York or London and an engineering team in New Delhi. Here is how today’s working days line up, live.

Three ways to work together

  1. 01

    Fixed-scope project

    A written scope, one fixed price and a dated plan. Suits websites, apps and MVPs.

  2. 02

    Dedicated team

    Designers and engineers on your roadmap every month, billed monthly.

  3. 03

    White label

    For US and UK agencies: our work, your brand, unbranded deliverables.

Every engagement

  • Fixed quote in USD, GBP or INR after a free 30-minute call
  • NDA before discovery. You own all code, designs and content
  • A working demo every sprint, not status slides
  • Reply within one business day, calls inside your hours
Book a call

Calls on ET or UK hours

FIG 15 · Hosting

Odoo Online vs Odoo.sh vs on-premise

Hosting decides your upgrade path. Odoo Online gets intermediate Online versions about every two months; Odoo says those are not released for Odoo.sh or on-premise, which get major versions only.

Odoo Online vs Odoo.sh vs on-premise
Odoo OnlineOdoo.shOn-premise
Who runs the serversOdooOdoo (cloud platform with Git-based staging)You or your host
Releases you getOnline versions about every two months, plus majorsMajor versions onlyMajor versions only
Custom Python modulesNo: Studio and standard appsYesYes
Odoo plan needed (read 23 Oct 2026)Any planCustom planCustom plan
Best forStandard processes, little custom codeCustom modules without running serversData that must stay on your own servers, or Community edition

FIG 16 · Partner tiers

About Odoo partner tiers: what they measure

Odoo ranks its partners mainly by how many new Enterprise users they sell each year and how many certified staff they have. That measures licence sales, not delivery quality. Elgrith holds none of these tiers; you can buy Enterprise subscriptions from Odoo or a partner and still hire us to build.

About Odoo partner tiers: what they measure
ReadySilverGold
New Enterprise users sold a year1075300
Certified staff136
Measures delivery quality?NoNoNo
Odoo’s cut of partner servicesNone: “Odoo will not take % from partner services”NoneNone

FIG 17 · Engage

Fixed-scope project vs dedicated Odoo developers vs team extension

We don’t publish rates. This is how the three ways to work with Odoo developers compare.

Fixed-scope project vs dedicated Odoo developers vs team extension
Fixed-scope projectDedicated specialistTeam extension
Best forA defined implementation, module or upgradeA steady backlog of changes, reports and integrationsA deadline, a migration wave or a backlog spike
Who manages the workUs, against a written scopeYou, in your sprintYou, with our lead
How it is pricedOne fixed quoteMonthly, per specialistMonthly, per team
Code, configuration and IPYoursYoursYours

FIG 18 · Compare

Odoo Community (LGPLv3) vs Enterprise

Odoo Community (LGPLv3) vs Enterprise
Odoo EnterpriseOdoo Community
LicenceOdoo Enterprise Edition License: needs a valid Enterprise subscriptionLGPL version 3 (open source)
AppsCommunity apps plus Enterprise-only apps such as StudioCore apps; community modules fill gaps
HostingOdoo Online, Odoo.sh or on-premiseOn-premise or your own cloud
UpgradesOdoo’s upgrade service is part of the subscriptionYou or your developer run them
Licence costPer-user subscription from Odoo (see odoo.com)No licence fee; you pay for hosting and development

FAQ

Frequently asked questions

Straight answers about Odoo Development with Elgrith.

It depends on how many apps and companies you go live with, how much data and history you migrate, the number of customisations and integrations, localisation needs and how quickly your team can test. After discovery you get a timeline in your fixed written quote.

Free 30-minute call

Plan your Odoo build for the next upgrade.

Tell us what you run today. After a free call you get a discovery plan, a written scope and a fixed quote for the implementation, modules and migration.

connect@elgrith.com+91 96039 20001Start a project

Pick a day for your call

Open

Pick a day. You'll choose a time in your own time zone on the next step.

See all times