01
Start with project structure
Agree the hierarchy of project, site and work package. The demonstration should report at the level your commercial team actually manages.
Plan / ERP buyer series
An EPC ERP demo should prove project control
Give every shortlisted ERP team the same anonymised project, budget and purchase scenario. Require them to follow approval, commitment, partial site receipt, invoice and billing effects. Record where configuration or custom work is needed. The goal is an accepted project-control design—not the largest collection of module screens.
Discuss my ERP scope See the buying checklist
No purchase commitment. Submitting an enquiry does not book a meeting.
Which path fits your situation?
02
Test a real exception
Add a budget overrun, split delivery or revised order. Require a normal user to follow the approval and correction process.
03
End with reconciliation
Ask finance to explain the budget, commitment and actual amount without double-counting an order and its invoice.
Put the decision in writing
Use the same requirements for every proposal. Record what is included, what needs validation and who owns unresolved work.
| Scenario | Ask the vendor to show | Acceptance evidence |
|---|---|---|
| Over-budget request | Route the request to the correct approver. | Approval history and the resulting available budget. |
| Partial site receipt | Receive part of an order at the right site. | Open quantity, receipt and project allocation reconcile. |
| Transfer between sites | Move stock without losing its cost ownership. | Source, destination and reporting treatment are visible. |
| Milestone billing | Apply the sample contractual billing rules. | The commercial and finance owners agree the output. |
Swipe the table sideways to compare all columns.
Bring a small but connected data pack
Use one project, two work packages, a supplier, a purchase order and a sample billing format. Add user roles for requester, approver, storekeeper and finance. Provide expected quantities and totals so the vendor cannot substitute a convenient generic demonstration. Keep all records anonymised and agree which documents will be retained after evaluation.
Distinguish commitment from actual cost
Ask when a purchase becomes a commitment and when it becomes an actual cost under your agreed accounting policy. Check what happens on a price revision, return and supplier credit. A project report should expose its calculation and drill back to relevant documents. A visually attractive dashboard is not sufficient if the finance team cannot explain its totals.
Convert the demo into the statement of work
For every unproven scenario, record the gap, delivery owner, estimate and acceptance condition. Include site connectivity, device access and training assumptions. Separate a demonstration of a standard capability from a promise to develop it later. Braincuber uses a workflow review to identify these decisions before proposing an EPC rollout; your contract should retain the resulting test script.
From comparison to a scoped proposal
Bring one workflow.
Ask better questions.
Braincuber offers Community-based custom ERP and Odoo Enterprise implementation. We will review fit, gaps and responsibilities before proposing delivery. Bring anonymised examples—not confidential records.
Request a scoped discussion
Questions before you commit
Is this an implementation tutorial?
No. It is a buyer acceptance script to use when evaluating a proposed ERP. The configuration depends on your project and accounting rules.
Can we begin with one site?
Yes, if its dependencies on purchasing, finance and shared stock are included in the scope. A small phase still needs a complete reconciliation boundary.
Should all EPC vendors use the same demo data?
Yes. Equivalent scenarios make gaps, manual steps and extra development easier to compare.
Sources and how to use this guide
Braincuber sells ERP implementation services. Product statements refer to the vendor sources below; the evaluation scenarios and recommendations are our analysis. Verify the current edition and commercial terms in your written quote. We have not assigned independent ratings, tested every configuration or invented customer results.
This is an original procurement checklist, not a claim about a particular software edition or a customer case study.