Independent ERP and system selection
How do you write ERP requirements and an RFP?
Write ERP requirements by walking through how the business actually runs, area by area, and stating each need as a testable sentence. Score every item must, should or could. Then turn the list into a weighted selection criteria matrix and an RFP that asks vendors to show, not claim. Good requirements are the cheapest protection against a wrong ERP decision.
Why do requirements matter more than the vendor list?
Most failed ERP projects did not pick a bad product. They picked a product against a vague idea of the business. When a vendor writes your requirements, they describe what the vendor does well. When you write them, you describe what you need. That difference decides the demos, the pricing and the contract. For the larger decision, see how to choose an ERP and our independent ERP selection page.
What should an ERP requirements checklist cover?
Use these areas as headings. Under each, write the specific things your company does. Delete areas that do not apply.
Finance
- Chart of accounts structure, entities, departments and locations.
- Multi-entity consolidation and intercompany eliminations.
- Month-end close steps and the target number of days.
- Revenue recognition rules, budgeting, fixed assets.
- Audit trail and approvals.
Order to cash
- Quote, order entry and customer-specific pricing and terms.
- Credit holds, back orders, returns, drop ship.
- Invoicing formats, tax handling, collections.
- Connection to ecommerce, EDI or point of sale.
Procure to pay
- Purchase requests, approvals and purchase orders.
- Three-way match of order, receipt and invoice.
- Vendor management and payment runs.
Inventory and warehouse
- Item master, units of measure, lot or serial tracking.
- Multi-location stock, transfers and cycle counts.
- Scanning, bins and pick, pack and ship.
- Replenishment and demand planning.
Manufacturing (if relevant)
- Bills of material and routings, including revisions.
- Work orders, shop floor reporting and capacity.
- Costing methods and variance tracking.
- Quality records and traceability.
Reporting
- The ten reports the owner and CFO actually use, listed by name.
- Dashboards by role, drill-down to transactions.
- Ad hoc analysis without custom coding.
Integrations
- List every system that must connect: CRM, payroll, ecommerce, shipping, banking, tax.
- For each: direction of data, frequency and who owns the connection.
Security
- Role-based access, segregation of duties, single sign-on.
- Logging, backup, recovery and data location.
- Vendor security documentation and audit reports you can review.
Data migration
- What history to bring over and what to archive.
- Who cleans customer, vendor and item data, and by when.
- Test loads, reconciliation checks and cutover approach.
How do you write a good requirement?
A good requirement is one sentence, in plain language, that a vendor can demonstrate. Compare these two:
- Weak: "System must support flexible pricing."
- Strong: "The system applies a customer-specific price list, with a quantity-break override, and shows the margin on the order before it is released."
The strong version can be scripted for a demo and scored. Include the real exceptions too: the odd customer, the split shipment, the intercompany sale. Exceptions are where systems fail.
On one multi-brand distributor engagement, the team wrote 240 business requirements and scored every platform considered against them. The list was long because the business was complicated, not because length was the goal. See the distributor case study.
How do you score requirements as must, should or could?
| Level | Meaning | How to use it |
|---|---|---|
| Must | The business cannot run, or breaks a legal or customer commitment, without it | A "no" disqualifies the vendor or requires a funded workaround |
| Should | Strong value, and a workaround exists | Weighted heavily in scoring |
| Could | Nice to have, or a later phase | Tiebreaker only |
Keep must-haves under about a fifth of the list. If the share is higher, you are describing today's habits, not needs. Ask for each one: what happens if we cannot do this on day one?
Before you write requirements, find out which of your current systems are already doing the job.
Take the Systems CheckWhat does a selection criteria matrix look like?
Group the requirements into categories, assign each a weight that totals 100, score each vendor from 0 to 5 per category from the scripted demo, and multiply. Here is a simple version:
| Criteria | Weight | Vendor A (0 to 5) | Vendor B (0 to 5) | Vendor C (0 to 5) |
|---|---|---|---|---|
| Functional fit: finance and order to cash | 25 | |||
| Functional fit: inventory, warehouse, manufacturing | 20 | |||
| Reporting and analytics | 10 | |||
| Integrations | 10 | |||
| Security and compliance | 5 | |||
| Implementation partner and approach | 10 | |||
| Total cost over five years | 15 | |||
| Vendor stability and references | 5 | |||
| Weighted total | 100 |
Score as a group, but have each person score alone first, then compare. Big disagreements show where a requirement was unclear. Do not skip the cost line: see ERP costs not in the quote.
What goes in the ERP RFP?
- Company overview. Size, locations, entities, industries, growth plans.
- Scope and goals. What problems this project must solve, and what is out of scope.
- Requirements. The scored list, with a response column: standard, configuration, customization, third party, or not available.
- Demo scripts. Real scenarios from your business that vendors must run live with your sample data.
- Implementation approach. Who does the work, the team, phases, timeline and what you must supply.
- Pricing in a fixed format. Subscription or license, implementation, data migration, integrations, training, support, and renewal increases, so vendors are comparable.
- References. Customers of your size and type that you can call.
- Contract terms. Data ownership, exit, service levels, price caps.
- Process and dates. Questions, submission deadline, demo window, decision date.
Send it to three or four vendors, not ten. Our list of questions to ask ERP vendors makes a good addendum.
What mistakes spoil an ERP requirements list?
- Copying the current system. A list of what the old system does reproduces its flaws. Start from the process you want.
- Letting vendors supply the template. Their template reflects their product.
- Skipping the people who do the work. The warehouse lead and the billing clerk know the exceptions.
- Treating data migration as an afterthought. Dirty customer and item data hurts any system.
- Never testing it. A requirement that nobody scripts in a demo was not a requirement.
Common questions
How many ERP requirements should we write?
Enough to describe how your business really runs, and no more. Many mid-size companies land between 100 and 250. One distributor we cite wrote 240. Quality matters more than count: each requirement should be testable in a demo.
Should every ERP requirement be a must-have?
No. If everything is a must, nothing is. Reserve must-have for what the business cannot run without, such as a legal or customer-contract need. Most requirements should be should-have or could-have.
Do we need a formal RFP to choose an ERP?
Not always. A shortlist of three or four vendors, a written requirements list and scripted demos can work as well. A formal RFP helps when the board, lender or sponsor expects a documented process, or when you need comparable written pricing.
Who should write the requirements?
The people who do the work, led by someone who owns the outcome. Finance, operations, sales and warehouse leads each write their own area. An independent lead keeps the list consistent and keeps vendors from writing it for you.
Not sure where to start?
Take a free three-minute score. If a conversation makes sense, it will offer one.