https://youtu.be/qJAEcyV9LUQ?si=eKtjzrM3p2mjQIBL “Let’s get into what happens when acquisitions outpace operational integration.” A manufacturing business acquires new facilities. Each one comes with its own ERP, its own workflows, its own costing methods, its own chart of accounts. Leadership focuses on integrating the revenue and the customer relationships, and the systems get pushed to “later.” Later turns into years. And somewhere along the way, the CEO, CFO, and COO realize they’re running a company where nobody can agree on the same set of numbers. If you’re leading a mid-market manufacturer with multiple facilities and that situation sounds familiar, this piece is written for you. Not to sell you a platform, but to walk through what unifying an operation like yours actually looks like, what the hard decisions are, and why most ERP projects fail to deliver the value the organization expected. The Hidden Cost of Growing Through AcquisitionsAdd Your Heading Text Here The cost of running fragmented systems doesn’t always appear on a P&L. It shows up in every decision that takes longer than it should, every report that requires manual reconciliation before leadership trusts it, and every capacity commitment made without reliable data behind it. Delayed reporting isn’t just inefficient. It introduces compliance risk with lenders and credibility risk with stakeholders. When your CFO can’t close the books for three weeks because month-end requires manual consolidation and intercompany eliminations across disconnected systems, the business is operating on backward-looking financials. Decisions about pricing, capital allocation, and headcount are being made with numbers that are already stale by the time anyone sees them. When inventory data isn’t trusted, working capital decisions are compromised. Days inventory outstanding climbs because planning can’t see what’s actually on the floor across facilities. You carry excess safety stock at one site while another expedites the same item. You tie up cash in buffers that exist only because the system can’t give you a number you believe. Manual consolidation across platforms increases audit exposure and the likelihood of financial misstatement, not from negligence, but from the structural impossibility of maintaining accuracy when the same data is being entered, reconciled, and reported from three different systems with three different costing methodologies and three different period-close processes. This was the situation at the contract bedding manufacturer Ascent Innovations worked with. Multiple facilities across the United States, each on a different ERP, each operating independently. One of the project managers described it accurately: it felt like each location was running its own company. Most Companies Don’t Have a System Problem. They Have a Standardization Problem. Here’s where most conversations about ERP go wrong. The assumption is that the problem is the technology and the solution is better technology. Pick the right platform, implement it, go live, problem solved. Most ERP projects fail to deliver value because they digitize existing complexity instead of eliminating it. If every facility is running a different costing method, standard cost at one site, weighted average at another, FIFO at a third, and you implement a new system on top of that without aligning the methodology first, you end up with the same fragmentation on a more expensive platform. The data looks cleaner. But the underlying model is still incoherent, and leadership still can’t trust the consolidated output. The technology matters. Dynamics 365 Finance and Operations is a strong platform for manufacturing. It handles finance, procurement, production control, advanced warehousing, and transportation management in a single integrated environment. But the platform is not the hard part. The hard part is standardization. Deciding on one costing method across every legal entity. One chart of accounts. One set of financial reporting dimensions. One inventory structure. One set of business processes that every facility follows, regardless of how they did things before. That’s an organizational challenge, not a technical one. It requires leadership to make decisions that some facility managers won’t like, to retire processes that people have been using for years, and to hold the line when someone says “but our site is different.” Some sites are genuinely different: different product lines, different customer requirements, different shipping environments. The system has to accommodate that. But the underlying operational framework has to be consistent, or the implementation just relocates the chaos into a shinier system. Why a Phased ERP Rollout Starts with a Pilot A multi-facility ERP consolidation requires a phased rollout. The pilot facility isn’t just a test site. It’s where the implementation model gets built. We started with a single facility, not because the scope was unclear, but because a pilot isn’t just a test of the software. It’s a test of the standardized business processes underneath it. Before you can roll out a unified Dynamics 365 Finance and Operations platform across multiple sites, you need to clean and validate your master data, align the costing methodology, and confirm that the configured workflows actually match how work gets done on the floor. You can’t do that reliably for five facilities at once. You do it once, correctly, and then replicate. The pilot gave us a controlled environment to test integrations, run data migration validation, confirm cutover sequencing, and fine-tune training for the team members who would carry the rollout to every remaining site. By the time we moved to the second facility, we had a proven playbook. Conversations with site leadership were different because we could point to a live system that was already working. For mid-market manufacturers considering a Dynamics 365 implementation across multiple locations, the pilot phase is where the project either builds momentum or starts accumulating risk. Get it right, and every subsequent rollout is a replication exercise. Skip it, and every facility becomes its own implementation. Batch Tracking and Advanced Warehousing in Dynamics 365 We implemented the core Dynamics 365 Finance and Operations modules: finance, accounts payable, accounts receivable, procurement, sales and marketing. Those are the foundation. But for a contract manufacturer operating at this scale, the foundation alone doesn’t solve the problem. A contract manufacturer produces goods for other brands under private labels. … Read more
