Explore Dika Ops

How to Choose an ERP System Without Buying Too Much

How to choose an ERP system: list your processes, set must-have requirements, compare vendors fairly, and check cost, fit and support before you sign.

7 min read Business software
A team placing sticky notes on a glass wall during a planning session

If you want to know how to choose an ERP system, start with your own processes, not with a list of software features. Write down how an order moves from quote to invoice, how stock is counted and moved, how purchases are approved and how month-end reporting is produced. The system that fits is the one that supports those steps with the least rework, not the one with the longest feature list.

This guide is for owners and managers of small and mid-size companies that make, move or sell products, and for teams that already know ERP is needed but have not yet narrowed the options. It covers how to set requirements, compare vendors fairly, read the true cost and avoid buying modules you will not use. For the basics first, see our explainer on what ERP software is.

Step 1: How to choose an ERP system by mapping your processes

Before you open any vendor website, draw the processes that matter to your business on one page. Keep it plain: a box for each step, an arrow for each handover, and a name next to each box. Most owners find two or three handovers that depend on a single person, or on a spreadsheet that only one person understands. Those are the points where an ERP can help most.

Include the people who do the work. A sales manager, a warehouse lead and an accountant will describe the same order in three different ways, and all three descriptions are useful.

Step 2: Write must-have requirements

Turn the process map into a short list. Split it into three groups: what must work on day one, what should work within a year, and what would be nice to have. A list of twenty must-haves usually means nobody has decided what matters. Aim for ten to fifteen items and make each one testable, such as "a purchase order over a set amount needs approval before it is sent".

  1. List every process and the systems or files it uses today.
  2. Mark the handovers that cause delays, errors or repeat entry.
  3. Write requirements as observable results, not as vendor features.
  4. Rank each requirement as must-have, should-have or nice-to-have.
  5. Agree the list with the people who will use the system every day.

Step 3: Compare vendors on the same script

A demonstration is only useful if every vendor shows the same scenario. Give each one a short script built from your own examples: a real order with a discount, a stock shortage, a supplier invoice that does not match the delivery note. Ask them to show the steps live, with a sample of your data where possible. Note who needed to click through a menu and who answered in plain terms.

Area to compareQuestions to askWhat good looks like
Fit with processesCan you show our order-to-cash steps with our example?Shows the scenario end to end without workarounds
Data and accessWho can see which records, and how is that enforced?Role-based access and an audit trail you can read
IntegrationsWhich online stores, payment providers and shipping services are supported today?A written list of what is live, not what is planned
MigrationWho imports our data, and what is checked before go-live?A named process for the first import, with a check-back
SupportWho answers when a stock report is wrong at month-end?A clear support route and response expectations in writing
Total costWhat is included, what is extra, and what changes as we grow?A cost model with all modules and users spelled out

Compare the answers, not the presentation quality. A polished slide deck does not show how the system handles a partial delivery or a currency change on an existing order.

Step 4: Read the real cost before you compare prices

An ERP price is rarely one number. It usually includes the licence or subscription, the set-up and data migration, training, integration work and the time your own staff spend away from daily tasks. Ask every vendor to put these into one table with the same assumptions, such as number of users, modules and locations.

Also ask what happens when you add a module, a user or a new company. Some pricing models make the first year look cheap and the third year expensive. If a vendor will not give you a written cost model, treat that as a finding in itself.

  • Subscription or licence fees, with the number of users and modules stated.
  • One-off set-up, data migration and training costs.
  • Integration costs for each online store, payment or shipping service you use.
  • Internal time for your team during the project and the first months.
  • Costs of changing the system later, including exporting your data.

Step 5: Check fit, data and control

An ERP holds your customer, stock and financial records, so check how the vendor protects them. Ask where the data is hosted, who can access it, how roles are assigned and whether you can export your records in a usable format if you leave. These questions matter more than a long list of reports.

Also check how the system deals with approvals. A good ERP should let you decide who can release a payment, change a price or post an adjustment, and it should keep a record of who did what. If the answer depends on a shared login, the system is not ready for a growing team.

Plan the rollout before you sign

The contract is the start of the project, not the end of the selection. Agree a rollout plan with the vendor or implementation partner: the order in which modules go live, the training plan, the data clean-up that you must do yourself and the acceptance tests for each step. A pilot in one area, such as purchasing or one warehouse, often reveals more than a full launch on paper.

If you are not sure how to run the project, our guide to ERP implementation steps sets out the stages in more detail.

Four people reviewing documents and samples at a white table
Compare vendors with the same documents and the same scenario, so the answers can be checked side by side.

Common mistakes when choosing an ERP

Most poor choices come from a few predictable habits. Buying for the features on the vendor's slide rather than for your own process is the most common. Letting one department decide alone is the second. The third is treating data migration as a technical detail rather than a business task that needs an owner and a deadline.

Keep the decision small enough to finish. Choose two or three candidates, run the same script, check the cost model and talk to the references the vendor gives you. A decision made on clear evidence in six to ten weeks is usually better than a long search that never ends.

Frequently asked questions

How long does it take to choose an ERP system?

For a small or mid-size company, a focused selection often takes several weeks, depending on how many people must agree and how quickly the vendors respond. The time goes on process mapping and comparing demonstrations, not on the software itself. Set a deadline at the start and keep the candidate list short.

Should we choose cloud or on-premise ERP?

That depends on your IT capacity, data rules and how many locations you run. Our article on cloud ERP vs on-premise compares costs and control. Whichever you choose, ask the vendor to explain where data is stored and how backups work.

Do we need a consultant to choose an ERP?

Not always, but an independent person can help with requirements and fair comparison if your team has never run a software selection. Make sure any adviser is paid for the work, not for a particular product, and that they test the vendors on your scenario rather than theirs.

What if we only need the accounting or the stock module?

Then you may not need a full ERP yet. Check whether the tools you already use can cover the process with a clean data flow. If one area is growing fast, a narrow system may be enough for now, but make sure it can connect to a wider system later without rebuilding your records.

Can we change ERP later if the choice is wrong?

Changing is possible but expensive, mainly because of data migration and retraining. That is why export options, data ownership and the vendor's support model should be part of the decision from the start. A cautious rollout in one area lowers the risk of a wrong choice.

Next steps for your shortlist

Write your process map this week, then set the must-have list with the people who run each process. Give two or three vendors the same script and ask for the same cost model. If you want a second opinion on the requirements or the rollout, contact our team at Dika Design. For the functional scope, Dika Ops covers sales, purchasing, stock, finance, HR and reporting on one record. To test it against your own scenario, request a demo. For wider integration work with existing systems, see our services or our enterprise applications service.

Have a project in mind? Let us talk it through.

Tell us what you want to improve. We will reply with a clear next step.