43. ERP for manufacturing-heavy businesses • EL BANTLI

The deal model had a clear manufacturing story: better procurement discipline, lower inventory, higher plant throughput, fewer quality escapes, and tighter standard cost control.

The target ran five plants on one ERP instance, two warehouse tools, a quality system that did not always post holds back to ERP, and production schedules maintained partly in spreadsheets. Management said the system supported the business. Plant managers were more precise: the system supported the current way of working because local teams knew where to route around it.

That distinction matters.

A manufacturing ERP does not only close the books. It decides whether a plant can plan material, release work orders, receive goods, price finished product, hold suspect inventory, trace lots, ship on time, and explain margin by SKU. When a buyer changes the operating model, those workflows become deal constraints.

The primary decision is:

Can ERP and adjacent manufacturing systems support plant-level operations, costing, inventory, quality, and supply chain value levers on the deal clock, or does the buyer need to fund stabilization, wrappers, replacement, or a slower value plan?

If this question is not answered before close, the investment case can carry hidden assumptions about working capital, EBITDA, service levels, and plant uptime.

Why manufacturing ERP changes deal economics

Manufacturing ERP risk shows up in the numbers before it shows up as an IT issue.

Working capital: inventory accuracy, safety stock settings, MRP parameters, cycle counts, and warehouse posting discipline determine whether cash can be released without starving production.
EBITDA: standard cost accuracy, scrap capture, labor routing, overhead absorption, and variance reporting determine whether margin improvement is real or only accounting noise.
Revenue and service: order promising, allocation, production scheduling, and shipping discipline determine whether commercial growth can be served by the plant network.
Synergy timing: procurement savings, plant consolidation, SKU rationalization, and supplier changes depend on clean item, vendor, bill of material, and recipe data.
One-time cash: MES integration, quality workflow fixes, label and traceability remediation, warehouse cleanup, and ERP configuration work can become mandatory before the value plan moves.

The wrong diligence answer is “ERP is adequate.” The useful answer is which value levers ERP can support now, which require plant-by-plant remediation, and which should be delayed until the data and controls can carry them.

The common mistake: treating manufacturing as another ERP module

Manufacturing diligence often spends too much time on the ERP brand and too little time on how the plant runs.

SAP, Oracle, Microsoft Dynamics, Infor, Epicor, QAD, Plex, NetSuite, and other platforms can all support manufacturing operations in the right setup. They can also become blockers when production control, inventory, quality, and costing are split across local tools and tribal knowledge.

The real issue is not whether the ERP has a production module. It is whether the implemented process matches the operating model the buyer wants.

A plant that runs make-to-stock with stable demand needs different controls from a plant that runs engineer-to-order. A food or medical device business needs tighter lot genealogy and quality release than a discrete components business. A business with high raw material volatility needs cost updates and margin analytics that a low-variation business may not need. A multi-plant network needs common item and routing discipline before it can shift volume, consolidate suppliers, or benchmark conversion cost.

If diligence ignores those differences, it can approve the system while missing the value constraint.

A manufacturing ERP diligence lens

The fastest way to test the system is to follow the flows that hit cash, margin, and service. Five flows matter most.

1) Plan-to-produce

Plan-to-produce is where sales forecasts, demand plans, material requirements, capacity, work orders, and production confirmations meet.

Ask whether ERP is the planning system of record or only the posting system after planning happens elsewhere. If production schedules are built in spreadsheets, Access databases, or plant-specific tools, the buyer needs to know why. Sometimes the workaround exists because ERP planning parameters are wrong. Sometimes it exists because the plant has real constraints ERP does not model: changeover windows, allergen sequencing, tooling, labor availability, curing time, or bottleneck equipment.

What to test:

forecast handoff into demand planning or MRP
MRP run frequency, exception messages, and planner overrides
bill of material and routing ownership by plant
capacity planning at bottleneck resources
work order release, confirmation, scrap, and rework capture
production schedule adherence and root-cause coding

If MRP is not trusted, inventory reduction and procurement savings are likely slower than the model assumes.

2) Inventory and warehouse control

Inventory is where manufacturing ERP failures become cash issues.

The diligence question is not only whether inventory exists in ERP. It is whether the system can show quantity, location, status, ownership, shelf life, and usability accurately enough to change safety stock or consolidate warehouses without service pain.

What to test:

inventory accuracy by plant, warehouse, and item class
cycle count cadence, adjustment value, and root causes
blocked, expired, obsolete, consigned, and in-transit inventory treatment
WMS integration with receipts, moves, picks, shipments, and production consumption
backflush logic and variance between theoretical and actual consumption
manual inventory journals and approval controls

If inventory accuracy is below 95% for A items or cycle count adjustments are not analyzed by root cause, do not count early working capital release without a funded inventory control sprint.

3) Costing and margin

Manufacturing cost is often where the ERP looks orderly but the deal case is weak.

Standard cost may be updated once a year, while commodity prices move monthly. Routings may not reflect current labor or machine time. Overhead absorption may sit at a plant average that hides SKU-level loss. Scrap may be captured as inventory adjustment instead of production variance. Freight, yield loss, and rework may sit outside product margin.

What to test:

standard cost update cadence and approval workflow
bill of material and routing accuracy for top revenue and top margin SKUs
purchase price, usage, labor, overhead, scrap, and yield variance reporting
actual-to-standard reconciliation by plant and product family
margin reporting by customer, product, plant, and channel
treatment of freight, duty, subcontracting, rework, warranty, and quality cost

If management cannot explain margin by SKU using system data, the buyer should be careful with pricing, SKU rationalization, and plant footprint assumptions.

4) Quality, traceability, and compliance

Quality workflows are frequently adjacent to ERP rather than inside it. That can be fine if the handoffs are controlled. It is a problem when quality holds, batch release, inspection results, complaints, nonconformance, CAPA, and recalls do not feed inventory status and shipping decisions.

What to test:

incoming inspection, in-process inspection, and final release workflows
quality holds and blocked stock posting back to ERP or WMS
lot, batch, serial, and genealogy tracking
certificate of analysis, label, and customer-specific quality requirements
nonconformance, CAPA, complaint, and recall process ownership
audit findings tied to system controls or manual workarounds

If a plant can ship inventory before quality release is reflected in ERP, the issue is not only compliance. It can become customer churn, warranty cost, inventory write-off, or a delayed plant consolidation.

5) Supply chain and supplier changes

Procurement synergy in manufacturing depends on more than negotiating better prices.

ERP must support supplier changes through qualified vendor lists, item sourcing rules, lead times, minimum order quantities, approved alternates, purchase price conditions, inbound logistics, and quality requirements. If that data is incomplete, the buyer may sign savings into the model before the plant can safely buy differently.

What to test:

supplier master quality and duplicate rates
item-supplier links, lead times, minimum order quantities, and price breaks
approved supplier and qualified material status
purchase requisition and purchase order approval controls
open purchase order cleanup and goods receipt discipline
supplier quality metrics and corrective action ownership

If more than 20% of direct spend lacks clean item-supplier mapping, procurement savings should be sequenced after master data cleanup and plant validation.

Evidence asks that cut through plant narratives

The best diligence artifacts are the ones plant teams already use to run the business.

ERP and manufacturing systems map

Ask for ERP instances, MES, WMS, QMS, planning tools, EDI, label systems, lab systems, maintenance tools, shop-floor data collection, and reporting tools by plant.

Why it matters:

The architecture shows whether ERP owns the process or only receives postings. It also shows which plants are common enough to standardize and which need local treatment.

Plant-by-plant workflow walkthroughs

Ask each plant to walk one order from forecast to production schedule, material issue, production confirmation, quality release, warehouse pick, shipment, invoice, and cost variance.

Why it matters:

Manufacturing workarounds are often local. A corporate ERP view can miss the planner spreadsheet, the local barcode tool, the manual quality hold, or the shipping label process that keeps one plant running.

Master data extracts

Ask for item master, bill of material, routing, work center, vendor, customer, pricing, unit of measure, lot control, shelf-life, and planning parameter extracts.

Why it matters:

Most manufacturing ERP value leakage starts as master data debt. If the buyer cannot trust item, routing, supplier, and cost data, it cannot safely move volume, reduce inventory, or standardize sourcing.

Inventory and adjustment history

Ask for cycle count results, inventory adjustments, blocked stock, aged inventory, obsolete stock, negative inventory incidents, and in-transit balances for the last 12 months.

Why it matters:

The inventory balance sheet can look correct while plant-level accuracy is weak. Adjustments show where the system is not matching physical flow.

Cost and variance packs

Ask for standard cost history, variance reports, margin bridges, scrap reports, rework cost, purchase price variance, and overhead absorption analysis.

Why it matters:

The value plan often assumes margin improvement before the company has cost facts good enough to steer it.

Quality and traceability evidence

Ask for quality hold reports, lot genealogy samples, recall mock-test results, nonconformance logs, CAPA aging, customer complaint trends, and audit findings.

Why it matters:

Quality system gaps are easy to underprice because they do not always hit EBITDA immediately. Under deal pressure, they can stop shipments or block site moves.

Decision triggers that should change the plan

Manufacturing ERP diligence should force explicit triggers. These are the ones that most often change timing, one-time cash, or the value case.

Trigger 1: MRP is bypassed for material planning at more than one major plant

If planners routinely override MRP or run material plans outside ERP, early inventory reduction is exposed.

What it changes:

fund planning parameter cleanup before reducing safety stock
sequence supplier consolidation after plant planner validation
delay procurement synergies tied to material availability until MRP trust improves

Trigger 2: Inventory accuracy for A items is below 95%

If high-value or high-velocity items are not accurate by location and status, warehouse consolidation, inventory release, and production scheduling become risky.

What it changes:

run cycle-count remediation before warehouse or plant moves
avoid aggressive working capital targets in the first 100 days
add WMS or scanning fixes where manual moves drive errors

Trigger 3: Standard costs are stale or not tied to current routings

If standard costs are older than 12 months in a volatile input-cost business, or routings do not reflect actual labor and machine time, margin analytics are weak.

What it changes:

treat SKU profitability work as a data project before a pricing decision
fund cost roll cleanup and routing validation
avoid plant footprint decisions based only on reported gross margin

Trigger 4: Quality holds do not control ERP or WMS availability

If suspect, quarantined, or unreleased inventory can be picked or shipped because quality status lives outside ERP, the buyer owns both service and compliance risk.

What it changes:

require a Day-1 quality hold control
delay site consolidation or SKU transfer until traceability is tested
fund QMS-ERP or QMS-WMS integration where manual controls are weak

Trigger 5: Item, bill of material, and routing ownership is unclear

If plants can create or change production master data without shared governance, benchmark and synergy work will stall.

What it changes:

appoint master data owners before any plant network redesign
build change approval controls for bills of material and routings
set plant-level data cleanup waves, starting with top revenue and high-margin SKUs

Trigger 6: Direct material spend cannot be mapped cleanly to item and supplier

If procurement cannot tie spend to item, supplier, plant, and approved source, negotiated savings may not convert into purchase orders.

What it changes:

split procurement synergy into negotiated rate, system readiness, and plant adoption
fund vendor and item master cleanup
validate alternate suppliers through quality and engineering before booking full savings

Trigger 7: Plant systems depend on local support with no backup

If one plant engineer, contractor, or superuser owns MES, label printing, PLC interface files, or quality extracts, the value plan depends on personal continuity.

What it changes:

add retention and documentation to closing actions
require support coverage before cutovers or production schedule changes
avoid parallel changes that depend on the same scarce plant resource

What goes wrong after close

Manufacturing ERP issues rarely fail as one big program. They appear as a series of operational compromises.

The buyer lowers inventory targets, but planners add local buffers because MRP is not trusted. Procurement negotiates new suppliers, but approved-source data and quality qualification lag. The team announces SKU cleanup, but item masters use inconsistent units of measure across plants. Finance asks for margin by product family, but standard cost hides rework and yield loss. A warehouse change is scheduled, but inventory status and lot traceability are not ready. The first plant move slips, and the value plan loses a quarter.

The mechanism is simple: the value lever depends on plant behavior, plant behavior depends on system trust, and system trust depends on data, controls, and support capacity.

When those pieces are weak, the buyer has two choices. It can slow the value plan intentionally, or it can let the plant slow it informally through workarounds.

What best teams do before close

Strong teams do not try to solve manufacturing ERP during diligence. They decide what the system can carry and what must be funded before operational value moves.

1) They split value levers by system readiness

They do not put all manufacturing value into one synergy bucket. They separate:

procurement price savings that can be captured through contract changes
procurement savings that require item, supplier, and quality data cleanup
inventory reduction that depends on MRP trust and warehouse accuracy
margin improvement that depends on cost and variance data
plant network changes that depend on traceability, scheduling, and integration readiness

This avoids one common trap: counting a value lever as early EBITDA when it is actually a systems and operations program.

2) They build a plant heat map

For each plant, they score readiness across planning, inventory, costing, quality, supply chain, interfaces, and support capacity.

The heat map is not a maturity assessment. It is a sequencing tool. A plant with clean inventory and weak costing can start working capital actions but should not drive pricing decisions. A plant with good costing and weak traceability may support margin work but not site consolidation. A plant with high local system dependency should not be first in a transformation wave.

3) They protect Day-1 operations before changing workflows

Manufacturing buyers are often tempted to move quickly on purchasing, warehouses, and reporting. The better first move is control of the operating baseline:

confirm who can release orders, change production master data, override inventory, and approve quality disposition
freeze or govern master data changes during the first close and first production cycle
monitor failed interfaces, late postings, and manual inventory journals daily
retain plant superusers and local system owners through the first wave of change

This does not slow value capture. It prevents avoidable operational drag from consuming the first 100 days.

4) They fund the minimum viable fixes

Manufacturing ERP programs can become too large. Best teams isolate the fixes required to unlock the deal case.

Examples:

clean top 500 items by revenue and top 200 items by direct material spend, not the full item master
validate bills of material and routings for SKUs that drive 80% of gross margin
implement quality hold integration for regulated or customer-critical products first
add interface monitoring for order, shipment, inventory, and invoice postings before broader architecture work
stabilize cycle counting in the highest-value warehouses before launching a full WMS program

The point is not perfect ERP. It is enough trust in the system to move the value lever without breaking the plant.

A practical decision tree

Use the first two weeks of diligence to force a manufacturing ERP posture.

If ERP is trusted for planning, inventory, costing, quality, and supplier execution across the plants that drive most EBITDA, the buyer can treat ERP as an enabler. The plan should still include controls, but value can move early.

If ERP is trusted in finance but weak in plant execution, do not count plant-level value in the first 100 days without a remediation wave. Use wrappers, daily controls, and master data cleanup while keeping the broader ERP strategy open.

If ERP is fragmented across plants and local tools own production, quality, or warehouse decisions, treat the value plan as a transformation case. Price the one-time cash, slow the value timing, and avoid promising fast plant consolidation.

If the business is in a carve-out and manufacturing ERP is shared with the seller, the buyer should negotiate TSA duration and exit waves around plant continuity, not only finance cutover. A manufacturing ERP exit is not complete until production, inventory, quality, labels, EDI, shipping, and costing can run without seller dependency.

What to do Monday morning

The deal lead, operations lead, CIO, and CFO should align on one manufacturing ERP question: which value levers can the system support in the first two quarters, and which need funded readiness work?

Start with five actions:

Pick the plants that drive 80% of EBITDA, revenue, or inventory value and run workflow walkthroughs for plan-to-produce, inventory, quality, and shipment.
Ask for master data extracts for items, bills of material, routings, suppliers, costs, lot control, and planning parameters.
Build a plant heat map across MRP trust, inventory accuracy, cost quality, quality release control, supplier data, interface stability, and support capacity.
Split manufacturing value levers into “ready now,” “ready after 30-60 day cleanup,” and “requires funded transformation.”
Add one-time cash, timing, and owner names to every ERP or manufacturing system action needed before inventory, costing, quality, or supply chain value is counted.

The decision is not whether manufacturing ERP is good. The decision is whether it can carry the specific plant-level changes the investment case depends on, at the speed the deal requires. If it cannot, the buyer should change the sequence, fund the readiness work, and protect plant continuity before pushing for value.