THE CENTRAL IDEA
Turn each workflow into an input, role and expected-result test, then compare configuration, customization and custom development. Includes an original downloadable worksheet.
Describe the workflow before choosing a module
Describe a business example without personal data: purchase request, manager approval, partial receipt, then invoice matching. Name the owner of each step and the exception that stops it. A list of modules does not establish that the required process is supported.
Classify fit using evidence
Classify each requirement as configuration, customization, integration, custom development or unverified. Link the decision to a test-environment screenshot or recorded scenario, and record the Odoo version, edition and modules. Do not turn an unverified item into a fit percentage.
Account for the cost of a gap
Customization entails development, testing and upgrade work. Check whether adjusting the workflow is simpler than changing the system. Compare effects on data, permissions, maintenance and exit options, then define the first release.
Set a release acceptance condition
Educational example: a buyer can prepare a request, cannot approve it without permission, and partial receipts retain their original line relationships. Test rejection, return and repeated imports. The worksheet supports discovery; it does not establish a client Odoo delivery or partner status.
EDUCATIONAL EXAMPLE / REVIEWABLE STEPS
Apply the method to illustrative data
The materials below are original educational examples, not client data or commercial delivery results.
- Read the assumptions and define success before testing.
- Test a valid case and an exception, then record the difference.
- Do not transfer the result to your project without testing its data and permissions.
ORIGINAL RESOURCE / EDUCATIONAL EXAMPLE
Try the method and keep the file
Version 1 — 7 September 2026. Synthetic data only, without submission or connection to a client system.
Download the worksheet (CSV)Fill in version, edition, evidence and owner for each requirement before accepting fit. Unverified cells receive no score.
Compare fit, not popularity.
Odoo configuration
Fits: The workflow is supported by tested configuration and modules.
Consider: Record version, edition and permissions in scope.
Customization or integration
Fits: A specific gap can be isolated and tested.
Consider: Upgrade cost and integration limits.
Custom ERP
Fits: Core business rules do not fit tested alternatives.
Consider: Responsibility for the entire system lifecycle.
This is decision support, not a service offer or a performance guarantee. Your final choice depends on your requirements and the versions selected at implementation.
Official sources for further reading
Odoo 19.0 — Export and import dataopens in a new windowSources describe technology characteristics. The scenarios and trade-offs are contextual guidance, not benchmark results.