A standard module is cheaper as long as it does what you need and its maker keeps maintaining it. It becomes more expensive the moment you have to adapt it, the moment it touches other parts of your system, or the moment the maker stops — and you only find that last one out at the next update.
Always start with the module
This article is not an argument for bespoke work. For most questions there is a module that solves it for a couple of hundred euros, and then that is the answer. We say so even when it costs us revenue.
The question is not "does a module exist" but "does that module fit what I actually do". That distinction costs people money.
The four cases where a module works out more expensive
- You have to adapt it. From that moment on you cannot update it without losing your change.
- It touches your back office. Modules that reach deep can make other screens unusable.
- You need three of them to do one thing. Three modules are three updates and three makers.
- The maker is unreachable. Check when the last update appeared before you buy.
An example from practice
At an importer we wanted to use a carrier's official module for shipping labels. On paper exactly right: made by the carrier itself, free, maintained.
After installation the product edit page in the back office stopped working. That is not a fringe effect — that is the screen the client sits in every day. We advised against the module and built our own integration that only does what was needed.
How to test it beforehand
- Install on a test environment, never straight onto live.
- After installing, walk through the screens you use daily, not just the feature you were after.
- Check how long ago the last update was and whether it supports your current major version.
- Ask what happens if you want to remove it again later.