Odoo Customization Services in Germany
Custom code is a liability you agree to carry. We keep it small, keep it in its own module, and write it so the next upgrade does not eat it.
What changes the cost of Odoo customization in Germany
The delivery method is the same everywhere. What moves the number is what this market demands of the system, and how much of that Odoo already covers.
Germany runs E-Rechnung. That is configuration and testing work inside the build, not an afterthought, and it is the item most often left out of a quote.
7 of the 19 payment options that matter in Germany are not shipped with Odoo, so they need a paid connector or a build. 12 ship in the box.
10 of the 14 couriers used in Germany have no Odoo connector. 4 do. Which ones you actually use changes the estimate more than the number of users does.
Odoo's Germany localization does not cover everything. The gaps are listed on the country page and each one is either a build or a bought module.
Statutory payroll in Germany has its own rules. Whether Odoo ships a payroll localization for this market decides if that is configuration or development.
Market facts on this page checked on 22 August 2026 by Waqas Riasat, Way4Tech.
Where Germany starts from
Germany has 6 native localization items in Odoo and 4 documented gaps beyond them. Customization work here usually starts at that gap list, not from a blank module.
Where we deliver in Germany
Customization does not change shape by city. The brief is written the same way for a team in Berlin as for one in Dรผsseldorf: what the process actually is today, and where Odoo's default flow does not match it. Berlin, Munich, Frankfurt, Hamburg, Cologne, Stuttgart and Dรผsseldorf, and Bavaria, North Rhine-Westphalia, Baden-Wรผrttemberg and Hesse, are covered.
What odoo customization has to satisfy in Germany
The rules that decide how much of this is configuration and how much is a build. Everything below is from our Germany register, checked against a primary source.
Every German business has had to be able to receive structured e-invoices since 1 January 2025. Issuing is still in transition: 2026 is the last full year in which paper or PDF is allowed with the buyer's agreement.
- A structured electronic format that is issued, sent and received electronically and meets the European standard under Directive 2014/55/EU. XRechnung (pure XML) and ZUGFeRD (PDF with embedded XML) both qualify. Parties may also agree another format if the required data can be extracted correctly and interoperably.
- Post-audit, not clearance. There is no government platform and no real-time reporting for B2B. Transmission is free choice, for example email or Peppol.
- Transition under section 27 UStG: paper and other electronic formats stay allowed with the recipient's consent for supplies up to 31 December 2026, and up to 31 December 2027 if the issuer's total turnover in the previous calendar year was 800,000 euro or less. Legacy EDI that does not meet the standard also runs to 31 December 2027.
- Invoices must be kept for 8 years under section 14b UStG.
- Federal B2G: XRechnung as the standard, the Leitweg-ID as a mandatory field carried in the buyer reference, plus bank details, payment terms and an email or De-Mail address, submitted through the federal portal after registering a user account. Direct contracts up to 1,000 euro are exempt.
- Accounting E-Bilanz under section 5b EStG: the balance sheet and the profit and loss account, including uncondensed account listings and the fixed asset schedule, must be transmitted to the tax authority electronically in the officially prescribed dataset. Exemption is only possible on hardship grounds.
- Accounting Invoices issued and received must be kept for 8 years, counted from the end of the calendar year in which the invoice was issued (section 14b UStG).
- Accounting German bookkeeping runs on the DATEV charts SKR03 and SKR04. Odoo supports both, installs SKR03 by default, and only lets you switch package before the first accounting entry exists.
- Accounting Odoo's German package ships the DATEV export in two parts, DATEV ATCH for documents and DATEV DATA for journal entries, which is how the books reach the Steuerberater. It also ships the Balance Sheet, Profit and Loss, Umsatzsteuervoranmeldung tax report, EC Sales List and Intrastat.
- Payroll 2026 social insurance contribution rates: pension 18.6%, unemployment 2.6%, health 14.6% general rate plus the fund's own supplementary rate, long-term care 3.6%. Each is split evenly between employer and employee. Employees without children pay an extra 0.6% on care insurance, giving 4.2%. As an example of the supplementary rate, TK charges 2.69% in 2026, shared 1.345% each side.
- Payroll 2026 contribution ceilings (Sozialversicherungsrechengroessen-Verordnung 2026): general pension insurance 8,450 euro a month or 101,400 euro a year; miners' pension insurance 10,400 euro a month or 124,800 euro a year; health insurance earnings limits of 77,400 euro a year and 69,750 euro a year (5,812.50 a month); Bezugsgroesse 3,955 euro a month or 47,460 euro a year.
- SKR03 and SKR04 charts of accounts, SKR03 by default
- Balance Sheet, Profit and Loss, Umsatzsteuervoranmeldung tax report, EC Sales List and Intrastat
- DATEV export for the tax adviser, split into documents and journal entries
- GoBD traceability: creator, creation date, modification date and modifying user on every record
- Point of sale technical security system and DSFinV-K export
- XRechnung CIUS and Peppol BIS Billing 3.0 among the standard e-invoicing formats, with Odoo acting as its own Peppol access point and SMP and Germany on the eligible list
- ELSTER filing. Odoo produces the Umsatzsteuervoranmeldung report but does not transmit it to ELSTER. Third-party export modules exist.
- Leitweg-ID for federal B2G invoices. Handled by a third-party module rather than the standard localization.
- E-Bilanz under section 5b EStG. Not in Odoo. It stays with the tax adviser's software.
- ZUGFeRD profile coverage and inbound reading of supplier e-invoices into vendor bills. Confirm per project rather than assuming.
Reviewed 2026-08-22. The full Germany register
How we run the work
5 stages, the same in every market: Requirement capture, Technical specification and estimate, Build in sprints, Test and review, Deploy and hand over. The method does not change by country, so it is written up once rather than repeated here.
The integrations this market usually needs
Badged by what it takes in Odoo. Anything not marked In Odoo is a paid connector or a build, and that is the part quotes usually miss.
Questions we get asked
- Will customisation break our next Odoo upgrade?
- Well-written custom modules do not break, they need porting, and the effort depends on how deeply they reach into standard behaviour. Code that extends existing models ports quickly. Code that replaces standard logic is expensive at every version. That is the single biggest reason we push back on requests that duplicate what Odoo already does.
- Do we own the code?
- Yes. Source goes to your repository with the commit history intact, plus build and deploy instructions. There is no licence key, no time bomb and no obfuscation. If you replace us, the next team can read what we wrote.
- Does Odoo have an official localization for Germany?
- Yes. Odoo ships 6 native items for Germany, covering the basics of the chart of accounts and statutory setup. 4 areas are still outside that localization and get built or bought separately.
- Is e-invoicing mandatory in Germany?
- Every German business has had to be able to receive structured e-invoices since 1 January 2025. Issuing is still in transition: 2026 is the last full year in which paper or PDF is allowed with the buyer's agreement. The Germany e-invoicing page carries the full detail and the sources.
- What VAT or sales tax does Odoo have to handle in Germany?
- The standard VAT rate is 19% and the reduced rate is 7% (section 12 UStG). A 0% rate applies to certain solar installations.
- Do you work with businesses in Berlin and other parts of Germany?
- Yes. Odoo customization runs remotely by default, and being based in one city inside Germany does not change the plan or the price. Cities we cover for on-site visits: Berlin, Munich, Frankfurt, Hamburg, Cologne, Stuttgart, Dรผsseldorf. Regions we cover: Bavaria, North Rhine-Westphalia, Baden-Wรผrttemberg, Hesse. We travel on-site for discovery workshops and go-live week when the engagement calls for it.