ERP guide by industry

Manufacturing ERP: Demo Scenarios Vendors Must Prove

A manufacturing ERP should prove it can absorb real shop-floor exceptions: material shortages, BOM changes, scrap, rush orders, quality holds, and inter-plant transfers. The demo should show the impact on planning, inventory, cost, quality, and customer promise dates, not just the ideal path.

Structure my ERP selection
Demonstration

The scenarios the ERP must prove

  • Material shortage. Replan an order, propose an approved substitute, and recalculate promise dates without losing visibility on other orders.
  • Engineering change. Change a BOM or routing on an active product while preserving revisions, costing, and traceability.
  • Quality and scrap. Hold a lot, create a non-conformance, trigger rework, and show the impact on cost and lead time.
  • Rush customer order. Insert a priority order, identify the bottleneck, replan capacity, and show which other commitments move.
  • Multi-site and subcontracting. Move material and work across plants, subcontractors, and warehouses without losing commitments, lead times, or cost visibility.
  • End-to-end traceability. Start from a component or lot and trace the affected production orders, quality checks, finished goods, and customer shipments.
Decision criteria

What matters most in the selection

  • Realistic planning. MRP, finite capacity, constraints, priorities, and promise dates should reflect the actual shop floor.
  • Governed technical data. BOMs, routings, versions, substitutions, and engineering changes should be controlled without parallel spreadsheets.
  • Shop-floor execution. Time, consumption, output, scrap, downtime, and rework should feed back fast enough to manage operations.
  • Quality and traceability. Lots, serials, inspections, holds, and product genealogy should connect to orders and costing.
  • Reliable product costing. Material, labour, overhead, variances, and inventory should produce usable cost visibility during the month, not only after close.
  • Integration architecture. MES, WMS, PLM, EDI, equipment, and specialist systems need a defined role before selection.
Operating risks

What the ERP must avoid making worse

  • Planning lives in Excel. The ERP becomes a system of record after the fact instead of a decision tool.
  • Late shop-floor data. Priorities change before the ERP knows what actually happened.
  • Poor revision control. Engineering changes create gaps between what is built, purchased, and costed.
  • Unreliable costing. Consumption, labour, and scrap variances surface too late to correct.
  • Customization starts too early. Teams code around unclear processes instead of testing the standard first.
  • Integrations are left until the end. MES, WMS, EDI, or PLM become budget and timeline surprises.
Integrations

The flows to validate before choosing

  • MES and shop-floor data collection: time, output, scrap, downtime, and order status.
  • WMS, barcode, and automation: movements, lots, serials, locations, and shipping.
  • PLM, CAD, and engineering: BOMs, revisions, ECO/ECN, and technical data.
  • QMS or LIMS: inspections, non-conformances, certificates, lab results, and lot release.
  • EDI, suppliers, and customers: orders, forecasts, ASN, invoices, and partner requirements.
  • Maintenance, IoT, and equipment: machine availability, counters, scales, sensors, and operational signals.
Selection questions

Questions to answer before the shortlist

  1. Does the planning engine account for real capacity, calendars, priorities, and material constraints?
  2. What happens when a BOM or routing changes after a production order is already in progress?
  3. Can you trace a lot or serial from supplier to customer, and back again, in minutes?
  4. How are scrap, rework, non-conformance, and quality holds reflected in product cost?
  5. How quickly does shop-floor activity become visible to planners and finance?
  6. Which scenarios require customization, an extension, or a third-party tool rather than standard capability?
  7. How does the ERP handle multiple plants, subcontractors, transfers, and local standards without duplicating master data?
  8. Which integrations are real time, which can be delayed, and who owns each interface?
PlanAxion perspective

Do not compare ERPs on their best demo. Compare them on the same 5 to 8 real scenarios, using the same data, volumes, exceptions, and decision rules.

For every scenario, require clear proof and classify the answer in one category only: standard, configuration, extension, third-party tool, or manual workaround. That is how you see cost, risk, and complexity before you sign.

Client-side decision

Compare ERP systems using real scenarios

PlanAxion structures criteria, demos and evidence so solutions and implementation partners can be compared on the same decision baseline.

Structure my ERP selection