Two large stainless steel tanks in a dark production room

Post-Merger Supply Chain Integration: Network, SKUs and Systems

Post-merger supply chain integration is the work of turning two supply chains into one. The combined company decides which plants, distribution centers and lanes stay, which SKUs and suppliers continue, and which planning system runs the business. Protect service first, then remove duplication, then redesign the network in one model that holds both companies.

What Is Post-Merger Supply Chain Integration?

Integration covers four layers: the physical network (plants, DCs, fleets and lanes), the assortment (SKUs, pack sizes and brands), the supply base (suppliers and contracts) and planning (systems, calendars, KPIs and the people who run them). Each layer depends on the one before it. A SKU cut changes supplier volumes, and both change how much capacity each plant needs.

The scope is rarely fixed on day one. AB InBev announced its bid for SABMiller in October 2015 and closed the deal in October 2016. US approval required SABMiller to give up its MillerCoors holdings, which went to Molson Coors (Wikipedia). The network AB InBev integrated was smaller than the one it bid for. Smaller deals have the same problem on a smaller scale: divestments required by regulators, carve-outs, and contracts with change-of-control clauses all move the boundary after the plan is drawn.

Where Do the Two Networks Overlap?

Start with a map of where the two companies do the same work twice. Places to look:

  • Facilities in the same service area. Two DCs 50 kilometers apart, each half full, are the first candidates for a decision.
  • Shared customers served by two fleets. A beer distributor that used to receive brands from two brewers, on separate trucks, can now receive them on one.
  • Lanes both companies run at partial loads. Combined volume can fill trucks that neither filled alone.
  • Suppliers both companies buy from, often at different prices and terms.
  • Capacity mismatches. One company’s plant may run near its limit while the other’s has spare shifts.

The overlap map depends on a shared master. Locations, products and customers have to be matched across the two companies, and where the same customer or product carries a different code in each, someone has to pair them. Budget time for this matching, because every later decision in the integration reads from it.

How to Rationalize SKUs and Suppliers After a Merger

SKU rationalization after a merger has three targets. Duplicates are the same product under two codes; merge them. Near-duplicates are the same product in a different pack or label; keep one if customers accept the switch. The tail is items whose volume no longer covers the cost of planning, producing and storing them.

Judge each SKU on its contribution after cost to serve, since revenue alone hides what small items cost to plan, produce and store. Then check substitution. If buyers of a cut item move to the surviving one, volume consolidates and lines run longer. If they move to a competitor, the cut loses sales. Regional products need care: beer, for example, sells on local brands, and a local brand with modest volume can still anchor a distributor relationship.

Supplier rationalization follows the SKU decisions, because those decisions set the volumes. Combined volume gives the buyer more negotiating power, but harmonize specifications before moving volume, and keep a second source where one supplier would carry too much risk. Check contract end dates and change-of-control clauses early. They set the earliest date a change can happen.

Consolidating Planning Systems Without Stopping the Business

The planning layer has three realistic paths. Keep both systems and report together; move one company onto the other’s system; or put both on one planning model that reads from each company’s ERP. The first is quick and leaves two plans. The second takes as long as the slower ERP migration. The third lets the combined business plan as one while the ERPs are still separate, so the planning change does not wait for the ERP project.

Whatever the path, harmonize three things early:

  • KPI definitions. Forecast accuracy, service level and inventory days are often calculated differently in each company, so the same number means different things.
  • Planning parameters. Safety stock policies, lead times and order cycles carry each company’s habits.
  • The planning calendar. One weekly cycle and one S&OP meeting, on one demand view, is what makes it one business.

Avoid cutting over systems during peak season. If the merged company sells most in summer, plan the switch for the quiet months and run both in parallel until the new plans match reality.

What Should Happen in the First 100 Days?

A workable sequence for the first 100 days:

  • Before close: agree with legal counsel what data the teams may share, and prepare the master-data matching and the network baseline within those limits.
  • Days 1 to 30: protect service. Set one escalation path, watch service and stock daily for the largest customers and SKUs, and hold network changes.
  • Days 31 to 60: finish the combined master data, start a joint S&OP meeting on one demand view, and take the quick wins, such as shared lanes and joint buying on contracts that expire soon.
  • Days 61 to 100: build the combined network model and run scenarios, make the first SKU and supplier decisions, and choose the planning system path with a migration plan.

The 100-day mark is a planning milestone. Network changes take longer, because leases, labor agreements and customer contracts set their own dates.

Using Network Design to Decide What Stays Open

Network design answers the biggest integration question: which facilities the combined company keeps. Put every plant and DC from both companies into one model as a candidate, with demand by customer zone, capacities, cost rates and service rules. Then compare scenarios: the combined network as it stands, closing or merging overlapping sites, a greenfield network, and versions with any divestments a regulator requires. Rank each scenario on Total Cost to Serve and service, and include the one-time costs of closing and moving. Our post on strategic network design and scenario planning covers how to set up those scenarios, and network design for Total Cost to Serve shows how cost and carbon are weighed in one model.

Schneider Electric is an example of the problem after many deals. It grew through acquisitions in Asia-Pacific, and the region’s supply chain cost structure was well above known benchmarks. Network design and supply chain re-engineering brought $16M in annual supply chain savings, with fewer DCs and an infrastructure ready for future acquisitions (Schneider Electric case study).

Run the model again after each major decision. A closed DC shifts demand to its neighbors, and a divestment can change which site is cheapest to keep.

How Solvoyo Supports Merged Supply Chains

Solvoyo is a supply chain decision automation platform. Its strategic network design builds a digital twin of the supply chain and ranks network configurations on cost, service and carbon footprint, which fits the question of which sites to keep after a merger. For the planning layer, Solvoyo connects to ERPs and ODBC-compatible systems through web service APIs, database transfers and native SAP RFC (integration and APIs), and for demand planning it reads what it needs from SAP ERP and writes plans back without a full data migration.

Plans are built on one data model with the capacities, lead times and pack sizes of both networks, so planners working with sites they inherited do not have to recheck every line. Over 95% of Solvoyo’s plans execute untouched. To see your combined network in one model, request a demo.

S&OP capacity planning view in Solvoyo

Frequently Asked Questions

What Is Post-Merger Supply Chain Integration?

Post-merger supply chain integration combines two companies’ supply chains into one: the network of plants, DCs and lanes, the SKU range, the supplier base and the planning systems and processes. Work in this order: protect service first, then remove duplication, then redesign the network in one model that holds both companies.

What Should a Supply Chain Team Do in the First 100 Days After a Merger?

Protect service with one escalation path and daily tracking of the largest customers and SKUs, match the two companies’ location, product and customer master data, start one S&OP meeting on a single demand view, take quick wins on shared lanes and expiring contracts, and build a combined network model to decide which facilities stay.

How Does Network Design Help After a Merger?

Network design puts every plant and DC from both companies into one model and compares scenarios such as keeping the combined network, merging overlapping sites or building a greenfield network. Each scenario is ranked on Total Cost to Serve, service and one-time closing costs, so the decision on which sites stay rests on numbers.


See It Run on Your Own Data

See how Solvoyo turns your supply chain plans into decisions that run on their own.

Solvoyo mascot