If you’ve ever experienced Odoo "hanging" while trying to confirm an order, or seen a spinning loading icon during a busy warehouse shift, you’ve likely hit a worker limit.
In the Odoo ecosystem, "How many workers do I need?" is the million-dollar question. Provision too few, and your business processes grind to a halt. Provision too many, and you are burning your IT budget on idle CPU cycles.
To scale Odoo effectively, you need to understand exactly what a worker is and how to calculate your requirement based on two factors: Internal Concurrent Users and External Website Traffic.
What Exactly is an Odoo Worker?
Think of an Odoo worker as a dedicated digital employee sitting inside your server. Their only job is to process requests.
When an employee clicks "Print Invoice" or a customer loads a product page on your website, that request goes to the server. A worker picks it up, does the "heavy lifting" (talking to the database, generating the PDF, etc.), and sends the result back.
Workers are finite: One worker can only handle one "heavy" request at a time.
The Queue: If all your workers are busy and a new request comes in, that request sits in a queue. This is when users start complaining that "Odoo is slow."
The Two Golden Rules of Calculation
At Skysize, we use two primary metrics to help our clients "right-size" their subscription.
1. The Internal User Rule (The 1:25 Formula)
For standard back-office operations (Accounting, CRM, Inventory, Manufacturing), the gold standard is:
1 Worker per 25 Concurrent Users
Important: "Concurrent" does not mean "Total Employees." It means people actively clicking and loading pages at the exact same moment. Usually, only about 15–20% of your total staff are sending a request to the server at the exact same millisecond.
2. The Website Traffic Rule
If you run an Odoo eCommerce store, your internal staff isn't the only load on the system. You must account for "Public" workers.
1 Worker per 5,000–10,000 Daily Visitors (Depending on complexity)
Real-World Examples
To help you visualize where your business fits, let’s look at three common scenarios:
Scenario A: The Professional Services Firm
Team Size: 50 staff members (Consultants and Accountants).
Usage: Heavy CRM and Billing, but no eCommerce.
Calculation: 50 users / 25 = 2 Workers.
Recommendation: A 2-worker subscription is perfect here. The load is predictable and entirely internal.
Scenario B: The Growing E-commerce Brand
Team Size: 10 staff members (Warehouse and Admin).
Traffic: 15,000 website visitors per day.
Calculation: * Internal: 10 users = <1 worker (Round up to 1).
Website: 15,000 visitors / 5,000 = 3 workers.
Total: 4 Workers. * Why? Even though the staff is small, the website traffic requires dedicated "lanes" so that a customer browsing the shop doesn't slow down the warehouse team’s barcode scanners.
Scenario C: The Mid-Sized Manufacturer
Team Size: 200 staff members.
Traffic: Minimal (B2B portal only).
Calculation: 200 users / 25 = 8 Workers.
Recommendation: High-intensity internal environments need more workers to prevent "blocking" during heavy data processing like MRP (Manufacturing Resource Planning) runs.
Why Subscription-Based Scaling Works Better
In the past, companies tried to "guess" their needs and hoped for the best. At Skysize, we’ve moved to a predictable subscription model. By calculating your worker needs upfront based on your real-world data, you get:
Fixed Costs: No surprise bills when you have a busy month.
Guaranteed Resources: Your workers are reserved for you. You aren't "fighting" other companies for CPU power on a crowded shared server.
Simplified Growth: As your team grows from 25 to 50, you simply move up one tier.
Stop Guessing, Start Performing
The goal of Odoo is to make your business more efficient, not to give you a headache every time you look at a loading screen. By right-sizing your workers, you ensure that your software moves as fast as your team does.