Odoo Integration Services in the USA
Integrations are easy to demonstrate and hard to run. The work is not the connection, it is what happens on the day one side is down.
What changes the cost of an Odoo integration in United States
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.
United States has no e-invoicing mandate to clear today. That lowers the build cost now, and it makes the invoicing design worth getting right anyway, because every market on this list that has since mandated one gave businesses months rather than years to comply.
7 of the 20 payment options that matter in United States are not shipped with Odoo, so they need a paid connector or a build. 13 ship in the box.
8 of the 13 couriers used in United States have no Odoo connector. 5 do. Which ones you actually use changes the estimate more than the number of users does.
Odoo's United States 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 United States 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 United States starts from
United States runs 6 native Odoo localization items and 5 custom ones. Integrations here sit on top of whichever of those already exists, which is a different job to building on a market with no localization at all.
Where we deliver in the United States
An integration depends on which systems sit on the other end, not on which city the business sits in. New York, Los Angeles, Chicago, Houston, Miami, Dallas, Atlanta, San Francisco and Seattle, and businesses across California, Texas, Florida, Illinois, Georgia and Washington, are covered on the same terms.
What odoo integration has to satisfy in United States
The rules that decide how much of this is configuration and how much is a build. Everything below is from our United States register, checked against a primary source.
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.
- Nothing for domestic B2B. Adoption is market-driven, not government-mandated, because the US has no VAT and no transaction-level tax reporting requirement.
- OMB M-15-19 directed agencies, by the end of FY 2018, to transition to electronic invoicing for appropriate federal procurements by one of three routes: migrating to a designated Federal Shared Service Provider and adopting its e-invoicing solution, using an OMB-approved e-invoicing solution, or ceasing investment in new e-invoicing solutions.
- The same memo defines electronic invoicing as payment requests managed as structured data elements exchanged through electronic workflow, with minimal manual interaction, and directs solution providers to integrate with the Integrated Award Environment including SAM, and to expose web services or APIs.
- In practice, a federal vendor keys or uploads invoices into IPP and matches on its SAM registration. There is no Odoo connector for this, so it is a parallel manual step.
- DBNAlliance runs a Peppol-style four-corner exchange network for B2B e-invoices and e-documents. Joining is an onboarding process, and it recently launched a mass adoption API. Treat it as a customer-driven requirement (a large buyer asks for it) rather than a legal one.
- Tax There is no federal sales tax and no VAT. Forty-five states levy a state-level sales tax; Alaska, Delaware, Montana, New Hampshire and Oregon do not. California has the highest state-level rate at 7.25 percent. Thirty-eight states allow local sales taxes on top, including Alaska which has no statewide tax, and local rates can rival or exceed state rates.
- Tax Sales tax registration is driven by economic nexus after South Dakota v. Wayfair. The most common test is 100,000 dollars in sales or 200 separate transactions in the current or previous calendar year, but six different threshold patterns exist across states, including 250,000 and 500,000 dollar variants with different measurement periods.
- Tax States are dropping the 200-transaction test. As of 1 August 2026, 17 states had eliminated it, including Illinois effective 1 January 2026 and Kentucky effective 1 August 2026. Any nexus logic hard-coded in an ERP needs a review schedule, not a one-time setup.
- Tax Form 1099-K: the One Big Beautiful Bill retroactively reinstated the pre-American Rescue Plan threshold. Third party settlement organisations are not required to file unless gross reportable payments to a payee exceed 20,000 dollars and the number of transactions exceeds 200.
- Tax Forms 1099-NEC and 1099-MISC: the reporting threshold rises from 600 dollars to 2,000 dollars, effective for tax year 2026, and will be inflation-adjusted from 2027. This changes which vendors an ERP has to flag.
- Tax Filers of 10 or more information returns in a calendar year must file them electronically.
- 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).
- 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.
Reviewed 2026-08-22. The full United States register
How we run the work
5 stages, the same in every market: Data flow mapping, Interface and access setup, Build with failure handling, Testing the unhappy paths, Go-live and reconciliation. 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
- How long does a typical integration take?
- A single well-documented flow with sandbox access on both sides is a short piece of work. What extends it is nearly always outside the code: waiting for credentials, discovering the other API is undocumented in the area you need, or finding that nobody has decided which system owns the customer record.
- Can you integrate a system that has no API?
- Often, through file exchange, database access or scheduled exports, and the result works. It is less immediate and needs stricter reconciliation because there is no acknowledgement to rely on. We would rather do that properly than pretend a scraped interface is an integration.
- Does Odoo have an official localization for United States?
- Yes. Odoo ships 6 native items for United States, covering the basics of the chart of accounts and statutory setup. 5 areas are still outside that localization and get built or bought separately.
- Is e-invoicing mandatory in the United States?
- 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. The United States e-invoicing page carries the full detail and the sources.
- What VAT or sales tax does Odoo have to handle in the United States?
- There is no federal sales tax and no VAT. Forty-five states levy a state-level sales tax; Alaska, Delaware, Montana, New Hampshire and Oregon do not. California has the highest state-level rate at 7.25 percent. Thirty-eight states allow local sales taxes on top, including Alaska which has no statewide tax, and local rates can rival or exceed state rates.
- Do you work with businesses in New York and other parts of the United States?
- Yes. An Odoo integration runs remotely by default, and being based in one city inside the United States does not change the plan or the price. Cities we cover for on-site visits: New York, Los Angeles, Chicago, Houston, Miami, Dallas, Atlanta, San Francisco, Seattle. Regions we cover: California, Texas, Florida, Illinois, Georgia, Washington. We travel on-site for discovery workshops and go-live week when the engagement calls for it.