- Home
- Arend Digital
- Custom or not?
Custom or not? Standard first.
Almost every company thinks its way of working is unique, and sometimes it is. But custom code in the database of your business software is rarely the answer. We choose standard first, then an integration outside the system, and anything else only as a last resort.
Why we do not put code in your database
Custom code sounds flexible: the system does exactly what you want. The trouble comes later. Every change to the core of your business software has to be re-examined with each new version. When the change no longer fits, you fall behind, or you pay to have it rewritten.
So we follow one fixed rule: what does not fit the standard settings is not built into the system itself. The missing piece lives in a separate layer next to your business software and talks to it through the API.
- Upgrades remain feasible, even years later
- Maintenance is predictable and does not depend on a single developer
- Your data stays in a standard structure that any party can understand

Three ways to meet a requirement
The same wish can be solved in three ways. These are the consequences, in broad terms.
| Configure standard | API integration | Custom code in the database | |
|---|---|---|---|
| Upgrades | Run smoothly | Remain possible, the integration is checked | Every upgrade becomes a separate project |
| Maintenance | Low | Medium, in a separate layer | High and dependent on the builder |
| Flexibility | Limited to what the system offers | Large | Large, but with a price later on |
| Risk | Small | Manageable | Being stuck on an outdated version |
“Meeting a wish is not the same as building a solution you can still work with in three years.”
Five questions before you have anything built
Work through these questions in this order. Usually the decision falls at the first or second.
- Can a standard setting solve it? Check the options the system already has. Often a field, a rule or a workflow covers the wish.
- Can we simplify the process itself? Sometimes the process is too complicated, and changing the process is better than changing the software.
- Does an integration or standard module already exist? That is usually cheaper and better maintained than something new.
- Can it live outside the system? A separate tool that talks through the API leaves your core untouched.
- Is it a real competitive advantage? Only then is special development justified, and still outside the database.
Development we do recommend
No custom code in the database does not mean everything has to stay standard.
Integration with your own system
Your till, production machine or specialist package gets a connector that exchanges data without touching the core.
A dedicated screen or portal
A customer portal or order screen for your dealers, with special logic, running alongside the system.
Automating a fixed process
A task that is the same every day, such as importing feeds or checking documents, can live in a separate service.
Read next
Odoo
What Odoo is, which apps and hosting options exist, and how we set it up as standard and upgrade-ready, with no custom code in the database.
Read more Arend DigitalSoftware & integrations
Webshop, till and supplier integrations, process automation and dashboards, so data is only ever entered once.
Read more Arend ConsultingProcess audits & transition
A down-to-earth review of your order flow, stock, invoicing and customer follow-up, with an action plan and support for the digital step.
Read moreGet in touch, no obligation
Tell us briefly where you stand. We reply personally, usually within one working day.
- Phone+32 (0)491 91 81 95
- Email[email protected]
- AddressCreyboschlaan 28, 2520 Ranst (Belgium)