Evaluation checklist
ERP, POS & Ecommerce Demo Checklist
Bring the same operating evidence to every ERP, POS and ecommerce demonstration. A shared acceptance pack makes the comparison more useful than separate feature tours built around each vendor’s strongest screen.
Written by Tellency · Reviewed October 24, 2026. This is a vendor-authored evaluation. Product editions, regional availability and commercial terms should be confirmed with each provider.
Plan a workflow demo →Prepare a small, connected record set
Use a customer, supplier, product, branch and the relevant opening balances. Add a second location or legal entity only when it is part of the requirement. Choose examples that reveal the actual units, prices, approval thresholds and reporting relationships.
- Customer with an outstanding balance.
- Product with a supplier, unit, price and stock location.
- An authorised operator and a user without approval authority.
Run purchasing and inventory exceptions
Create a purchase, receive only part of it and correct a difference. Transfer stock and inspect the status before and after receipt. Record the documents, quantities, financial effect and responsible roles. Keep the evidence for each candidate system under the same scenario name.
Test checkout and the customer account
Sell, return and correct a transaction. Add loyalty, gift cards or layaway when relevant. Confirm the proposed hardware and payment method and what happens during a connection failure. Inspect the resulting customer balance rather than stopping at the printed receipt.
Place a web or app order end to end
Find a product, change a cart, select delivery or pickup and place the order. Follow acceptance, packing and completion. Compare the customer-facing status with the branch process, invoice, payment record and stock result. Include an unavailable item or an address outside the delivery area.
Evaluate an agent with the same controls
Ask an agent to perform a supported action on the sample records. Inspect required inputs, permission checks, approvals and execution evidence. Test a refused action as carefully as a successful one. Confirm the exact tools and usage terms included in each offer.
Write down evidence, gaps and ownership
For each scenario, record demonstrated behaviour, configuration work, integrations, unresolved gaps and the person responsible. Agree acceptance criteria, costs and the retest date. A useful final scorecard explains the remaining work rather than awarding a generic winner badge.
Questions before you choose
Should every vendor see the same demo scenario?
Yes. Comparable records, exceptions and expected results help the team distinguish demonstrated behaviour from assumptions.
What should the final evaluation document contain?
The scenario evidence, unresolved requirements, proposed configuration and integrations, costs, responsibilities and acceptance criteria.
Official sources and review notes
Sources were reviewed on October 24, 2026. Vendor documentation describes capabilities; your proposal and configured demonstration establish the scope you purchase.