Odoo’s modular architecture is its biggest advantage: you can shape the ERP around how your business really works. It is also its largest attack surface. Custom add-ons written in-house, by an outsourced agency or with rapid prototyping tools often build up security debt.

When a module ignores Odoo’s security framework, it quietly bypasses the access controls the rest of the system relies on. This article is part of our Odoo security series.

The flaws we find most often

• Missing access rights. A new models.Model without rows in security/ir.model.access.csv. Standard users either hit errors, or someone “fixes” it by granting everything to everyone.
• Rules that are too broad. No multi-company or departmental restriction, so any internal user can read or edit sensitive financial or HR records.
• Unsafe controllers. @http.route endpoints with auth='public' or auth='none' that change data, or that switch off CSRF checks.
• Raw SQL built with string formatting. cr.execute() with f-strings or % formatting opens the door to SQL injection.
• .sudo() as a shortcut. Used to silence an access error, and then returning privileged data to the user.

Secure development practices

1. Least privilege by default. Give each group (internal users, portal, your own groups) only the read, write, create and delete rights it needs.
2. Restrict records, not just models. Up to Odoo 19 that means record rules; in Odoo 20, put the domain on the access right. Always include the company restriction for multi-company databases.
3. Stay in the ORM. When raw SQL is truly needed for performance, use parameter binding (cr.execute(query, params)) or Odoo’s SQL wrapper, never string formatting.
4. Lock down controllers. Declare auth explicitly, validate every input, check record ownership before returning data, and keep CSRF protection on for forms.
5. Review sudo(). Keep it to the smallest operation and never pass sudo-ed recordsets back to the browser.
6. Test as a normal user. Log in as a restricted employee and a portal user before every release.

For broader design advice, see our complete guide to Odoo custom modules and common customization mistakes.

How Mediod can help

Mediod’s Odoo development team runs source-code security reviews of custom modules: access rights, controllers, SQL and privilege escalation. We then fix what we find or refactor modules ahead of your next upgrade. Short on in-house capacity? You can also hire Odoo developers by the month.

More from our Odoo security series

• Hardening a Dedicated Odoo Server (VPS or On-Premise): An Infrastructure Blueprint
• Odoo.sh Security: What’s Handled for You and What You Still Need to Protect

See all Odoo Security articles →

Frequently Asked Questions

What happens if a custom Odoo model has no access rights?

Odoo denies access to non-admin users and logs a warning. Teams often work around it by granting broad rights, which is where data exposure starts. Define explicit access rights for each group instead.

Is raw SQL safe in Odoo?

Only with parameter binding. Pass values separately (cr.execute(query, params)) or use Odoo’s SQL wrapper. Never build queries with string formatting.

Does Odoo 20 still have record rules?

According to the Odoo 20 release notes, record rules are removed and a domain is added directly on the access right to decide which records it applies to. Existing rules need to be reviewed during the upgrade.

The post Custom Modules and Security Debt: Writing Safe Odoo Apps from Scratch appeared first on Mediod Consulting.

Running Odoo on your own server — a VPS on AWS, DigitalOcean or Google Cloud, or hardware in your own data centre — gives you full root access and complete freedom over the architecture. It also means you carry 100% of the security responsibility.

A new Linux server on the public internet sees automated port scans and password-guessing attempts within minutes. Hardening is not optional. This is the blueprint Mediod uses for self-hosted Odoo. This article is part of our Odoo security series.

Common infrastructure weaknesses

• Open database ports: PostgreSQL listening on all interfaces invites remote password guessing.
• Default SSH settings: password logins on port 22 are the first thing bots try.
• Unprotected database manager: a weak or default master password lets anyone with the URL back up, duplicate or drop your databases.
• Unencrypted local backups: dumps and filestore copies sitting on the same disk, readable by other users.
• Verbose errors: tracebacks and debug mode exposing internal details to visitors.

The hardening blueprint

1. Lock down SSH

Disable password authentication and allow key-based logins only. Disable direct root login, use a named sudo user, and allow SSH only from known IP addresses where you can.

2. Keep PostgreSQL private

In postgresql.conf, set listen_addresses = 'localhost' (or the private network address if the database sits on its own server), restrict pg_hba.conf to the Odoo host, and give the Odoo database user no superuser rights.

3. Harden the Odoo configuration file

• Set a long, unique admin_passwd (the master password).
• Set list_db = False and a dbfilter so the database manager and selector are not public.
• Bind Odoo to localhost and enable proxy_mode when it runs behind a reverse proxy.
• Run Odoo as its own unprivileged system user, and keep the config file readable only by that user.

4. Put Nginx in front

Terminate SSL in Nginx, redirect HTTP to HTTPS, add security headers (HSTS, X-Content-Type-Options, a referrer policy) and rate-limit /web/login to slow down password guessing. Block /web/database from the internet.

5. Add intrusion prevention

Configure fail2ban to watch SSH and Odoo login failures and ban repeat offenders. Enable a host firewall (ufw or firewalld) that only allows ports 22, 80 and 443.

6. Encrypt and test backups

Back up both the PostgreSQL database and the filestore, encrypt them, and copy them to a different provider or location. Restore a backup to a test server regularly — a backup you have never restored is a guess, not a plan.

7. Patch and monitor

Apply OS and Odoo source updates on a schedule, monitor disk, memory and login failures, and alert someone when something looks wrong.

How Mediod can help

Self-hosting needs ongoing DevOps work. Mediod sets up hardened Odoo servers, automated encrypted backups and monitoring, and looks after them through our support and maintenance plans. Moving an existing server? Our migration team can rebuild it on a hardened base.

More from our Odoo security series

• Custom Modules and Security Debt: Writing Safe Odoo Apps from Scratch
• Odoo.sh Security: What’s Handled for You and What You Still Need to Protect

See all Odoo Security articles →

Frequently Asked Questions

Should PostgreSQL be reachable from the internet for Odoo?

No. PostgreSQL should only accept connections from the Odoo server itself, either on localhost or a private network.

How do I hide the Odoo database manager?

Set list_db = False and a dbfilter in the Odoo configuration file, use a strong master password (admin_passwd), and block /web/database at the reverse proxy.

Do I need Nginx in front of Odoo?

For production, yes. A reverse proxy such as Nginx handles SSL, security headers and rate limiting, and Odoo runs with proxy_mode enabled behind it.

The post Hardening a Dedicated Odoo Server (VPS or On-Premise): An Infrastructure Blueprint appeared first on Mediod Consulting.

When a business moves to Odoo.sh, the platform-as-a-service run by Odoo S.A., a lot of infrastructure work disappears: server provisioning, OS patching, SSL certificates and daily backups are all automated. That relief often turns into a risky assumption — that “cloud-managed” means “secure by default”.

Odoo.sh gives you a strong infrastructure foundation. Application security, repository hygiene and who can deploy what are still your team’s responsibility. This article is part of our Odoo security series.

The shared responsibility model on Odoo.sh

• What Odoo.sh handles (infrastructure): hosting and network protection, container isolation, operating-system updates, SSL/TLS certificates, and automated backups of your production database.
• What you handle (application and operations): the quality of your custom modules, who can push to your GitHub repository, where API keys and passwords are stored, which collaborators have access to the Odoo.sh project, and the access rights of every Odoo user.

If you are still choosing a hosting model, our comparison of Odoo Online vs Odoo.sh vs on-premise explains what each option leaves to you.

Common risks in Odoo.sh projects

• Careless staging branches. Staging builds start from a copy of production data. Connecting them to live third-party services, sharing their URLs widely or leaving verbose debug logging on can expose real customer records.
• Weak GitHub accounts. A developer account without multi-factor authentication (MFA) is enough for an attacker to push code that Odoo.sh then builds and deploys.
• Secrets in the repository. Payment gateway keys, API tokens or database passwords hardcoded in module files stay in Git history even after you delete them.
• Forgotten collaborators. Former employees, agencies and CI tools that still hold deploy keys or project access.

Odoo.sh security checklist

1. Protect the production branch. Limit who can push to it, and require reviewed pull requests before merging.
2. Require MFA on GitHub for every member of the organisation that owns the repository.
3. Keep secrets out of Git. Store keys in Odoo’s system parameters or the relevant app configuration on each database, and rotate any key that has ever been committed.
4. Review access every quarter. Remove collaborators, SSH keys and integrations that are no longer needed.
5. Treat staging data as live data. Restrict who can open staging builds and disconnect live payment, shipping and email integrations there.
6. Enable two-factor authentication in Odoo for administrators and other high-privilege users.

How Mediod can help

Mediod’s Odoo support and maintenance team runs Odoo.sh security reviews: branch and collaborator permissions, deployment pipeline, secrets handling and user access rights. You get a short report with the fixes ranked by risk. If your project is built on custom code, our development team can review it too.

More from our Odoo security series

• Custom Modules and Security Debt: Writing Safe Odoo Apps from Scratch
• Hardening a Dedicated Odoo Server (VPS or On-Premise): An Infrastructure Blueprint

See all Odoo Security articles →

Frequently Asked Questions

Is Odoo.sh secure?

Odoo.sh provides a secure, managed infrastructure. Application security still depends on your custom code, GitHub access, how you store secrets and how you configure user access rights.

Who is responsible for security on Odoo.sh?

It is shared. Odoo S.A. runs the infrastructure: hosting, patching, SSL and backups. The customer and their developers are responsible for code, repository access, secrets and Odoo user permissions.

Does an Odoo.sh staging branch contain real data?

Yes. Staging builds are created from a copy of the production database, so they should be protected like production.

The post Odoo.sh Security: What’s Handled for You and What You Still Need to Protect appeared first on Mediod Consulting.

When companies plan an Odoo rollout, one question comes up early: do we really need to pay a full licence for every employee? In most cases the answer is no. Odoo now has four access levels — Portal, Light, User and Administrator — and the new Light User role lets front-line and self-service staff work inside Odoo at a fraction of the cost of a full user.

As an Official Odoo Partner, Mediod Consulting sizes licences for clients every week. This guide explains what a Light User can do, who fits the role, and the settings that quietly turn a Light User into a paid Full user. This article is part of our Odoo 20 series — start with Odoo 20: what’s new and should you upgrade?.

The four Odoo access levels

• Portal user — customers, vendors and partners who log in to your website portal to see quotes, invoices, tickets or timesheets. Free.
• Light User — employees who only handle their own HR tasks or front-line work. Light pricing.
• User — employees who sell, buy, invoice, run projects or manage other people’s records. Full user pricing.
• Administrator — owners, IT staff and key users who configure the database and manage users. Full user pricing.

What a Light User can do

According to Odoo’s pricing page, Light Users get:

• Self-service: My Time Off, My Expenses, My Appraisals, My Attendances, My Referrals and My Planning.
• Front-line tools: Field Service, Inventory Barcode operator, Point of Sale and the Manufacturing Shop Floor.
• Payslips and read-only access to Knowledge articles.

Odoo 20 also lets administrators restrict Light Users to the Barcode module only — useful for warehouse teams who should see nothing else.

What a Light User can’t do

Light Users have no access to core business apps such as Sales, Purchase and Accounting. They can’t create quotes, approve purchases, post invoices, configure projects, customize Odoo or change settings. If someone needs any of that, they need a Full user licence.

Why Light Users save money

Most employees don’t manage the books, send quotes or buy stock. They clock in, request leave, scan boxes or ring up sales. Paying a full licence for those roles rarely makes sense.

• Lower licence costs: pay full price only for people who need full access.
• One system for everyone: no separate HR, attendance or shift tools on the side.
• Tighter security: staff only see what their job requires.
• Predictable growth: hiring more hourly or front-line staff doesn’t multiply your bill at full-user rates.

Example: in a 100-person distribution company, the sales reps, buyers, accountants and managers (say 25 people) need full access. The other 75 — warehouse pickers, drivers, cashiers and technicians — can usually work as Light Users.

How to decide: Light User or Full user?

Ask three questions for each employee:

1. Do they create or approve quotes, orders, invoices, purchases or projects? If yes, they need a Full user licence.
2. Do they configure Odoo or manage other people’s records? If yes, they are a Full user or Administrator.
3. Is their work limited to their own HR tasks or front-line jobs (POS, scanning, shop floor, field service, shifts)? If yes, they fit the Light User profile.

Watch-outs for administrators

• Accidental upgrades: granting a Light User access to Sales, Purchase or another core app automatically makes them a billed Full user. Review access rights before each renewal.
• Employees without logins count: Odoo defines a Light User as any active user marked “Light” or any active employee record not linked to an active non-portal user. Archive leavers and count every active employee when you ask for a quote.
• Getting the licence: Odoo currently provides Light User pricing through a quote from an Odoo advisor or partner, so plan it into your subscription conversation.

To set the role, go to Settings → Users & Companies → Users, open the user and set the Role to Light.

Plan your licence mix before you buy or renew

Light Users arrived alongside a 20–31% increase to the Custom plan, so getting the user mix right matters more than ever. Our Odoo subscription & licensing service maps every role to the cheapest licence that still covers the work, and our guide to optimizing Odoo subscription costs covers the other levers. You can also explore Odoo Employees and HR apps on odoo.com.

More from our Odoo 20 series

• Odoo 20 Is Here: What’s New and Should You Upgrade?
• Mediod Consulting at Odoo Experience 2026: Exploring Odoo 20 AI

See all Odoo 20 articles →

Frequently Asked Questions

What is a Light User in Odoo?

A Light User is an internal user who only uses Odoo for their own HR tasks (time off, expenses, attendance, appraisals, payslips) or front-line work such as Point of Sale, Inventory Barcode, Shop Floor, Planning and Field Service. They cost less than a full user.

Can a Light User access Sales or Accounting?

No. Light Users have no access to core business apps such as Sales, Purchase and Accounting. Giving them access to one of those apps automatically upgrades them to a billed full user.

Do employees without an Odoo login count as Light Users?

Yes. Odoo’s pricing page counts any active employee record that isn’t linked to an active non-portal user account as a Light User, so include every active employee in your licence planning.

How do I set a user as a Light User?

Go to Settings → Users & Companies → Users, open the user and set the Role field to Light.

Source: Light User definition and capabilities from odoo.com/pricing (checked 30 September 2026). Prices and licence terms differ by country and can change — confirm them on your own quote.

The post Odoo Light Users Explained: Cut Licence Costs Without Cutting Access appeared first on Mediod Consulting.

Odoo 20 was unveiled at Odoo Experience 2026 in Brussels, and Odoo has published the full Odoo 20 release notes. They run to hundreds of changes across every app. This guide picks out what matters for a typical business: the new AI agents, accounting and inventory improvements, country updates for Pakistan and the USA, and the changes you need to plan for before you upgrade.

Odoo 20 AI: agents that do the work

The biggest change is how far Odoo’s AI agents can go. According to the release notes, agents can now:

• Create and update records on request, including from an uploaded file of instructions such as a PDF.
• Run inside automations — agents can be triggered by automated and scheduled actions, and you can review how they handled each run.
• Answer questions about a file while you preview it, and accept dictated requests by voice.
• Generate images and buttons for websites and mailings.
• Connect to other tools through the Model Context Protocol (MCP).

Two practical points. First, all AI features now need IAP credits, bought separately from your user licences, so budget for usage. Second, Odoo now lists “Agentic AI” on the Custom plan card, next to Odoo Studio — at the same time as a 20–31% Custom plan price increase. Our Odoo AI guide covers practical use cases, and you can explore Odoo AI on odoo.com.

Accounting: less manual entry, fewer mistakes

• Bill line prediction: when you enter or import a bill, Odoo suggests the product, account, tax and analytic distribution from your bill history.
• Customer invoice reminders can be sent manually or automatically from the Accounting settings.
• Better duplicate detection with two warning levels — red for likely duplicates, yellow for ones to check.
• Bank consistency: every journal entry that touches a bank account must now come from a bank transaction.
• New reports: a bank reconciliation summary, and a Cumulative Translation Adjustment line for multi-currency groups.
• Renamed payment statuses: “In Process” becomes “Paid” and “Paid” becomes “Reconciled” — worth a short briefing for your finance team.
• Expenses: approved expenses now create draft bills that accountants review alongside vendor bills.

See our Odoo Accounting guide or try Odoo Accounting.

Inventory and manufacturing

• Suggested reordering levels: minimum and maximum stock are suggested from demand history, desired days of coverage and order frequency.
• Stock aging report and an improved view of inventory at a past date.
• Landed costs per product, and delivery values that update when a product’s cost changes afterwards.
• Intercompany flows: resupply one company from another and deliver from another company’s warehouse.
• Manufacturing: continuous production across work orders, splitting ongoing manufacturing orders, resetting orders to draft, and provisional vs. real MO cost.
• A redesigned manufacturing-order Kanban grouped by week, with component status and remaining time.

More in our Odoo MRP guide, or explore Odoo Inventory.

Sales, CRM and Point of Sale

• Sales: a dashboard on the quotations list, pricelist rules for specific periods or weekdays, payment-based and manager commissions, and editable margins on order lines.
• CRM: lead generation now uses the Dun & Bradstreet company database, plus new lead rotation rules for sales teams.
• Point of Sale: multiple currencies at checkout, service fees, “snoozing” unavailable products, several printers per POS, and a simplified inventory mode that works without the Inventory app.
• Offline mode: create and edit records while offline.

Retailers can explore Odoo Point of Sale; see also Odoo for retail businesses.

Odoo Studio

Studio gets a new report editor, drag-and-drop ordering of form buttons and tabs, Kanban stage editing from the form view, many-to-many fields in PDF reports and more readable technical names for new fields. Remember that installing Studio moves you to the Custom plan — see Odoo Studio vs custom development.

Country updates: Pakistan, USA and Germany

Pakistan

• FBR e-invoicing integration for registered businesses, in line with S.R.O. 1852(I)/2025.
• FBR integration for Point of Sale for real-time reporting of POS orders — mandatory for Tier-1 retailers.
• A restructured chart of accounts aligned with the Companies Act 2017, and taxes consolidated into sales tax, further tax and withholding tax.
• A “Business Identification Number” field that accepts NTN or CNIC, plus a separate consumer identification field.
• Payroll: payslips include end-of-year income tax adjustments.

Pakistani businesses that relied on custom FBR connectors should review them before upgrading. See our Odoo price increase in Pakistan post and Odoo services in Lahore.

United States

• “Avalara Included” — a new, more affordable AvaTax integration for small and mid-sized businesses in the USA and Canada.
• A redesigned US sales tax report with multi-jurisdiction breakdowns and state summaries.
• Payroll: New York City and Yonkers local taxes; Tennessee, Iowa, Georgia, Mississippi and New Jersey support; qualified overtime deduction rules.

US teams: see Odoo price increase in the USA and our Odoo services in the USA.

Germany

The Odoo 20 release notes list no Germany-specific localization changes. German companies still benefit from the general accounting improvements above; for DATEV and GoBD topics see our Odoo DATEV guide and Odoo services in Germany.

What to check before upgrading to Odoo 20

Several changes affect databases with custom modules or Studio customizations:

• Simplified access rights: record rules have been removed in favour of a domain on the access right itself. Custom security rules need to be reviewed.
• Chatter tracking: stored tracking values have been removed and tracking messages are generated on the fly. Custom reports built on tracking data need checking.
• Icons: Font Awesome has been replaced by Material Symbols, which can affect custom views and website themes.
• Push notifications no longer use Firebase.
• Process changes such as the renamed payment statuses and the removed “Employee Expenses” menu need user training.

Our advice: test the upgrade on a copy of your database first, check every custom module and integration, and train key users on the renamed flows before go-live. Odoo Online databases are upgraded on a schedule set by Odoo, while Odoo.sh and on-premise customers choose their timing. Read our Odoo upgrade guide, or let our Odoo migration team run a test upgrade for you.

Should you upgrade now?

• Starting a new implementation? Starting on Odoo 20 avoids an upgrade later — check that your localization and any apps you rely on are ready.
• On Odoo 19 with little customization? Plan the upgrade once you have tested it on a copy; the new AI and accounting features are worth it.
• On Odoo 17 or older, or heavily customized? Start planning now. Budget time for rewriting custom security rules and reviewing integrations.

Going deeper? Our Odoo 20 series covers each change in detail — Light User licensing, AI agents and credits, payroll, field service, offline mode, direct bill payments and the technical side of the upgrade.

Frequently Asked Questions

When was Odoo 20 released?

Odoo 20 was unveiled at Odoo Experience 2026 in Brussels (24–26 September 2026), and Odoo published the Odoo 20 release notes in September 2026.

What are the main new features in Odoo 20?

AI agents that can create and update records, work from files and run inside automations; MCP connectivity; bill line prediction and automatic invoice reminders in Accounting; suggested reordering levels and a stock aging report in Inventory; continuous production in Manufacturing; and multi-currency checkout in Point of Sale.

Are Odoo 20 AI features free?

No. According to the release notes, all AI features now need IAP credits, which are bought separately from user licences. Odoo also lists Agentic AI on the Custom plan.

Does Odoo 20 support FBR e-invoicing in Pakistan?

Yes. Odoo 20 adds an FBR e-invoicing integration for registered businesses (S.R.O. 1852(I)/2025) and an FBR integration for Point of Sale for real-time reporting, which is mandatory for Tier-1 retailers.

Will my custom modules work in Odoo 20?

Not automatically. Odoo 20 changes access rights, chatter tracking and the icon set, so custom modules and Studio customizations should be reviewed and tested on a copy of your database before you upgrade.

Source: Odoo 20 release notes (odoo.com, September 2026). Feature availability can differ by edition, hosting type and country.

The post Odoo 20 Is Here: What’s New and Should You Upgrade? appeared first on Mediod Consulting.

Odoo has raised the price of its Custom plan in Pakistan from $10.80 to $13.40 per user per month on yearly billing — about 24% more. The Standard plan is still $7.25 and One App Free is still $0. If you run Odoo Studio, more than one company, integrations or Odoo.sh, the change will show up on your next invoice.

Odoo pricing in Pakistan: before and after

Pakistan remains one of the lowest-priced Odoo markets: the same Custom plan costs $61.00 in the USA and €44.90 in Germany. Compare the full picture in Odoo price increase 2026: what to consider.

What it costs in rupees

At an indicative rate of about PKR 280 to the US dollar (your bank’s card rate and charges will differ), yearly list prices work out as follows:

For comparison, 10 users on Standard cost $870 a year (≈ PKR 244,000). Custom is now almost 1.85× the price of Standard per user, so choosing the right plan is the biggest saving available.

Which Pakistani businesses are affected

You pay the Custom price if your database uses any of these:

• Odoo Studio — installing it moves the database to Custom automatically.
• Multi-company — for example a trading company and a manufacturing unit in one database, or separate entities in Lahore and Karachi.
• The external API or custom modules — for example custom connectors for couriers, payment gateways, marketplaces or older FBR digital-invoicing setups.
• Odoo.sh or on-premise hosting.

Good news for FBR compliance: Odoo 20 adds FBR e-invoicing to the standard Pakistan localization and real-time FBR reporting for Point of Sale, which is mandatory for Tier-1 retailers. That can remove the need for a custom connector — and for some businesses, the need for the Custom plan.

Textile, wholesale and distribution businesses in Pakistan often need at least one of these. See how Odoo fits textile manufacturing and wholesale and retail.

Five ways to control your Odoo cost in Pakistan

1. Stay on Standard where you can. If Studio was installed for a few fields, or a second company is no longer used, moving back to Standard cuts the per-user price from $13.40 to $7.25.
2. Audit users. Customers and vendors on the portal are free; staff who only need leave, attendance or expenses may qualify for the new Light User licence.
3. Pay yearly. Monthly billing costs more per user than yearly billing.
4. Plan for the exchange rate. Odoo bills in US dollars; paying yearly locks in the dollar amount for the year.
5. Buy through a local partner. Mediod’s partner discount applies to your Odoo subscription, and support is in your time zone.

Mediod has offices in Multan and serves clients in Lahore and across Pakistan — see Odoo services in Multan and Odoo services in Lahore. For a full budget including implementation, read our Odoo pricing in Pakistan guide and the Odoo implementation cost guide. US readers can see the Odoo price increase in the USA.

Frequently Asked Questions

What is the Odoo price in Pakistan in 2026?

On yearly billing, Odoo Standard is $7.25 per user per month and Odoo Custom is $13.40 per user per month. One App Free is $0 for a single app with unlimited users.

How much did Odoo increase prices in Pakistan?

The Custom plan rose from $10.80 to $13.40 per user per month on yearly billing, about 24%. The Standard plan stayed at $7.25.

Is Odoo billed in rupees or dollars in Pakistan?

Odoo shows and bills Pakistan prices in US dollars, so the rupee amount depends on the exchange rate and your bank’s card charges.

Do I need the Custom plan for FBR e-invoicing in Odoo?

Not necessarily. Odoo 20 adds an FBR e-invoicing integration to the standard Pakistan localization (S.R.O. 1852(I)/2025) and an FBR integration for Point of Sale, so a custom connector is no longer the only route. On older versions, FBR connectors were usually custom modules, which need Odoo.sh or on-premise hosting and therefore the Custom plan.

Is Odoo Community free in Pakistan?

Odoo Community has no licence fee, but you pay for hosting, maintenance and any development yourself, and you do not get Studio, Enterprise-only apps or Odoo’s official support.

Sources: odoo.com/pricing checked on 24 September 2026; earlier prices from archived copies of the same page on the Internet Archive (US, 8 Dec 2025) and (euro, 3 Jan 2026); Pakistan prices as displayed on odoo.com for Pakistan in September 2026. Odoo sets prices per country and can change them at any time — always confirm the figure on your own quotation.

The post Odoo Price Increase in Pakistan: Custom Plan Now $13.40 per User appeared first on Mediod Consulting.

Odoo has raised the price of its Custom plan in the United States from $46.70 to $61.00 per user per month on yearly billing — an increase of 30.6%. The Standard plan stays at $31.10, and One App Free is still $0. Here is what changed, what it costs a US team, and how to decide which plan you actually need.

Odoo pricing in the USA: before and after

Archived snapshots show the change landing between the end of December 2025 and 9 January 2026; every US snapshot since then shows $61.00. The latest update to the page, visible this week as Odoo 20 is announced at Odoo Experience, adds “Agentic AI” to the Custom plan card and introduces a Light User licence.

What it costs a US business now

The same 25-person team on Standard pays $9,330 a year at list price. Custom now costs almost twice as much per user as Standard ($61.00 vs $31.10), so the plan decision is worth more than any other licence saving.

Do you need the Custom plan?

Custom is required if any of these apply — otherwise Standard on Odoo Online covers all Odoo apps:

• Odoo Studio — installing it switches the database to Custom automatically.
• More than one company — common for US groups with several LLCs or a holding structure.
• The external API — needed for most integrations with tools such as Shopify, WooCommerce or a custom app.
• Custom modules, Odoo.sh or on-premise hosting.

If only one of these applies, ask whether there is a standard-feature alternative. For example, a one-off data sync might be handled with import templates, and a few extra fields may not justify Studio. If you need several, Custom is still good value compared with most US ERP suites — see Odoo vs NetSuite.

How US companies can soften the increase

1. Audit users before renewal. Remove leavers, move view-only staff to portal access, and use Light User for employees who only need HR self-service.
2. Stay on yearly billing. Monthly Custom is $76.20 vs $61.00 yearly — about 25% more.
3. Check your renewal quote early. Existing subscribers typically move to new prices at renewal, and the first-year discount ends after 12 months.
4. Consolidate companies where the business allows. Separate entities often need multi-company; dormant ones may not.
5. Buy through a partner. Mediod’s partner discount (below) applies to your Odoo subscription.

Mediod Consulting LLC is registered in Sheridan, Wyoming, and our Odoo services in the USA cover implementation, integrations and support across US time zones. If you are comparing partners, read how to choose an Odoo implementation partner in the USA.

For the global picture, including Germany and Pakistan, see Odoo price increase 2026: what to consider.

Frequently Asked Questions

How much is Odoo per user in the USA in 2026?

On yearly billing, Odoo Standard is $31.10 per user/month ($24.90 in year one for new users) and Odoo Custom is $61.00 ($49.00 in year one). Monthly billing is $38.90 for Standard and $76.20 for Custom. One App Free is $0.

How much did the Odoo Custom plan go up in the USA?

From $46.70 to $61.00 per user/month on yearly billing, an increase of about 31%. The first-year price rose from $37.40 to $49.00.

Did the Odoo Standard plan price change in the USA?

No. Standard has stayed at $31.10 per user/month on yearly billing ($24.90 in year one) and $38.90 on monthly billing.

Does the Odoo price increase affect my existing subscription?

Existing subscribers typically see new prices when the subscription renews, not mid-term. Check your renewal date and confirm the figure on your renewal quotation from Odoo or your partner.

Is Odoo still cheaper than other ERP systems after the increase?

For most small and mid-sized US businesses, yes — the Custom plan includes every Odoo app for one per-user price, while suites such as NetSuite or Dynamics charge per module plus implementation. Compare total cost, not just licences.

Sources: odoo.com/pricing checked on 24 September 2026; earlier prices from archived copies of the same page on the Internet Archive (US, 8 Dec 2025) and (euro, 3 Jan 2026). Odoo sets prices per country and can change them at any time — always confirm the figure on your own quotation.

The post Odoo Price Increase in the USA: Custom Plan Now $61 per User appeared first on Mediod Consulting.

Odoo has raised the price of its Custom plan — the plan you need for Odoo Studio, multi-company, the external API, Odoo.sh or on-premise hosting. Depending on the country, the yearly list price has gone up by 20% to 31%. The Standard plan has not changed in the markets we checked, and One App Free is still $0/€0.

The timing matters: Odoo 20 was unveiled at Odoo Experience 2026 this week, and the Custom plan card on odoo.com now lists “Odoo Studio / Agentic AI” alongside a new Light User licence. Below is what changed in the USA, Germany and Pakistan, what it costs a typical team, and what to check before your next renewal.

Odoo price increase 2026 at a glance

All prices are per user per month with yearly billing, as shown on odoo.com. “First-year price” is Odoo’s introductory rate, which odoo.com says is “valid for 12 months, for initial users ordered”.

Monthly billing costs more: in the USA the Custom list price is now $76.20 per user/month (was $58.40), and in Germany €56.90 (was €46.80). Standard monthly list prices are unchanged at $38.90 and €31.10.

What changed on the odoo.com pricing page

Three things are new, beyond the price:

• “Agentic AI” is now part of the Custom plan description. Odoo positions its new AI agents next to Odoo Studio, so AI-heavy use cases point you towards Custom. See our Odoo AI guide for what the AI features actually do.
• A Light User licence (€7.90 per month in Germany) for employees who only need HR self-service — leave, expenses, attendance, appraisals — plus planning, logging into a Point of Sale session, read-only Knowledge and basic logistics tasks.
• The Standard plan did not move. The gap between Standard and Custom is now much wider, which makes choosing the right plan more valuable than ever.

What the increase costs a typical team

Yearly list prices, so this is what you pay once any first-year discount has ended:

Implementation, Odoo.sh hosting and custom development come on top of licences — see our Odoo implementation cost guide for the full budget picture.

Things to consider before your next renewal

1. Check whether you really need the Custom plan

Odoo moves a database to Custom automatically when you install Studio or add a second company. Custom is also required for the external API, custom modules, Odoo.sh and on-premise hosting. If you only switched to Custom for a couple of Studio fields or a second company you no longer use, going back to Standard can halve your licence cost. Our Odoo Studio vs custom development guide explains the trade-offs.

2. Budget for the end of the first-year discount

Odoo’s introductory price only covers the users you order initially, for 12 months. Year two moves to the list price, and users added later are billed at list price. After this increase, the step up at renewal is larger than many teams expect — we covered why in how to optimize Odoo subscription costs.

3. Move occasional users to Light User or portal access

Warehouse staff who only check stock, employees who only submit leave and expenses, or shop staff who only open a POS session may not need a full licence. Customers and vendors who only use the portal are free. A user audit is usually the fastest saving.

4. Pay yearly, and read your renewal quotation

Monthly billing costs around 25% more per user than yearly billing on both plans. Existing subscribers typically see new prices at renewal rather than mid-term, so check your renewal date and confirm the exact figure on your renewal quote. Our Odoo contract renewal guide walks through what to review.

5. Plan Odoo 20 and hosting together

If you are planning an upgrade to Odoo 20, decide your hosting at the same time: Odoo Online, Odoo.sh or on-premise. The plan you need follows from that choice — compare them in Odoo Online vs Odoo.sh vs on-premise, and see our Odoo migration service if you are moving versions.

6. Compare Community Edition honestly

Odoo Community has no licence fee, but you lose Studio, the Enterprise-only apps, Odoo’s hosting and official support, and you pay for hosting and maintenance yourself. For some teams with in-house developers it is cheaper; for most it is not. See Odoo Community vs Enterprise.

Country details

We break down the local prices, examples and options in two companion articles: Odoo price increase in the USA and Odoo price increase in Pakistan. For Germany, our Odoo services in Germany page covers DATEV and GoBD-ready implementations, and the general Odoo pricing guide explains how Odoo’s per-user model works.

Frequently Asked Questions

Did Odoo increase its prices in 2026?

Yes. The yearly list price of the Custom plan rose by about 31% in the USA ($46.70 to $61.00 per user/month), 20% in euro markets such as Germany (€37.40 to €44.90) and 24% in Pakistan ($10.80 to $13.40). The Standard plan and One App Free did not change.

Is the Odoo Standard plan more expensive now?

No. Standard is still $31.10 per user/month (yearly) in the USA, €24.90 in Germany and $7.25 in Pakistan, with the first-year discount still available for new users in the USA and Germany.

When did the Odoo price increase happen?

Archived copies of odoo.com show the US Custom price changing between late December 2025 and 9 January 2026. The euro and Pakistan increases were visible on odoo.com in September 2026, the week Odoo 20 was announced at Odoo Experience.

What is the Odoo Light User licence?

A lower-cost licence (€7.90 per month in Germany) for employees who only need HR self-service such as leave, expenses, attendance and appraisals, plus planning, POS login, read-only Knowledge and basic logistics tasks.

How can I reduce my Odoo subscription cost after the increase?

Check whether you need the Custom plan at all, pay yearly instead of monthly, move occasional users to Light User or portal access, and review your renewal quotation before signing. Buying through a partner such as Mediod can also lower the price.

Sources: odoo.com/pricing checked on 24 September 2026; earlier prices from archived copies of the same page on the Internet Archive (US, 8 Dec 2025) and (euro, 3 Jan 2026). Odoo sets prices per country and can change them at any time — always confirm the figure on your own quotation.

The post Odoo Price Increase 2026: Custom Plan Up 20%+ — What to Consider appeared first on Mediod Consulting.

When scaling an enterprise, flexibility is everything. The Odoo App Store serves as one of the largest ERP extension ecosystems in the world, giving businesses access to tens of thousands of specialized modules designed to bridge functional gaps without requiring costly custom engineering from scratch.

Whether you need to connect your ERP to local payment gateways, automate regional tax compliance, or deploy custom industry workflows, the Odoo App Store provides a turn-key framework to customize your environment.

1. Thousands of Apps at Zero Additional Software Cost

One of the biggest strengths of the Odoo ecosystem is the vast selection of 100% free apps and extensions.

• Free Community Modules: Independent developers, open-source contributors, and top consultancy firms regularly publish completely free add-ons on the marketplace.
• Core Functional Enhancements: From print format upgrades and field automation to advanced filtering and bulk actions, thousands of utilities can be downloaded directly into your database without monthly subscription fees.
• Budget Optimization: By pairing core open-source modules with free marketplace utilities, businesses can build an enterprise-grade setup at a fraction of standard ERP licensing costs.

If you are looking to run your system cost-effectively, explore our detailed guide on How to Use Odoo Free of Cost: Community, OCA & App Store Tools.

2. Pre-Built Connectors for Seamless Integration

Modern businesses rarely run on a single isolated platform. The Odoo App Store offers hundreds of specialized third-party connectors and integration bridges built to synchronize Odoo automatically with your existing tech stack:

• E-Commerce & Marketplaces: Plug-and-play synchronization for Shopify, WooCommerce, Magento, Amazon, and eBay.
• Payment Gateways & Financial Tools: Connectors for Stripe, PayPal, local banking APIs, and automated statement reconciliation tools.
• Shipping & Logistics Services: Direct integrations with DHL, FedEx, UPS, and local fulfillment logistics networks.
• AI & External Services: Emerging AI bridges, such as Model Context Protocol (MCP) servers, that connect AI models directly to your Odoo database.

Before deploying third-party connectors into your production instance, make sure you understand the initial download and setup options by reading our article on How to Download Odoo: Official Repositories, ZIP & Git Clone Methods.

3. Developed by Industry-Leading Gold & Silver Partners

Quality, stability, and maintainability are critical when installing third-party code. The Odoo App Store features software created by certified Odoo Gold Partners, Silver Partners, and recognized open-source maintenance groups like the Odoo Community Association (OCA).

Choosing apps developed by certified partners gives you several key advantages:

• Standardized Architecture: Built following Odoo’s official technical guidelines to prevent database conflicts.
• Regular Version Updates: Maintained and upgraded alongside official Odoo version releases.
• Proven Security Standards: Checked for stability and performance before being deployed in live enterprise environments.

4. Explore Verified Modules by Mediod Consulting

At Mediod Consulting, our engineering team builds custom, high-performance Odoo modules crafted to solve complex operational challenges. From localized compliance extensions to specialized workflow automation tools, our solutions are engineered for stability, speed, and seamless adoption.

Browse our official catalog of published apps and integrations directly on the marketplace:

Explore Mediod Consulting’s Odoo Apps Catalog

Ready to Elevate Your Odoo Implementation?

Installing the right apps is only half the equation—ensuring they fit your business processes without causing technical debt is what creates long-term success.

Whether you need help selecting marketplace modules, building a proprietary connector, or planning your upcoming Odoo rollout, our expert consultants are here to help.

Planning to visit Odoo Experience? Read our update on Mediod Consulting at Odoo Experience 2026 and book a 1-on-1 strategy meeting with our leadership team in Brussels!

Contact Mediod Consulting Today for a Free Consultation

The post Odoo App Store Guide: Free Apps, Connectors and Community Modules appeared first on Mediod Consulting.

Every active internal user in Odoo directly impacts your monthly software bill. Conducting a periodic user audit allows you to reclaim unused licenses, reassign roles to free Portal access, and eliminate license bloat prior to your annual subscription renewal.

Use this operational checklist to perform a full backend user audit across your organization.

1. Export & Inventory All Active Users:Prerequisite: Settings Access (Access Rights Administrator).

Navigate to Settings > Users & Companies > Users in your Odoo database. Filter by Internal Users and export the list to CSV/Excel with the following fields:

• Name, Login / Email
• Access Rights / Groups
• Last Connection Date (latest_execution_date or connection logs)
• Created On date

2. Identify & Archive Inactive or Dormant Accounts:Target: Zero login activity in past 60–90 days.

Filter your exported sheet by Last Connection Date:

• No activity > 90 days: Contact line managers to confirm offboarding status. If departed or no longer needing backend access, Archive the user immediately.
• Generic / Shared Accounts: Identify accounts like sales@company.com or warehouse1. Convert shared credentials into distinct named users or move shared operations to public/portal workflows to prevent compliance issues.
• Note: Archiving a user preserves all historical records, chatter comments, and document audit trails while freeing up a paid backend slot.

3. Reclassify Operational Roles to Free Portal Access:Target: Staff needing read-only or self-service access.

Odoo Portal Users are 100% free and do not count toward your paid internal license count. Audit current internal users against these operational rules:

• Contractors & External Vendors: Should be converted to Portal Users with access to Purchase Orders, Invoices, and Task Tracking.
• Field Staff & Light Requesters: Employees who only submit expense reports, request time off, or check project status can often be shifted to Portal or self-service interfaces rather than full backend internal accounts.
• Customers / B2B Clients: Ensure client contacts are strictly set to Portal / Contact access and not accidentally created as internal users.

4. Consolidate Administrator & API Service Accounts:Target: System integration & service endpoints.

• Review third-party API integrations (e.g., e-commerce connectors, shipping integrations, custom external apps).
• If an integration requires an internal user login, evaluate whether API keys can be grouped under a single dedicated system integration account rather than maintaining separate paid licenses for each secondary connector.

5. Adjust Odoo Subscription User Count:Final Action: Lock in savings with Odoo / Partner.

Archiving users in your Odoo database stops internal access, but your billing user count must be adjusted separately on your subscription contract:

• Log in to your account portal at odoo.com/my/subscription.
• Update your active user count to match your newly audited total prior to your upcoming contract renewal window.
• If purchasing through Mediod Consulting, send your revised active user count to your dedicated account consultant to update your subscription agreement.

Quick Reference Matrix: Internal vs. Portal User

As an official Odoo Partner, Mediod Consulting acts as an intermediary and strategic advisor between businesses and Odoo S.A. Rather than treating annual contract renewals as a routine administrative task, Mediod helps organizations audit usage, right-size infrastructure, and structure long-term licensing agreements to protect against unnecessary cost creep.

Mediod Consulting assists companies through four key phases of the renewal cycle:

1. Pre-Renewal Usage & License Auditing

Before entering contract discussions, Mediod conducts an internal system audit to identify hidden cost drivers:

• Active User Right-Sizing: Uncovering inactive backend accounts or reclassifying light operational roles (such as suppliers, field staff, or client requesters) to free Portal User access, reducing total paid user counts.
• Standard vs. Custom Plan Alignment: Evaluating whether your organization truly requires Odoo’s Custom Plan (required for Studio, multi-company setups, external APIs, or custom hosting) or if your database can be streamlined onto the lower-cost Standard Plan.

2. Strategic Contract Structuring

Mediod helps structure contract terms to minimize rate fluctuations:

• Multi-Year Rate Locks: Assisting businesses in negotiating multi-year commitments (e.g., 3-to-5-year contracts) prior to major upgrade cycles or regional price adjustments. This locks in baseline user rates and protects against annual renewal increases.
• Co-Terming & Add-On Alignments: Structuring user expansion seats and secondary module licenses under a unified, co-termed renewal date so mid-year additions don’t trigger unexpected pro-rated charges or multi-invoice confusion.

3. Partner-Assisted Advocacy & Co-Negotiation

As an accredited partner, Mediod works directly alongside Odoo’s official account managers:

• Tiered & Volume Discounting: Leveraging partner ecosystem channels to advocate for volume-based pricing or retaining grandfathered promotional rates for growing teams.
• Hosting & Infrastructure Optimization: Helping evaluate hosting costs (Odoo Online vs. Odoo.sh vs. self-hosted cloud on AWS/DigitalOcean) to ensure you aren’t overpaying for server resources or staging environments.

4. Hybrid Architecture Advisory (Community vs. Enterprise)

For companies facing steep enterprise license scaling costs, Mediod provides architectural options:

• Selective Hybrid Deployment: Advising on whether certain non-critical modules can be offloaded to high-quality, open-source Odoo Community Association (OCA) tools or third-party marketplace apps, keeping your core Enterprise user footprint lean and cost-effective.

The post Odoo Contract Renewal: User Audit Checklist to Cut License Costs appeared first on Mediod Consulting.