Business software · Buyer guide
ERP or custom software: what should your business choose?
Compare ERP and custom software for an Ethiopian business. Map stock, purchasing, approvals, integrations and data before choosing a system.
Jump to the project checklistThe short answer
Choose ERP when the main need is shared stock, purchasing, approvals and reporting. Choose custom software when an important workflow does not fit a standard system. Some businesses need an ERP foundation with a custom portal or integration around it.
Choose around the work, not the product name.
| Your situation | A useful starting point | Check before committing |
|---|---|---|
| Stock and buying live in separate spreadsheets | ERP with inventory and purchasing | Locations, units, approval roles and opening balances |
| Customers need a specific booking or service journey | Custom software or a portal | Exceptions, permissions and connection to existing records |
| Core ERP works but one department has a special process | Keep ERP; assess an extension | Available interfaces, ownership and upgrade impact |
Start with one complete workflow.
Follow a real request from the person who raises it to the person who receives or approves the result. For construction, that might mean a site material request, head-office approval, store dispatch and site receipt. Write down who records each step, what they need to see and where mistakes happen.
For a warehouse or factory, make the locations and movements explicit. ERP inventory systems can record receipts, internal transfers and deliveries; the software still needs accurate records and consistent staff use. A new dashboard cannot fix movements that were never recorded.
Keep what is useful. Check what can connect.
List the systems already used by finance, operations and customers. Ask which can export data or provide a supported interface. A spreadsheet import, scheduled exchange and live integration are different scopes. Decide who resolves a failed transfer or conflicting record.
Compare configuration against custom development using the same example workflow. A demonstration with your own sample request is more useful than a long feature list. Include the difficult cases: partial receipts, rejected requests, returns and changes after approval.
Compare the full delivery cost.
Ask the proposal to separate licences or subscriptions, implementation, data preparation, integrations, training and ongoing support. Confirm which party owns the data and how it can be exported. Do not choose on the first installation price alone.
For a business with several sites in Ethiopia, agree connectivity needs, local support arrangements and the workflow during an outage. Offline operation must be specifically designed and tested; it is not a feature to assume.
Make the first phase useful on its own.
Start with a defined department or process, clean its data and give staff time to test it. Agree practical acceptance checks: a request reaches the right approver, a receipt updates the correct store and the manager can explain the resulting report.
Black Mount can help assess the workflow, plan the ERP or custom scope, connect compatible systems and train the people using them. Expand after the first workflow is reliable.
Project checklist
Bring these to an ERP or software discussion
- One real workflow, including a difficult exception
- Sample stock, supplier or customer records with sensitive details removed
- The departments, users and sites involved
- Your existing systems and available export or integration options
- The reports, support and handover you expect
References & further reading
Primary sources for the technical background. Our comparisons and checklists are planning guidance; the project scope follows an assessment.
- Odoo: inventory operation types
An example of how an ERP records stock movements. Product selection depends on your requirements.