How to Choose Manufacturing ERP Software: The Mid-Market Buyer's Guide

MonitorZ is a comprehensive guide for mid-market manufacturers evaluating job shop ERP software. It provides a vendor-neutral framework that includes defining manufacturing modes, building a requirements scorecard, and understanding total cost of ownership to help manufacturers make informed decisions.

By Dave Medinis in Guides

A vendor-neutral framework for evaluating ERP for job shops, discrete manufacturers, and mixed-mode facilities. Covers requirements scoring, TCO calculation, scripted demos, and red flags.

Why Most ERP Evaluations Fail Before They Start

Most manufacturers approach ERP selection backwards. They schedule demos before they've defined requirements, compare pricing before they understand total cost of ownership, and end up buying software built for someone else's operation.

This guide gives you the framework that systems integrators use internally — the one rarely shared with buyers.

Step 1: Define Your Manufacturing Mode First

ERP software is not one-size-fits-all. The single biggest determinant of whether a system will work for you is whether it was designed for your manufacturing mode:

  • Discrete manufacturing (make-to-order, engineer-to-order, assemble-to-order): Requires strong BOM management, work order routing, and job costing. Systems like MonitorZ, Epicor, and JobBOSS are designed for this.
  • Process manufacturing (batch, continuous): Requires formula management, lot traceability, and yield tracking. SAP, Oracle, and Infor are the dominant players.
  • Mixed-mode: Requires flexibility across both models. Most mid-market systems claim to handle this — few do it well.

Selecting a process manufacturing ERP for a job shop is one of the most common and expensive mistakes in the industry.

Step 2: Build Your Requirements Scorecard

Before touching a vendor, document your must-have vs. nice-to-have requirements across these eight functional areas:

  1. Production planning and scheduling — Can it do finite capacity scheduling, or only infinite?
  2. Bill of Materials management — Does it support multi-level BOMs, revision control, and BOM explosion into work orders?
  3. Shop floor data collection — Does it have mobile/tablet interfaces for operators, or does data entry require desktop access?
  4. Job costing and variance analysis — Can it track actual vs. estimated labor and material costs at the work order level?
  5. Inventory and warehouse management — Does it handle lot/serial tracking, cycle counting, and multiple locations?
  6. Quality management — Built-in inspection workflows, non-conformance tracking, and corrective actions, or is quality an add-on?
  7. CRM and customer order management — Native sales order management, or does it require a separate CRM integration?
  8. Reporting and analytics — Configurable dashboards, or fixed reports you can't modify without a consultant?

Step 3: Calculate Total Cost of Ownership Honestly

The license or subscription price is rarely more than 30-40% of what you'll actually spend over five years. A complete TCO model must include:

  • Implementation and configuration (typically 1x to 3x the first-year license cost for mid-market ERP)
  • Data migration from your current systems
  • Training — both initial rollout and ongoing for new hires
  • Annual support and maintenance fees
  • Customization and integration costs when the base system doesn't fit your process
  • Internal IT or project management resources diverted during implementation

A system priced at $2,000/month can easily cost $150,000-$300,000 in total first-year spend when implementation is included.

Step 4: Run a Scripted Demo, Not a Sales Demo

Never let a vendor run their own demo script. Prepare your own three to five key business scenarios — real workflows from your operation — and require every vendor to demonstrate those exact workflows. Common scenarios worth scripting:

  • A customer places a rush order for a configured product. How does that flow from quote to work order to shop floor to shipment?
  • A component comes in short. How does the system notify production scheduling, and how are affected work orders rescheduled?
  • A quality reject happens mid-production. How is the non-conformance logged, disposition decided, and cost captured?

If a vendor cannot demo your actual workflow, they cannot run your actual operation.

Step 5: Reference Check the Right Way

Vendor-provided references are pre-screened for satisfaction. Ask instead for:

  • Three customers in your specific manufacturing mode who went live in the last 18 months
  • One customer who had implementation challenges and how they were resolved
  • Direct contact with the implementation team (not just the sales team) who will be assigned to your project

The Mid-Market ERP Shortlist for Manufacturers (2026)

For discrete and mixed-mode manufacturers under $100M in revenue, the realistic shortlist typically comes down to four categories:

  • Purpose-built manufacturing platforms like MonitorZ — designed from the ground up for production control, typically fastest to implement and lowest TCO for job shops
  • Mid-market ERP suites like Epicor Kinetic, JobBOSS2, or Macola — broader functionality but heavier implementation requirements
  • Platform extensions like Zoho Creator or Microsoft Business Central with manufacturing add-ons — flexible but require significant customization
  • Legacy systems like older versions of Infor or Syspro — often underpriced but with technical debt and limited roadmaps

Red Flags During Evaluation

These should trigger serious concern during any ERP evaluation:

  • The vendor cannot name three customers in your manufacturing mode
  • The implementation timeline is under 8 weeks for any system with real ERP scope
  • Pricing requires a "custom quote" with no published starting point
  • The demo requires significant setup and cannot show live data workflows
  • Contract terms lock you in for 3+ years with no exit provisions

Making the Final Decision

Score each vendor on your requirements scorecard, add the TCO estimate, factor in implementation risk based on references, and rank. The winner is rarely the cheapest or the most feature-rich — it's the one with the best fit to your specific mode, your team's technical capacity, and your implementation timeline requirements.

MonitorZ is specifically designed for discrete manufacturers who need production control running in weeks, not years. If you want to see how it maps to your scripted demo scenarios, request a workflow demo.

Common questions

How do I evaluate manufacturing ERP software?

To evaluate manufacturing ERP software effectively, start by defining your manufacturing mode and building a comprehensive requirements scorecard. This approach ensures that you select a system tailored to your specific operational needs, avoiding common pitfalls like comparing pricing before understanding total cost of ownership.

What should be included in a scripted ERP demo?

A scripted ERP demo should focus on your specific requirements rather than a generic sales presentation. This allows you to see how the software handles your unique processes, ensuring it meets your operational needs before making a commitment.

What are the common mistakes in ERP evaluations?

Common mistakes in ERP evaluations include scheduling demos before defining requirements and comparing prices without understanding total cost of ownership. These errors can lead to selecting unsuitable software that doesn't align with your manufacturing operations.

How can I calculate the total cost of ownership for ERP software?

To calculate the total cost of ownership (TCO) for ERP software, consider not just the subscription price but also implementation costs, training, support, and any necessary customizations. A complete TCO analysis helps you understand the full financial impact over the software's lifecycle.

What functional areas should I assess when choosing ERP software?

When choosing ERP software, assess functional areas like production planning, inventory management, and quality control. Documenting must-have and nice-to-have features across these areas ensures that the selected system meets your operational requirements.