⚙ Odoo Community implementation & managed hosting
Odoo classifies third-party modules as “custom code” for its per-line maintenance fee, not just the code someone writes for you. Install the open-source modules that make Odoo do your job and the meter starts running. We implement the same stack on Community, on a server you own, and keep it patched, monitored and backed up.
Odoo’s maintenance fee is charged per 100 lines of custom code per month. The part that surprises people: modules you did not write count too, including the free, community-maintained OCA modules that close most of Community’s gaps. An OCA-heavy build is therefore almost entirely “custom” by Odoo’s own definition, and the fee scales with every module you add.
So we measured one. Below is a real equipment-and-service build: field service with equipment tracking, recurring contracts, and the financial reports Community leaves out. OCA repositories at branch 19.0, counting .py, .xml, .js and .css, tests excluded.
| Module group | Lines |
|---|---|
| fieldservice plus equipment_stock, equipment_warranty, sale, stock, account, recurring, agreement, sale_agreement | 8,145 |
| contract and contract_sale | 4,391 |
| account_financial_report | 12,831 |
| account_usability | 420 |
| Total, before a single line of bespoke work | 25,787 |
Measured August 6, 2026. Add the bespoke module such a build needs, roughly 1,500 to 3,000 lines, and you land at 27,000 to 29,000.
Odoo’s published rate runs about $13 to $18 per 100 lines per month (€12 to €16 in their own forum answers, $18 per 100 reported by customers). Multiply it out:
That is on top of per-user Enterprise licensing, and it buys maintenance of code that is already free and already maintained by the community that wrote it.
You can decline the per-line maintenance fee by owning the code repository. It is a real option and any honest version of this argument has to say so. But declining means Odoo will not maintain or upgrade that code, so you self-maintain it regardless, which is most of what Odoo.sh was being paid to do in the first place.
Either the fee is charged and the number above is absurd, or it is declined and Odoo.sh has lost its reason to exist for an OCA build. That is the whole argument. It does not need to be exaggerated, and we would rather you hear it here than from a sales call where it lands as a gotcha.
Check it yourself, it takes ten minutes. Clone the OCA repositories your build needs at your target branch, count the non-test source lines, multiply by the rate. A vague “open source is cheaper” becomes a specific number you can put in a budget, and we will happily run that count for your module list before you commit to anything.
Enterprise seats are licensed to the subscribing company. If you are planning franchises, multiple locations under separate entities, or a white-label rollout, that is a structural problem on Enterprise, not just a cost one. Worth settling before you sign, not after.
Enterprise runs $31 to $47 per user per month. Self-hosted Community is flat: the eleventh user costs what the tenth did, which is nothing. Hiring stops being a line item in your ERP budget.
MRP core ships in CE: Manufacturing Orders, multi-level BoMs, Work Centers, routing, Work Orders, subcontracting. Only barcode shop floor, Quality, MPS, PLM and IoT are Enterprise-gated. Most prospects assume manufacturing forces the upgrade. It does not.
For equipment-centric businesses, OCA fieldservice outruns Enterprise’s own FSM plus Maintenance: equipment auto-created from a serialized delivery, native warranty tracking, sale-agreement linkage. The install is the start of the service relationship, and the software should know that.
Community is not Enterprise with the price removed. Four real losses, and what we do about each. If any of these is a dealbreaker for you, we would rather find out in the first call than in month four.
Six phases, in order, each ending in something you can look at. Nothing is billed against a phase you have not signed off.
We sit with the people who will use it and map the actual workflow, not the org chart. Output is a written scope: what gets built, what gets configured, what deliberately stays out. Surprises belong here, where they are cheap.
Production and staging servers, Odoo Community, PostgreSQL, TLS, automated backups, monitoring. Hosting is billed at cost on an account you own. We do not mark up infrastructure, and a typical 3 to 6 user deployment runs $40 to $60 a month all in.
Chart of accounts, products, pricing, users and access rights, plus the OCA modules your scope calls for, wired together and tested against real scenarios from Discovery.
The part no module does yet, built as a clean Odoo module in your repository. Owned by you, upgradeable, and reviewable by anyone who comes after us.
Customers, vendors, products, open balances and history moved and reconciled, written documentation for your team, training, then cutover with hands-on hypercare through the first live weeks.
Up to four hours of free follow-up within 90 days of go-live for questions and guidance, after the paid hypercare above. Then an ongoing tier, or nothing at all, as you prefer.
Keeping it running.
The build is quoted as a project. What happens afterward is your choice of three, and one of them is free.
You run it, we answer the phone
The honest minimum for a server in production
Everything above, plus a person who knows your build
Not ready to talk? Leave your address and we send the Odoo Implementation Playbook: nine plain-language articles on what Enterprise actually buys you, which gaps close for free, and where paying is worth it. One follow-up from a human, no spam.
No spam, unsubscribe anytime. See also AI for Community books and our own build.
Tell us what you are running, or what you were quoted, and we will run the same line count against the modules your build actually needs and send back the arithmetic. No charge, and no obligation to hire us afterward. If Enterprise is genuinely the right answer for you, we will say so.
Get the count for your buildor email [email protected]