Custom ERP Software for Gaziantep Factories: Off-the-Shelf or Bespoke? (2026)
The ERP decision for manufacturers in Gaziantep: off-the-shelf or custom? Decision matrix, production modules, e-invoicing and PLC integration guide.
The shift has started, the line is running, two forklifts in the warehouse are waiting on a despatch. Yet the production manager is still working through three separate Excel files to answer the question "is there enough raw material for this order?"; sales is manually correcting the proforma invoice for the export container that loads tomorrow; and accounting has just noticed that the stock figures do not reconcile in the month-end e-invoice check. This is the scene a growing factory in Gaziantep knows best: the processes work, but the data is fragmented and everyone looks for the truth in their own spreadsheet. The question that arises at this point is not a one-word one — saying "let us buy an ERP" is easy; the real decision is whether you will install an off-the-shelf package or develop a system built for your factory. This article puts that decision on a concrete, defensible footing for the Gaziantep factories producing carpets, machinery, textiles, food and plastics.
What an ERP Is and What It Does in a Factory
ERP (Enterprise Resource Planning) is software that brings a factory's finance, production, inventory and sales processes together in a single data model. The aim is to remove the "every department has its own truth" problem and get everyone looking at the same, up-to-date data.
A manufacturing ERP typically contains the following modules:
- Production management / work orders: bill of materials (BOM), routing definitions, opening and closing work orders, recording actual production.
- MRP (Material Requirements Planning): calculating raw material and semi-finished goods requirements from orders and demand.
- Inventory / warehouse management: multi-warehouse stock, lot/batch and serial tracking.
- Costing: standard versus actual cost comparison, unit cost of finished goods.
- Quality management: incoming, in-process and outgoing quality control; reject and waste tracking.
- Despatch / logistics: the order-delivery note-invoice chain, export shipments.
- Maintenance: machine maintenance plans, breakdown and downtime tracking.
Which of these modules is "non-negotiable" and which is "later" changes from factory to factory. That is exactly where the heart of the decision lies: a standard package delivers these modules in a standard way; if your factory's work is not standard, the trouble starts.
The Off-the-Shelf ERP Landscape
Knowing the common off-the-shelf ERP options in Türkiye with their objective strengths and weaknesses takes the decision out of the realm of feeling and ties it to a measure:
- Logo (Tiger, Netsis): a widely used domestic ERP in the Turkish market. Its greatest strength is compliance with local legislation; e-transformation updates come from the vendor. It covers standard commercial and production processes quickly.
- SAP Business One: an international package for small and mid-sized businesses. It offers mature process models and is preferred in institutionalised, multi-site structures.
- Microsoft Dynamics 365 (Business Central): for mid to large scale, with strong alignment to the Microsoft ecosystem.
- Odoo / ERPNext: modular, open-source-based options that stand out for flexibility and customisability.
Nobody should impose a single answer here in the form of "this package is better than that one". Each is the right choice for a particular profile. The general logic of an off-the-shelf package is this: it covers standard processes quickly and at a relatively predictable cost, and the vendor takes on the burden of legislative maintenance. In return, once a process specific to your factory falls outside the package, you begin to force the package — and "forcing" is usually expensive, fragile and unsustainable.
When Custom ERP Makes Sense
Custom development does not mean "let us write everything from scratch". There are usually two realistic routes: a system built entirely for the factory, or the far more common hybrid model — keeping an off-the-shelf ERP as the core (finance, accounting, e-transformation) and completing the factory-specific requirements with custom software and integration.
Typical situations in which custom development comes to the table:
- Business rules outside the package, embedded in the factory. Processes such as length- and pattern-based production in carpets, project-specific manufacturing in machinery, or batch and shelf-life rules in food do not fit a standard package cleanly.
- When your competitive advantage sits in your process. If what separates you from the competition is your production flow, forcing that flow into a standard mould dissolves the advantage.
- When shop-floor integration runs deep. If you are going to build a close link to layers such as machine data collection, MES and barcode/RFID, a flexible custom layer makes the job easier.
- When you want to reduce vendor dependency. You may not want a critical process locked to the roadmap of a single package.
Pan Innovation House's approach rests on the same hybrid philosophy: use mature packages where "reinventing the wheel makes no sense", such as legislation and accounting, and build a precise fit through custom software development for factories in the processes where the factory genuinely creates value.
Decision Matrix: Off-the-Shelf or Custom?
The table below exists to tie the decision to criteria rather than instinct. You decide how to weight the rows according to your factory's profile, rather than by any single line.
| Criterion | Off-the-shelf ERP | Custom / hybrid ERP |
|---|---|---|
| Initial cost | Generally more predictable, varies with scope | Requires analysis and development; varies with scope |
| Time to go live | Faster for standard processes | Delivered module by module; planned around a first phase |
| Process fit | You fit the process to the package | You fit the software to the process |
| Flexibility / customisation | Limited; as far as the package allows | High; designed around the requirement |
| Legislative updates | Provided by the vendor | In a hybrid these come from the core; the custom part is planned |
| Shop-floor/MES integration | Depends on the package, sometimes difficult | Can be designed in from the start |
| Vendor dependency | Higher | Lower, control stays with you |
| Maintenance model | Vendor subscription/licence | Maintenance agreement with the developer |
The practical reading is this: if your processes are largely standard and speed is your priority, an off-the-shelf package is a strong candidate. If your factory's work does not run "by the book", and the point where you make a difference is precisely that "off-book" process, a hybrid or custom approach is more sustainable.
Two Examples of Production Modules in Real Working Life
The following are representative, general examples; they are not a real customer or case. The aim is to make concrete how the modules behave on the shop floor.
Example scenario: carpet / machine-made carpet factory
In machine-made carpet, production tracking, batch (lot) management and waste management are the backbone. A typical sequence of requirements:
- Work orders and bills of materials: yarn, backing and dye consumption for a given pattern and length is tied to the BOM; MRP derives the raw material requirement from that BOM.
- Batch/lot traceability: yarn batches are tracked at lot level so that the same shade does not drift between batches; when a customer complains, it is possible to trace back which batch was used where.
- Waste tracking: waste arising from edge trimming, faulty weft or colour deviation is recorded; actual cost is calculated including that waste, so the gap between "the cost on paper" and "the real cost" closes.
Where the rules specific to the carpet industry do not fit a standard package in processes like these, solutions built for the carpet and home textiles industry come into play.
Example scenario: machinery / metal factory
Machinery production is mostly project-based manufacturing — every order is a little different. What stands out here:
- Multi-level BOM: a machine is made up of sub-assembly groups, and those in turn of parts. The ERP has to carry a multi-level product tree and be able to manage the question of "which part is needed, when and how many".
- Project/assembly tracking: work orders are tied to a project code; assembly progress, missing parts and delayed items become visible at project level.
- Cost accumulation: the cost of materials, labour and subcontracted operations accumulates under the project; when you quote, that actual data makes the pricing of later projects realistic.
Standard commercial packages usually do not offer this project-centred logic "as is"; a custom module or hybrid setup can become unavoidable here.
Non-Negotiable: Integrations
However good an ERP is, it stays half-finished if it runs disconnected from the factory's other systems. The critical integration points for Gaziantep factories:
Türkiye e-transformation (GİB)
This is not a preference, it is a legal requirement. Businesses above a given turnover threshold are required to move to e-Invoice, e-Archive, e-Delivery Note and e-Ledger; the thresholds have been lowered step by step in recent years. The great majority of Gaziantep factories with high production and export volumes fall within this scope. The practical conclusion is clear: every ERP that is installed or written has to integrate with the GİB (Turkish Revenue Administration) e-transformation processes, whether through a private integrator or the GİB portal. Current thresholds and dates change; for your exact position it is right to consult your financial adviser.
Machine / PLC-SCADA data collection and MES
The ERP is the planning and recording layer; it is the machines that know the reality on the shop floor. PLC and SCADA are the control and monitoring layer for the machines; MES (Manufacturing Execution System) is the bridge between the shop floor and the ERP — it carries real-time production, downtime, OEE and traceability data. When the two work together, the gap between "the plan on paper" and "the reality on the floor" closes. One point to watch: older machines do not always give up data; where a PLC or sensor is missing, the data collection plan has to be built accordingly.
Barcode / RFID and finance
Barcode/RFID is needed for stock, lot and despatch traceability; API integration is needed to exchange data with banks, couriers and logistics providers, and with e-commerce systems where relevant. Feeding customer and stock data from a single source cuts out duplicate records and reconciliation problems at the root.
For factories working mainly on exports, these integrations show their real value when they can also be connected end to end with your e-export operations.
"Fitting the Factory to the Package" or "Software Built for the Factory"?
This is the philosophical core of the decision. When you buy an off-the-shelf package, you usually adapt your factory to the process the package assumes: "the software wants it this way, so let us change our workflow." In some processes that is healthy — pulling a bad habit into a standard is a good thing. But forcing the processes where the factory makes a difference, the ones that carry its competitive edge, into a standard mould files that edge away.
In the custom approach the equation is reversed: the software fits the factory. The price of that is more analysis up front and a disciplined development process. In return you get a system a shift operator can genuinely use, one that speaks the language of the shop floor and speeds the factory's work up. The right answer is usually not at either extreme but in the middle: keep the core off the shelf, write the difference yourself.
Conclusion: Not a Decision Tool, but the Right Order of Questions
There is no single right answer to the off-the-shelf versus custom question; what is right is taking the decision in the right order. First get your processes clear on the shop floor, separate the "non-negotiable" from the "later", and put obligations such as e-transformation and shop-floor integration on the table from the start. After that, the package-custom-hybrid decision becomes clear by itself. An ERP decision taken in haste is a burden carried for years; a system designed with care is the ground a factory grows on.
If you would like to put your factory's processes on the table with us and work out whether an off-the-shelf package, custom development or a hybrid model suits you, get in touch — our Gaziantep-based team starts with a discovery call, listens to your shop floor, and talks afterwards.
Related guides: