How to Choose an ERP System: Criteria, Scorecard and Demo Script

Most ERP selection guides stop at a list of features. Buyers need a method they can defend to the board, and our ERP and Odoo consulting services are built around that method: criteria, weights, scripted demos and evidence.

This guide is for owners, CFOs and operations heads who know they need an ERP and now have to select one. If you are still deciding whether you need one at all, start with our ERP readiness checklist.

What is the ERP selection process, step by step?

The ERP selection process runs in eight steps, from problem statement to signed contract, and usually takes six to twelve weeks for a small or mid-size company. Skipping a step is where most bad choices start.

1. Write the problem statement: the three to five business problems the ERP must fix, in money or hours.
2. Document requirements: processes, volumes, reports and integrations, ranked must, should or could.
3. Agree ERP evaluation criteria and weights: before you speak to any vendor, so the demos cannot set the agenda.
4. Build a long list: six to ten options from peers, analysts and comparison pages.
5. Shortlist to three: apply knockout rules and a short paper review.
6. Run scripted demos: same scenarios, same data, same scorers for every finalist.
7. Check references and price five years: customer calls, partner checks and a total cost model.
8. Negotiate and sign: scope, milestones, data ownership and exit terms in writing.

Step 2 deserves its own document. Our guide to an ERP requirements document gives a template with priorities and sign-off.

Which ERP selection criteria matter most?

Six ERP selection criteria decide most projects: functional fit, usability, integration and data, total cost, implementation partner and vendor future. Everything else is a detail inside one of these.

Use these as ERP evaluation criteria for every vendor, not only your favorite.

The user on the Odoo forum who asked how to identify the right ERP features was told to "talk to the people who use those processes daily". That advice applies to every criterion here.

How do you build a weighted ERP scorecard?

A weighted ERP scorecard turns opinions into a number: give each criterion a weight that adds up to 100, score each vendor 1 to 5 against a written definition, and multiply. Agree the weights before the first demo.

The table shows an illustrative weighting for a mid-size distributor. Change the weights to match your own problem statement.

Score each criterion from 1 (fails) to 5 (fully meets), then multiply by the weight. A vendor scoring 4 on fit earns 120 points there. The maximum total is 500.

Three rules keep the ERP scorecard honest:

• Score alone first: each scorer fills in the sheet before any group discussion.
• Write the reason: every score needs one line of evidence from the demo or documents.
• Knockouts beat points: a vendor that fails a must-have is out, whatever its total.

How do you build an ERP shortlist?

Build an ERP shortlist by applying knockout rules to a long list of six to ten systems, then keep the three that pass with the best paper fit. Three finalists is enough to compare without exhausting your team.

Typical knockout rules:

• Hosting: do you need cloud only, your own servers, or both?
• Localization: tax, e-invoicing and payroll rules for every country you trade in.
• Must-have processes: manufacturing, multi-company, project billing or whatever your business cannot run without.
• Budget ceiling: a five-year range the board will approve.
• Local support: a partner who works in your time zone and language.

For the long list, our ERP comparison hub compares Odoo with SAP, NetSuite, Zoho and ERPNext. Our guide to ERP systems examples explains what each type of ERP is built for.

Hosting is a common knockout for Odoo. The Odoo Online documentation says it is "incompatible with custom modules or modules from the Odoo Apps Store", so custom code means Odoo.sh or on-premise.

What should an ERP demo script include?

An ERP demo script is a written set of your own business scenarios, with your sample data, that every vendor must run live in the same order. It stops vendors showing only their best screens.

Build the script in six parts:

1. Context: one page on your company, volumes and the problems you want fixed.
2. Sample data: 20 to 50 real products, customers and vendors, sent a week ahead.
3. Five to eight end-to-end scenarios: quote to cash, procure to pay, stock moves, month end and your one awkward process.
4. Reports: the three reports management reads every week, built live.
5. Admin tasks: add a user, change an approval rule, import a price list.
6. Questions: integration, upgrades, data export and support, answered in writing.

Give each scenario a clear "pass if" line. Ask vendors not to use slides during scenario time. Let key users drive the screens for at least ten minutes.

The best answer on the Odoo forum thread how would I know if Odoo is the right ERP puts it simply: "Conduct a Trial or Pilot Run."

Example: an Odoo 20 demo script for a distributor

Here is how one ERP demo script looks when the vendor is Odoo 20 and the buyer is a 25-user distributor with two warehouses. Use it as a pattern; swap in your own scenarios.

Two Odoo 20 points belong in the questions part of the script. First, XML-RPC and JSON-RPC are deprecated in Odoo 20, with removal scheduled for Odoo 22, so new integrations should use the newer API.

Second, Odoo 20 AI features run on Odoo AI IAP credits at EUR 1 per credit, and the setting for your own OpenAI or Gemini key was removed. Ask the vendor to estimate monthly credit use. Our Odoo 20 release notes list what changed by app.

You can also test before the demo. Odoo offers a free trial database, and shared demo databases need no registration but last only a few hours.

How do you run ERP reference checks?

Run ERP reference checks by calling two or three customers of the same size and industry, chosen partly by you, and asking what went wrong as well as what went right. References picked only by the vendor tell you little.

Questions that get real answers:

• Scope: which apps went live, and what was cut or pushed to phase two?
• Time and budget: how far did the project run over, and why?
• Team: was the consultant in the sales meeting the one who did the work?
• Data: how was migration tested, and what had to be fixed after go-live?
• Support: how fast are tickets answered now, and who answers them?
• Hindsight: what would you do differently, and would you hire this partner again?

Check the vendor's support policy as well. Odoo publishes a standard and extended support table: each major version gets three years of standard support, and Odoo 20 is planned to September 2029.

How do you compare ERP total cost of ownership?

Compare ERP total cost of ownership over five years: licenses, implementation, data migration, training, support, hosting and version upgrades. The first-year license is often the smallest line.

For Odoo, the Odoo pricing page lists US$31.10 per user a month for Standard and US$61.00 for Custom, billed yearly, with lower first-year prices.

Custom adds Studio, multi-company, the external API and Odoo.sh or on-premise hosting. One App Free covers a single app for unlimited users.

As list-price math, 25 Custom users cost US$18,300 a year in licenses. Our published Odoo implementation ranges are US$3k to US$9k for small projects, US$9k to US$27k for mid-size and US$27k to US$150k+ for large. Data migration adds US$1.2k to US$9k.

Ask every finalist for the same cost lines. Our Odoo implementation cost guide explains what drives each range. For a quick number on your own scope, try the Odoo project estimate tool.

Once proposals arrive, the scoring moves from software to partners. Our guide on how to compare Odoo implementation proposals gives a separate scorecard for that step.

How should ERP selection differ by industry?

ERP selection should weight the criteria that carry your industry's biggest cost, so a manufacturer weights production depth while a services firm weights project billing. The table shows where we usually move the weights.

ERP selection checklist: what to confirm before you sign

Use this ERP selection checklist as the final gate: if any line is still open, you are not ready to sign. Each item should have a document or demo note behind it.

• Problem statement: signed off by the owner or board.
• Requirements: ranked, with must-haves agreed by each department.
• Scorecard: weights fixed before demos, scores and reasons filed.
• Demo evidence: every scenario passed or a written fix agreed.
• Fit gaps: each gap priced as configuration, add-on or custom code.
• References: at least two calls completed and notes shared.
• Five-year cost: every line priced, including upgrades.
• Contract: data ownership, exit terms and support levels in writing.

Gaps found late cost the most. Our Odoo fit gap analysis guide shows how to score and price them before you commit.

What are the most common ERP vendor selection mistakes?

The most common ERP vendor selection mistakes are letting vendors run the demo, choosing on first-year price, and picking the software before the partner. Each one is easy to avoid with the steps above.

• Unscripted demos: the vendor shows strengths and skips your hard process.
• Feature counting: more features is not better fit, and unused apps still need training.
• Copying old processes: paying to rebuild a spreadsheet habit as custom code.
• Ignoring upgrades: heavy customization makes every future version upgrade costly.
• One champion: a single manager chooses, and the users who must adopt it are never asked.

How iVentureTeam helps you choose an ERP system

iVentureTeam runs ERP selection as a short consulting project, so you leave with a scored decision rather than a sales pitch. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• Criteria and weights: we facilitate the workshop and build your ERP scorecard.
• Demo script: scenarios and sample data written from your real processes.
• Odoo 20 demo: we run your script on Odoo 20 and mark where it fails as well as where it fits.
• Discovery: our ERP discovery phase turns the chosen scope into a priced plan.
• Honest options: we also implement ERPNext and Zoho, so we can tell you when Odoo is not the answer.

ERP selection case study: KMF Technologies

An IT services and hardware distributor in The Gambia chose Odoo to replace manual product tracking, starting from a requirements phase. KMF Technologies supplies IT services, hardware and network infrastructure to institutions across West Africa.

Products and categories lived in hand-maintained lists. Stock was not visible in real time, which led to overstocking and stock-outs, and sales, purchase and store teams could not see each other's data.

We ran a seven-phase implementation: requirements, system design, configuration, report customization, data migration, training and post-go-live support. Sales, Purchase, Inventory and Accounting went live in 8 weeks with a phased rollout and a chart of accounts built for The Gambia.

KMF now runs an integrated purchase-to-delivery workflow with real-time stock across warehouses. Read the KMF Technologies Odoo inventory implementation case study.

The bottom line on how to choose an ERP system

Choose an ERP system with a process, not a presentation: fixed criteria and weights, three finalists, a scripted demo, real reference calls and a five-year cost. The winner is the system and partner that pass your scenarios.

Odoo 20 is a strong candidate for many small and mid-size firms, but it should earn its place on your scorecard like every other vendor. If it fails a must-have scenario, choose something else.

Ready to run a scored ERP selection?

Get a scorecard and demo script built around your own processes. Plan your ERP selection with an iVentureTeam consultant, call +91-90235-15208, or email business@iventureteam.com.