Questions to ask when choosing an ERP: a checklist

· Panda Yazılım

When choosing an ERP, look first at your own business, not at the software's features. Does it carry your sector's process, can it take your old data, does it talk to e-invoicing and your bank, who will train your team, and what will you pay after the first year? Rule out any vendor who cannot give written answers to these six questions. Compare the answers, not the demo; the rest is the implementation of those answers.

Where are mistakes made most often when choosing an ERP?

The most common mistake is deciding from the demo. A demo runs on clean data prepared by the vendor and on the tidiest flow. In your business there are orders invoiced before they ship, waybills with two items merged, and special discount lists kept in Excel.

So make the choice with a checklist. Ask every vendor the same questions, get the answers in writing and lay them side by side. The number of decision makers matters too: have at least one person each from accounting, the warehouse and purchasing in the meetings.

How do you tell whether it fits your sector?

A general-purpose ERP covers the basic needs of every sector, but a sector's own process often calls for customization. Ask the vendor for a conversation with a user from your sector and for a walk through your own process from start to finish.

  • Write down the three hardest steps in your process (for example colour-size variants, lot tracking, recipe-based production) and have them shown in the demo.
  • Ask whether these steps are solved with the standard product or with separate development. Separate development means maintenance on every version upgrade.
  • Ask to talk to a reference customer from the same sector.

Why should data migration count as a separate project?

If the customer/supplier accounts, stock cards, open balances and opening stock from the old system are not moved to the new ERP, you cannot start work on day one. Data migration often takes longer than expected, because old data is not clean: the same customer is recorded in three spellings, units are mixed up on stock cards.

  • Put in writing which data will be moved and which will stay in the archive.
  • Make it clear who does the cleanup: your team or the vendor?
  • Run a trial migration that checks whether balance and stock totals match the old system exactly after the move.
  • If you are coming from Excel, ask for the template file before setup.

What should you look at on integration?

An ERP does not work alone. It has to talk to your e-invoicing and electronic delivery note service provider, your banks, your e-commerce channels and, if any, your courier companies. Ask the vendor by name: do you pull this bank's statement automatically, do you bring in orders from this marketplace?

  • Is the integration in the standard product, a separate module, or a separate fee?
  • Is taking data out allowed? Can you pull your own reports via API or export?
  • If you change your integrator, what changes in the ERP?

An open API is insurance for something you do not need today. If you want to add an automation or an AI agent tomorrow, the ERP must let it read and write data without changing the ERP's screens.

What assurances should you ask for on training and support?

ERP projects get stuck on user habits more than on software. Ask who will be trained, in how many sessions, in what setting, and who will train a new employee afterwards. Training should not be just a talk in launch week but a trial of your process with your own data.

  • Through which channel (phone, email, WhatsApp, remote connection) and during which hours is support given?
  • Are the first-response and resolution times written in the contract?
  • When regulations change (for example e-document rules), is the update free and when does it arrive?
  • Do you speak to the same person, or explain from scratch every time?

What items make up the total cost?

The licence fee is only part of the cost. To be able to compare, ask every vendor to write the same items in the same order. We give no prices, because scope differs from company to company; but knowing the items is the first step in comparing quotes.

  • Licence or subscription: per user, per module or per company?
  • Setup, data migration and customization work
  • Training days and extra training
  • Annual maintenance, support and version updates
  • Integrations: e-document, bank, e-commerce and courier connections
  • Server or cloud hosting, backups
  • Adding a user, opening a branch, adding another company
  • The cost and format of getting your data out when the contract ends

Process time goes into this table too. If two people spend 10 hours every month on month-end close, that is 240 person-hours a year. If the new system really shortens that work, measure the saving with your own team's numbers, not the vendor's.

Which contract clauses should be checked?

A promise made in a sales meeting is forgotten during setup if it was not written down. Have everything you discussed carried into the quote and the contract. Look especially at these clauses:

  • Scope: which modules, how many users, which branches and companies are included?
  • Delivery plan: dates and owners for data migration, training and go-live.
  • Acceptance criterion: under what condition is the system considered delivered? A trial with your own data can serve as this criterion.
  • Termination and data exit: if the contract ends, in what format and by when do you get your data?
  • New regulation: the scope and timing of the update when e-document rules change.

This list does not replace legal advice; but it helps you prepare your own questions before you sit down with the vendor.

Whom should you invite to the selection meeting?

The ERP is not used only by the person who makes the purchase decision. Accounting, the warehouse, sales and purchasing will do their daily work in this system. Having at least one person from each of these teams at the vendor meetings resolves half of the objections that would come up after setup.

  • Accounting: chart of accounts, e-document flow, closing reports.
  • Warehouse: shipping, counting, barcode and lot tracking.
  • Sales and purchasing: order, price list, supplier and customer/supplier account flow.
  • Management: which report do you want to see, and how often? Write down the three reports you look at in the morning and have them shown in the demo.

Finally, score the quotes. Give each topic (sector fit, data migration, integration, training, support, cost) a weight by its importance to you and score every vendor on the same scale. Scoring does not make the decision automatically, but it lets you explain afterwards who came out ahead and why.

In reference calls ask: did the setup finish on the planned date, what did you need the most support with in the first three months, and if you were choosing again a year later, would you pick the same vendor? A vendor's reference list is a selected list; still, the common thread in the answers is valuable.

What small trial should you run before deciding?

If possible, ask for a trial with a small part of your own data: one month of invoices, a hundred stock cards, one bank's statement. In the trial you see how the system handles your documents. If the vendor is reluctant to run a trial, that too is an answer.

If your current ERP meets your needs but Excel and manual entries have piled up, buying a new ERP may not be necessary. Putting an AI agent on top, that is, adding a layer that reads and matches documents and that a person approves, is also an option. The checklist tells you which one suits you.

Frequently asked questions

How long does choosing an ERP take?

The time depends on the size of the company and the scope of data migration; we cannot give a fixed duration. If you settle your sector process, integrations and data migration in writing at the selection stage, there are fewer surprises during setup.

Cloud ERP or on-premises installation?

The question is the same for both: who is responsible for backups, access, updates and getting the data back? In the cloud, hosting and updates are on the vendor; on-premises they are on you. Always have the data exit terms written into the contract.

Can you close the gaps without replacing the current ERP?

Often yes. Repetitive jobs such as reconciliation, invoice matching or stock differences can be solved by an agent or a flow built on top of the ERP. The ERP stays the data source; the agent reads and suggests, and a person approves.