What are ERP selection criteria?

ERP selection criteria are the documented, weighted requirements an organization uses to evaluate and score competing ERP platforms before choosing one. They typically span functional fit, total cost of ownership, technical architecture and integration, vendor and partner viability, implementation readiness, security and compliance, scalability, and usability. Criteria turn ERP selection from a demo-driven impression into an evidence-based comparison that holds up to later scrutiny.

What should be included in an ERP RFP?

An ERP RFP should include a company and project overview, the weighted requirements list organized by category, specific questions on functional capability, integration and technical architecture, implementation methodology and timeline, total cost of ownership across license, implementation, and ongoing administration, vendor and partner references, and the evaluation criteria and scoring method the vendor will be judged against. An RFP built directly from a scored requirements set produces comparable, apples-to-apples vendor responses instead of marketing material.

How do you weight ERP selection criteria?

Weight ERP selection criteria by business impact, not by ease of comparison. Start by separating must-have requirements, which disqualify a platform outright if unmet, from weighted preferences. Then assign relative weight to each preference category based on how much it actually affects the outcome for that specific organization: a company with complex multi-entity consolidation weights financial architecture heavier than a single-entity business would. Score every candidate on the same numeric scale in every category, then multiply by weight and total the result.

Who should be involved in building ERP selection criteria?

ERP selection criteria should come from the people who will actually operate inside the system: controllers and accounting staff who close the books, operations and supply-chain leaders, IT for the technical and integration requirements, and an executive sponsor who can arbitrate a weighting disagreement between departments. Criteria written by a single function, often IT or finance alone, tend to underweight the categories the excluded departments would have flagged as critical. Lightbridge ERP builds every requirements set with representatives from each function the platform will touch, then runs the weighted result through the full ERP selection process.

How many ERP vendors should you evaluate?

There is no fixed number. A shortlist needs enough candidates for the scorecard to show real contrast between platforms, and few enough that each one gets a genuine scored evaluation rather than a rushed pass. In practice, most organizations land on a handful of platforms once an initial landscape scan filters out anything that fails a must-have requirement. The right count follows from how sharply the must-haves narrow the field, not from a target set before the requirements exist.

Should price be the primary ERP selection criterion?

No. Total cost of ownership belongs on the scorecard as one weighted category among several, never as the sole deciding factor. Implementation, integration, data migration, training, and ongoing administration typically add up to more than the license line over the life of the system, but the entire point of weighting is that no single category overrides the rest on its own. A platform picked mainly for a low sticker price commonly turns out to be the costlier choice once the other categories are counted.

What is the most common mistake in building ERP selection criteria?

The most common mistake is skipping a disciplined requirements-gathering step and scoring platforms against a generic feature checklist instead of the organization's actual workflows. A close second is letting a demo, rather than the scorecard, drive the decision: a well-rehearsed demonstration can make a poorly-fitting platform look strong. Criteria built with the people who run finance and operations, and scored consistently across every candidate, are what keep the decision anchored to evidence.

Do ERP selection criteria differ by industry?

Yes. A government contractor weights DCAA-compliant timekeeping and incurred-cost reporting as must-haves that a retailer would never list. A distributor weights inventory and warehouse depth heavier than a professional-services firm would, which instead weights project accounting and resource management. The category structure, functional fit, TCO, architecture, vendor viability, implementation readiness, security, is consistent across industries. What changes is which requirements inside each category are must-haves versus preferences.

KB Written by Kristy Barber with Robert LabardeeERP Selection Lead and Founder and CEO

Last updated August 2026.

ERP selection criteria: how to build the scorecard.

ERP selection criteria are the weighted requirements an organization scores every candidate system against before choosing an ERP: functional fit, total cost of ownership, technical architecture, vendor viability, implementation readiness, and security. A documented scorecard, not a demo, is what turns an ERP decision into evidence an executive team and a board can stand behind.

See the selection method Why ERP projects fail Try the scorecard tool

A demo is not evidence. A scorecard is.

Every ERP platform demos well when the vendor controls the script. The gap between a polished demonstration and how a system performs against a specific business, its transaction volume, its entity structure, its compliance obligations, only shows up when the evaluation is run against documented, weighted criteria instead of an impression. Organizations that skip this step tend to choose the platform with the best sales team, not the best fit.

Selection criteria also produce a paper trail. A board, an audit committee, or a new finance leader two years into the system can ask why a particular platform won, and a scored evaluation answers that question with evidence. A gut call cannot. If you are earlier in the process and want the full context on how a selection failure compounds into an implementation failure, start with why ERP implementations fail.

The eight categories every ERP selection scorecard should cover.

Not every business weights these the same way, but a complete scorecard touches all eight. Leaving one out is how a platform that fails on integration or security still wins on a feature checklist.

Functional fit

Does the system handle the processes the business actually runs, financials, order management, inventory, project accounting, at the depth the industry demands? Score against documented workflows, not a generic feature checklist.

Total cost of ownership

License or subscription fees are the smallest line. Implementation, integration, data migration, training, and ongoing administration usually cost more over five years than the software itself. Score the full curve, not the sticker price.

Technical architecture and integration

How the platform connects to CRM, payroll, industry-specific tools, and existing data warehouses. Native connectors, a documented API, and a sane data model matter more than a long feature list if the ERP has to sit in a real stack.

Vendor and partner viability

Financial stability, release cadence, the depth of the implementation-partner bench, and how the vendor has behaved in past price increases or acquisitions. A five-year platform choice deserves a five-year view of who is behind it.

Implementation and change readiness

Realistic timeline, the internal bandwidth the project will actually consume, and how much of the organization's process has to bend to fit the platform versus the reverse. The best-scoring system on paper can still be the wrong choice if the business cannot absorb it.

Security, compliance, and data governance

Role-based access, audit trail, SOX and segregation-of-duties controls, and any regulatory posture the industry requires (GovCon, healthcare, financial services). Score this as a gate, not a preference: a system that fails a compliance must-have is disqualified regardless of its other scores.

Scalability and industry fit

Whether the platform holds up at twice the current transaction volume, entity count, or user base, and whether its edition or module set was actually built for the industry, not adapted after the fact.

Usability and adoption

A system the finance and operations teams will not fight to use every day is worth less than its feature list suggests. Adoption risk belongs on the scorecard, not just in the post-go-live retrospective.

How to weight and score ERP selection criteria.

A list of criteria without weights is not a scorecard, it is a wish list. Weighting is what forces the evaluation to reflect what actually matters to this business, in this decision, rather than treating every category as equally important.

Separate must-haves from preferences

A must-have disqualifies a platform outright if unmet: a required compliance control, a hard integration, a functional capability the business cannot operate without. Everything else is a weighted preference, not a gate.

Assign relative weight by business impact

Weight each preference category by how much it actually moves the outcome, not by how easy it is to demo. A finance-led organization typically weights functional fit and TCO heavier than a lightly customized front-end.

Score every platform on the same scale

Use one numeric scale, for example 1 to 5, applied identically across every candidate and every category. A scorecard where one platform is scored generously and another strictly is not a scorecard, it is a foregone conclusion with paperwork.

Weight-adjust and total the score

Multiply each raw score by its category weight, then sum. The result is a single comparable number per platform, defensible line by line if a board or an internal stakeholder asks why one system beat another.

Sanity-check against the must-haves

A high weighted score cannot rescue a platform that failed a must-have gate. Run the disqualification check before the ranking is finalized, not after a recommendation has already been shared.

A worked example: if functional fit carries a weight of 30 percent and a platform scores 4 out of 5 on that category, it contributes 1.2 points to that platform's total, out of a possible 1.5. Run the same math for every category and every candidate, and the platform with the highest weight-adjusted total is the one the evidence supports, not the one that presented last and best.

Turning the scorecard into an ERP RFP.

The request for proposal is where selection criteria get tested against real vendor responses instead of a hypothetical scorecard. An RFP built directly from the weighted requirements list, rather than from a generic template, produces answers that map cleanly back onto the scoring model.

A working ERP RFP generally covers a company and project overview so the vendor understands the operating model, the requirements list itself organized by the same categories as the scorecard, specific questions on integration and technical architecture rather than open-ended feature claims, the implementation methodology and a realistic timeline, total cost of ownership broken out by license, implementation, and ongoing administration, and named references at organizations of comparable size and complexity.

The most common RFP mistake is sending every vendor a slightly different set of questions, whether from reusing old documents or from letting each vendor conversation drift. When the RFP is generated from a single, fixed requirements set, every vendor answers the same questions, and the responses can be scored against each other rather than read in isolation.

Building criteria you can trust starts with who builds them.

A weighting model is only as neutral as the person setting the weights. Lightbridge ERP is an independent ERP advisory firm that holds no referral fees, partner-tier incentives, or reseller quotas with any software vendor, so a category does not get quietly upweighted because it favors a platform the firm is paid to sell.

This guide describes the framework anyone can apply. Lightbridge ERP runs the same framework as a structured, evidence-based engagement, from current-state assessment through a documented recommendation and an implementation roadmap. See the full ERP selection method for how the stages connect, or read what an ERP consultant does across the broader lifecycle.

ERP selection criteria: frequently asked questions

What are ERP selection criteria?: ERP selection criteria are the documented, weighted requirements an organization uses to evaluate and score competing ERP platforms before choosing one. They typically span functional fit, total cost of ownership, technical architecture and integration, vendor and partner viability, implementation readiness, security and compliance, scalability, and usability. Criteria turn ERP selection from a demo-driven impression into an evidence-based comparison that holds up to later scrutiny.
What should be included in an ERP RFP?: An ERP RFP should include a company and project overview, the weighted requirements list organized by category, specific questions on functional capability, integration and technical architecture, implementation methodology and timeline, total cost of ownership across license, implementation, and ongoing administration, vendor and partner references, and the evaluation criteria and scoring method the vendor will be judged against. An RFP built directly from a scored requirements set produces comparable, apples-to-apples vendor responses instead of marketing material.
How do you weight ERP selection criteria?: Weight ERP selection criteria by business impact, not by ease of comparison. Start by separating must-have requirements, which disqualify a platform outright if unmet, from weighted preferences. Then assign relative weight to each preference category based on how much it actually affects the outcome for that specific organization: a company with complex multi-entity consolidation weights financial architecture heavier than a single-entity business would. Score every candidate on the same numeric scale in every category, then multiply by weight and total the result.
Who should be involved in building ERP selection criteria?: ERP selection criteria should come from the people who will actually operate inside the system: controllers and accounting staff who close the books, operations and supply-chain leaders, IT for the technical and integration requirements, and an executive sponsor who can arbitrate a weighting disagreement between departments. Criteria written by a single function, often IT or finance alone, tend to underweight the categories the excluded departments would have flagged as critical. Lightbridge ERP builds every requirements set with representatives from each function the platform will touch, then runs the weighted result through the full ERP selection process.
How many ERP vendors should you evaluate?: There is no fixed number. A shortlist needs enough candidates for the scorecard to show real contrast between platforms, and few enough that each one gets a genuine scored evaluation rather than a rushed pass. In practice, most organizations land on a handful of platforms once an initial landscape scan filters out anything that fails a must-have requirement. The right count follows from how sharply the must-haves narrow the field, not from a target set before the requirements exist.
Should price be the primary ERP selection criterion?: No. Total cost of ownership belongs on the scorecard as one weighted category among several, never as the sole deciding factor. Implementation, integration, data migration, training, and ongoing administration typically add up to more than the license line over the life of the system, but the entire point of weighting is that no single category overrides the rest on its own. A platform picked mainly for a low sticker price commonly turns out to be the costlier choice once the other categories are counted.
What is the most common mistake in building ERP selection criteria?: The most common mistake is skipping a disciplined requirements-gathering step and scoring platforms against a generic feature checklist instead of the organization's actual workflows. A close second is letting a demo, rather than the scorecard, drive the decision: a well-rehearsed demonstration can make a poorly-fitting platform look strong. Criteria built with the people who run finance and operations, and scored consistently across every candidate, are what keep the decision anchored to evidence.
Do ERP selection criteria differ by industry?: Yes. A government contractor weights DCAA-compliant timekeeping and incurred-cost reporting as must-haves that a retailer would never list. A distributor weights inventory and warehouse depth heavier than a professional-services firm would, which instead weights project accounting and resource management. The category structure, functional fit, TCO, architecture, vendor viability, implementation readiness, security, is consistent across industries. What changes is which requirements inside each category are must-haves versus preferences.

Turn the scorecard into a defensible decision.

Lightbridge ERP builds the weighted requirements, runs the scored evaluation, and carries the recommendation into an RFP process, with no vendor kickbacks steering the outcome.

Talk to an ERP advisor See the selection method