Acquisitions move fast. Network rationalization rarely does, and that gap is where costs quietly pile up.
When a deal closes, the focus naturally shifts to integration: systems, people, branding, culture. The supply chain gets addressed operationally, keeping inventory moving, maintaining service levels, avoiding disruption. But the harder strategic question often gets deferred: do we actually need two networks, and if not, what should one network look like?
That question doesn’t have an obvious answer. And the longer it goes unasked, the more expensive the delay becomes.
What You’ve Actually Inherited
The first thing to understand after an acquisition is that you didn’t just acquire a company. You acquired its distribution footprint, along with all the decisions that created it.
The acquired network was built for a different business, serving different customers, often with different service expectations and order profiles. It may have been optimized for regional coverage, or for product characteristics that don’t match your existing SKU mix. Its facility locations, lease terms, and labor arrangements reflect choices made under a different ownership structure, at a different point in time.
Your existing network was built for your business, under your constraints. Neither network was built with the other one in mind.
That misalignment is the starting point, not the problem. The problem is assuming the two networks can simply coexist indefinitely without a deliberate plan. They usually can’t, at least not without paying more than you need to, serving customers less efficiently than you could, or both.
Why This Is Harder Than It Looks
Post-acquisition network rationalization gets complicated quickly for a few reasons.
The data is messy and asymmetric. Your organization has years of clean order history, freight data, and cost accounting. The acquired business may have none of that in usable form. Understanding what the combined network actually costs to operate, and what it should cost, requires assembling data from two different systems, often with different definitions, different lanes, and different approaches to cost allocation.
Lease timelines create real constraints. Network design in theory and network design with three facilities coming up for renewal in the next 18 months are very different exercises. The leases you’ve inherited may force decisions on a timeline that doesn’t match your planning cycle. Some facilities will look suboptimal in a model but be operationally unavoidable for years. Understanding those constraints early shapes what’s actually executable.
Customer commitments don’t pause for integration. Both customer bases expect the same service levels they had before the deal closed. Any network consolidation has to be sequenced in a way that doesn’t disrupt fulfillment, which means phasing decisions carefully and building transition plans before you move anything.
The politics are real. Network rationalization after an acquisition often means deciding that a facility associated with one side of the deal is redundant. Those conversations involve people, communities, and sometimes contractual obligations. A rigorous analytical foundation doesn’t eliminate the difficulty, but it makes the path forward defensible and easier to communicate.
The Right Questions to Answer First
Before jumping to conclusions about what the combined network should look like, it’s worth being disciplined about what you’re actually trying to solve.
A few questions worth working through early:
What does the combined customer base actually look like? Where are your customers, both sets of them, and what are their service expectations? Some acquisitions bring geographic expansion. Others bring customer segments with very different order patterns. The right network for the combined business may look very different from what either standalone network looked like.
What does combined demand look like by location? Order volume, order frequency, and unit weights all affect where DCs should sit. If the acquired business is heavily concentrated in a region you barely served, that changes the math on facility location materially.
Where does the overlap actually exist? It’s tempting to assume that two networks mean obvious redundancy, but the picture is often more nuanced. Two DCs 40 miles apart may sound wasteful, unless one holds product the other doesn’t, or one is contractually obligated, or the geographic coverage they provide together is actually intentional.
What’s the realistic planning horizon? Lease expirations, capital cycles, and service commitments all affect what changes are possible when. A network design that’s theoretically optimal but requires actions you can’t take for four years isn’t a plan. It’s a diagram. The analysis needs to account for what’s actually executable.
What a Rationalization Study Should Produce
A network rationalization after an acquisition isn’t just a facility footprint exercise. Done properly, it produces:
A baseline model that accurately reflects the cost and service performance of the combined network as it exists today, before any changes. This is harder than it sounds when you’re working with two sets of data, but it’s essential. You can’t evaluate alternatives honestly without knowing what you’re starting from.
A set of strategic scenarios that test different configurations: full consolidation, partial consolidation, network expansion, footprint shift. Each scenario should be evaluated on total cost, service coverage, risk exposure, and operational feasibility, not just transportation savings.
A sequenced implementation plan that accounts for lease timelines, integration dependencies, and customer commitments. The best network design in the world is useless if the path to get there disrupts service for six months or violates a lease you can’t break.
A sensitivity analysis that shows how the recommended scenario holds up under different demand assumptions, cost conditions, or growth projections. The combined business will continue to evolve. The network design needs to be durable enough to stay relevant as it does.
Timing Matters More Than Most Companies Realize
One of the most common mistakes in post-acquisition integration is treating network rationalization as a second-phase problem, something to address once the operational dust has settled. In reality, waiting too long creates its own costs.
Redundant facilities continue to carry full operating costs. Suboptimal freight lanes continue to run. Lease renewal decisions get made without the benefit of a clear network strategy, locking in configurations that a study might have changed. The longer rationalization is deferred, the more the status quo calcifies.
The right time to start the analysis isn’t after integration is complete. It’s during integration, early enough to inform the real estate decisions that can’t wait, and with enough rigor to make the results actionable when they’re needed.
How OPSdesign Can Help
OPSdesign works with companies navigating the network complexity that comes with acquisitions, building the combined baseline, running the scenarios, and developing a rationalization plan that’s grounded in operational reality and executable on a realistic timeline.
If you’ve recently closed a deal and the network question is still open, or if you’re in the planning stages and want to understand the supply chain implications before the deal closes, we can help you get ahead of it.
