Should You Fix Your Business Processes Before Replacing Your ERP?

When an ERP system struggles, the software usually takes the blame. Often the real problem sits upstream. Orders get entered three different ways. Each plant schedules production differently. Purchasing works around the system because the approval process does not match reality. A new ERP will not resolve any of that on its own. It will either enforce one version of the process or get customized to accommodate all of them.

Automating a broken process makes it faster, not better. Customizations built to preserve old workarounds raise implementation cost, slow upgrades, and make the system harder to support for years. Process confusion also shows up as poor adoption after go-live. Users who never agreed on how the work should be done will not agree on how the new system should do it.

• The same process runs differently across plants, warehouses, or shifts.
• Key steps depend on spreadsheets, email, or one experienced employee.
• Order-to-cash has frequent manual holds, rework, or credit memos.
• Inventory and cost reconciliation consume the first week of every month.
• Nobody can describe the end-to-end process without pulling in four departments.

Some companies hear “fix processes first” and launch a year-long improvement program before they touch ERP selection. That often stalls momentum and produces process designs the eventual software cannot support. The better approach is to fix decisions, not every detail. Agree on the future-state design for core processes, standardize where it matters, and remove obvious waste. Then let that design drive requirements and selection, with detailed process configuration finished during implementation.

1. Run a business process review. Interview process owners and walk the floor to understand how work actually moves today.
2. Map current-state processes. Document order-to-cash, procure-to-pay, plan-to-produce, and record-to-report end to end, including the workarounds.
3. Find the waste and the risk. Identify duplicate steps, manual handoffs, bottlenecks, and control gaps.
4. Design the future state. Agree on how each core process should run across the business, and who owns it.
5. Standardize and document. Write down the future-state processes so they become the basis for requirements and training.
6. Turn the design into requirements. Use the future-state processes to define ERP requirements and script vendor demos.

Ultra Consultants follows a process-first methodology. Before recommending any software, Ultra’s team uses Business Process Review, Business Process Mapping, and Business Process Reengineering to define how a manufacturer or distributor should operate. Those future-state designs feed directly into ERP Selection Consulting and support adoption through Change Management Consulting. Ultra has applied this approach across Distribution, Consumer Products, and Industrial Equipment companies.