How to Select an ERP System: An SME Guide
Choosing the right ERP is a strategic decision for SMEs. This guide outlines the key steps to help you select the best system for your business needs.

For manufacturing and industrial SMEs in Turkey, the path to growth and maintaining a competitive edge lies in operational efficiency. One of the most fundamental tools for achieving this efficiency is Enterprise Resource Planning (ERP) software, which manages all business processes within an integrated structure. However, the right ERP selection is a strategic decision that shapes the future of the company, representing much more than just a software purchase. A poor choice can lead not only to financial loss but also to operational disruptions, inefficiency, and a decline in employee motivation. Therefore, the process must be managed with methodical and deliberate steps, without being rushed.
The complexity of this decision-making process can understandably concern SME managers. The market is filled with numerous domestic and international ERP solutions, each offering different features, modules, and pricing models, which can make the landscape seem even more bewildering. The purpose of this guide is to clearly present the steps that decision-makers in manufacturing and industrial SMEs should follow when choosing the most suitable ERP system for their business. By approaching the process not as a technology project but as a business transformation project, we aim to illuminate the path to achieving the highest return on investment.
Current State Analysis and Defining Needs
Before seeking any solution, it is essential to have a clear understanding of the problems to be solved and the current situation. ERP selection is no exception to this rule. The first step is to analyse your company's existing business processes in detail. How do the workflows in all departments progress, from purchasing and production to stock management, sales, shipping, finance, and human resources? Where are the inefficiencies, repetitive tasks, information gaps, or processes that require manual tracking? The answers to these questions will reveal what you should expect from a new ERP system.
During this analysis phase, it is crucial to gather the opinions not only of managers but also of the key users who are directly involved in the processes (e.g., operations, planning, warehouse, and sales supervisors). The challenges they face in daily operations, the reports they need, and the functions that would make their jobs easier will form the foundation of the requirements list. This exercise is also a practice in creating an operations map, allowing you to identify which processes are standard and which are unique to your company. The requirements list should contain concrete items such as “creating an automatic purchase request when stock levels fall,” “enabling real-time cost tracking linked to a production order,” or “managing customers with different shipping addresses.”
Budget and Resource Planning
The cost of an ERP project is often one of the most significant decision criteria for SMEs. However, considering only the software's licence or subscription fee when budgeting is a major mistake. Calculating the Total Cost of Ownership (TCO) allows for more realistic financial planning. This cost includes the following elements:
- Software Cost: A one-time licence fee or a monthly/annual subscription (SaaS) fee.
- Implementation and Consultancy Cost: The fee for installing the software at your company, adapting it to your processes, and for consultancy services.
- Hardware Cost: If an on-premise solution is chosen, hardware investments such as servers, data storage units, and network infrastructure.
- Training Cost: The cost of the training required for all users to be able to use the system effectively.
- Maintenance and Support Cost: The fee for software updates and technical support services, typically calculated as a certain percentage of the annual licence fee.
- Customisation Costs: Additional development costs for company-specific needs that are not met by the standard software.
In addition to financial resources, the internal resources to be allocated to the project must also be planned. A project leader should be appointed to manage the project, and key users from each department who will dedicate time to the process should be identified. A project timeline should be created considering the existing workloads of these individuals, ensuring the project progresses without disrupting daily operations. It should not be forgotten that the success of an ERP project depends as much on the human resources who own and adopt the project as it does on the technology itself.
Determining the Software Type: Cloud or On-Premise?
Once the needs and budget have been clarified, one of the fundamental decisions to be made is about the software's architecture. Today, ERP solutions are primarily offered in two models: On-Premise and Cloud (SaaS).
On-Premise ERP: In this model, software licences are purchased and installed on the company's own servers. Full control over all data and infrastructure remains with the company. This can be an advantage, particularly for businesses that are sensitive about data security or have special integration requirements. However, the initial investment cost (server, licences, etc.) is high, and an IT team or external support is needed for system maintenance, updates, and security.
Cloud-Based (SaaS - Software as a Service) ERP: In this model, the software is accessed via a web browser, typically for a monthly or annual subscription fee. The software is hosted on the service provider's servers. The biggest advantage of this model is the low initial cost and the absence of any IT infrastructure management burden. Issues such as updates, backups, and security are managed by the service provider. Furthermore, the ability to access the system from anywhere with an internet connection provides flexibility and mobility. For SMEs, it often stands out as a more scalable and manageable option.
When choosing between these two models, factors such as your company's IT capabilities, budget structure, growth targets, and data management policies should be taken into account. In some cases, hybrid solutions that combine features of both models can also be considered.
Researching Potential Vendors and Creating a Shortlist
Now you have a list of requirements, a budget, and a preferred architecture. The next step is to research potential ERP vendors that meet these criteria. At this stage, the goal is to start with a broad pool and narrow it down to a shortlist of 3-5 firms.
One of the most important things to consider when researching vendors is their experience in the manufacturing and industrial sectors. Software that only offers general accounting or sales management cannot meet the complex needs of a manufacturing business (e.g., bill of materials management, production planning, route tracking, quality control). Review the vendor's website, customer references, and case studies to check if they have worked with firms of a similar sector and scale to yours.
The vendor's local support capacity is also important during the evaluation process. It is logical to prioritise firms with a strong office or partner network in Turkey that can respond quickly and competently to any issues that may arise during and after the project implementation. The firm's financial strength and market presence also signal reliability for a long-term partnership. The shortlist you create as a result of this research will make the subsequent steps of the evaluation process more manageable.
Vendor Evaluation and the Demo Process
You can now enter a more detailed evaluation process with the vendors on your shortlist. The most critical part of this stage is the demo meetings, where the software is presented live. However, to ensure these meetings are productive, you need to be prepared.
Instead of asking the vendor for a general presentation, request specific scenarios based on the requirements list you prepared earlier. For instance, a specific request like, “Could you show us the entire process on your software, from purchasing raw material A and booking it into stock, to creating the production order for product B, completing production, and shipping it to customer C?” will allow you to see how well the software fits your workflows.
What to look for during the demo:
- User Interface: Is the system easy to use and intuitive? Can users from different departments adapt to the system easily?
- Flexibility and Customisation: How easily can the software adapt to your company's specific processes beyond its standard features?
- Reporting Capabilities: Can you easily obtain the basic reports you need (production cost, stock turnover rate, profitability analysis, etc.)? How easy is it to design custom reports?
- Integration Capability: Can it integrate with your other existing software (e-invoicing, payroll, etc.) or your machinery?
After the demo process, ask the vendor for the contact details of reference customers in the same sector and of a similar size to you. The conversations you have with these references will provide the most honest and valuable information about the vendor's and the software's performance. Find out how the implementation process went, whether they are satisfied with the post-sales support, and whether the software delivered its promised benefits.
Contract and Implementation Plan
After all the evaluations, the stage following your decision is the contract and implementation process. The contract is a legal document that contains all commercial and technical details and protects the rights and responsibilities of both parties. It is important to carefully review all clauses with a legal advisor before signing. You should particularly focus on critical clauses such as the scope of the licence, the increase rates for annual maintenance/support fees, data ownership (especially in cloud solutions), service level agreements (SLAs), and the conditions for project cancellation.
A detailed project implementation plan should be provided by the vendor along with the contract. This plan should clearly define all the steps from the project's start to the go-live, the timeline, and who will be responsible for each step (from both your company and the vendor). This plan, which includes phases such as analysis, installation, customisation, data migration, testing, training, and go-live, is the roadmap for the sound management of the project. A good implementation plan greatly increases the likelihood of completing the ERP project on budget and on time.
Conclusion
ERP selection is a long-term, strategic investment that will form the operational backbone of a manufacturing SME. Rushing the process or opting for popular or cheap solutions without a proper needs analysis will lay the groundwork for much more costly problems in the future. For a successful selection and implementation, you must analyse your own processes in depth, plan your budget realistically, evaluate potential vendors meticulously, and take project management seriously.

