Odoo Development Company in the USA
Odoo partner in New York, LA, Chicago. Sales Tax & 1099 ready.
- Reporting currency
- USD
- Locale code
- en-US
- Cities covered
- 9
- Odoo versions
- v12 to v19
Odoo localization in United States
A United States deployment is not a stock Odoo install with the currency swapped. Tax handling, invoice layout, payroll rules, and the reports your accountant actually files all have to line up before go-live. These are the United States items we configure and test as part of the build:
- โ Avalara / TaxJar integration
- โ Multi-state sales tax nexus
- โ 1099 reporting
- โ ACH & check-run
- โ US GAAP reporting
Checked Localization notes on this page checked on 22 August 2026.
Rates, filing formats, thresholds, and submission windows change. We configure against the rules in force at build time and confirm every figure with your accountant or tax advisor before sign-off. If a rule moves after go-live, it is a support ticket, not a rebuild. Read more on our Odoo localization service.
E-invoicing in United States
The scheme, who it binds, and what it makes your system do.
No national scheme. DBNAlliance Exchange Framework (voluntary industry network) plus the Invoice Processing Platform (IPP) for federal procurement.
Authority: None at federal level for B2B. The DBNAlliance governs the voluntary exchange network. The US Department of the Treasury runs IPP, under OMB Memorandum M-15-19 issued 17 July 2015.
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.
Tax in United States
What the tax configuration has to get right before go-live.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Filers of 10 or more information returns in a calendar year must file them electronically.
Payroll in United States
What payroll has to calculate, withhold, and file.
-
FICA: Social Security is 6.2 percent on the employer and 6.2 percent on the employee, 12.4 percent combined. Medicare is 1.45 percent each side, 2.9 percent combined. An Additional Medicare Tax of 0.9 percent applies to employee wages above 200,000 dollars a year, withheld by the employer with no employer match.
-
The Social Security wage base limit is 184,500 dollars for 2026. There is no wage base limit for Medicare tax.
-
FUTA is 6.0 percent on the first 7,000 dollars of wages per employee, reduced by a credit of up to 5.4 percent when Form 940 is filed, giving a common net rate of 0.6 percent. Credit reduction states are announced by the Department of Labor after the 10 November deadline each year.
-
Federal tax deposits must be made by electronic funds transfer, on a monthly or semi-weekly schedule set annually by liability. FUTA deposits are only required when quarterly tax exceeds 500 dollars.
-
Reporting forms: Form 941 quarterly for most employers, Form 943 for agricultural employers, Form 944 annually if the IRS notifies you, Form 945 for nonpayroll withholding, Form 940 annually for FUTA, Form W-2 to employees and Form W-3 to the Social Security Administration by 31 January.
Accounting in United States
The reporting framework your books sit inside.
-
The FASB sets GAAP for nongovernmental entities and the FASB Accounting Standards Codification has been the single official source of authoritative US GAAP since 15 September 2009. There is no statutory chart of accounts imposed by the government, no SAF-T equivalent and no mandated ledger export file.
-
Because no chart of accounts is imposed, the l10n_us module's GAAP-oriented chart is a starting template, not a legal requirement. Odoo structures it around seven categories: Receivable, Payable, Equity, Assets, Liability, Income and Expenses. You can and often should restructure it to match the client's reporting.
-
The audit-file question that dominates European Odoo projects does not exist here. The US compliance load sits in sales tax across up to 45 state regimes plus local jurisdictions, and in 1099 and payroll reporting, not in ledger format.
Payment gateways in United States
The providers a checkout in United States actually needs, and how each one reaches Odoo.
The default gateway for US direct to consumer brands, and US sits in the supported country list inside Odoo 19's Stripe module. One US Stripe account covers cards, ACH Direct Debit, Cash App Pay, Affirm, Klarna, Afterpay, Link and Amazon Pay.
One of the oldest US gateways and still the thing sitting in front of a lot of established US merchant accounts, so an Odoo migration usually has to keep it. Odoo 19's module turns on ACH Direct Debit alongside cards by default.
Still an expected second button on US checkouts and the account many US shoppers pay from without re entering card details. Odoo 19 ships the PayPal provider and supports USD.
The usual pick once a US retailer runs stores and a website on one contract, or is selling into Europe as well. Its Odoo 19 mapping includes ACH, Cash App Pay and Apple Pay.
The US bank to bank rail behind eCheck payments and the cheapest way to collect large B2B invoices instead of eating card interchange. Odoo 19 reaches it two native ways: Authorize.Net enables it by default, and Stripe maps it to us_bank_account for USD and US customers.
Block's Cash App at checkout, USD and US customers only, and a real conversion lever for younger US buyers who keep a balance there. Odoo 19's Stripe module maps cash_app_pay to Stripe's cashapp, so a US Stripe account reaches it with no extra module.
Most US mobile checkout traffic expects one of these buttons before a card form. Odoo 19's Stripe provider ships express checkout, which Odoo's own field help describes as paying with Google Pay and Apple Pay.
A US based card network that plenty of American shoppers carry and that plain international card setups sometimes decline. Odoo 19 turns Discover on by default with Stripe, Adyen, Authorize.Net, Worldline, Buckaroo and Nuvei.
US instalment lender used on higher ticket items such as furniture, bikes and electronics, where it moves basket size. Stripe supports it for US and Canadian businesses in USD, and Odoo 19 ships an Affirm payment method record.
Stripe lists the US among the business locations that can accept Klarna in USD. Odoo 19 ships Klarna plus the separate Klarna Pay Now and Klarna Pay over time methods so you can expose the right one.
Pay in four provider with real US apparel and beauty volume. Odoo 19's Stripe module maps both afterpay and clearpay to Stripe's afterpay_clearpay, and Stripe supports it for US businesses in USD.
Lets a US shopper check out with the address and card already on their Amazon account, which cuts form abandonment. Stripe supports amazon_pay for US businesses and Odoo 19 ships an Amazon Pay payment method record.
US B2B still settles a lot of invoices by paper check and by wire, so the order has to sit unpaid until the finance team reconciles it. Odoo 19 ships Wire Transfer as a bank payment method that prints your bank details and a payment reference at checkout.
PayPal owned and US only, and a habit for younger American buyers. Odoo 19's native PayPal module only switches on the PayPal method, so Venmo needs a Braintree connector from the store.
The stack under most US small retail, restaurants and services, so an Odoo project usually has to keep taking payments there and reconcile them. Odoo does not ship a Square provider, but eleven connectors cover 19.0, including a free one from Silver Touch.
PayPal's US gateway and the single integration that gets you PayPal, Venmo, cards, Apple Pay and Google Pay at once. Sixteen connectors cover Odoo 19, several of them adding Braintree ACH.
Turns up with larger US merchants who want their own acquiring relationships and cross border processing. Not native to Odoo, but seven connectors cover 19.0.
A US gateway that sits behind a lot of ISO and reseller merchant accounts, so it appears when a client came in through a payments broker rather than direct. Paid Odoo 19 connectors exist for both card and eCheck ACH.
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.
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.
Shipping and couriers in United States
The carriers that move volume here, and what it takes to rate, label, and track them from Odoo.
Reaches every US residential address and is the cheapest route for light parcels, which is why US ecommerce sellers rate shop against it constantly. Odoo 19 ships a direct USPS connector that needs a USPS business account through the Business Customer Onboarding Portal, and it offers USPS Domestic Service and USPS International Service.
One of the two national ground and air networks US shippers negotiate rates with, and the usual default for B2B pallets and heavier parcels. Odoo 19 ships a UPS connector.
The other national network, and the one most US merchants keep as a second contract so they can play rates off against UPS. Odoo 19 ships a FedEx connector.
Used from the US mainly for international air freight and express export rather than domestic ground. Odoo 19 ships a DHL Express connector and its doc says plainly that other DHL services are not supported.
The one shipped Odoo 19 connector aimed at North America, and the practical way to reach US regional carriers that have no Odoo module of their own. Odoo's doc calls it a service that connects you to multiple carriers and requires an EasyPost business account with test and production API keys, so that account and its fees are a dependency.
Calls itself the largest alternative carrier network in the country, running coast to coast ecommerce ground seven days a week, and DTC brands use it to undercut UPS and FedEx ground. No OnTrac module exists on the Odoo store, so it comes in through EasyPost or ShipStation and that aggregator account plus its fees are a required dependency.
Regional western US parcel carrier with more than 27 locations plus US to Canada cross border, strong with wine and spirits, perishables and healthcare shippers on the West Coast. Softhealer sells a GLS United States connector for Odoo 19.
US last mile carrier built for ecommerce brands, delivering next day and two day including weekends and holidays. There is no Odoo connector, but EasyPost lists Veho among its carriers, so it arrives through the native EasyPost integration and needs an EasyPost account.
Amazon sells delivery for orders that were not placed on Amazon, and US sellers use it as a cheaper residential option. No Odoo module exists for it, so it comes through EasyPost with an EasyPost account behind it.
The shipping desk a large share of US ecommerce teams already work in every day, especially anyone who came from Shopify or Amazon. Odoo does not ship a ShipStation connector, so it is a paid store module plus a ShipStation subscription, and fourteen connectors cover 19.0 including a free multi instance one from Globalteckz.
Multi carrier label buying that smaller US merchants use to get discounted USPS and UPS rates without their own contracts. Not native to Odoo, so it needs a paid store connector plus a Shippo account.
The API layer US developers reach for when they want rates and labels across USPS, UPS and FedEx from one place. Odoo does not ship it, so it is a paid store connector plus a ShipEngine account.
A major US less than truckload carrier, which is what wholesalers and manufacturers running Odoo actually ship once orders go on pallets. Odoo ships no LTL support at all, but a paid Odoo 19 connector handles freight booking, rating, bills of lading and tracking from the sales and delivery orders.
What Odoo covers out of the box in United States
The question behind every quote: how much of this is configuration and how much is a build. The first list ships with Odoo. The second is a paid connector, a community module, or work we scope and price up front.
l10n_us United States - Accounting l10n_us_reports US accounting reports l10n_us_check_printing pre-printed check layouts l10n_us_payment_nacha NACHA ACH file export l10n_us_1099 1099 data for third-party e-filing account_avatax Avalara AvaTax integration l10n_us_hr_payroll US payroll rules l10n_us_hr_payroll_account payroll accounting l10n_us_hr_payroll_adp work entry export to ADP - 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.
Everything under "Needs work" is quoted as scope, not discovered mid-project. Bring your own module list to a scoping call and we will mark it up the same way against United States.
Odoo services in United States
We work as an Odoo development company and Odoo implementation partner for businesses in United States. That covers the whole engagement: consulting on whether Odoo fits, configuring it, writing the custom modules that fit requires, connecting it to the systems you already run, and supporting it afterwards. Our Odoo developers and consultants deliver remotely, and travel for discovery, training and go-live week.
If you are moving off spreadsheets or replacing older ERP software, an ERP migration is the shape of the project and the United States items on this page decide how hard it is. As ERP consultants we will say when Odoo is the right ERP solution for you and when it is not. We work on Odoo 17, 18 and 19, on Odoo Community and Odoo Enterprise, and on Odoo cloud hosting or your own servers. Odoo customization, an Odoo upgrade from an older release, and Odoo AMC and support contracts are all in scope. We will say plainly when the edition you run is the wrong one, and what the Enterprise license would change.
Odoo pricing and what an Odoo project costs in United States and the Odoo modules we publish
How we deliver in United States
Delivery is remote-first. We do not claim a branch office in every city we serve, and we do not price one into your project. We travel on-site for discovery workshops, user training, and go-live week when the work calls for people in the room. What you get either way is senior engineers on the build.
- 1 Timezone overlap. Our teams shift to hold working-hour overlap with local office hours, so New York gets live hours, not overnight email.
- 2 English delivery, multilingual team. Documentation and training are in English. Our project teams also work in Arabic and Urdu.
- 3 Visible progress. Daily stand-ups, weekly demos, and a written weekly report. You see the build as it happens, not at handover.
- 4 Test-database sign-off. Your team runs the United States configuration in a test environment and approves it before cutover, with a rollback plan in writing.
- 5 Support after go-live. SLA-backed contracts with 2h, 4h, or 8h response tiers, 24/7 monitoring, verified backups, and security patching.
Odoo services we run in United States
Ordered by what the United States scope above usually needs first.
Country-specific compliance out of the box.
End-to-end Odoo deployment, from discovery to go-live.
Custom modules built to match your exact workflow.
Upgrade safely from older Odoo versions.
24/7 monitoring, bug fixes, performance tuning.
Connect Odoo with your stack and third-party APIs.
Dedicated developers by the week or month.
Role-based training for users, admins, developers.
Multi-tenant Odoo hosting with 99.9% SLA.
Industry builds for United States
Industry-specific Odoo builds, each with its own module set and reports.
Containers, coupons, rounds, dispenser rental.
Patient records, OPD/IPD, pharmacy, billing, insurance.
Appointments, prescriptions, billing for clinics.
Batch, expiry, narcotic control, POS.
Treatment plans, procedures, imaging.
Front desk, housekeeping, F&B, revenue.
Way4Tech modules for United States projects
Modules we build and maintain ourselves, ordered by how closely each one matches the United States scope above. They ship as part of an implementation or drop into an Odoo instance you already run.
Distributor sales with territory and commissions.
Turn your server into a multi-tenant Odoo SaaS.
Pipeline, win rate, activity tracking.
Property listings, leases, tenant management.
Full-screen barcode scanner with offline cache.
Employee dashboard, approval engine, HR foundation.
Selected client work
Odoo rollouts we have delivered elsewhere. Each card names the country the project ran in.
OPD + IPD + pharmacy + insurance on one Odoo instance.
Multi-project BOQ, subcontractors, progress billing at scale.
12 stores + online, unified inventory, HMRC MTD VAT.
Cities and regions we serve in United States
We deliver Odoo projects remotely and on-site across United States. The places below are the ones we cover for on-site work. Books run in USD, with multi-currency switched on where you trade across borders.
Not on the list? Remote delivery is the default anyway, so location inside United States rarely changes the plan or the price.
Odoo in United States
Straight answers on scope, cost, and how a build in United States actually runs. Still stuck? Ask us directly.
Do we need to be in New York to work with you? +
No. Odoo projects are delivered remotely by default, and location inside United States rarely changes the plan or the price. We travel on-site for discovery workshops, user training, and go-live week when the work calls for it. 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.
Which timezone and language does a project in United States run in? +
Delivery, documentation, and training run in English. Our teams also work in Arabic and Urdu. We hold working-hour overlap with your own office hours, with daily stand-ups and a written weekly report, so progress never depends on one call landing.
Can Odoo run in USD for an entity registered in United States? +
Yes. Odoo is multi-company and multi-currency, so your books can run in USD while you buy or sell in other currencies. The locale code we set up for this market is en-US, and Odoo supports multi-language and right-to-left layouts where a deployment needs them.
How long does an Odoo implementation in United States take? +
Single-module projects run 3-4 weeks. Multi-module rollouts run 8-12 weeks. Multi-company or multi-country programmes run 4-9 months with phased go-lives. The United States localization items above are configured inside that build, not after it.
What does an Odoo project in United States cost? +
From $4,900 for a Starter scope (Up to 2 modules, 10 users, Discovery + config + training). From $14,900 for a Growth rollout (Up to 6 modules, 50 users, Custom modules + reports). Larger multi-company programmes are priced on scope after discovery. Localization work is scoped and priced up front, not added later.
Do you work with Odoo Community or Enterprise in United States? +
Both, and we migrate in either direction. The choice comes down to how technical your team is and whether you need Studio, IoT, or MRP II. The United States configuration described on this page is done in whichever edition you run.
Which Odoo versions do you work on? +
Current releases, including Odoo 17, Odoo 18 and Odoo 19, on Community and on Enterprise. If you are on an older version the first question is whether to upgrade before or after the United States work, and that depends on how much of what you need already ships in the newer release.
Can we see an Odoo demo before committing? +
Yes. We set up an Odoo demo on your own data rather than a generic one, because the United States specifics are the part worth seeing. Ask and we will scope what to load.
We are replacing spreadsheets or an older ERP system. Where does that start? +
With the data, not the software. An ERP implementation in United States usually stalls on master data quality rather than configuration, so the first phase is deciding what comes across, what gets cleaned, and what stays behind.
Scope your United States Odoo project.
A 30-minute call: your current stack, the United States items above, and what a realistic first phase looks like. You leave with a written scope. No obligation, no sales script.