Manufacturing ERP Selection Checklist: 7 Key Requirements to Evaluate

A manufacturing ERP selection checklist should cover seven core requirements: production planning, bills of materials (BOMs), inventory management, shop-floor reporting, costing, quality control, and multi-site operations. Manufacturers should prioritize these capabilities and establish clear evaluation criteria before shortlisting ERP vendors.

Integration deserves particular attention. Rockwell Automation's July 2026 Scaling MES Across the Enterprise Report, based on responses from 1,560 manufacturing and industrial decision-makers across 17 countries, found that only 23% reported full integration of their manufacturing execution systems (MES) with ERP, product lifecycle management (PLM), quality, and operational technology (OT) systems. For manufacturing CFOs, COOs, and CIOs, evaluating these integration requirements early can help identify operational gaps, reporting risks, and potential implementation costs.

How Manufacturing Requirements Differ by Production Model

Manufacturing ERP requirements depend on how a company designs products, manages demand, and schedules production. Before evaluating vendors, manufacturers should identify the workflows their ERP system must support and determine which capabilities are essential to their operating model.

Make-to-Stock and Make-to-Order Manufacturing

• Make-to-Stock (MTS) manufacturers produce goods based on anticipated demand. ERP requirements typically emphasize demand forecasting, material requirements planning (MRP), inventory replenishment, and capacity scheduling.

• Make-to-Order (MTO) manufacturers begin production in response to customer orders. They need reliable order-level material planning, production scheduling, lead-time visibility, and delivery-date commitments.

For manufacturers using both approaches, the selection team should verify that an ERP system can support different planning methods across products without creating conflicting inventory or production records.

Engineer-to-Order and Configure-to-Order Manufacturing

• Engineer-to-Order (ETO) manufacturers design or modify products to meet specific customer requirements. Their ERP systems may need project-specific bills of materials, engineering revision controls, job costing, and coordination between engineering and production.

• Configure-to-Order (CTO) manufacturers assemble product variations from predefined options. Important capabilities include product configuration rules, automated BOM generation, component compatibility checks, and accurate pricing.

A useful vendor evaluation scenario involves changing a product specification after an order has been accepted. The manufacturer should verify how the system updates material requirements, production instructions, and associated costs.

Discrete and Process Manufacturing

• Discrete Manufacturers produce identifiable products or components, often using assembly operations. ERP selection criteria may prioritize multi-level BOMs, production routings, serial tracking, and work order management.

• Process Manufacturers produce goods using formulas, recipes, or batch-based production. They may require batch traceability, yield calculations, formula management, quality testing, and controls for variable material quantities.

Manufacturers with hybrid operations should confirm that prospective ERP solutions can accommodate both production methods, including their inventory, quality, and costing requirements.

The selection team should document these production-specific needs before assigning requirement weights. This helps ensure that vendor evaluations reflect the manufacturing processes the organization actually operates.

Manufacturing ERP Selection Checklist: 7 Critical Requirement Categories

Once the production model is established, manufacturers can define the capabilities an ERP system must support across daily operations. The following seven categories provide a practical framework for documenting manufacturing-specific functional requirements and evaluating prospective ERP solutions.

Each category includes criteria to assess and a suggested vendor demonstration scenario. These requirements should be adapted to the manufacturer's processes, products, and operational priorities. They should also be evaluated alongside broader selection considerations, including cybersecurity, data migration, deployment architecture, total cost of ownership, and implementation-partner capabilities.

1. Production Planning and Scheduling

Production planning capabilities determine how effectively manufacturers can coordinate customer demand, material availability, equipment capacity, and production commitments. An ERP system should give planners visibility into potential shortages and scheduling conflicts before they disrupt production.

Requirements to evaluate:

• Material requirements planning (MRP): Calculate material needs based on demand, inventory balances, BOMs, and purchasing lead times.

• Capacity planning: Account for work-center availability, equipment constraints, and production capacity.

• Work order scheduling: Create, release, adjust, and monitor production orders.

• Planning exceptions: Identify material shortages, overloaded work centers, and orders at risk of missing delivery dates.

What to verify: Ask the vendor to demonstrate how the system handles a delayed material delivery affecting several scheduled production orders. Planners should be able to identify affected jobs, evaluate scheduling alternatives, and determine the impact on committed delivery dates.

Read More: How ERP Software Transforms Production Planning in Discrete Manufacturing

2. Bills of Materials and Engineering Change Control

Bills of materials establish the components and quantities required to manufacture a product. Inaccurate BOMs or poorly controlled engineering changes can affect purchasing, production instructions, inventory consumption, and product costs.

Manufacturers should assess whether the proposed ERP system can manage their product structures and maintain reliable revision histories.

Requirements to evaluate:

• Multi-level BOMs: Support finished products, subassemblies, components, and required quantities.

• Engineering revisions: Track approved changes, revision histories, and effective dates.

• Production routings: Define manufacturing operations, work centers, and processing sequences.

• Component substitutions: Manage approved alternate materials and their effect on production.

What to verify: Present a scenario in which engineering changes a component after purchasing has placed an order but before production begins. The vendor should demonstrate how the revision affects existing material commitments, BOM records, and production instructions.

Read More: ERP for Hardware & IoT: Managing Complex BOMs and Supply Chains

3. Inventory and Warehouse Management

Inventory accuracy directly affects production schedules, purchasing decisions, and financial reporting. Manufacturers need dependable records of raw materials, work-in-process (WIP), and finished goods as inventory moves through the organization.

ERP selection criteria should reflect the manufacturer's actual storage locations, material handling methods, and traceability needs.

Requirements to evaluate:

• Inventory visibility: Track quantities and availability across warehouses, storage locations, and production areas.

• Material transactions: Record receipts, issues, transfers, returns, and adjustments.

• Lot and serial tracking: Maintain traceability where required by products, customers, or applicable standards.

• Work-in-process tracking: Account for materials consumed and goods moving between production stages.

What to verify: Follow a lot-controlled material from receiving through warehouse storage, production consumption, and finished-product shipment. Confirm that inventory records update correctly and that users can retrieve the material's transaction history.

4. Shop-Floor Reporting and Production Visibility

Shop-floor reporting connects manufacturing activity with production planning, inventory, and financial records. The ERP system must support how operators and supervisors actually record work during production.

Manufacturers should evaluate both the information captured and the practicality of collecting it on the factory floor.

Requirements to evaluate:

• Production progress: Record completed quantities, partial completions, and work order status.

• Labor reporting: Capture labor hours against the appropriate jobs or operations.

• Scrap and downtime: Document rejected quantities, equipment interruptions, and production exceptions.

• Material consumption: Record actual materials used and update related inventory transactions.

What to verify: Ask the vendor to demonstrate an operator reporting a partially completed work order with additional material consumption and rejected units. Review how those transactions affect inventory, production status, and job costs.

Also confirm that the required data collection methods are practical for the manufacturer's equipment, workforce, and shop-floor conditions.

Read More: ERP in Manufacturing: What It’s Really Like Day to Day

5. Manufacturing Costing and Financial Integration

Manufacturing costing determines how accurately production activity is reflected in inventory values, product margins, and financial statements.

Finance teams should evaluate how operational transactions move into accounting records and whether the system supports the organization's costing approach.

Requirements to evaluate:

• Product costing: Support required standard, actual, or other applicable costing methods.

• Work-in-process valuation: Capture material, labor, and overhead costs associated with unfinished production.

• Variance analysis: Identify differences between expected and actual manufacturing costs.

• Financial integration: Connect manufacturing transactions with inventory valuation, general ledger postings, and financial reporting.

What to verify: Use a production order where actual material usage and labor hours exceed planned quantities. Ask the vendor to demonstrate how the system calculates production costs, records variances, values completed inventory, and posts the relevant financial transactions.

Controllers should confirm that these results can be reconciled and analyzed without extensive manual adjustments.

Read More: How Small-to-Mid Manufacturers Can Maximize ERP ROI

6. Quality Management and Traceability

Quality management requirements vary by product, manufacturing process, customer obligations, and applicable standards. Some manufacturers need straightforward inspection records, while others require detailed traceability and controlled corrective-action processes.

The ERP evaluation should establish whether the required quality workflows can be supported consistently.

Requirements to evaluate:

• Quality inspections: Record incoming, in-process, and finished-product inspection results.

• Nonconformance management: Identify defective materials and control their disposition.

• Material traceability: Connect affected materials with production orders, inventory lots, and finished products.

• Corrective actions: Document quality issues, responsible personnel, actions taken, and approval status.

What to verify: Simulate a defective component discovered after it has been used in production. Ask the vendor to identify affected materials and finished products, demonstrate inventory hold procedures, and show how the issue would be documented.

Where industry-specific quality controls are necessary, determine whether they are available through standard functionality, additional modules, or integrations.

7. Multi-Site Operations and System Integration

Manufacturers operating multiple facilities need consistent information across locations while retaining the flexibility to manage local production requirements.

The ERP system should support the organization's reporting structure, intercompany activities, and connections with existing business applications.

Requirements to evaluate:

• Multi-site inventory: Track materials, transfers, and availability across plants and warehouses.

• Shared master data: Maintain consistent item, supplier, customer, and other relevant records.

• Intercompany transactions: Support required transfers, purchasing arrangements, and financial transactions between entities.

• Application integration: Exchange data with manufacturing execution systems (MES), warehouse systems, product lifecycle management (PLM), and other necessary applications.

What to verify: Ask the vendor to demonstrate a production scenario where one facility supplies components to another. Review how the system handles material transfers, inventory availability, production requirements, and related accounting entries.

IT leadership should confirm which integrations are supported through standard interfaces and which require additional development or third-party software. Where practical, vendors should demonstrate how transactions move between connected systems, including error handling, data synchronization, and reconciliation. Interface availability alone does not establish that an integration will support the manufacturer's operational requirements.

Where existing applications, data quality, or integration architecture require further assessment, RubinBrown's IT and Data Services can help organizations evaluate technical dependencies and identify risks that may affect ERP implementation planning.

Read More: How to Integrate ERP Systems with Legacy Software

Turning the Checklist Into Evaluation Criteria

After reviewing the seven categories, the selection team should consolidate its findings into a shared requirements worksheet. Each requirement should identify its business owner, priority, validation method, and relevant technical dependencies.

The resulting document provides a consistent basis for preliminary vendor qualification and the weighted scoring process that follows.

How to Build a Weighted Manufacturing ERP Requirements Scorecard

A weighted ERP requirements scorecard helps manufacturers compare software vendors based on the capabilities that matter most to their operations. By assigning priorities and scoring each system against consistent criteria, the selection team can evaluate functional fit and document the reasons behind its recommendations.

Before evaluating vendors, manufacturing leaders should agree on requirement weights, mandatory capabilities, and the evidence needed to validate functionality.

Step 1: Assign Weights Based on Business Priorities

ERP selection criteria should reflect the operational and financial impact of each requirement. Production scheduling, inventory accuracy, costing, and quality controls may carry different levels of importance depending on the manufacturer's production model.

The following example shows how a mid-market manufacturer might distribute evaluation weights across seven requirement categories.

These weights are illustrative and should be adjusted to the organization's needs. For example, a manufacturer with strict product traceability requirements may assign greater importance to quality management, while one facing frequent capacity constraints may prioritize production scheduling.

Requirements essential to production continuity, financial controls, or customer obligations should also be identified as mandatory qualification criteria, regardless of their assigned weight.

Step 2: Score Vendor Capabilities Consistently

A standardized scoring scale helps stakeholders assess competing ERP systems using the same criteria.

Scores should reflect the level of functional support established through product documentation, vendor responses, and demonstrations using relevant manufacturing scenarios. Preliminary scores may be assigned during vendor screening, but they should be identified as provisional until sufficient evidence supports a final assessment.

For each requirement, record a separate evidence status: vendor-reported, documented, demonstrated, or unverified. If a capability remains unverified, mark its final score as pending rather than assuming that vendor claims establish full functionality.

Step 3: Calculate Weighted Scores and Review Gaps

Calculate each category's contribution by dividing the vendor's score by the maximum available score, then multiplying the result by the assigned category weight.

Weighted Score = (Vendor Score ÷ 4) × Category Weight

For example, a vendor receiving 3 out of 4 in production planning, weighted at 20%, earns 15 percentage points toward its overall evaluation score.

The same calculation applies to each requirement category. The following illustrative comparison shows how two vendors might score across the seven manufacturing requirements.

Although Vendor B receives the higher overall score, that result should not determine the recommendation on its own. If Vendor B fails a mandatory production or financial-control requirement, it may be unsuitable regardless of its weighted total.

These scores are illustrative. Actual evaluations should be supported by documented evidence and reviewed against mandatory requirements, implementation risks, and unresolved functionality gaps.

A high overall score should not override failure to meet mandatory requirements. The selection team should review significant functionality gaps, customization assumptions, integration dependencies, and unresolved technical requirements before making a recommendation.

ERP Vendor Evaluation Checks Before Shortlisting

Weighted scores provide a useful comparison, but the selection team must also confirm that each vendor satisfies essential manufacturing requirements and that significant risks have been addressed.

Use the following six evaluation checks before advancing a vendor to detailed demonstrations.

How to Use the Checklist Before Shortlisting ERP Vendors

Once manufacturing requirements and evaluation priorities are approved, the selection team can use them to identify ERP vendors worth considering. This preliminary screening should establish whether each solution can support the manufacturer's essential workflows before committing resources to detailed demonstrations.

A practical qualification process involves four steps:

1. Identify vendors with relevant manufacturing capabilities. Research solutions that support your production model, industry requirements, and operational complexity. Consider experience with comparable manufacturing environments and the availability of appropriate implementation support.

2. Issue a structured requirements questionnaire. Ask vendors to indicate whether each critical capability is available through standard functionality, configuration, additional modules, third-party integrations, or customization. Request clarification for incomplete responses.

3. Assess technical and commercial feasibility. Review deployment options, integration requirements, implementation assumptions, and preliminary costs. Identify dependencies that could affect the project budget or implementation schedule.

4. Approve a qualified vendor shortlist. Compare the findings against mandatory requirements and documented evaluation criteria. Advance vendors that demonstrate sufficient functional fit and have manageable outstanding risks.

For example, an engineer-to-order manufacturer may eliminate a vendor whose system cannot adequately manage engineering revisions across active production orders. Identifying this limitation during preliminary qualification can prevent unnecessary demonstrations and further evaluation costs.

The resulting shortlist should include vendors that appear capable of meeting mandatory manufacturing requirements and have acceptable preliminary technical and commercial assumptions. At this stage, functional suitability remains provisional.

Detailed demonstrations should then test the manufacturer's highest-priority workflows, validate vendor-reported capabilities, and identify unresolved gaps before final vendor recommendations are made.

Read Next: ERP Software Selection Process: How to Choose the Right System

Who Should Help Define Manufacturing ERP Requirements?

Manufacturing ERP selection requires input from the departments responsible for production, inventory, quality, finance, and technology. Each stakeholder should help define requirements, assign priorities, and evaluate vendor capabilities within their area of expertise.

The weighted scorecard should reflect these responsibilities, with designated reviewers accountable for validating scores and documenting supporting evidence.

Each stakeholder should support their scores with documented evidence, such as vendor responses, process demonstrations, or technical assessments. For example, production planning may score scheduling functionality highly, while IT identifies integration limitations that require further investigation.

The ERP selection lead should consolidate departmental findings, reconcile scoring differences, and document unresolved risks. Before shortlisting, the team should confirm mandatory requirements and preliminary vendor qualifications. Following detailed demonstrations, stakeholders should validate final scores and formally acknowledge any remaining gaps before recommending a preferred solution.

Read Next: ERP Risk in Manufacturing: How to Avoid Costly Failures

Common Mistakes in Manufacturing ERP Requirements Evaluation

A structured scorecard does not eliminate evaluation risk. The following four warning signs can reveal weaknesses in vendor scoring, functionality validation, or technical due diligence.

1. Every Vendor Receives Similar Scores

When competing ERP systems receive nearly identical scores, the evaluation criteria may be too broad or fail to distinguish critical manufacturing capabilities. Review requirement weights and confirm that scoring reflects actual differences in production functionality.

2. Demonstrations Avoid Complex Production Scenarios

Standard vendor demonstrations may overlook scheduling conflicts, engineering changes, or material shortages. If these situations remain untested, the selection team cannot reliably assess how the system performs under real operating conditions.

3. Manufacturing Costs Cannot Be Reconciled

If finance cannot trace material consumption, labor, and production variances into inventory valuation and financial records, important costing requirements may be unresolved. Controllers should verify these transactions before confirming a vendor's financial suitability.

4. Critical Capabilities Depend on Unverified Customization

Vendor responses that rely on future development, additional modules, or third-party integrations require closer examination. Confirm the scope, estimated costs, technical responsibilities, and implementation implications before accepting these capabilities as supported.

When these warning signs appear, the ERP selection lead should document the outstanding issues, assign responsible reviewers, and obtain additional evidence before advancing the affected vendor.

Read More: Red Flags in ERP Proposals: A Proactive Guide to Successful System Implementations and Integration

Selecting Manufacturing ERP Software With Clear Requirements

A manufacturing ERP selection checklist is most valuable when its requirements translate into measurable vendor evaluations. For mid-market manufacturers, four priorities help connect functional fit, operational risk, and cross-functional decision-making:

1. Validate critical manufacturing workflows. Confirm that prospective systems can support production planning, BOM management, inventory transactions, and shop-floor operations.

2. Apply consistent evaluation criteria. Use weighted scoring to compare vendor capabilities while treating mandatory requirements as qualification conditions.

3. Resolve significant functionality gaps. Investigate customization, integration dependencies, and costing limitations before approving a shortlist.

4. Secure cross-functional agreement. Ensure operations, finance, quality, supply chain, and IT have reviewed the findings and documented outstanding concerns.

Before detailed vendor demonstrations, the selection team should finalize requirements, confirm evaluation weights, and establish approval responsibilities. After demonstrations, the team should review validated functionality, unresolved gaps, and technical dependencies before recommending a solution. These findings also inform implementation planning by identifying potential data, integration, and process changes.

RubinBrown provides vendor-independent ERP Advisory Services for Manufacturers and Distributors. Its advisors help manufacturing organizations assess business processes, define requirements, and evaluate ERP solutions against operational and financial priorities.

Frequently Asked Questions

How do you choose the right ERP system for a manufacturing business?

Start by documenting your production model, critical workflows, and operational requirements. Evaluate how each ERP system supports production planning, inventory, costing, quality management, and financial reporting. Use weighted selection criteria to compare vendors and require demonstrations of your actual manufacturing processes. The right ERP system should meet mandatory requirements with acceptable implementation costs and risks.

What should be included in a manufacturing ERP requirements template?

A manufacturing ERP requirements template should document specific business needs, requirement priorities, responsible stakeholders, and methods for validating functionality. Include production scheduling, BOM management, shop-floor reporting, supply chain processes, costing, quality controls, and integration requirements. Each requirement should be measurable so vendors can provide comparable responses during the ERP selection process.

How does ERP selection affect manufacturing implementation costs?

Decisions made during ERP selection influence the cost and complexity of implementation. Requirements involving customization, data migration, integrations, and employee training can increase the resources needed to deploy a new ERP system. Manufacturers should evaluate the total cost of ownership, including software licensing, implementation services, ongoing support, and internal labor, before approving an ERP investment.

Should manufacturers upgrade their legacy ERP system or select a new one?

Manufacturers should assess whether their current ERP system can support essential business requirements through configuration, upgrades, or process improvements. Review functional gaps, integration limitations, vendor support, and long-term costs. If the legacy system cannot reliably support critical manufacturing workflows, evaluating a replacement may be appropriate. The decision should account for operational disruption and implementation risk.

What should manufacturers evaluate when choosing an ERP implementation partner?

Manufacturers should assess an implementation partner's experience with comparable production environments, industry requirements, and ERP platforms. Review the proposed project team, implementation approach, data migration capabilities, integration responsibilities, and post-launch support. Request relevant client references and clarify which activities the manufacturer must handle internally. These findings help establish realistic expectations for the implementation process.