| Plan | Price | Apps | Hosting | User and storage limits | Studio and code | Support | Multi-company | API | |---|---|---|---|---|---|---|---|---| | One App Free | Free | One app of your choice | Odoo Online | Online storage allowance | No custom code | Limited | No | No | | Custom | Per user, monthly | All apps | Odoo Online | Online storage allowance | Studio included | Included | Yes | Yes | | Odoo.sh | Enterprise licence plus platform hosting | All apps | Odoo's managed platform | Set by hosting package | Full custom code | Included | Yes | Yes | | Self-hosted Enterprise | Enterprise licence | All apps | Your own server | Whatever your hardware holds | Full custom code | Included | Yes | Yes | | Community | Free licence | Core apps only | Your own server | Whatever your hardware holds | Full custom code | Community forums only | Limited | Yes | Read the price column as the licence only. It's the smallest line on your bill. The catch sits in the columns: the cheaper tier lacks multi-company and external API access, so a business with two legal entities or an integration to a warehouse system is pushed up to Custom before it's written any code. ### Odoo.sh and self-hosted Enterprise Both use the Enterprise edition, which adds the proprietary apps and official support on top of the open-source core. Odoo.sh is a managed platform built around Git deployment, with staging and test branches, so custom modules run without you operating servers.  Self-hosted Enterprise gives you the same software on infrastructure you control. You pay the same kind of licence either way, then pick between paying for a platform or paying someone to patch, back up and monitor a server. ### Odoo Community and what it leaves out Free to download and run, Community is the open-source edition. It omits several Enterprise apps, Studio and official support, and it relies on forums and partners when something breaks. ## Estimating your Odoo bill in four stages Start by counting users, the first of four stages; each one leaves a single figure that feeds the next: headcount, app list, plan and hosting, then implementation hours. **Count anyone who logs into the back office**, because Odoo bills for internal users. Customers and vendors who only use the portal are treated differently, so check the page's wording before you count them. Counting every employee instead of the people who will actually log in is the quickest way to overpay before you've started. Write the apps down by name: sales, inventory, accounting, whatever your daily work touches. Mark each as needed now or maybe later. The page prices around what you select, so a padded list inflates the plan and widens the scope a partner will quote against. ### Stage 3: Price the plan and the hosting Take your headcount and app list to the pricing page and read off the plan and the hosting option that match them. Use only the values published there. If a tier forces you into a sales call just to learn its price, record that as an unknown in your estimate, not a guess. Your figure is a monthly or annual platform cost, and you should note whether it assumes custom code, because that decides which hosting choices remain open. ### Stage 4: Add implementation and run two examples Ask what hours a partner would need for setup, data import, configuration and training, then multiply by their rate. This is the line that turns a modest subscription into the real bill.  The table shows where each example's effort lands. Both are estimates, to be replaced with your own figures. | Stage | Team of 5 | Team of 25 | |---|---|---| | Users | Small headcount, so the per-user price barely moves the total | Seat cost becomes a visible line | | Apps | Often a few core apps | More departments, so more apps and more configuration | | Plan and hosting | Standard options usually suffice | Custom code or tighter controls may force a different hosting choice | | Implementation | Short engagement | Longest line, driven by data migration and training | On Monday, start a trial of the one app that matters most and see how far it gets you without help. ## Hidden Odoo costs and limits teams hit Ask for an itemized quote and it exposes the costs the per-user price leaves out, and **the largest is usually the implementation hours**. The list below tags each omitted cost as either Odoo source (stated in Odoo's own pages or docs) or partner practice (what implementers commonly charge or do), so you know which lines you can verify and which you must negotiate. ### Odoo implementation and partner hour pack costs Buy hours and you buy them in packs, with the rate per hour falling as the pack grows. [Opsily](https://opsily.com/hosting/odoo/odoo-success-pack-pricing) lists the Starter 4h pack at 499 €, about 125 € an hour, which buys a scoping call and little else.  The Basic 25h pack is 2635 €, or about 105 € an hour. The Standard 50h pack is 4675 €, about 94 € an hour. At 100 hours the discount stops. The Custom 100h pack is 8415 € and the Pro 200h pack is 16830 €, both about 84 € an hour, so a bigger pack buys no cheaper hours. Estimate your hours first and buy the pack that covers them, not the largest one. ### Customisation limits by plan Studio, Odoo's point-and-click customisation tool, covers fields, views and simple automations. Custom Python modules are a separate matter, and Odoo Online doesn't run them. If a partner proposes code, ask which hosting option it requires, because that choice can change your bill more than the seat count. **Treat any quote that adds code to a hosted plan without naming the hosting move as incomplete.** ### Storage, upgrades and extra hosting Plans include 100 GB of storage and 200 outgoing emails a day (Odoo source). A team sending order confirmations and marketing mail from one database can reach the email cap before it reaches the storage cap, so count your daily sends. Then come upgrades between major versions, another cost. Under partner practice, a migration with custom fields is billed as project hours, not as part of the subscription. Add-ons and extra apps are priced separately (Odoo source), and renewal true-ups (partner practice) bill any users added mid-term at the next renewal. ### Connecting Odoo to the rest of your stack Confirm external API access in writing before you design around it. It depends on your plan, and Odoo has restricted it on some Online tiers. If the API is available, a workflow tool can sit between Odoo and your other systems and move records on a trigger. That replaces custom code for many integrations, which keeps you out of the higher-priced hosting. If the only gap is passing data between Odoo and one other tool, the way the tool meters usage matters more than its connector. [Activepieces](https://www.activepieces.com) counts the run as the meter: 1 credit per flow run, however many steps sit inside it.  A sync broken into ten small, retry-friendly steps therefore costs the same as the two-step shortcut, while Zapier's pricing page bills per task and Make's bills per module, so every extra step you add for reliability shows up on the invoice. The free plan's 1,000 credits a month and unlimited flows mean this line stays out of your Odoo estimate. If the API isn't available on your plan, the integration needs an upgrade or a partner build, and both belong in the quote. ## Odoo pricing against ERPNext, Business Central and Zoho Put the same quote requirements to each of Odoo's closest rivals and the ranking shifts. Odoo wins on modular entry cost, ERPNext wins if you can host it yourself, and Business Central and Zoho win only when their bundling matches what you would otherwise buy separately. I've left out dollar amounts. Each vendor's page was checked, but the entry prices move with billing term and edition, and a figure I can't pin to a date would mislead you. | | Odoo | ERPNext | Business Central | Zoho | |---|---|---|---|---| | Entry price per user | Public, per user, all apps on paid plans | Cloud hosting priced per site rather than per user | Public, per user, by edition | Public, per user, by product | | What is bundled | Apps you pick; the rest is add-on cost | Full suite in one install | Finance and operations core; extras by edition | Separate products that integrate with each other | | Self-host or open source | Open-source Community edition, paid Enterprise | Fully open source, self-hostable | Microsoft cloud only | Vendor cloud only | | Seat floors | Set by plan | None on self-hosting | Set by edition and reseller | Set by product tier | | Implementation burden | Moderate; heavier with custom code | Moderate to heavy if you self-host | Heavy; usually a certified partner | Light for a single product, heavier across several | So **the per-user line is the least informative row**. ERPNext's cost sits in your own hosting and admin time, Business Central's sits in the partner invoice, and Zoho's sits in the number of products you stitch together before the suite behaves like one system. Odoo suits you if you want a broad app set, a fair number of users, and a choice between its cloud and your own server without leaving one vendor. If you have someone who can run a server and would rather pay in labour than licences, ERPNext suits you. Business Central suits you if accounting depth and a Microsoft-centred shop matter more than a low entry price, and you accept a partner-led rollout. If you need one or two functions, such as CRM and invoicing, and not a full ERP, Zoho suits you. ## What Activepieces does about this The expensive step in the bill is the jump to custom code, because code forces the move to Odoo.sh or your own server. Activepieces is built to stop that jump happening for integrations. It sits outside Odoo, picks up a trigger, and moves records between Odoo and your other tools through flows you build in a visual editor. That only works if your plan includes external API access, so check that first, as above. A flow that syncs orders or invoices into another system is the usual reason a team thinks it needs a custom module. Run it in Activepieces and the module never gets written. Your Odoo plan stays set by users and hosting, and the implementation hours go to configuration instead of code you will have to carry through every upgrade. The pricing is easy to estimate. A flow run is 1 credit however many steps it has, and the free plan gives you 1,000 credits a month with unlimited flows. The community edition is open source under the MIT licence, so if you already run your own Odoo server you can run Activepieces beside it. Add the credits, or the server, as one line in stage 3 of your estimate.  ## Frequently asked questions Mostly, the questions left over are about what the headline price hides, and each answer below reflects Odoo's own pages as of November 2026. ### Is Odoo really free? Partly. Odoo Community, the open-source edition, costs nothing to download, but you host it, secure it and maintain it yourself. That's the bill. Odoo also has a free Online plan limited to a single app, which suits a company that needs only one function. Once you want several apps, Enterprise features or Odoo's hosting, you're on a paid plan.  ### Can I move from Odoo Online to Odoo.sh later? Yes, Odoo documents a migration path, but plan for it as a project, not a switch. Odoo Online doesn't run custom code, while Odoo.sh exists largely so you can add it. If you expect custom modules within a year or two, price Odoo.sh from the start. Moving later means paying for the migration and re-testing every workflow. Confirm the current steps on Odoo's documentation before committing. ### Does Odoo charge per user or per app? Per user is how Odoo's pricing page frames the paid plans: you pick a plan, then multiply by the number of users. You aren't billed app by app on those plans. That's why the user count is the first input in your bill, and why unused apps don't lower it. The exception is the single-app free plan, where the app limit is the whole point. ### Is there a free trial and does it need a card? Odoo has a trial of its Online product on its pricing and signup pages. Whether it asks for payment details is shown on the signup form, so read that before you enter anything. Treat the trial as a way to test your workflow, not your costs. A trial database has no custom code, no migrated data and none of the integrations you'll pay for later. ### How often does Odoo change its pricing? No fixed schedule is published. Plan names, user prices and what each hosting option includes are set on its pricing page and have changed over time. Before you sign, capture the quote in writing with the contract term. At renewal, compare the new price against the page that day, not against the number you remember. Any figure in this article carries the date of the check, and your quote should too. ## Related reading - [Postgres Pricing: What Managed Hosting Costs in 2026](https://www.activepieces.com/blog/postgres-pricing-what-managed-hosting-costs-in-2026) - [Langflow Pricing: Free Software, Hosting Costs (2026)](https://www.activepieces.com/blog/langflow-pricing-free-software-hosting-costs-2026) - [LiteLLM Alternatives Pricing and Hosting Costs in 2026](https://www.activepieces.com/blog/litellm-alternatives-pricing-and-hosting-costs-in-2026) ## References - [Opsily](https://opsily.com/hosting/odoo/odoo-success-pack-pricing)Developer time, hosting and upgrade work are the real costs here, not the licence.