Evaluate ERP vendors against the same business scenarios, data and acceptance evidence. A polished demonstration shows what a vendor chose to show; a buyer-led demonstration reveals how the proposed system handles your routine work and its exceptions. Score demonstrated outcomes separately from promised development, and record the configuration, manual steps and dependencies needed to achieve each result.
Let’s plan your ERP evaluation.
Bring your workflow and the decisions you need to make. We’ll help you define the requirements, examine the trade-offs and plan a practical next step.
Prepare a demonstration pack
Choose one operational transaction that crosses meaningful boundaries. For example, purchase materials, receive a partial delivery, place a quantity on hold, release it and dispatch a customer order. Add a correction that your staff regularly encounter.
Use sanitised records with realistic item types, quantities and roles. Explain the expected business outcome without dictating every screen interaction. Give every vendor the same pack and enough preparation context to avoid rewarding familiarity with hidden instructions.
Name the people judging each outcome. Operations should assess usability and exception handling; finance should assess posting and reconciliation; engineering should assess integrations and supportability. One impressive dashboard should not decide all three.
Use a scored script
| Scenario | Evidence to request | Suggested classification |
|---|---|---|
| Receive a partial delivery | Remaining commitment and receipt history | Demonstrated / unresolved |
| Reject part of a receipt | Hold status and authorisation | Demonstrated / unresolved |
| Correct a posted quantity | Linked correction and final balance | Demonstrated / unresolved |
| Lose an integration connection | Pending state and recovery process | Demonstrated / unresolved |
| Attempt an unauthorised change | Enforced refusal and useful record | Demonstrated / unresolved |
| Export operational records | Usable sample export and ownership terms | Demonstrated / unresolved |
Add a business importance score if it helps, but agree the scoring before the meetings. A numerical total must not conceal failure of a non-negotiable requirement.
Separate a product capability from a proposal
Classify each result as demonstrated in the offered configuration, demonstrated using an extension, planned development, or unsupported. Record the version and configuration actually shown.
A supplier saying “we can build that” may be making a valid proposal. It is different evidence from an existing capability. Ask for the proposed scope, acceptance criteria and responsibility for maintaining the addition. Carry the estimate and dependency into the comparison.
Test an interruption
During a hypothetical dispatch demonstration, pause the accounting connection after the dispatch is committed. Ask what the operator sees, how the request is retried and how a duplicate is prevented. Then ask the vendor to reconcile the transaction after recovery.
The purpose is not to manufacture a surprise technical challenge. It is to reveal whether your staff would know what to do on an ordinary difficult day. Schedule this scenario in the pack so suppliers can bring the appropriate specialist.
Turn findings into a decision register
For every unresolved point, name the affected process, business consequence, evidence still needed and decision owner. Keep implementation effort, recurring costs and commercial terms alongside the functional assessment.
The Microsoft process-focused implementation guide provides useful context for organising implementation around business processes. The demonstration worksheet here is an original buyer planning tool, not a Microsoft certification procedure.
Questions procurement teams ask
Should we choose the highest score?
Use the score to structure discussion. Reject or resolve critical gaps explicitly rather than allowing many minor conveniences to outweigh an essential control.
Can a recorded demo replace a live session?
It can establish basic capability, but it rarely resolves your actual exception paths. Request evidence tied to your scenario and offered configuration.
Before selecting a supplier
Complete the decision register and compare the same scope. Use the build-or-buy framework and ERP development overview to connect the demonstration findings with the delivery decision.
