What an Odoo implementation costs in United Kingdom

3 payment rails need a paid connector

The connector licence sits outside our fee and is quoted separately by whoever sells it. Our side is configuration, the four-test cycle per provider, and the reconciliation mapping. Budget for keeping each one current across Odoo upgrades, because a connector that stops at your next version is a cost you meet later.

3 carriers have no Odoo connector

Rating, label printing, tracking and cash on delivery reconciliation are four separate pieces of work with four separate failure modes, and we quote them separately. Carrier test credentials rarely carry your negotiated rates, so the account and the rate card get validated before the connector is written.

• DX. DX runs over 110 depots across the UK and Ireland and specialises in irregular dimension and weight freight, secure document exchange and same day courier work that parcel carriers refuse. The apps store returned zero Odoo 19 modules for DX, so this one is a custom build against their API.
• Whistl and Parcelhub. Whistl handles high volume UK business mail as a Royal Mail alternative and runs parcels through its Parcelhub brand. The apps store returned zero Odoo 19 modules for either name, so integration is a custom build.
• InPost UK. Runs the UK locker estate and, since absorbing Yodel in July 2026, the former Yodel home delivery network too. That makes it one of the largest UK parcel carriers. No native Odoo connector, so it is reached through an aggregator or a build.

7 carriers sit behind a paid connector

Cheaper than a build and not free. The licence is quoted separately, and our work is the account setup, the rate check against your contract, and the label and tracking test on real shipments.

Payroll is built here, not switched on

No payroll localization module appears in our United Kingdom module list, so every contribution, ceiling, deduction and statutory file becomes a salary rule, a bank file or a report that we write and test. Add at least one parallel run against your current system, reconciled line by line, before anyone switches.

• UK payroll. Odoo ships no official UK payroll localization: the payroll localizations documented for v19 are Australia, Belgium, Egypt, Hong Kong, India, Jordan, Kenya, Mexico, Saudi Arabia, Turkiye, UAE and the US. The documented UK route is the Employment Hero Payroll integration. RTI submissions, auto-enrolment assessment and statutory payments are not in the standard product.

3 items Odoo does not cover for United Kingdom

This is the honest part of a quote. Each line below is scoped, priced and agreed as a build before the project starts, rather than discovered halfway through and raised as a change request.

• iXBRL statutory accounts. Odoo does not tag accounts for HMRC or Companies House. That stays with the accountant's software, which matters more now that HMRC's free filing service closed on 31 March 2026 and Companies House goes software-only in April 2028.
• Multi-company HMRC submissions. Only one company and one user can be connected to HMRC at a time, so group filings have to be run in sequence.
• The 2029 e-invoicing build cannot be scoped yet. Peppol is confirmed as the network but the format, phasing and legacy EDI treatment come with the Budget 2026 roadmap.

15 statutory items to configure, test and hand over

Tax, accounting and payroll items on our own United Kingdom list. Each one becomes a configuration, a test document and a number your accountant checks independently before sign-off. Individually cheap, collectively the reason a localization is a work package rather than a setting.

18 open questions in our own United Kingdom notes

Where our research did not reach a primary source, we mark it open rather than pricing a guess. Those questions get closed in discovery against your entity, your documents and your advisor, which is exactly why a fixed price comes after discovery and not before it.

5 official Odoo modules cover part of this market

Configuration and testing, not development. Anything on this list is install, configure and verify work that sits inside the tier price rather than beside it.

What you get without a build

Printed as checked. Where a requirement is met by something below, the work is proving it against your documents, not writing it.

• CT600-ready chart of accounts and a VAT100-ready tax structure
• UK accounting reports and VAT return submission to HMRC through the MTD VAT API
• Bacs files for paying suppliers and collecting from customers
• CIS monthly returns to HMRC and CIS deduction reporting
• Peppol exchange: Odoo runs its own access point and SMP, and the UK is on Odoo's list of countries eligible for Peppol registration

11 payment providers ship with Odoo

Configured before anyone buys anything. Starting from what already ships is the cheapest checkout you can have, and it keeps the number of things that break after an upgrade down.

4 carriers ship with Odoo

Rating, labels and tracking without a connector purchase or an API build. If your volume can move to one of these, that is a real saving on build and on support.

3 items have a community module

Install and test rather than build, then budget a little for keeping it current across upgrades. Cheaper than a build, and not free.

No live authority integration to build here, on this evidence

Where documents are exchanged or filed rather than cleared in the moment, e-invoicing is a format and archive job instead of a live integration, which is the cheaper end of this work. It also moves. Schemes get mandated with lead time, so we get the invoice data right now rather than retrofitting it under a deadline later.

• No B2B e-invoicing mandate is in force. Public-sector obligations already exist: UK contracting authorities must be able to receive and process EN 16931-compliant e-invoices, and NHS England requires Peppol.
• Businesses are not obliged to issue e-invoices to each other. If you sell to the public sector, your buyer is already required to be able to receive a compliant e-invoice, so Peppol capability is a practical requirement on B2G contracts.