An OCA module tends to fit very well when the use case is mature, a branch exists for your version, and the implementation does not need much customization. A custom module usually wins when the local market needs more refinement, stronger support, or a tighter flow for a specific carrier.
When OCA usually wins
- The use case is fairly standard.
- The community maintains the branch well.
- You want flexibility and full code transparency.
When a custom module usually wins
- The functional gap in OCA is clear.
- You need direct support from the developer.
- You want less adaptation work and less operational ambiguity.
Useful links
OCA serviceSee how we implement open-source modulesCustom modulesReview the custom-module approachLogistics consultingChoose the architecture before building
What we do about this
Want to choose the right architecture?
We can decide with you whether OCA, a custom module, or a mix is the best fit.