A manufacturer keeps its orders in Excel, its stock in a warehouse clerk’s notebook, and its accounts in the bookkeeper’s program. None of the three agree with each other. This is exactly where an ERP (enterprise resource planning) system earns its place: it gathers every process — from sales to production, from inventory to accounting — into a single database. But the wrong ERP turns scattered data into an expensive headache instead of solving it.
For small and mid-sized companies, this decision can no longer be postponed. As e-invoicing and electronic document mandates widen, businesses still cutting invoices by hand are approaching a threshold. The right ERP brings that compliance along for free while preparing the company to grow. This article offers a framework for making the choice soundly.
Why SMEs are moving to ERP now
Two pressures are rising at once. The first is regulatory. In Türkiye, electronic document rules keep expanding: companies whose gross sales pass a set threshold must move to e-invoicing — for the 2025 fiscal year the commonly applied general threshold sits around 3 million TL (lower in sectors such as e-commerce). From the start of 2026, invoices issued by businesses that are not e-invoice registrants are also expected to be drawn up as e-archive invoices regardless of amount. Confirm the threshold and timeline that apply to your business with the tax authority or your accountant — these figures change with each circular.
The second pressure is operational. As turnover grows, Excel and disconnected programs stop coping. The same product shows three different stock counts in three places, month-end reconciliation drags on for days, and no one can say where an order is stuck. ERP closes these gaps, and e-document compliance ships built in with most modern systems.
Why ERP projects fail
Not every company that adopts ERP comes out ahead. Annual ERP reports from consulting firms show that a significant share of projects exceed their original budget or timeline. The causes usually lie not in the software but in how the project is run:
- Weak planning. Moving to software before deciding how each process should work is the most common trap.
- Carrying processes over as-is. Digitizing a broken process only breaks it faster. Value from ERP starts with simplifying processes first.
- Poor localization. Software that doesn’t fit Türkiye’s tax rules, e-document formats and accounting order needs constant patching.
- User resistance and thin training. If the people on the floor don’t adopt the system, even the best software gathers dust.
- The “ERP is IT’s job” fallacy. ERP is a business transformation, not an IT project; ownership must sit with senior management.
SMEs are more exposed to these risks because of limited resources. That makes the right implementation partner as decisive as the right software.
Seven criteria for choosing the right ERP
| Criterion | Why it matters |
|---|---|
| Industry fit | Manufacturing, trade, services and export need different modules. An ERP that already knows your sector cuts the customization burden. |
| E-document readiness | E-invoice, e-archive, e-waybill and e-ledger integration should be native; bolt-on solutions are fragile. |
| Scalability | Today’s 10 users may be 50 tomorrow. Both software and license model should stretch with growth. |
| Integration | It should talk to banks, e-commerce, shipping, production machinery and reporting tools. |
| Ease of use | A clunky interface is the number-one cause of user resistance. People must get daily work done quickly. |
| Total cost of ownership | The license is only the tip of the iceberg; setup, training, customization, maintenance and hosting all count. |
| The partner’s track record | The team that implements and sustains the system — not the one that sells it — shapes the project’s fate. |
Weight these criteria against your own priorities. For an exporter, e-document and currency/customs integration come first; for a service business, ease of use and flexible reporting may matter more.
Cloud or on-premise?
For most SMEs, cloud-based ERP makes more sense. It needs no hardware investment, updates arrive automatically, the team accesses it from anywhere, and the upfront cost is low. Enterprise cloud platforms such as Microsoft Azure take the backup and security load off the company’s shoulders.
On-premise installation still has a place for businesses that want to keep data physically on their own servers or have very specific connectivity needs — but maintenance, security and continuity become entirely the company’s responsibility. When deciding, base the call not on “where should the data sit” but on “who should carry this load and keep pace with growth.”
The rollout: step by step, not all at once
A healthy ERP transition is not a single end-to-end go-live; it is a path of measurable steps. The framework we follow has three layers:
- Discovery and analysis. Current processes, data sources and real needs are mapped. This is where you decide which process should be simplified.
- Pilot. Start small and controlled, with a single module or department. Mistakes surface before they grow.
- Scale-up. Once the pilot is validated, the system rolls out across the business step by step, with user training and support at every stage.
We describe this approach in detail on our methodology page. The cost and duration of an ERP project depend on company size and process complexity; be wary of “turnkey in X days” promises made before a clear scope exists.
Combining ERP with automation and sustainability
ERP is not an end but a foundation. Once data lives in one place, two more layers can be built on top. The first is automation: repetitive tasks (invoice matching, stock alerts, approval flows) move off people’s desks through RPA and process automation. The second is measurement: the same ERP data is the raw material for energy and emissions tracking. When production and consumption data already sit in the system, carbon footprint reporting or CBAM/CSRD compliance is derived from existing data rather than collected from scratch.
Our approach is to build this chain from a single hand: measurement and data first, then the right software, then compliance and reporting. The digital transition side makes the business measurable and automated, while the same data feeds sustainability goals through the twin transition approach. Choosing an ERP is the first stone of this larger picture.
Drawing on Qera’s experience, İkiz Eksen carries more than 100 ERP migrations, over 15 sectors and more than 550 businesses served. We work across Türkiye, on Microsoft Azure infrastructure, with a turnkey setup. To choose the right ERP and plan a sound transition, get in touch or explore our solutions.
Frequently Asked Questions
What size ERP does my SME need?
There is no single correct size. A 10-person company and a 100-person company have different needs. The deciding factor isn’t headcount but process complexity: multi-channel sales, production, export or multi-branch structures call for a more comprehensive ERP. A business running a few standard processes can start lighter and expand as it grows.
Am I required to adopt ERP?
ERP is not legally mandatory, but e-document applications such as e-invoice and e-archive are compulsory for businesses above certain turnover thresholds. The most practical way to meet that requirement is an ERP with e-document support built in. Confirm the obligations that apply to your business with the tax authority or your accountant.
Is cloud ERP secure?
Enterprise cloud platforms such as Microsoft Azure offer a higher level of backup and security than most SMEs could provide on their own servers. What matters is that your provider’s security and data-handling processes are transparent.
Will the data in my existing Excel files and programs be lost?
In a healthy transition, existing data (accounts, stock, invoice history) is carried into the new system. Data migration is the most delicate step of an ERP project, and the implementation partner’s experience makes the difference — old records are mapped correctly through planning, not at the last minute.
How long does an ERP project take?
Duration depends on company size and the number of processes. A step-by-step rollout (pilot first) may look longer than a single go-live, but it lowers risk and delivers lasting results. A firm timeline only emerges after the discovery and analysis stage.