Manufacturing ERP Selection Checklist

Introduction

Manufacturing ERP selection is a process and operating-model decision disguised as a software purchase. Products can all show purchasing, inventory and production orders. The differentiators emerge in real scenarios: engineer-to-order changes, formula version and yield, partial completion, subcontracting, quality hold, lot genealogy, capacity constraints, rework, by-products, landed cost and month-end reconciliation.

This checklist helps a cross-functional team define fit and implementation risk. Logic Unit must not imply it sells or implements a specific ERP unless approved; KSEW content must state the exact verified role.

Table of Contents

1. Define manufacturing model and outcomes
2. Core requirements
3. Planning and production
4. Inventory, quality and traceability
5. Finance and commercial operations
6. MES, CMMS and integration
7. Data, security and deployment
8. Implementation/vendor evaluation
9. Demo scorecard
10. FAQs

The Manufacturing Model

Document whether operations are discrete, process, mixed-mode, make-to-stock/order, engineer/configure-to-order, repetitive, batch, project or combinations. Identify sites, products, BOM/formula depth, routing, work centers, capacity constraints, subcontracting, quality/regulation, lot/serial, warehouses and markets.

Map value streams and exceptions. Do not buy from industry label alone; two factories in the same sector can operate differently.

Desired outcomes must be explicitly baselined, targeting common master data, planning visibility, traceability, inventory accuracy, and the retirement of unsupported legacy systems.

Core Enterprise Requirements

• Multi-entity/site/currency/tax/localization.
• Chart, dimensions/cost centers, consolidation.
• Customer/order/pricing/credit.
• Supplier/procurement/contract.
• Item/product/BOM/formula/routing/work center.
• Inventory/warehouse and valuation.
• Production planning/execution.
• Quality and traceability.
• Project/asset/maintenance relationships if in scope.
• Role, approval, audit and reporting.

Separate mandatory current scope from later modules. Avoid selecting a suite on features no one can implement.

Product and Engineering Data

Test:

• Item variants/configuration.
• Engineering vs manufacturing BOM.
• Multi-level BOM and alternatives/substitutes.
• Formula/recipe with co/by-products and yield where relevant.
• Routing/operation/work center and setup/run time.
• Revision/effective date and engineering change.
• Unit/pack conversions.
• Cost roll-up.
• Document/instruction links.

PLM/PDM and document-system ownership must be established, including clear rules for handling open orders when engineering revisions change.

Planning and Production

Demand and MRP

Use realistic forecast/sales/order/safety stock/lead time/lot size and supply constraints. Inspect planned-order explanation and exception messages.

Capacity and scheduling

Distinguish infinite/finite capacity, rough-cut and detailed sequencing. Determine whether ERP is sufficient or advanced planning/MES is needed.

Execution

Test release, material issue/backflush, labor/machine reporting, partial completion, scrap/rework, substitution, subcontracting, WIP and close. Include operator/user experience.

Cost

Validate standard/actual or selected cost method, material/labor/overhead, variances and financial posting with finance.

Inventory, Warehouse and Traceability

• Locations/bins/status.
• Lot/serial/batch and expiry/shelf life.
• Receiving/inspection/quarantine/release.
• Transfers, picking, staging and production supply.
• Cycle/physical count and variance.
• Reservations/allocations.
• Reorder and safety stock.
• Landed cost where required.
• Recall/genealogy exercise.

Run a trace scenario from supplier lot through production to customer shipment and reverse, including rework/substitution. Regulated requirements need specialist review.

Quality

• Specifications/test plans and effective versions.
• Incoming/in-process/final inspection.
• Sampling and instrument/LIMS links.
• Nonconformance, hold/release, deviation and CAPA link where in scope.
• Certificates/records.
• Rework/scrap disposition.
• Audit/retention/e-signature requirements.

Regulated compliance should never be inferred simply from a software module's name; it must be validated through configuration, process audits, and concrete evidence.

Finance and Commercial Operations

Test order-to-cash, procure-to-pay, inventory-to-finance, production/WIP/cost, fixed assets/projects where needed and month-end close. Finance should reconcile sample transactions through subledger/general ledger.

Include intercompany/inter-site, taxes/localization, foreign currency and revenue/cost rules relevant to the business.

MES, CMMS, WMS and Other Integrations

ERP need not own every execution process. Define:

• MES: detailed production/WIP/genealogy/operator execution.
• CMMS: maintenance assets/work/PM/history (e.g., Titan if fit).
• WMS: complex warehouse execution.
• PLM: engineering product data.
• QMS/LIMS: quality/lab.
• CRM/ecommerce/EDI.
• Banking/tax/e-invoicing.
• Data/BI.

For each object, assign system owner, key, direction, timing, error and reconciliation. Avoid double entry.

Data Migration

Inventory item/BOM/routing, supplier/customer, inventory, orders, production/WIP, finance balances, assets and history. Profile duplicates, obsolete records, unit/cost/tax issues and open transactions.

Decide history vs archive. Run trial loads and reconcile quantity/value and financial control totals. Data ownership is a business responsibility.

Security, Deployment and Non-Functional

Qualified reviewers assess cloud/on-prem, identity/MFA/RBAC, entity/site segregation, audit, encryption, backup/recovery, incident/vulnerability, data location/subprocessors, performance/availability, integration security, accessibility, retention/export and support access.

Test peak MRP, month-end, production posting and interface volumes. Confirm release/customization upgrade policy.

Implementation and Vendor/Partner

Evaluate:

• Manufacturing sub-model experience.
• Discovery/process design.
• Standard template vs customization discipline.
• Data/integration capability.
• Testing/cutover/parallel run.
• Change and training.
• Governance and benefits.
• Local/global support.
• Named team and references.
• Product roadmap and ecosystem.
• Commercial clarity.

Ask references about what was underestimated and what remained manual.

Scenario Demo and Scoring

Use buyer scripts:

1. Forecast/order creates planned supply.
2. BOM/routing revision affects the correct orders.
3. Constraint/material shortage changes plan.
4. Production reports partial, scrap/rework/substitution.
5. Quality hold controls movement.
6. Lot genealogy supports trace.
7. Finished receipt and cost/variance post.
8. Customer shipment/return completes financial flow.

Example weights: process fit 30, finance/control 15, usability 10, data/integration 15, security/non-functional 10, implementation/partner 10, TCO 10. Mandatory gaps override average.

TCO and Contract

Include licenses/modules/users/entities, environments, implementation, data, integrations, customizations, testing, training/change, infrastructure, support, internal team, upgrades and exit. Model growth. Clarify assumptions, fixed/estimate/usage, renewal and data portability.

Common Mistakes

• Choosing brand before mapping process.
• Letting generic demo avoid exceptions.
• Recreating every legacy customization.
• Ignoring operator adoption.
• Underestimating master data and change.
• Making ERP own MES/CMMS needs by default.
• Big-bang multi-site without template proof.
• Counting go-live rather than outcome.

FAQs

Which ERP is best for manufacturing?

The one that fits the specific production model, enterprise needs, users, integrations and implementation capacity. Validate through scenarios.

How long does selection take?

It depends on scope and governance. Allow enough time for discovery, data/system assessment, demos, due diligence and business case.

Should ERP include MES/CMMS?

Only if those modules meet critical execution workflows. Compare integrated specialist systems when needed.

How much customization is acceptable?

Use it for justified differentiated/mandatory gaps after process/configuration/integration alternatives. Govern upgrade/support cost.

What data should be cleaned first?

Items/BOM/routing/units, suppliers/customers, locations/inventory, open transactions and financial dimensions required for scope.

How should vendors be scored?

Weighted scenarios, mandatory gates, evidence, implementation risk and normalized lifecycle cost.