< All Posts

ERP Selection for Supply Chain: How to Get It Right

ERP Selection for Supply Chain: How to Get It Right
ERP Selection for Supply Chain: How to Get It Right
Written by:
Mathew Tolley
Three connected circles forming a molecular structure icon on a dark blue background, with two blue circles and one grey circle linked by grey and white lines.
Written by:
Trace Insights
Publish Date:
Mar 2026
Topic Tag:
Technology

Ready to turn insight into action?

We help organisations transform ideas into measurable results with strategies that work in the real world. Let’s talk about how we can solve your most complex supply chain challenges.

Trace Logo

ERP selection is one of the highest-stakes technology decisions most organisations make. It shapes supply chain, procurement, finance, and operations for a decade or more. It consumes significant implementation budget — typically $1–10 million for Australian mid-market businesses, substantially more for large enterprises. And the cost of getting it wrong — years of operating on a poorly fitted system, eventually culminating in a costly rip-and-replace — is dramatically higher than the cost of the initial selection process.

Yet most organisations approach ERP selection reactively, under-resourced, and without the operational expertise to evaluate supply chain capability properly.

This article covers what a rigorous ERP selection process looks like for supply chain-intensive Australian organisations — and the most common mistakes to avoid.

Why ERP Selections Go Wrong

Before covering what to do, it's worth understanding the failure modes that are most common.

Buying brand, not fit. The major ERP vendors — SAP, Oracle, Microsoft Dynamics 365, NetSuite — all have strong brand recognition. Organisations often select a vendor based on brand confidence, peer reference, or analyst positioning rather than on a rigorous assessment of fit against their specific supply chain requirements. Brand is not irrelevant — vendor financial stability, ecosystem depth, and implementation partner availability all matter — but it is not a substitute for functional fit analysis.

Evaluating features, not use cases. ERP vendor demonstrations are designed to showcase capability. The demonstration shows the system doing impressive things — but not necessarily the specific things your supply chain needs to do, in your specific operational context, with your specific data. Selecting a system based on a vendor-led demonstration without testing it against your own use cases is the most common source of post-selection regret.

Under-investing in requirements definition. The quality of an ERP selection is directly proportional to the quality of the requirements that drive it. Organisations that invest three to four weeks in rigorous requirements definition — engaging supply chain, procurement, operations, and finance — select better and implement better. Organisations that shortcut this step typically find gaps post-selection that are expensive to close.

Underestimating implementation cost and complexity. ERP vendors quote software licences. Implementation costs — the consulting and integration work to configure, customise, migrate data, integrate systems, train users, and manage change — are typically three to five times the licence cost. Organisations that select a system based on licence cost alone without a realistic total cost of ownership model make commercially poor decisions.

Ignoring supply chain fit. Many ERP selections are led by finance or IT, with supply chain as a secondary stakeholder. This is backwards for supply chain-intensive businesses. The supply chain module of an ERP — demand planning, inventory management, procurement, warehouse management, manufacturing — is typically where the most process-critical functionality lives, and where the gap between different vendors is most material.

The Eight Requirements That Matter for Supply Chain

Not all ERP supply chain requirements are equally important. The following eight are the most critical to evaluate rigorously.

Inventory management. How does the system manage multi-location inventory, serialisation and batch tracking, FIFO/FEFO/LIFO costing, and inventory adjustments? For businesses with complex inventory — multiple warehouses, expiry dating, product traceability requirements — the depth of inventory management capability is a primary selection criterion.

Demand planning and forecasting. Does the system have native demand planning capability, or does it require a best-of-breed planning tool? What statistical methods does it support? How does it handle seasonal patterns, promotions, and new product introductions? For businesses where forecast accuracy has a material impact on inventory and procurement decisions, the quality of planning functionality is critical.

Procurement and purchase order management. How does the system manage the procure-to-pay process — from requisition through supplier management, purchase ordering, goods receipt, and invoice matching? Does it support three-way matching? How does it handle blanket orders, price books, and supplier catalogues?

Warehouse management. Does the system have a native WMS module, or does it integrate with third-party WMS solutions? For businesses with complex warehousing operations — multi-bin, pick-and-pack, cross-docking, returns management — the depth of WMS functionality (or the quality of integration to a best-of-breed WMS) is important.

Manufacturing and production planning. For manufacturers, MRP (Material Requirements Planning) and production scheduling capability is a core requirement. The quality of MRP logic — how it handles multi-level bills of materials, capacity constraints, lead time variability — varies significantly between ERP vendors and even between versions of the same vendor's product.

Integration capability. ERPs rarely operate in isolation. Integration with 3PL systems, carrier platforms, e-commerce platforms, supplier portals, and specialist planning tools is standard. The quality of the ERP's integration framework — API capability, pre-built connectors, data exchange standards — significantly affects implementation cost and operational reliability.

Reporting and analytics. What reporting and analytics capability does the system provide natively? What data model does it expose for external analytics tools? For supply chain teams that depend on data for performance management and decision-making, the reporting capability — or the cost and complexity of building it — is a material evaluation criterion.

Scalability and configurability. Will the system scale with the business as it grows? Can it be configured to match the organisation's operating model without expensive custom development? How does the vendor manage upgrades — will customisations need to be rebuilt with each major release?

The Selection Process

A rigorous ERP selection for a supply chain-intensive business follows five phases.

Requirements definition (4–6 weeks). Document current state processes, identify pain points and capability gaps in the current system, define future state requirements by process area, and develop a weighted requirements matrix that scores requirements by business criticality. Engage all major stakeholders — supply chain, procurement, operations, finance, IT.

Vendor longlist and RFI (2–3 weeks). Develop a longlist of vendors appropriate to the organisation's scale, sector, and requirements. Issue a Request for Information to the longlist — typically 6–10 vendors — to gather basic capability and commercial information. Score RFI responses against the requirements matrix and develop a shortlist of 3–4 vendors for detailed evaluation.

Detailed evaluation (6–8 weeks). Issue a detailed RFP to the shortlist. Conduct scripted demonstrations — vendor demonstrations conducted against your specific use cases, with your own sample data, rather than vendor-scripted showcases. Reference check with comparable Australian deployments. Conduct an implementation partner assessment alongside the software assessment.

Commercial negotiation (4–6 weeks). Negotiate licence terms, implementation scope, support terms, and total cost of ownership with the preferred vendor. Clarify contract terms — particularly around customisation, upgrade paths, and exit rights — before committing.

Business case and decision (2–3 weeks). Develop a total cost of ownership model across 5–7 years (licence, implementation, support, internal resource, opportunity cost of transition) and a benefits case (efficiency gains, capability improvements, cost savings). Present to the decision-making committee with a clear recommendation and risk assessment.

Implementation Partner Matters as Much as Software

In ERP selection, the implementation partner selection is as important as the software selection. Most ERP implementation problems are not software problems — they are implementation problems. A capable, experienced implementation partner with deep supply chain expertise and a track record of successful deployments in comparable Australian businesses is the most important risk mitigation in an ERP programme.

The major ERP vendors have large implementation partner ecosystems. The quality across these ecosystems varies significantly. Evaluating the specific partner — not just the vendor relationship — including team credentials, supply chain methodology, Australian references, and senior resource commitment, is essential.

How Trace Consultants Can Help

Trace Consultants provides independent ERP selection support for Australian supply chain-intensive organisations — helping define requirements, run vendor selection processes, evaluate supply chain functionality, and build business cases that support well-informed technology decisions.

Requirements definition: We facilitate structured requirements workshops with supply chain, procurement, operations, and finance stakeholders — producing a requirements document that drives a rigorous selection process.

Vendor selection management: We manage the RFI/RFP process, scripted demonstration design, reference checking, and commercial evaluation — providing independent assessment and recommendation.

Business case development: We build total cost of ownership models and benefits cases that give leadership teams the financial framework to make technology investment decisions confidently.

Explore our Technology services →Speak to an expert at Trace →

Ready to turn insight into action?

We help organisations transform ideas into measurable results with strategies that work in the real world. Let’s talk about how we can solve your most complex supply chain challenges.

Trace Logo