Odoo Customization Services in France
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 France
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.
France runs Facturation electronique (mandatory B2B e-invoicing and e-reporting reform). That is configuration and testing work inside the build, not an afterthought, and it is the item most often left out of a quote.
6 of the 19 payment options that matter in France are not shipped with Odoo, so they need a paid connector or a build. 13 ship in the box.
11 of the 15 couriers used in France have no Odoo connector. 4 do. Which ones you actually use changes the estimate more than the number of users does.
Odoo's France 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 France 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 France starts from
France has 6 native localization items in Odoo and 6 documented gaps beyond them. Customization work here usually starts at that gap list, not from a blank module.
Where we deliver in France
Customization does not change shape by city. The brief is written the same way for a team in Paris as for one in Nantes: what the process actually is today, and where Odoo's default flow does not match it. Paris, Lyon, Marseille, Toulouse, Lille, Bordeaux and Nantes, and รle-de-France, Auvergne-Rhรดne-Alpes, Occitanie and Hauts-de-France, are covered.
What odoo customization has to satisfy in France
The rules that decide how much of this is configuration and how much is a build. Everything below is from our France register, checked against a primary source.
Live from 1 September 2026. Every business subject to French VAT must be able to receive e-invoices from that date, and large companies and ETIs must also issue them and file e-reporting; PME, TPE and micro-enterprises follow on 1 September 2027.
- Invoices must be issued, transmitted and received through a Plateforme Agreee (PA, formerly called PDP), a private operator registered by the DGFiP for three renewable years. Article 289 bis of the Code general des impots. The list of registered platforms is published on impots.gouv.fr.
- The chosen PA passes the invoice data to the tax administration (article 289 E CGI). This is continuous transaction control by reporting through an accredited intermediary, not per-invoice clearance where the tax authority validates an invoice before it is legally valid.
- The public portal (PPF) no longer acts as a free exchange platform. Article 123 of the loi de finances pour 2026 formalised the simplification announced in August 2025, leaving the private platforms at the centre of the flow.
- A central annuaire (directory) routes invoices to the recipient's platform. It is made available to the PAs and holds the addressing data. SIREN, SIRET and recipient establishment on the customer record are what make routing work.
- Structured format built on the EN 16931 semantic model. DGFiP external specifications version 3.2 dated 30 April 2026, backed by AFNOR norms XP Z12-012 (invoice and lifecycle status formats and profiles), XP Z12-013 (APIs between business systems and approved platforms) and XP Z12-014 (B2B use cases). The three accepted syntaxes are Factur-X (hybrid PDF plus XML), UBL and CII.
- Accounting The Plan Comptable General is set by the Autorite des normes comptables (ANC), the French accounting standard setter. The base text is reglement ANC 2014-03, amended since, most recently by reglement ANC 2026-04 of 4 May 2026 on accounting for corporate income taxes and related contributions.
- Accounting The reformed PCG from reglement ANC 2022-06 applies to financial years opened from 1 January 2025. Reported effects include cutting the account list from around 2,000 to around 1,600, a narrower definition of exceptional result, and removal of the transfer-of-charges accounts 791, 796 and 797. Secondary sources only; read the reglement text before quoting the numbers.
- Accounting The Fichier des Ecritures Comptables (FEC) must be handed to the tax administration on a tax audit by any taxpayer keeping computerised accounts. Article L47 A-I of the Livre des procedures fiscales sets the obligation; article A47 A-1 sets the format. XML is accepted and the DGFiP publishes XSD schemas (A47A-I-VII-1, A47A-I-VIII-3, A47A-I-VIII-5, A47A-I-VIII-7) to validate against.
- Accounting Odoo ships FEC import (l10n_fr_fec_import) for loading history. FEC export is not in the standard France localization; the OCA module l10n_fr_fec_oca covers it.
- Payroll The Declaration sociale nominative (DSN) is the single monthly electronic filing built from payroll data. It goes through net-entreprises.fr, which is the deposit point, and it replaced the separate social declarations for private-sector employers.
- Payroll The DSN deadline splits by headcount: the 5th of the month following the pay period for employers with 50 or more employees, the 15th for employers under 50. Widely stated by secondary sources; confirm against URSSAF before quoting it to a client.
- Payroll Odoo has no documented French payroll localization. France does not appear on Odoo's list of payroll localization countries, which covers Australia, Belgium, Egypt, Hong Kong, India, Jordan, Kenya, Mexico, Saudi Arabia, Turkiye, UAE and the United States. Odoo ships l10n_fr_hr_payroll_account, which supplies the accounting side of French payroll rules only.
- Chart of accounts, fiscal positions and tax configuration for companies based in mainland France (l10n_fr_account). The module is scoped to mainland France, so overseas departments need separate handling.
- French VAT report export that can be sent to the DGFiP, an OGA or an accountant (l10n_fr_reports).
- POS anti-fraud certification under CGI article 286 I-3 bis (l10n_fr_pos_cert).
- Mandatory e-invoicing. Odoo completed the DGFiP registration and is an approved platform, and ships l10n_fr_pdp to send and receive through it, plus l10n_fr_pdp_pos for POS e-reporting. Activation is in Accounting or Invoicing, Configuration, Settings, French Electronic Invoicing.
- Factur-X and UBL generation, and Chorus Pro submission for public-sector customers (l10n_fr_facturx_chorus_pro).
- FEC import for loading opening balances and prior-year history (l10n_fr_fec_import).
- French payroll. France is not on Odoo's payroll localization list and l10n_fr_hr_payroll_account only carries the accounting postings. DSN generation, URSSAF contribution logic, conventions collectives and the bulletin de paie layout are not in the box. Budget for a separate payroll tool plus an interface, not an Odoo payroll build.
- Partner and product master data for the four new mandatory invoice mentions. Buyer SIREN on every B2B partner, delivery address when it differs, and operation nature per line. This is a data cleanup project across the customer master, and it is where go-lives slip.
- Annuaire routing. Wrong or stale SIREN and SIRET on customer records is the main cause of invoices that never reach the recipient's platform. Build validation and a monitoring view for undelivered invoices and returned lifecycle statuses before go-live.
- Lifecycle status handling. The platform sends statuses back and the business has to act on rejections. Standard Odoo screens will usually need extending into a proper exception queue.
- FEC export, CA3 and CA12 filing forms, and DAS2 all sit in OCA modules rather than the standard localization, so a Community or Enterprise stack needs those pulled in and version-matched.
Reviewed 2026-08-22. The full France 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 France?
- Yes. Odoo ships 6 native items for France, covering the basics of the chart of accounts and statutory setup. 6 areas are still outside that localization and get built or bought separately.
- Is e-invoicing mandatory in France?
- Live from 1 September 2026. Every business subject to French VAT must be able to receive e-invoices from that date, and large companies and ETIs must also issue them and file e-reporting; PME, TPE and micro-enterprises follow on 1 September 2027. The France e-invoicing page carries the full detail and the sources.
- What VAT or sales tax does Odoo have to handle in France?
- The standard TVA rate is 20 percent. Reduced rates of 10 percent, 5.5 percent and 2.1 percent apply only to categories expressly listed in the Code general des impots. Guadeloupe, Martinique and La Reunion run a separate 8.5 percent standard rate.
- Do you work with businesses in Paris and other parts of France?
- Yes. Odoo customization runs remotely by default, and being based in one city inside France does not change the plan or the price. Cities we cover for on-site visits: Paris, Lyon, Marseille, Toulouse, Lille, Bordeaux, Nantes. Regions we cover: รle-de-France, Auvergne-Rhรดne-Alpes, Occitanie, Hauts-de-France. We travel on-site for discovery workshops and go-live week when the engagement calls for it.