How to choose an Odoo integrator for your UK business

Odoo is an open, modular ERP that a business can, in principle, set up on its own. In practice, a project touching accounting, stock, sales and payroll rarely goes well without an experienced Odoo integrator. The software is the same whoever configures it; the result is not. A good partner designs processes that fit how you trade, migrates your data cleanly and stays around once the system is live. A poor one leaves you with an expensive, half-configured database.

This page explains how Odoo's partner programme works, which criteria matter when you choose an Odoo partner, what to ask in meetings, which warning signs to take seriously, and how to read competing quotes.

Odoo integrator, partner, consultant, expert: what are you actually hiring?

The vocabulary is loose, so start by being clear about it.

• Odoo partner: a company registered in the publisher's partner programme. It resells subscriptions, implements, trains and supports.
• Odoo integrator: a partner (or occasionally an independent firm) whose main business is delivering implementation projects.
• Odoo consultant or Odoo expert: usually a person, either employed by a partner or working freelance, who analyses requirements and configures the system.

When you assess a firm, you are really assessing the people who will be assigned to your project. A well-known name means little if your project is staffed by someone who joined last month. Ask who the project lead will be, who configures, who develops, and who answers the phone after go-live.

We are not affiliated with Odoo or with any integrator, so nothing below is a sales pitch for a particular firm. Our role is to introduce you to an integrator suited to your project, free of charge. How that works is described on how our introduction service works.

How the Odoo partner programme is structured

According to the publisher's partner registration page, the programme has a learning status (Learning, 590 €/year) and three official levels: Ready, Silver and Gold (2,950 €/year for Gold). To remain a partner, a firm has to meet annual requirements:

Partners earn up to 20 % commission on Enterprise sales and a commission on Odoo.sh hosting (up to 150 €/month). They must obtain Odoo certification, train their own staff and provide first-line support.

Three things follow from this.

1. The tier measures volume and certified headcount, not fit. A Gold partner has sold many users and kept most of its customers; that is reassuring, but it says nothing about your sector.
2. Retention is a useful signal. Silver and Gold levels require a share of customers to stay. A firm that loses its clients does not keep its level.
3. Partners have a commercial interest in subscriptions. That is normal, but it means you should ask how they would size your user count and edition. Our Odoo pricing guide explains how subscriptions are counted: only users with back-end access are paid users, while customer and supplier portal users are not.

What the UK directory shows

The publisher's directory for the United Kingdom lists 37 implementation partners: 5 Gold, 6 Silver and 26 Ready. Each profile gives a success rate, typical medium and large project sizes in number of users, the number of customer references, the sectors served and the number of certified experts per version. The directory can be filtered by sector (23 categories, from agriculture to wholesale and retail), by company size and by country.

Treat these figures as a starting point. Success rates and reference counts are declared, and you should ask the firm to substantiate them with conversations, not only with a profile page.

The criteria that really matter

1. Experience in your sector

A manufacturer needs bills of materials, routings and shop-floor tracking. A wholesaler needs pricing rules, drop-shipping and credit control. A professional services firm needs time sheets, project billing and revenue recognition. An integrator who has done your kind of business before will ask better questions in the first meeting and avoid expensive detours. Look at the Odoo industries page to see what your sector typically needs, then ask the candidate to walk you through a comparable project.

2. Command of UK obligations

Odoo is built abroad; a UK implementation needs local competence. Ask specifically about:

• VAT returns and how they connect to HMRC under Making Tax Digital (see our guide to Making Tax Digital and your ERP);
• the chart of accounts and reporting your accountant expects;
• payroll and Real Time Information submissions, which are often handled in a dedicated payroll product rather than inside the ERP;
• bank feeds, direct debit and the way your accountant will access the books.

Our page on Odoo in the UK sets out how the local layer fits together. If a candidate answers these points vaguely or says "we will look into it", that tells you where the risk sits.

3. Team size and depth

A small team can be excellent, but ask what happens when the lead consultant is ill or leaves. Look for a mix of functional consultants (who configure) and developers (who customise), with a named project manager. Check how many people hold current certification for the version you will run; the directory shows certified experts by version. If you plan to rely on custom code, see what we say about Odoo customisation before you accept a quote that leans on it.

4. Method

Ask the integrator to describe its method in concrete steps: discovery, scoping, configuration, data migration, testing, training, go-live and aftercare. The publisher itself promotes a "Quickstart" approach that splits a project into short stages with a defined scope, objectives and results, so that a business reaches production quickly. Whether or not your integrator uses that label, you want a phased plan with deliverables you can check at each stage, not a vague promise to "get started and see". Our overview of Odoo implementation shows what a sensible sequence looks like.

5. Support after go-live

Most problems appear in the first weeks of live use, not during the project. Ask for the support model in writing: who answers, how, during which hours, how issues are prioritised and what is included in a monthly fee versus billed separately. See Odoo support and maintenance for what a sound arrangement covers, including version upgrades.

6. Proximity and working style

Remote delivery works well for many Odoo projects, but workshops with finance, warehouse and sales are better held in person, at least at the start. Publisher Success Packs, for instance, bill on-site travel separately, and your integrator may do the same. If you want a team within reach of your premises, our regional pages list integrators by area of the UK, from London to Scotland, Wales and Northern Ireland.

Questions to ask in the first meetings

Prepare these and note the answers; they separate firms that have done this many times from those that are improvising.

About the firm

• Which partner level do you hold, and how many certified consultants do you have on the version I would use?
• Who exactly would work on my project, and will they be there from start to finish?
• Can I speak to two customers of a similar size and sector, one of whom went live more than a year ago?

About the project

• What would you need from me before giving a firm scope?
• How do you handle data migration from my current system, and who is responsible for cleaning the data?
• Which parts of my requirements would be standard and which would need development?
• How will you test the system before go-live, and who signs it off?

About the commercial terms

• Is the price fixed, capped or time and materials?
• What is excluded, and how are changes to scope priced?
• Who holds the subscription, and who owns the database and custom code if we part ways?

About the future

• How do you handle upgrades between Odoo versions? Our Odoo versions and editions page explains why this matters.
• What does support cost after go-live, and what is the response commitment?

Warning signs

Be cautious when you see any of the following.

• A fixed price before any discovery. Without analysis, either the price is padded or the scope will be cut later.
• Everything is "standard". Almost every business has a process that does not fit out of the box. An integrator who never mentions gaps has not listened.
• No references you can call, or only references from unrelated sectors.
• Heavy reliance on custom development for things Odoo already does through configuration.
• Vague answers on VAT, Making Tax Digital or payroll.
• One person holds all the knowledge. If that person leaves, so does your project.
• No written support terms, or support that depends on the goodwill of the consultant.
• Pressure to sign quickly with a discount that expires this week.
• Data migration treated as an afterthought. It is often where projects slip.

If you are already part-way through a project that shows several of these signs, an independent review may help before you commit more budget: see Odoo audit and project rescue.

Comparing Odoo quotes fairly

Two quotes for "an Odoo implementation" can differ widely because they do not describe the same thing. Before comparing totals, line them up.

Some points specific to Odoo are worth knowing. The publisher's own Success Packs, sold as bundles of consulting hours, were shown in euros from Starter at 499 € to Pro at 16,830 €, covering from 4 to 200 hours of consulting. A pack includes a dedicated consultant, a project manager, configuration, training and key-user support, data import help and phone and email support, with on-site travel billed separately. The publisher claims a 98 % implementation success rate with a Success Pack against 65 % without, and that 80 % of projects of that scope go live in 200 hours or fewer; these are the publisher's own figures, not an independent measurement. Use them as a reference for how an engagement can be structured, not as a promise.

Also note that subscription costs are separate from implementation costs. Odoo Standard and Custom are priced per user per month, and Custom adds Studio, multi-company and external API access. Make sure each quote states which subscription it assumes, so you are not comparing one firm's licence-inclusive price with another's services-only price. Our Odoo pricing page breaks this down.

How to shortlist without wasting months

A practical sequence for a small or mid-sized business:

1. Write a short requirements note. Processes, volumes, the systems you have today, the people who will use the system. A page or two is enough to begin. Our guide on choosing an ERP integrator gives a wider framework that applies beyond Odoo.
2. Identify a handful of candidates using the publisher's UK directory, your accountant's recommendation, and peers in your sector.
3. Hold an initial call with each using the questions above and compare how well they listen.
4. Ask for a short paid discovery from your preferred one or two, so you compare scoped proposals rather than guesses.
5. Take references, then decide on method and people as much as on price.

If you would rather not do the legwork yourself, our service introduces you to an integrator suited to your sector, size and region, at no cost to you. You describe your project; we present a firm that fits it. The integrator then delivers the work under its own contract with you.

Choosing a partner for a specific situation

• Replacing an existing system or spreadsheets. Prioritise data migration experience. See Odoo migration.
• Multi-site or multi-company groups. Ask about consolidation, inter-company flows and access control.
• Manufacturing. Insist on shop-floor references; planning logic is where weaker integrators struggle.
• Small team, limited budget. A smaller partner with a tight, phased scope is often a better fit than a large firm with overhead; start with the essential applications and add more later.

Before you sign

Check that the contract names the project lead, defines the deliverables and acceptance criteria, sets out how scope changes are agreed, states what support covers and confirms you keep access to your own data and database. A good integrator will not object to any of this. If an integrator resists clarity, that is the answer to your question.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.