What is ERP, and what is it for?
Before ERP, companies keep sales in one program, stock in a spreadsheet and accounting in other software; the same customer and product information is updated in several places. ERP joins these islands in a single database. A record is entered once, and every process that uses it sees the same data.
The ERP concept grew out of material requirements planning (MRP): first only when and how much material was needed was calculated, then capacity and production resources were added, and finally sales, purchasing and finance were brought into the same system. That is why the bill of materials, the routing and the requirements calculation still sit at the core of a production-focused ERP.
In manufacturing, the ISA-95 model places ERP in the business planning and logistics layer: what to produce, which material is needed when and how cost builds up are decided in this layer. Recording how the work actually runs on the shop floor is the job of MES.
How does ERP work? The journey of an order
The easiest way to understand ERP is to follow a single order from start to finish. Each step uses the record of the step before; no information is typed in again. An error or a missing record at one step is carried to the next steps in the same way; that is why data quality is decisive in ERP.
- Quotation and orderCustomer, price and delivery date; stock and capacity check.
- Requirements calculationMissing material and the quantity to produce, from the bill of materials.
- Purchasing and work orderSupplier order and a production order based on the routing.
- Production and qualityMaterial consumption, labour, inspection and receipt into stock.
- Shipping and invoiceDispatch note and invoice; e-dispatch note and e-invoice.
- Accounting and costJournal entry, collection and actual cost.
What are the ERP modules? The core modules for a business
ERP software is made up of modules, and each module keeps the records of one business area. What matters for a business is not the number of modules but that the modules work together on the same data. Production and planning modules come in where the business manufactures.
| Module | What it records | Question it answers |
|---|---|---|
| Sales | Quotations, orders, price lists, shipments | What did we sell, and when will we deliver? |
| Purchasing | Requisitions, supplier orders, goods receipt | What should we buy, from whom, and when? |
| Inventory and warehouse | Stock movements, lot and serial numbers, storage locations | What do we have, and where? |
| Production | Bill of materials, routing, work orders, consumption | What will we produce, with which material, in which steps? |
| Planning | Requirements calculation and rough-cut capacity | Will material and capacity be enough? |
| Quality | Incoming, in-process and final inspection records | Does the product meet the specification? |
| Costing | Allocation of material, labour and overheads | What does this product or service cost us? |
| Finance and accounting | Journal, customer and supplier accounts, collections and payments | What is the cash and profitability position? |
Bill of materials (BOM): glossary entry
ERP, MES, APS, CRM and others: which system does what?
ERP is the company’s shared record, but it is not the best at every job. In a company’s system map, each system has a responsibility, and when the boundaries are drawn clearly the same data is not held in two places. The table below sets these responsibilities side by side; MES and APS appear where the business manufactures.
| System | Main task | Relationship with ERP |
|---|---|---|
| ERP | Records of orders, stock, purchasing, production orders and finance | The shared system of record; the others draw on it or feed it |
| MES | In manufacturing, running the work on the shop floor and recording what actually happens | Takes the work order from ERP, returns actual quantities and times |
| APS | Detailed scheduling on finite capacity | Takes the order and the routing from ERP, returns a sequenced plan |
| CRM | Leads, opportunities and the sales funnel | A won quotation becomes an order in ERP |
| PLM | Product design, revisions and engineering changes | Passes the approved bill of materials to ERP |
| WMS | Storage locations, picking and shipping operations inside the warehouse | Reconciles stock movements with ERP |
The boundary between ERP and MES: the MES and IIoT guide
If you manufacture: what should you expect from ERP, depending on how you produce?
In businesses that manufacture, the same ERP does not fit every way of producing equally well. The way you manufacture determines which capability is critical in ERP; writing down your own way of manufacturing and your exceptions before the selection starts lets you ask the right questions in demos.
| Way of manufacturing | Typical example | What is critical in ERP |
|---|---|---|
| Make to stock | Standard products, produced to a forecast | Demand forecasting, safety stock, series planning |
| Make to order | A product configured to the customer’s options | Variant management, order-linked requirements and delivery date |
| Engineer to order and projects | Machinery, moulds, one-off manufacturing | Project costing, a changing bill of materials, milestone invoicing |
| Batch and process manufacturing | Food, chemicals, plastic raw materials | Recipes, lot traceability, shelf life |
| Subcontract manufacturing | An operation done outside, or production with the customer’s material | Subcontract orders, material dispatch and receipt back |
What should a growing company expect from an ERP?
Growth exposes the limits of work run on spreadsheets and separate programs: the same customer and product data is updated in several places, delivery dates are worked out by hand and cost is known only at month end. A growing company’s ERP has to carry tomorrow’s needs as well as today’s:
- one record: the same master data from sales to finance,
- gradual growth: no data migration when a new function, company or site is added,
- local compliance: e-invoicing, e-archive, e-dispatch notes and e-ledger flows running inside the system,
- integration: documented interfaces to CRM, MES, planning and e-commerce,
- sustainable adaptation: company-specific changes kept through version upgrades.
Cloud ERP or ERP on your own servers?
With cloud ERP, the software runs on the provider’s infrastructure and is used on subscription (SaaS); with an installation on your own servers, the infrastructure and its operation are your responsibility. The real difference between the two models is not technology but who holds the responsibility.
For any ERP that processes personal data, where the data is held and whether it is transferred abroad is assessed separately under the Turkish Personal Data Protection Law (KVKK).
| Topic | Cloud ERP (SaaS) | ERP on your own servers |
|---|---|---|
| Infrastructure and backup | Largely with the provider | With you or your hosting company |
| Version upgrades | Regular, on the provider’s schedule | At your decision; they can be postponed but they pile up |
| Legal updates | Published by the provider or its localisation provider | Applied to your installation by you or your support team |
| Flexibility to adapt | Within the limits the provider allows | Wider, but the cost of upgrades rises |
| Where the data is held | The provider’s data centre region | A location you choose |
Data security and backup in ERP: what to ask, in the cloud and on premises
ERP holds the company’s customer, supplier, employee, price and cost data in one place, so its security is a management matter, not only an IT one. With cloud ERP, the security of the infrastructure lies largely with the provider, but who can see which data and how user accounts are managed stay with the company. With an installation on your own servers, all of these responsibilities lie with you or your hosting company.
Under the Turkish Personal Data Protection Law (KVKK), the data controller must take the technical and administrative measures needed to prevent personal data from being processed or accessed unlawfully and to keep it safe. Where another person or company processes the data on its behalf, the controller is responsible for these measures jointly with them. During selection, ask every candidate:
- where the data lives: in which country and on whose infrastructure is it held, and is it transferred abroad?
- authorisation: can roles be defined by job, so that, for example, the sales team works without seeing cost data and the warehouse team without seeing finance records?
- authentication and audit trail: is there multi-factor authentication, and can you trace who changed which record and when?
- backup: how often are backups taken and where are they kept, is restoring tested regularly, and how long does the system take to come back after an outage?
- updates: who applies security patches, and on what schedule?
- end of contract: if the contract ends, in what format and how is your data handed over?
What an ERP in Türkiye has to cover
The ERP of a company operating in Türkiye carries not only its business processes but also the regulations. In global software these requirements are usually met with a localisation package, in local software in the core; what matters is who keeps them current.
- e-invoice, e-archive invoice and e-dispatch note: the e-document rules of the Revenue Administration of Türkiye (GIB), usually through a private integrator,
- e-ledger: keeping the statutory books electronically and obtaining the approval receipt (berat),
- the uniform chart of accounts and local reporting,
- KVKK: the processing, storage and transfer of personal data,
- public support: the TÜR document requirement for software under the Digital Transformation Programme, and KOSGEB support.
e-invoice in Türkiye: glossary entry
When is ERP needed?
What decides it is not headcount but the point where the work can no longer be managed with the current tools. If several of these signs apply, ERP comes onto the agenda, or the current ERP needs to be reviewed:
- the same customer, product or stock information is updated separately in several places,
- delivery dates and product cost are worked out by hand, in spreadsheets,
- month-end closing brings surprises, and stock counts do not match the system,
- finding out where an order stands means asking several people,
- adding a new company, site or product group means rebuilding the data.
How to choose ERP software
The winner is not the software with the longest feature list but the one that carries your processes with the least adaptation. The way to see this is to describe your order, purchasing, inventory and, where you manufacture, production flows in a common language, for example BPMN, and look at how each candidate handles them as standard. A need met by a standard capability is a «fit»; one that needs adaptation or a process change is a «gap».
A demo shows the vendor’s scenario; the decision should be made on yours. A sound selection proceeds in this order:
- measure the current state: processes, data quality, systems and problems,
- write down the critical processes and prioritise the requirements,
- run a Gap / Fit exercise with each candidate,
- ask each candidate to run the same scenario with your own sample data,
- compare the total cost of ownership on the same items,
- listen to references with a similar way of working, then decide.
Five capabilities not to miss when choosing an ERP
Six mistakes growing SMEs often make when choosing an ERP
The question of which ERP suits a growing SME has no answer in the form of a single product name. The right ERP is the system that carries the company’s current processes with the least adaptation and can absorb growth without rebuilding the data. What spoils a selection is usually not the software itself but how the selection is made; the six mistakes below are the ones growing businesses make most often.
| Mistake | Why it is a problem | What to do instead |
|---|---|---|
| Choosing by feature list | A long list does not show whether your processes are covered as standard; the chosen software is later bent to fit the company through customisation. | Write down your critical processes and see how each candidate covers them with standard capability, using your own sample data. |
| Not planning for growth | A system chosen for today’s needs may require the data to be rebuilt when a new company, site, product group or set of users is added. | Write down the direction of growth and ask candidates to show how a new company, site or function is added. |
| Over-customisation | Every custom development adds upkeep and makes version upgrades harder; work that a standard process could handle turns into code. | Try fitting the process to standard capability first; limit customisation to what truly sets the company apart, and ask how it is kept through upgrades. |
| Postponing data cleansing | Duplicate customer and product records, incomplete bills of materials and stock that does not match produce the same errors in the new system once migrated. | Start reviewing master data during selection; write into the plan who owns which data and when the cleansing will be finished. |
| Leaving local compliance and e-documents to the end | If e-invoice, e-archive, e-dispatch note and e-ledger flows are left to the last stage, go-live can slip because of them or start with stopgaps. | Put these flows into the selection scenarios from the start; ask whether they are provided in the core, in an add-on module or through an integrator connection, and who keeps them up to date. |
| Leaving users out | If the people who will use the system every day are not part of selection and testing, requirements are written incompletely and, after go-live, people drift back to the old spreadsheets. | Bring a key user from each main process into the selection, the demo scenarios and acceptance testing. |
Does it fit your industry? Does standard capability cover the need (Gap / Fit)
Fit with an industry is not your industry’s name appearing in an ERP’s marketing, but the extent to which your processes are covered by that software’s standard capabilities. The way to see this is a Gap / Fit exercise: for every critical process step, write down whether it is covered by standard capability (fit) or needs adaptation or a process change (gap).
What changes from one industry to another is which capability is critical: prices, promotions and multi-warehouse stock in wholesale and retail; projects, time recording and contract-based invoicing in service businesses; bills of materials, routings, requirements planning and costing in manufacturing; lot traceability and shelf life in food and chemicals. The number of gaps alone does not decide; what decides is which gap sits in a critical process and how it will be closed.
Fit-gap analysis: glossary entry
Usability and local support: what to look at in daily use
An ERP proves its value when users actually work in it every day. If the screens are hard, support is far away and local flows are missing, users soon drift back to spreadsheets. In demos and reference calls, look at the following:
- Turkish interface: are menus, field names, reports and help texts available in Turkish, and in the other languages your users work in, and does the translation cover every screen?
- ease of use: how many screens and how long does a frequent task such as order entry or goods receipt take?
- local team: is there a team in Türkiye that knows the software well and can deliver the implementation and later support in your language and in your working hours?
- e-document integration: does the e-invoice, e-archive and e-dispatch note flow run from the user’s daily screen, or does it require switching to a separate program?
- mobile and remote access: can warehouse, field and sales staff do the tasks they need from their own devices?
- training: is there training material in Turkish, and a learning path for new employees?
The kinds of ERP a growing SME can choose from
The options are easier to read when they are compared by class rather than by product name. Each class answers a different company profile; the difference between products within one class only shows in a Gap / Fit exercise run with your own processes.
| Kind of ERP | Suits | Strength | Watch out for |
|---|---|---|---|
| Accounting-led package | A business weighted towards finance and invoicing, with simple operations | Fast start, accounting ready for local regulation | Production planning and costing may stay shallow; more programs are needed as the company grows |
| Modular business applications | A business that opens functions step by step, from sales to accounting | Applications are added as needs arise, all on the same data | The more customisation, the heavier the upkeep of each version upgrade |
| Manufacturing-focused ERP | A company that makes to order, by project or with a multi-level bill of materials | Depth in planning, requirements calculation and production costing | Implementation and learning effort is high; processes need to be clear beforehand |
| Enterprise ERP suite | A multi-company, multi-country group with a complex structure | Breadth of scope and global process standards | At SME scale, the implementation and ownership burden can be heavy |
How is an ERP project implemented?
An ERP project is not a software installation but a redefinition of how the company works. The typical stages are: discovery and scope, process design, configuring the system, data migration, user acceptance testing, go-live and the period of intensive support that follows go-live straight away (hypercare).
What affects the timeline and the budget most is also well known: a scope that is not clear from the start, customisation that grows unchecked, data that is migrated late and uncleaned, users who join testing late, and decision authority that stays unclear. That is why the scope has to be fixed with evidence before implementation.
Data migration: glossary entry
How do you choose an ERP consulting firm?
The right implementation firm shapes the outcome of the project as much as the right software. A consulting firm is chosen by comparing candidates through a request for proposal sent on a written scope, a demo built on your own scenarios, references you can talk to and the total cost of ownership.
How to choose an ERP consulting firm: process, criteria and questions to ask
What does the cost of ERP depend on?
The cost of ERP is more than the licence price. When comparing proposals, ask about each item of the total cost of ownership separately:
- licence or subscription: by the number of users and modules,
- implementation services: priced by the person-day or by scope?
- customisation and development: is it kept through version upgrades?
- integration: e-documents, banks, CRM, MES and other systems,
- data migration and cleansing,
- training, go-live support and annual maintenance,
- infrastructure: a cloud subscription, or servers and their operation.
Five line items to check in an ERP quote
How is the return on an ERP (ROI) measured?
The return on an ERP comes from the company’s own baseline measurement, not from a general rate in a presentation. Before selection, the current state is recorded with a few measures, and the same measures are taken again after go-live with the same method; the difference shows what the ERP has brought to that company. A promised return that has not been measured is an estimate, not a result.
Which items to measure depends on the business’s priorities; the typical ones are:
| Item | What it shows | How the baseline is taken |
|---|---|---|
| Month-end close time | How late and how manually the accounting records are completed | Record how many working days recent closes took and which corrections were made by hand. |
| Inventory accuracy | How closely the stock in the system matches the stock on the shelf | Compare count results with the system records and note in which products and warehouses the differences cluster. |
| Manual work and double entry | In how many places, and by whom, the same data is typed again | List the manual transfers and spreadsheets used for orders, invoices and stock movements, together with the people responsible. |
| Reporting delay | How quickly and how reliably a management question gets its answer | Record how long sales, stock and profitability reports take to prepare, and whose effort they take. |
| On-time delivery | To what extent promised delivery dates are kept | Compare promised and actual delivery dates across orders. |
Total cost of ownership (TCO): glossary entry
Validating the scope independently of any software before selection
Vendor demos and proposals naturally highlight the strengths of their own software. That is why, in a sound selection, the company’s needs are first written down independently of any software: critical processes, the state of master data, integrations, local compliance flows and the direction of growth. Only then are the candidates compared on the same scope and the same scenario, and the proposals read against the same items.
MindDX does this validation in Assess: the scope is established with evidence before purchase, and the product decision comes after that evidence.
abas ERP: for the business that manufactures and needs depth in production
abas ERP is a production-focused ERP that Forterro positions for mid-sized companies in discrete manufacturing. It targets one-off, series, project-based, make-to-order and contract manufacturing, and groups that run several sites and companies in one system.
Planning centres on material requirements planning: every requirement is automatically assigned to stock or a work order, and the delivery date is derived from that assignment. Company-specific adaptations sit in a layer outside the core, so they are kept through version upgrades; for companies with heavy customisation needs this is a deciding criterion.
Odoo: for the business that starts with one app and grows step by step
Odoo is a suite of business applications on an open-source core that brings apps such as CRM, sales, inventory, manufacturing, accounting and human resources onto one platform. Apps are added as needs arise and all run on the same database; when accounting or manufacturing is added later, no data is migrated.
Odoo states that fields, views and workflows can be adapted without code in Studio; deeper adaptation is done with a separate module. There are Community and Enterprise editions, and a localisation for Türkiye.
Which ERP programs are used in Türkiye?
In Türkiye a wide range is in use, from local accounting-led packages to production-focused ERPs and enterprise suites. For an international group setting up or reviewing the ERP of its subsidiary in Türkiye, a separate guide explains localisation, electronic documents and the right set-up; rather than «best ERP» lists, we recommend comparing against your own processes.
ERP in Türkiye: localisation, e-documents and the right set-up
How to decide between them, and where to start
Broadly: if production planning, project-based or make-to-order manufacturing and heavy customisation come first, the production depth of abas ERP is the first candidate; if opening a wide range of functions from sales to accounting step by step comes first, the modular structure of Odoo is. This is a starting hypothesis, not a decision.
The decision is made on your proven processes, not on a demo scenario. MindDX does this in Assess: processes, data and the direction of growth are reviewed, which product fits is established with evidence and the scope is written into the Validated Scope document. The product decision comes after that evidence.