01
Community-based custom ERP
Evaluate when you want a tailored operational system and can agree responsibility for hosting, support and upgrades. Request the exact module list and third-party licence terms.
Plan / ERP buyer series
Custom ERP or Odoo Enterprise: what are you actually buying?
Braincuber offers two separate routes: a Braincuber-branded custom ERP based on Odoo Community, and an Odoo Enterprise implementation. Choose by demonstrated workflow fit and lifetime ownership—not by assuming that open-source software removes delivery costs or that an Enterprise subscription includes every implementation task.
Discuss my ERP scope See the buying checklist
No purchase commitment. Submitting an enquiry does not book a meeting.
Which path fits your situation?
02
Odoo Enterprise
Evaluate when the proposed Enterprise apps meet your needs. Confirm the subscription, deployment option and edition-dependent requirements directly in the quote.
03
Wait for a fit-gap review
If neither proposal demonstrates your critical workflow, defer the edition decision. Buying licences does not resolve an untested operational gap.
Put the decision in writing
Use the same requirements for every proposal. Record what is included, what needs validation and who owns unresolved work.
| Contract question | Custom ERP proposal | Enterprise proposal |
|---|---|---|
| What is included? | Named Community and third-party modules plus scoped custom work. | Named apps, subscription plan, configuration and scoped extensions. |
| Who runs it? | Named hosting, backup, patching and incident owners. | Responsibility split between Odoo, hosting provider and implementation team. |
| What happens at upgrade? | Price and acceptance checks for modules, data and integrations. | Clarify standard upgrade coverage versus custom-code and integration work. |
| How do we leave? | Document exports, source access where agreed and handover obligations. | Document data exports, subscription conditions and custom-work handover. |
Swipe the table sideways to compare all columns.
Require the same acceptance scenario
Bring one transaction that crosses your most difficult boundary. For EPC, it may be a purchase whose value exceeds the remaining project budget. For cosmetics, it may be a batch that fails quality checks after packaging has been reserved. Ask both teams to demonstrate the proposed solution with user permissions. Classify each step as standard, configuration, third-party integration or new development.
Separate branding from licensing
A branded implementation is not a different licence for the underlying software. Ask the provider to identify the components supplied, the rights attached to each and the maintenance obligations. Do not assume Enterprise-only modules are included in a Community-based product. Your written agreement should distinguish ownership of business data, rights to custom deliverables and access needed for a future support handover.
Budget for a supported system
Compare the first year and subsequent years separately. The proposal should identify implementation, migration, subscriptions where applicable, hosting, backups, support and upgrade testing. An inexpensive licence can still lead to an expensive operating model if every change requires unsupported custom work. Choose the smallest maintainable scope that satisfies your acceptance checks, with a clear process for later changes.
From comparison to a scoped proposal
Bring one workflow.
Ask better questions.
Braincuber offers Community-based custom ERP and Odoo Enterprise implementation. We will review fit, gaps and responsibilities before proposing delivery. Bring anonymised examples—not confidential records.
Request a scoped discussion
Questions before you commit
Is Community-based ERP free to implement?
No. Software licensing and implementation are different cost categories. Configuration, hosting, migration, training and support still require work.
Does Enterprise mean there will be no custom work?
No. Validate the fit before signing. Industry rules, connectors and reports may need additional configuration or development.
Can we change editions later?
Possibly, but treat it as a migration assessment. Data, custom modules, third-party dependencies and licensing must be reviewed first.
Sources and how to use this guide
Braincuber sells ERP implementation services. Product statements refer to the vendor sources below; the evaluation scenarios and recommendations are our analysis. Verify the current edition and commercial terms in your written quote. We have not assigned independent ratings, tested every configuration or invented customer results.
- Odoo plans and exclusions
Check your country, billing term, renewal terms and implementation exclusions before budgeting.