feliXart
All articles

A packaged ERP or a custom build?

This gets argued as “which is better”. That is the wrong question. The right one is which job you give to which.

Miktad Tahir Durak · Published: 31 August 2026

The short answer

For accounting, invoicing and statutory reporting, packaged products are strong and they carry the burden of tracking regulation; commissioning custom software there is unnecessary for most companies. The difference appears in operations: where production, warehouse, dealer or field flows depart from the sector norm, bending the package to fit creates customisation debt. The common answer is to run both.

01

What do packaged products do well?

Accounting, invoicing, filings and statutory reporting. What these have in common is that the rules are set by the state rather than by you — e-invoicing and tax legislation change every year, and following those changes is a job in itself.

That is where the real value of a package sits. When regulation changes the update arrives from the vendor, your accountant already knows the screen, and staff who can run it are easy to find. Commissioning custom software for this side is money badly spent.

02

Where does customisation debt start?

In operations. Where your production flow, warehouse layout, dealer pricing or field service arrangement departs from the standard, the package has to be bent to fit — through extra modules, custom development or a consultant.

The cost is invisible on day one. Every version upgrade means retesting and often rewriting those changes. That is customisation debt, and the interest is paid annually.

Off-the-shelf or custom?

03

How should cost be compared?

The licence fee alone misleads. Compare across five lines and over several years: licences or per-user subscription, annual maintenance and upgrades, customisation and consultancy, training, and integration.

Of those five, the third is what surprises people. Licensing is transparent and predictable; customisation and consultancy vary from project to project and often exceed the licence itself.

04

Can you run both?

That is the common answer. Accounting and statutory reporting stay in the package; production, warehouse, a dealer portal or field work — the flows particular to the company — are built separately, and the two talk through integration.

It works on one condition: the integration is designed at the start. If which record is born where and which way it flows is unclear, the two systems produce two truths, and at that point neither can be trusted.

System integration

05

What question settles it?

One is enough: at how many points will we have to change this package? If the answer is “a few screens”, the package is right and the discussion ends there.

If the answer is “the order flow, pricing and production planning”, you are buying custom software anyway — only inside a package, through a consultant, and for more money.

Frequently asked

Which product do you recommend?

We do not recommend products; on that side the right people to ask are your accountant and financial adviser. Our job is the operations side the product cannot cover, and making the two talk.

Do we have to replace our current ERP?

Usually not. Replacing a working accounting system is risky and often unnecessary; building the operations side separately and integrating it carries less risk.

Does an open-source ERP make sense?

Customisation is flexible, but maintaining those customisations stays with you. Licence cost falls while technical responsibility rises — a trade that works badly without a team of your own.

Written by

Miktad Tahir Durak

Founder, feliXart

Founded feliXart in Kayseri in 2013. He took the company from a VR/AR studio to one building enterprise software and AI integration. He has spoken by invitation at universities and served on the jury of artificial intelligence competitions.

About us

Let’s talk about where you are.

Tell us what you want to build — and we will say so plainly if you do not need it.