Odoo ERP implementation: inventory, orders and accounting in one place

Who this is for

• Product brands that have outgrown spreadsheets plus an accounting app.
• Multi-channel sellers whose stock counts disagree between Shopify, Amazon and the warehouse.
• Brands using a 3PL who need purchase orders, receipts and stock movements in one system.
• Businesses selling both wholesale and direct-to-consumer that need clean revenue by channel.
• Existing Odoo users facing a version upgrade with custom modules nobody maintains.

What's included

• Process and data design. One owner for each kind of data, written integration specs, and the inventory decisions below agreed before anything is configured.
• Configuration. Inventory, purchasing, sales, accounting and the channel connectors set up in a test database first.
• Data migration. Products, customers, vendors, opening stock, open orders and opening balances, with counts reconciled at every step.
• Integrations. Native connectors where they exist, and custom integrations on the JSON-2 API where they don't, with API keys scoped to a dedicated integration user.
• Go-live and training. A parallel run, cutover at a period boundary, and role-based training.
• Ongoing management. Connector monitoring, key rotation, and version upgrades tested before production.

How an Odoo implementation runs

ERP mistakes we design out

• The same orders imported twice through two routes — common with Faire orders arriving via Shopify and a separate import.
• Assuming connectors are real time. With a ten-minute order cycle, fast-selling stock can oversell unless buffers are set.
• SKUs that don't match across Shopify, Amazon and the warehouse.
• Customizing with Studio before the standard processes have been tried.
• Choosing the Standard plan, then discovering a 3PL integration needs the external API.
• A new integration built on XML-RPC in 2026, with a removal date already published.
• Two systems both believing they own inventory.
• Going live in the last week of the month.

Odoo editions and plans, in plain terms

Odoo comes in two editions: Community, which is open source, and Enterprise, which is licensed and built on top of Community.

On Odoo's pricing page, subscriptions are per user per month across three tiers: One App Free (a single app, unlimited users, on Odoo Online), Standard (all apps on Odoo Online) and Custom (all apps, plus Odoo Studio and agentic AI, multi-company, the external API, and hosting on Odoo.sh or on-premise). Odoo's FAQ notes that installing Studio or adding companies moves a paid database to Custom, and that Odoo.sh hosting costs are billed on top. Three more details shape most projects:

• "External API" means another system calling Odoo. Odoo defines it as external software initiating API calls into Odoo to query or update data. Calls that Odoo initiates — to payment providers, carriers or bank feeds — are part of the standard plan. If your 3PL or a custom tool needs to push data into Odoo, plan for the Custom tier.
• Portal users don't count as paying users. Customers and suppliers viewing invoices on the portal, and shoppers placing website orders, are free; anyone working in the backend is a paid user.
• Implementation isn't included. Odoo says small companies (under 50 employees) usually work directly with Odoo through Success Packs, mid-size companies usually work with a partner, and companies over 250 employees can contact Odoo directly.

The integration map

The API and upgrade rules that outlast go-live

Building on the JSON-2 API

Odoo 19 documents a new External JSON-2 API, and states that the XML-RPC and JSON-RPC endpoints are scheduled for removal in Odoo 22, in fall 2028. Three details from that documentation change how we build:

• Authentication uses API keys sent as bearer tokens, and keys can't last more than three months, so every integration needs a rotation routine and an owner.
• Each call runs in its own database transaction. Multi-step operations such as reserving stock and confirming an order can't be chained atomically, so integrations have to check state between calls.
• Calls run with the permissions of the key's user, so each integration gets its own least-privilege user and key, which also makes auditing and revoking simple.

Planning for upgrades

Per Odoo's upgrade documentation, each major version is supported for three years. On Odoo Online, major-version upgrades become mandatory every two years and run automatically if you don't act by the deadline. A database with custom modules can't be upgraded until those modules are ported to the new version, and Odoo's upgrade service covers standard apps and Studio customizations but not third-party or partner-built modules without a maintenance contract. Upgraded test databases also disable scheduled actions and outgoing email, so connectors have to be tested deliberately rather than assumed to work. This is why we keep custom code to a minimum and check the Odoo Community Association for a maintained module before writing one.

Inventory decisions that shape the build

Most of an ERP's long-term value is decided in a handful of early choices. We make them explicitly, in writing, before configuration starts:

• Warehouses and locations. Your own stockroom, each 3PL and Amazon FBA modeled as separate locations, so "available to sell" is calculated per channel instead of guessed.
• Product structure. Variants for size and color, one SKU per sellable unit, and the same SKU used on every channel so connectors can match products automatically.
• Units of measure. Wholesale case packs and retail eaches defined as units of the same product, so a Faire order for two cases deducts the right number of units.
• Lot and serial tracking. Switched on only for products that genuinely need traceability, such as batches with expiry dates; it adds a scan to every movement.
• Replenishment. Reordering rules from real lead times and sales velocity, with buffers sized for the connector sync interval.
• Costing method. Standard, average or FIFO costing agreed with your accountant before the first receipt, because changing it later means revaluing stock. If you report under IFRS, note that IAS 2 doesn't permit LIFO.

Why we're cautious about go-live

ERP cutovers fail loudly. In Harvard Business Review, Bent Flyvbjerg and Alexander Budzier describe Levi Strauss's move to a single SAP system: a project budgeted at under $5 million left the company unable to fill orders, closed its three U.S. distribution centers for a week, and ended in a $192.5 million charge against earnings. Your project will be far smaller, but the failure modes are the same. Our go-live checklist:

• Every channel has replayed real orders in the test database, including a return and a refund.
• Stock counts in Odoo match a physical count, by location, the day before cutover.
• Open purchase orders and unshipped sales orders are migrated and reconciled line by line.
• Opening balances are signed off by your accountant for the period start date.
• A tested database backup exists, and someone has restored it at least once.
• Every integration has an owner, a key expiry date and an alert if it stops syncing.

Pricing and engagement

A fixed-fee discovery, then a fixed-scope implementation quote, then optional monthly management. Your Odoo subscription is billed by Odoo. The main cost drivers are the number of channels and integrations, data volume and cleanliness, and how much customization your processes truly require. Per our pricing page, there are no percentage fees and no long contracts.

Platforms we work in

Odoo and the channels and tools we connect to it.

Odoo Shopify Amazon Seller Central FFaire QuickBooks SShipStation PGPostgreSQL

Proof you can check before you call

There's no Odoo case study on this site yet, so here's the published integration work you can judge us on. In the Squeaky Clean Turf migration we moved customers, order history and products from WooCommerce to Shopify with counts reconciled, surfaced live subscriptions for a human decision rather than migrating billing silently, built a custom Merchant Center feed from live Shopify data, and wired orders into the CRM. The same habits — inventory everything, one owner per data type, verify with real transactions — are how we run an Odoo project.

Frequently asked questions

Talk to us about Odoo

Tell us your sales channels, warehouse or 3PL setup, current accounting system, and how many people will use the ERP.

Top 25 references

The primary sources, standards, research, and tools we rely on for this work. Every link was checked on 2026-10-11. We aren't affiliated with these publishers unless noted.

Official documentation

1. Odoo pricing — Odoo
   One App Free, Standard and Custom plans, what Custom adds (Studio, multi-company, external API, Odoo.sh or on-premise), and the definition of external API.
2. Odoo editions comparison — Odoo
   Which apps and features are in Community versus Enterprise, checked before choosing the open-source edition.
3. Shopify Connector — Odoo 19.0 documentation
   Sync direction for each data type, cron-based sync every 10 minutes by default, and how returns behave depending on where deliveries are handled.
4. Amazon Connector features — Odoo 19.0 documentation
   FBA and FBM order import, FBM stock and shipment push, and the data that stays in Seller Central.
5. External JSON-2 API — Odoo 19.0 documentation
   The Odoo 19 API with bearer API keys capped at three months, one transaction per call, and XML-RPC and JSON-RPC scheduled for removal in Odoo 22 (fall 2028).
6. Upgrade — Odoo 19.0 documentation
   Three years of support per major version, mandatory upgrades on Odoo Online, and the rule that custom modules block an upgrade until they're ported.
7. Reordering rules — Odoo 19.0 documentation
   Min and max quantities, lead times and automatic versus manual replenishment in Odoo Inventory.
8. What is Shopify order sync? — Faire Help Center
   How accepted Faire orders are created in Shopify with custom tags, which is how they reach Odoo without a second import.
9. Inventory and locations — Shopify Help Center
   Shopify's location-based stock model, which has to map cleanly onto Odoo warehouses.
10. GraphQL Admin API reference — Shopify.dev
    The API behind any custom Shopify integration that the native connector doesn't cover.
11. What is the Selling Partner API? — Amazon Developer Docs
    Amazon's API for orders, inventory and reports, the layer every Amazon connector depends on.
12. Backup and restore — PostgreSQL documentation
    The database Odoo runs on; self-hosted deployments need tested dumps and restores before go-live, not after the first incident.

Standards & policy

13. Publication 538: Accounting Periods and Methods — Internal Revenue Service
    IRS rules on accounting methods and inventories, which is why the costing method is agreed with your accountant first.
14. Recordkeeping — Internal Revenue Service
    What records a business has to keep and for how long, relevant when deciding what history to migrate.
15. IAS 2 Inventories — IFRS Foundation
    The international standard for inventory cost and valuation, including why LIFO isn't permitted under IFRS.
16. X12 transaction sets — X12
    The EDI standard (850 purchase orders, 856 ship notices, 810 invoices) many retailers and 3PLs still require.
17. GS1 EDI standards — GS1
    GS1's EDI messaging standards used alongside GTINs in retail supply chains.
18. Global Trade Item Number (GTIN) — GS1
    The product identifier that lets Odoo, Shopify, Amazon and retailers agree on what each SKU is.

Research & studies

19. Why Your IT Project May Be Riskier Than You Think — Harvard Business Review
    Flyvbjerg and Budzier's study of IT project overruns, opening with Levi Strauss's $192.5 million charge after an ERP switchover.

Leading tools

20. odoo/odoo — Odoo on GitHub
    The Community edition source code, where you can read exactly how a module behaves before relying on it.
21. QuickBooks Online API: get started — Intuit Developer
    The API used when Odoo runs operations but the books stay in QuickBooks for a transition period.
22. ShipStation API documentation — ShipStation
    Shipping platform API for label and shipment data when fulfillment runs outside Odoo.

Communities & courses

23. Odoo Community Association — OCA
    The non-profit that maintains hundreds of community modules, and the first place to check before commissioning custom code.
24. Odoo Help forum — Odoo
    Odoo's official user forum, where connector edge cases and configuration questions are answered by users and staff.
25. Odoo Community Association on GitHub — OCA
    The OCA's module repositories, organized by Odoo version, so you can check whether a module exists and is maintained for your release.

Related services