What an Odoo implementation costs in United States

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.

• Sezzle. US pay in four provider offering Pay in 4, Pay in 5 and monthly plans, plus a Sezzle Anywhere virtual card. The only Odoo module on the store stops at 14.0, so Odoo 19 needs a build or a route through an acquirer that already carries it.
• FedNow Service. The Federal Reserve's instant payment service, live and used by US banks for round the clock account to account settlement. It shows up in US B2B collections rather than at web checkout, so in Odoo it lands as a bank transfer you reconcile.

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

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

5 items Odoo does not cover for United States

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.

• Sales tax without AvaTax. Odoo's native tax engine will not track economic nexus, jurisdiction boundaries or product taxability across 45 states with local add-ons. The decision is buy AvaTax or accept manual rate maintenance, and it should be made before the project starts, not during UAT.
• Nexus monitoring. Nothing in Odoo tells you that you crossed a state's threshold, and thresholds keep moving as states drop the 200-transaction test. That is a reporting build or a subscription to a nexus service.
• Sales tax return filing. Odoo prepares data; the return goes through Avalara or a filing service.
• Payroll tax filing and deposits. Odoo produces payslips and journal entries. Forms 941, 940, W-2 and W-3, EFTPS deposits, state withholding registrations and SUTA are not in the box. Most US Odoo clients keep ADP, Gusto or Paychex and use l10n_us_hr_payroll_account for the postings.
• Federal government invoicing. There is no IPP connector and no DBNAlliance connector in Odoo, and Odoo's Peppol support does not list the United States as an eligible country. Federal vendors submit into IPP separately.

14 statutory items to configure, test and hand over

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

19 open questions in our own United States 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.

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

• GAAP-oriented chart of accounts across Receivable, Payable, Equity, Assets, Liability, Income and Expenses, plus US financial statement reports (l10n_us, l10n_us_reports).
• Check printing on the three common pre-printed positions, top, middle and bottom (l10n_us_check_printing). Still a live requirement for a lot of US AP.
• NACHA file export so vendor and payroll payments can be uploaded to the bank (l10n_us_payment_nacha).
• 1099 data prepared for e-filing through a third party (l10n_us_1099).
• Avalara AvaTax for sales tax rate lookup, jurisdiction assignment and product taxability (account_avatax). This is the practical answer to 45 state regimes plus local add-ons.
• US payroll rules, contracts, allowances, deductions and payslips, with an ADP work-entry export (l10n_us_hr_payroll, l10n_us_hr_payroll_adp).

Payroll starts from a localization rather than a blank page

A payroll localization module is in the list above, so the structure exists and the work is configuration, employee data quality and a parallel run. Bad master data, not missing code, is what slips a payroll go-live.

• NACHA file export so vendor and payroll payments can be uploaded to the bank (l10n_us_payment_nacha).
• US payroll rules, contracts, allowances, deductions and payslips, with an ADP work-entry export (l10n_us_hr_payroll, l10n_us_hr_payroll_adp).

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.

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

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.

• Nothing for domestic B2B. Adoption is market-driven, not government-mandated, because the US has no VAT and no transaction-level tax reporting requirement.
• There is no US federal or nationwide B2B e-invoicing mandate as of 22 August 2026, and no VAT to drive one. The only compulsory piece is federal procurement: OMB M-15-19 directed agencies to move to electronic invoicing by the end of FY 2018, and many now require vendors to bill through Treasury's IPP.