What an Odoo implementation costs in France

2 payment rails have no Odoo connector we would put in production

Each one is an API build with its own tests: authorization, capture, refund and a deliberate failure in sandbox, repeated once in production with a small live amount, then settlement mapped to the ledger so the bank reconciliation clears. Price them one at a time. This is where a checkout budget doubles quietly.

• Lyra. French PSP for online and point of sale payments that hosts merchant and cardholder data on servers in France, which matters to French buyers with data residency clauses. Its platform sits behind a number of French bank branded checkout products.
• Monext (Payline). French payment services provider handling Carte Bancaire, Visa, Mastercard, Apple Pay and PayPal for French merchants, plus card issuing. Widely used in French travel, events and retail.

4 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.

1 carrier has 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.

• Boxtal. French shipping broker with around 30,000 active clients that resells pre negotiated rates across French carriers. Smaller French merchants use it because they cannot sign their own Colissimo or DPD contract yet.

10 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.

6 items Odoo does not cover for France

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.

• 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.
• Anything beyond the VAT report: liasse fiscale, CVAE, and OGA-specific exports.

13 statutory items to configure, test and hand over

Tax, accounting and payroll items on our own France 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 France 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.

12 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.

• 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).

13 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.