How to choose the right ERP for your business

Most ERP selections start with a demo and a feature checklist. Both are useful, and neither tells you whether the system will work for your business. Every serious ERP can post a journal, run payables and produce a balance sheet. What separates a good choice from an expensive one is how well the system fits the way you operate, and how much of your business has to bend to fit it.

After more than 250 ERP implementations, these are the questions we ask before anyone looks at a demo.

1. How does your business actually make money?

Write down the handful of processes that matter most: how an order becomes cash, how a purchase becomes a paid invoice, how you plan and make or buy what you sell, and how you close the books. A distributor with a warehouse and a 3PL has different needs from a services firm billing time, or a manufacturer costing work in progress. The right ERP handles your core processes as standard, so customization is the exception rather than the plan.

2. How many entities, currencies and locations do you run?

Multi-entity consolidation, intercompany trading, multiple currencies and many locations are where systems differ most. If you consolidate in a spreadsheet today, the new system should do it for you. Ask to see your own structure set up, not a generic demo company.

3. How much will you grow, and how complex will you get?

As a rough guide, and only a guide:

• Dynamics 365 Business Central suits growing companies that want an all-in-one system closely tied to Microsoft 365.
• Dynamics 365 Finance and Supply Chain Management suits larger or more complex organizations: many entities, manufacturing, advanced warehousing or demanding controls.
• Oracle NetSuite suits companies that want a cloud suite with strong multi-entity finance, particularly where Microsoft 365 fit matters less.

Choosing a system you will outgrow in three years is expensive. So is buying far more system than you will use.

4. What has to connect to it?

List every system that sends or receives data: CRM, e-commerce, banks, payroll, warehouse and 3PL systems, EDI partners, spreadsheets. Integrations are often where projects run late, so understand early which connections are standard, which need building and who will maintain them.

5. What will you bring across, and what will you leave behind?

Decide how much history you need in the new system. Open items and balances are essential. Years of detailed transactions often are not, and older detail can usually stay searchable in an archive. Clean customers, vendors and items before the move, not after it.

6. Where will AI help, and where must people stay in control?

AI is now part of every ERP roadmap. The useful question is not whether a system "has AI" but where it would change your work: reading invoices, proposing bank matches, flagging control exceptions. Make sure your data, security roles and approvals are set up so those features work, and that every decision that changes the books still has a named person behind it.

7. Who will implement and support it?

The partner matters as much as the product. Ask who will be on your project, how scope and changes are agreed, how testing works with your real data, and who answers the phone after go-live. Ask to speak to a customer with a similar business.

A simple way to decide

1. Write down your core processes, entities and integrations on one page.
2. Shortlist two systems that handle them as standard.
3. Ask each to show your own scenarios, not a script.
4. Compare total cost over five years: licences, implementation, integrations and support.
5. Choose the system and the partner together.

Skalable implements Dynamics 365 Business Central, Dynamics 365 Finance and Supply Chain Management, and Oracle NetSuite, so we can compare them on your processes rather than sell you one. Plan your implementation with us, or start with the quick-win finder if you are not ready to replace anything yet.