When it comes to ERP, the cost of getting it wrong is higher than the cost of delay.
In an industrial M&A deal, integrating the ERP system is often treated like a tech project. It’s not. For distributors of ceramics, refractories, glass, or any industrial material, the ERP system is the nervous system—it governs inventory accuracy, order flow, invoicing, and even customer experience.
Yet too many post-acquisition integrations force a rushed, top-down ERP migration without understanding how orders are placed, SKUs are managed, or credits are applied in real life.
Here’s how to approach ERP integration after a merger or acquisition—without breaking what you just bought.
Start With a Ground-Level Process Map
Before touching a line of code, map out how the acquired company actually runs:
How does a customer place a custom tile or refractory order?
Who triggers replenishment for standard SKUs?
How are adjustments handled for damaged ceramic pallets or delayed LTL freight?
These real-world flows often don’t match the existing ERP logic. If you try to migrate without respecting the nuances of the field operation, your integration will stall—or worse, crash fulfillment.
Prioritize What Needs to Be Unified—and What Can Wait
Not all ERP features need to be centralized Day One. Finance and reporting? Yes. Customer master data and price books? Probably. But forcing immediate warehouse or fulfillment module integration may disrupt operations unnecessarily.
Choose a phased approach:
Financial unification for clean audit trails
Shared product catalog and order entry tools
Gradual rollout of inventory, pick/pack, and logistics modules
This minimizes risk while maintaining service levels to customers and vendors.
Don’t Assume SKU Logic Is Transferable
In ceramics and refractories, SKU logic is often homegrown and reflects years of operational quirks. One system may use internal codes for 2300°F castables, while another appends modifiers for grain size or packaging format.
Before merging ERP catalogs, run a full SKU mapping exercise. Standardize descriptions, packaging units, and unit of measure codes. Be aware that a “box” of ceramic tile in one system may be tracked as a “pallet” in another—and customer-facing documents will need to reflect those realities.
Prepare for Data Hygiene Battles
Acquisitions often come with messy data: duplicate vendors, outdated customer records, mismatched payment terms. Don’t dump legacy data into your master ERP. Invest in cleansing and enrichment before importing. Use the integration period to correct pricing tiers, discount logic, and freight charge structures.
Your long-term reporting accuracy—and margin visibility—depends on it.
Communicate Changes Internally and Externally
Don’t forget the human side of ERP integration. Field reps need to know how to price and invoice under the new system. Customers need clear instructions on new PO numbers or billing formats. And your warehouse team needs training on barcode scanning, pick tickets, and returns.
A successful ERP integration doesn’t just happen in IT. It requires change management, communication, and patience.
