How to Select an ERP for Your Business
The warehouse says 38 units are available. The accounting report says 34, and a customer order for 36 is waiting for confirmation. That mismatch is exactly the kind of moment that sends an owner looking for an enterprise resource planning system, or ERP. The difficult part is not finding software with inventory screens. It is determining whether a system can represent the work, controls, and exceptions that keep your business running.
An ERP connects core business records and processes such as purchasing, inventory, order management, accounting, and production. It can reduce repeated entry and give teams a consistent view of transactions. It also makes choices about data, workflow, and responsibility more consequential. A poor fit can turn ordinary exceptions into expensive workarounds, so selection should test real operations before contract terms and demonstrations carry the day.
Define the operating problem and boundaries
Name the decisions that the ERP must improve. Examples include knowing whether promised stock is actually available, seeing the margin on an order, reconciling receipts to supplier invoices, or closing the books with fewer manual adjustments. Avoid goals such as “modernize everything” unless you can say what better operation means and who will measure it.
Map the process from a real transaction. Follow one purchase from request through approval, purchase order, receipt, invoice, and payment. Follow one customer order through allocation, fulfillment, shipment, invoicing, and cash receipt. A manufacturer should trace a product through its bill of materials, work order, material issue, production completion, and finished goods. Identify handoffs, approvals, corrections, and information that currently exists only in someone’s memory.
Set boundaries. Decide which departments, legal entities, locations, product lines, currencies, and processes belong in the first release. Write down what remains outside the ERP and how it will exchange data. An ERP does not need to own every function to be useful. Payroll, ecommerce, customer support, or specialized production planning may remain separate when the boundary is explicit and the connection is supportable.
Give each process a decision owner. Finance should own financial definitions and close controls. Operations should own inventory and fulfillment rules. An executive sponsor should settle tradeoffs across departments. If every issue waits for the owner, implementation will stall even when the vendor's software works as promised.
Conduct fit gap analysis before demos
Fit gap analysis compares a documented business requirement with what a proposed system can do through standard configuration, an available module, a partner extension, a custom change, or a manual workaround. Those options have different cost and operational consequences. Ask the vendor to label every response, rather than calling all of them a fit.
For each requirement, record the business reason, current method, expected control, volume, exception, owner, and evidence needed. Include accounting periods, tax handling, units of measure, lot or serial tracking, approval limits, returns, credit holds, and inventory adjustments when they apply. In Puerto Rico, confirm the relevant entity, tax, shipping, currency, and reporting needs with your accountant and qualified advisers. Do not assume a generic United States configuration answers every local obligation.
Classify each item as standard fit, configured fit, extension, custom work, workaround, or not supported. For a workaround, name its owner and the extra reconciliation it creates. For custom work, ask who upgrades and tests it later. If a requirement is legally or financially material, a promise to “handle it during implementation” is not evidence.
Make the demo earn your confidence
A polished demonstration can make any product look simple because the vendor controls the data and the path. Bring your own fictional or safely masked examples instead. Prepare a small data set that includes an ordinary customer, a duplicate supplier, a partial receipt, a returned item, an order with a discount, and a period end adjustment. Ask the vendor to show the same transaction in the systems of the people who touch it.
Walk through one order from beginning to end. Enter the order, check availability, reserve stock, fulfill part of it, record shipment, invoice the customer, and inspect the accounting entries. Then introduce a change. The customer needs a different quantity, or the shipment arrives late. Observe whether history remains clear, who can approve the change, and how inventory, finance, and the customer record stay aligned.
Do not let the presenter skip the uncomfortable part. Ask to see how a failed posting is corrected, how a closed period is protected, how an approval is recorded, and how a user finds an order from an invoice. A screen that looks comprehensive may conceal a handoff to a spreadsheet or a separate module. Ask which functions require an extra license or implementation partner.
Use a fixed script for every finalist. Have an employee who understands the process but did not design the script perform the task. Record time, number of handoffs, unclear labels, and missing controls. The purpose is not to reward the fastest demo. It is to find out whether the system exposes a process your team can reliably operate.
Compare systems with a weighted scorecard
Choose weights before demonstrations. Rate evidence on the same scale and retain notes that explain each rating. Set must have thresholds for compliance, accounting, data export, and critical operations rather than assuming a high total score compensates for a failure in one area.
| Criterion | Suggested weight | Evidence |
|---|---|---|
| Core process fit and controls | 25 percent | Complete sample transactions and exceptions |
| Finance and reporting accuracy | 20 percent | Trace entries and reconcile sample balances |
| Usability for daily roles | 15 percent | Observe staff performing their tasks |
| Integration and data access | 15 percent | Test an interface and export relationships |
| Implementation partner and support | 15 percent | Review team, references, scope, and escalation |
| Lifecycle cost and exit | 10 percent | Price three years and document a migration path |
Adjust the weights to match your operation. A distributor with complex allocation may prioritize inventory and order flow. A service business may emphasize project costing and time capture. Keep risk visible as a separate list even if it is also reflected in scores. A spreadsheet does not make uncertainty disappear.
Calculate the total cost of ownership
Total cost of ownership includes more than recurring licenses. Count implementation and partner fees, process redesign, data profiling and cleanup, migration, integrations, reports, testing, training, project management, and employee time. Include ongoing administration, support, version upgrades, custom work, additional storage, and the cost of keeping interfaces running.
Ask how subscriptions are priced. A vendor may charge by named user, concurrent user, module, entity, transaction volume, or a mixture. Confirm which environments are billable, what functionality comes with each tier, and whether partner or third party software carries separate fees. Request a written view for the number of users and modules you actually expect, not a generic starting estimate.
Price scenarios that could change the deal. What if you add a location, legal entity, or warehouse? What if you reduce seats? What happens to renewal pricing after an introductory discount? How are required updates, storage growth, and extra support billed? Ask whether the agreement guarantees access to your data and states the process and fee for exporting it.
Illustrative example. A proposed ERP is quoted at $24,000 per year for subscriptions. The implementation estimate is $85,000. Internal staff are expected to spend 1,100 hours at an illustrative loaded cost of $42 per hour, or $46,200. Integration work adds $18,000, and annual support and administration are estimated at $15,000. The first year planning total is $188,200, before contingency and any production disruption. The number is hypothetical. Its value is that it shows what a license only comparison leaves out.
Ask for a range and assumptions when uncertainty is real. A responsible estimate states what data volumes, locations, integrations, customizations, and staff availability it assumes. It separates one time work from recurring fees, identifies exclusions, and explains how a change request affects price and schedule. A precise total built on untested assumptions is not more reliable than an honest range.
Check references and implementation capability
The implementation partner can matter as much as the product. Ask who will lead discovery, data conversion, configuration, testing, training, and cutover. Request the names and roles of the people expected to work on your project. Confirm their availability and what happens if a key consultant leaves.
Speak with references that match your size, industry, operational complexity, and region. Ask how the partner handled a disagreement about process, a data problem, and a scope change. Ask whether the delivered system matched the written scope and whether staff can now make routine changes. A reference who has only just gone live cannot tell you much about support over time.
Confirm what the implementation partner will document and transfer. You should receive data mappings, configuration decisions, integration specifications, test cases, operating procedures, training materials, and an issue list with owners. Ask who owns custom code and whether it is held in an account you control. The contract should specify acceptance criteria, change control, access, and what happens if the project pauses or ends early.
Treat migration and cutover as business risks
Old records are not automatically ready for a new system. Profile duplicates, inactive items, inconsistent units, missing customer terms, invalid addresses, and unexplained opening balances. Decide what history must move, what can remain read only, and what should be archived. Preserve source identifiers so a new record can be traced back to the old one.
Plan trial conversions. Load representative data into a test environment, run real transactions, and reconcile counts and balances. For finance, agree with the controller on which ledgers, open receivables, payables, inventory values, and retained history must match. For operations, test locations, lots, reservations, and units of measure. Fix the mapping when the reconciliation fails rather than adding a manual adjustment to make the numbers look right.
Cutover needs a decision rule. Name the people who can approve go live, the conditions that must pass, the transactions that must stop during conversion, and the process for transactions that arrive during the pause. Define what evidence would trigger rollback and how you would restore access to the prior system. A parallel run can compare outputs, but it costs staff time and must have an end date. Running two systems indefinitely is not a transition plan.
Ask these questions before signing
Ask which requirements are delivered without customization and which depend on a partner or future release. Ask who is responsible when an integration fails across vendor boundaries. Ask how critical reports are defined and tested. Ask for the process to restore a backup and for evidence that restoration is tested. Ask how quickly you are notified about a security incident and which subcontractors can access data.
Ask what you can export without professional services, including attachments, audit history, and links between records. Ask whether the subscription permits a test environment and what its limits are. Ask for the product roadmap only as context, not as a substitute for capabilities available today. Put important promises in the order form or implementation statement of work.
Have legal, tax, accounting, security, and operational advisers review the terms that concern them. Requirements vary by business and jurisdiction, and this article is not legal or tax advice. In particular, verify retention, privacy, tax treatment, and service commitments with people qualified to advise your business.
Start with a controlled first release
Choose a release boundary small enough to test but large enough to complete a meaningful process. Identify the owner for each data domain, the decisions that remain manual, and the acceptance tests that prove the new workflow works. Train by role. An order clerk needs a different lesson from a controller or administrator.
For Monday morning, pick one transaction that crosses two departments and write down every system, approval, and correction it touches. Ask finance and operations to agree on the result that must match at the end. Then use that transaction as the first fit gap and demonstration script. If a vendor cannot explain it plainly, the implementation will not become easier after signing.
An ERP selection is a choice about how the company will record and control its work for years. Compare operational evidence, honest lifecycle cost, and the ability of your own staff to maintain the result. If your team needs help turning that evidence into an integration or operations plan, Ozcorp InfraOps can support that evaluation. Keep the decision grounded in the transactions that matter most.
Discuss your infrastructure requirements
Review the current service offer or schedule a conversation about the scope you need.
Stay in touch
Follow Ozcorp
Leave your details for occasional notes about new articles and Ozcorp updates.