Dynamics 365 Manufacturing Implementation: What It Takes to Unify a Multi-Facility Operation
Dynamics 365 Manufacturing Implementation: What It Takes to Unify a Multi-Facility Operation
“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. The customer buying a mattress sees one brand name. The actual manufacturing is done by this client. That business model creates a specific set of traceability and inventory requirements that most ERP implementations either handle generically or skip entirely.
Lot and batch traceability was critical, not as a compliance checkbox, but as the operational backbone that connects inbound raw materials to outbound finished goods. When raw foam enters a facility, the lot number needs to follow that material through every production step: cutting, assembly, finishing, packaging, all the way to the finished goods label and the outbound shipment. Because the finished product ships under multiple brand labels with different quality specifications and customer requirements, traceability has to resolve at the brand and customer level, not just the lot level.
Without it, you get inventory counts that technically balance but carry no useful information. You can’t trace a quality issue back to source material. You can’t confirm which lot went into which customer’s product. You can’t support a recall or a dispute with a documented chain of custody. In a private label business, that’s not an operational inconvenience. It’s a contract liability.
We introduced full batch numbering with FEFO (First Expired, First Out) picking logic in Dynamics 365, ensuring that material rotation aligned with production scheduling and shelf-life requirements. That tied directly into the advanced warehousing configuration: location-level tracking across every facility, system guided put away and picking to eliminate informal floor decisions, real-time inventory movements, and cycle counting to replace the disruptive annual physical inventory with continuous, location-level reconciliation.
The practical outcome: leadership could drill into inventory across all facilities for the first time. Not through a spreadsheet someone compiled the night before. Not through a phone call to a warehouse manager at a specific site. Through the system, in real time, with numbers that matched what was physically on the floor.
For a CFO, that changes month-end close from a three-week reconciliation exercise to a reporting function. For a COO, that changes capacity planning from an educated guess to an informed decision. For a CEO presenting to a board or a PE sponsor, it means the inventory numbers are defensible.
Production Control in Dynamics 365: Enterprise-Level Visibility
With Dynamics 365 production control in place, leadership could finally see what materials were being consumed against each production order, where each job sat relative to its routing, and how throughput was trending across all sites in a single view. That’s not a dashboard feature. It’s a structural change in how production planning and scheduling work.
Before, production orders were managed at the site level with no enterprise visibility into work center capacity, material availability, or cross-facility scheduling. Production planning was based on local data. Capacity decisions were informal. Actual cost versus planned cost variance was rarely captured in time to act on it.
After the implementation, material consumption was tracked at the production order and operation level. Scrap reporting flowed into job costing automatically. Work center utilization became visible across all facilities, so scheduling decisions could factor in capacity across the enterprise rather than just the one site in front of you.
During go-live, one of the warehouse managers called Matt and said he could finally see what was happening in every location. That wasn’t a comment about a dashboard. It was a reaction from someone who had spent years making decisions without the information to make them well.
Transportation Management in Dynamics 365: The Last Workflow to Get Connected
This is the part of a manufacturing operation that gets the least attention during an ERP implementation and causes the most daily friction after go-live.
Everything upstream gets connected. Finance is unified. Inventory is visible. Production is trackable. And then the order hits shipping, and the team at the dock is still doing everything manually.
This client shipped to major national retailers from some facilities and direct to customers from others. Each retail customer had a routing guide with specific carrier requirements, barcode label specifications, pallet-level serial container codes, and Advanced Ship Notice (ASN) mandates that had to be transmitted within defined windows after shipment. Before the implementation, every one of those requirements was managed manually against a printed reference, entered separately for each shipment, and checked by whoever happened to be at the dock.
The financial exposure at the shipping level is often underestimated. A labeling error on a shipment to a major retailer triggers a vendor compliance chargeback. A late or malformed ASN creates a receiving dispute. A routing guide violation, wrong carrier, wrong service level, wrong collect vs. prepaid freight designation, generates a freight chargeback that often isn’t caught until it hits accounts payable weeks later. These aren’t edge cases. In a high-volume shipping environment serving national retailers, they’re daily exposure that erodes margin in a place where most leadership teams aren’t looking.
Using transportation management in Dynamics 365, we automated order tracking, Bill of Lading (BOL) generation, compliant label printing, shipment closing, and EDI integration for ASN transmission. Customer-specific routing guide requirements were configured against the customer record so the correct carrier, service level, and freight terms populated automatically at shipment. No re-entry. No manual lookups. No reference binder at the dock.
This saved hours of manual work every day and reduced shipping errors to the point where the team stopped treating each retailer shipment as a high-risk event and started treating it as a process.
ERP Go-Live in Manufacturing: What Happens After the Switch
Shipping was the biggest challenge during this project, not because the configuration was complex, but because delays were not an option. The Black Friday holiday season was, in itself, its own project within the project. You can’t tell a major national retailer that shipments will be delayed because you’re going live on a new system. The system has to perform at full production volume from day one.
We ran extensive user acceptance testing during live production. Not in a sandbox, not in a test environment, but with real orders, real carrier pickups, and real retailer compliance requirements. That’s what go-live readiness means in a manufacturing context: proving the system performs under the conditions it will actually face.
Training was the other major challenge. The core project team adapted quickly. Warehouse floor users were a different story. Some had never used mobile scanning devices before. These were people who had been doing their jobs effectively for years using paper pick tickets, verbal instructions, and institutional knowledge. Asking them to follow system-directed workflows on a handheld device instead of the process they’d relied on for a decade is a real change management ask.
Our team at Ascent Innovations provided dedicated post-go-live support through the transition window and beyond, spending time on the warehouse floor during night shifts, not directing from a project room but working alongside the team until the new workflows became the normal workflows. That phase lasts until the team is genuinely confident. For some users, that takes longer than the project plan accounts for.
That level of post-go-live engagement is the difference between a system that runs the operation and a system that the operation runs around.
What Actually Changed
Before the implementation: every facility on a different ERP. No unified chart of accounts. No consolidated financial reporting without manual intercompany eliminations. Inventory that couldn’t be trusted across sites. Production managed locally with no cross-facility visibility. Shipping managed manually against retailer routing guides. Month-end close taking weeks. Leadership making strategic decisions on numbers nobody fully believed.
After: one unified Dynamics 365 Finance and Operations environment. Inventory matching physical counts for the first time, supported by continuous cycle counting. Month-end close dropping from weeks to days. Production scheduling informed by enterprise-level planning and real work center capacity data. Shipping automated with EDI integration, compliant label generation, ASN transmission, and routing guide requirements built into the workflow. Actual versus planned cost variance captured at the production order level. Manual adjustments reduced significantly across every facility.
The client is still growing. Ascent Innovations is now supporting a custom bulk shipment solution that builds on the same Dynamics 365 foundation, because the architecture was designed to extend, not just to survive implementation.
This Isn't Unique. It's a Pattern.
This bedding manufacturer’s situation was specific. The operational pattern behind it is not.
Ascent Innovations sees this across mid-market manufacturing: private equity rollups consolidating multiple acquisitions onto one platform, multi-plant manufacturers that have grown organically and accumulated different systems at each site, and companies scaling through acquisition where every new entity inherits its own legacy ERP and its own version of the truth.
The core challenge is always the same. An organization that has outgrown its systems needs to standardize before it can scale, and that work is operational, not just technical. The question isn’t whether these problems exist in your operation. If you’ve grown through acquisitions or expanded across multiple facilities over the past decade, they almost certainly do. The question is whether the cost of continuing to manage around them has started to outweigh the cost of fixing them.
The Decision Point
If your organization is growing through acquisitions, this isn’t a future problem. It’s already happening. Every month that passes with fragmented systems is another month of manual reconciliation, another month of decisions made on data leadership doesn’t fully trust, another month of working capital tied up in buffers that exist only because the inventory numbers aren’t reliable.
Most companies don’t have a system problem. They have a standardization problem. And the longer standardization waits, the more expensive and disruptive it becomes.
Most of our conversations start with a short operational review. Not a product demo, not a pitch. A conversation about where the friction is, what it’s costing, and where the highest-impact starting points tend to be. If the situation described in this piece sounds like the one you’re managing right now, that conversation is worth having.
Key Takeaways
Ascent Innovations implemented Dynamics 365 Finance and Operations for a multi-facility contract bedding manufacturer, consolidating multiple legacy ERP systems and costing methodologies into one unified platform. The implementation covered finance with intercompany trade and financial consolidation, advanced warehousing with lot traceability, FEFO picking, and location-level inventory control, production control with enterprise-level planning and work center visibility, and transportation management with EDI integration, ASN automation, and retailer routing guide compliance. A phased rollout starting with a single-facility pilot established a repeatable model that reduced cutover risk and accelerated every subsequent facility rollout. Standardization of the chart of accounts, costing methodology, and master data across all facilities was the operational foundation of the project’s success.
Ascent Innovations Dynamics 365 Finance and Operations | Manufacturing | Public Sector 17 years of operational transformation for mid-market manufacturers ascent365.com
Ready to start transforming your business?
Talk to us about how Ascent Innovations can help you realize business value faster with end-to-end solutions and cloud services.
