Off-the-shelf ERP or custom software? A neutral decision matrix
Logo, Mikro, Netsis or SAP is already installed, but at some point you say "this process doesn't fit the package". This page will not sell you a package, and it will not push custom software on you either. It sets out which decision is right in which situation along the axes of cost, integration, process fit and lock-in, and it ends with the third way that works for most businesses: the existing ERP stays where it is, and a measured custom layer goes on top.
The question is not "which is better" but "which is right for you"
Off-the-shelf ERP and custom software are not rivals; they are two different tools that each do a different job well. Packages such as Logo Tiger, Mikro, Netsis and SAP Business One bring decades of accumulated references, ready-made regulatory compliance (e-invoicing, e-ledger, social security reporting) and a wide dealer network. Custom software, by contrast, can model the distinctive flow of the business exactly as it is, without forcing it into the standard mould the package imposes.
In practice, the wrong question costs a great deal of money. A business that asks "which is the best ERP" ends up having to fit its own process differences into the package's standard flow, and that adaptation usually comes back as a 'customisation' line on the invoice. A business that says "let's have everything written from scratch" tries to reinvent the work the package gives it for free: accounting, e-invoicing and statutory reporting.
The right approach clarifies one thing first: is this process standard in the sector, or is it a distinctive flow that is the source of your competitive advantage? What is standard is solved with a package; what sets you apart is solved with custom software. The matrix below reduces that distinction to seven concrete criteria.
By criterion: off-the-shelf package or custom software
No single row decides the matter; look at all seven criteria together, since their weight differs from business to business. The assessment below is indicative and based on general market tendencies, not a firm quote.
| Criterion | Off-the-shelf package (Logo/Mikro/Netsis/SAP) | Custom software |
|---|---|---|
| Cost / TCO | Low to start with; TCO builds over time through annual per-user and per-module licences plus customisation items | Higher initial investment; no licences, cost is set by scope and maintenance; can be more predictable over the long run |
| Implementation time | Fast; goes live relatively quickly on ready-made modules and a familiar rollout path | Longer; requires analysis, development and testing, in direct proportion to scope |
| Sector / process fit | Fits standard processes very well; with a distinctive flow you have to adapt the process to the software | Modelled exactly on the process; works without breaking the logic of the business |
| Integration | Common integrations come ready; with unusual systems you can hit the limits of the package | Designed around the need; connects flexibly to points such as e-invoicing, banks, the production line and marketplaces |
| Scalability | Scales well within a given structure; the package architecture may limit the way you grow | Built around the way your business model grows; the limit is set by your own design |
| Lock-in | Dependence on the vendor and its dealer; licences, versions and the roadmap are under their control | You own the code and the data; dependence on the developer is managed through the contract and documentation |
| Regulatory compliance | Regulation such as e-invoicing, e-ledger and social security comes ready and continuously updated; a genuine strength | You have to keep up with regulation yourself; this burden should usually be left with the package |
When an off-the-shelf package is the right choice
If most of the following describe you, an off-the-shelf ERP is very probably the healthiest and most economical choice. You do not need custom software.
- Your processes are close to the sector standard; you have no distinctive operational flow that sets you apart
- Speed is the priority: you want to move to a proven, working system in a short time
- Accounting, e-invoicing, e-ledger and social security compliance are critical for you, and having them ready is the greatest relief
- Your team is small; you want to deal with the business itself, not with managing software
- It suits you to plan the budget as a predictable annual licence rather than a large upfront investment
- Your needs are largely met by the package's standard modules, and your customisation list is short
When custom software is the right choice
If the following signs are piling up, the package is slowing you down. Here custom software is not a cost but an investment in recovering the productivity you are losing.
- You are distorting the way you work in order to squeeze a critical process into the package, patching it with Excel files and manual steps
- Your competitive advantage comes precisely from the distinctive workflow the package is trying to standardise
- Customisation quotes from the dealer pile up with every new requirement, and the TCO quietly inflates
- Integration with a system the package does not support (a bespoke production line, an unusual marketplace, a device, a sensor) is unavoidable
- You want full control over your data and your process knowledge; dependence on the vendor is a strategic risk
- The way you grow does not match the structure the package assumes; the system constrains you as you get bigger
The real answer for most businesses: keep the package, add a custom layer on top
The decision is usually presented as a binary choice, but in the field it is most often resolved on a third path. Your existing ERP (Logo, Mikro, Netsis or SAP) does its own job well: accounting, statutory reporting, regulatory compliance. The problem starts where the package is pushed to cover the entire operation. In that case the right move is not to replace the ERP but to leave it in place and add a custom layer at the operational point where it falls short.
In this hybrid model the ERP remains the system of record and the regulatory backbone; work that does not fit the package, such as shop-floor operations, production tracking, dealer/B2B ordering, custom reporting or marketplace integration, is handled in the custom software layer. The two systems talk through integration: the custom layer reads data from the ERP, produces its own and writes it back. That way you keep the proven infrastructure of the package and gain the flexibility of your own process.
The advantage of this approach is that it caps both the cost and the risk. Instead of ripping out the whole ERP and rewriting it, you invest only in the narrow area that genuinely causes trouble; the regulatory burden stays with the package and the transition risk drops. The exact budget depends on the scope of the project, and a firm quote only follows a process analysis.
How Pan Innovation House positions itself
We do not sell ERP, and we are not here to rip out your existing package. At Pan Innovation House we start by understanding what is actually causing you trouble: which process does not fit the package, where Excel is being used as a patch, which integration is missing. Most of the time the answer is not to replace Logo, Mikro, Netsis or SAP, but to leave it in place and build a measured operational layer on top of it.
After the process analysis we design the custom software layer so that the existing ERP stays where it is; we build the integrations to points such as e-invoicing, banks, the production line and marketplaces; and we put in place the reporting and BI side that brings the data together in a single source of truth. You own the code and the data, and we hand over the documentation; the aim is not to create another dependency.
If the analysis concludes that "an off-the-shelf package is already right for you and you do not need custom software", we say so plainly. As a Gaziantep-based team that knows the shop floor and the sector, we put the right decision ahead of the sale. Get in touch to work out where to start.
The questions we hear most
I already have Logo, so why would I commission custom software as well?
Packages like Logo handle accounting, e-invoicing and statutory reporting very well; rewriting them is pointless. Custom software comes in where the package does not fit: distinctive shop-floor operations, production tracking, dealer/B2B ordering, custom reporting or integrations the package does not support. The aim is not to replace Logo but to leave it in place and complete the narrow area where it falls short with a custom layer. If you have a process you are currently patching with Excel and manual steps, that is usually the real need.
Is custom software risky? I worry it will be left half-finished or leave me dependent.
The risk is manageable and depends largely on scope and contract. The strongest way to lower it is to build a custom layer over only the narrow area that causes trouble, instead of writing everything from scratch, and to keep the ERP in place; that leaves the transition risk and the regulatory burden with the package. On dependence: you should own the code and the data, the documentation must be handed over, and the work should proceed against a clear specification. Vague projects with no boundaries are risky; projects whose scope has been clarified through analysis are not.
Can an off-the-shelf ERP and custom software work together?
Yes, and in practice this is the most frequently chosen route. In the hybrid model the ERP remains the system of record and the regulatory backbone; operational work that does not fit the package is handled in the custom software layer. The two systems talk through integration: the custom layer reads data from the ERP, does its own job and writes the result back. That way you lose neither the proven infrastructure of the package nor the flexibility of your own process. The soundness of the integration is the heart of the job; set up properly, the two systems behave as a single whole.
If SAP or Netsis is no longer enough, should I replace it straight away?
Usually not. The feeling that it "is not enough" rarely comes from the whole package; it comes from a few specific processes. Replacing an entire ERP is an expensive, risky and lengthy project, whereas if the problem is confined to a narrow area, solving that area with a custom layer is far cheaper and faster. The first step is to analyse which processes are genuinely causing the trouble. Replacement only makes sense if even the backbone of the package fails to meet the need.
Is a local Turkish ERP or a global solution such as SAP the better fit?
Both have their place, and the decision depends on your scale, your regulatory needs and your budget. Local packages (Logo, Mikro, Netsis, DİA and the like) offer ready compliance with Turkish regulation, a wide dealer network and pricing suited to SMEs. SAP and comparable global solutions provide depth in large, multi-site organisations, but they cost more and carry a heavier regulatory-adaptation load. What matters is choosing not the brand but the fit with your processes and with the way you grow; that decision becomes clear through a neutral analysis.
Should every criterion in the decision matrix carry equal weight?
No. The matrix is a checklist, not a mechanical scoring system. Your business decides which criterion weighs most: if regulatory compliance is critical, you weight it towards the package; if a distinctive process is your competitive advantage, you weight it towards custom software. In most businesses the criteria do not all point one way; some point to the package and some to custom. That is precisely why the third way, a custom layer on top of a package, is usually the most balanced answer.
Let's work out together which route is right for you
A package, custom software, or the hybrid model in which the two work together? Let us listen to your processes and produce a neutral assessment. If an off-the-shelf package is already right for you, we will say so plainly.