Horizontal integration: more of the same stage under one management

What combining similar plants really merges

On paper the two operations do the same thing. In practice one runs a different heat treatment, buys a different grade, holds a certification the other lacks, and has customer approvals tied to a named site and a named process. The commitment made at completion is to keep both supplying while the differences are worked through, because customers do not pause for a reorganisation. Cataloguing what is genuinely common — specifications, routes, tooling, approvals — before promising any synergy is the least glamorous and most useful early task. The differences surfacing late are almost always the ones nobody thought worth writing down.

Rationalising a combined range

Overlapping ranges invite immediate pruning, and pruning is riskier than it looks: a low-volume item may be the reason a large account stays. Load allocation between sites has to consider what each is qualified and approved to make, not merely what each could physically produce. Stock consolidates slowly, since pooling finished goods requires customers to accept product from either source, which for approved or regulated items means notification and sometimes re-qualification. Meanwhile both sites hold their own cover and the combined balance sheet looks worse before it improves. Pruning decided on unit margin alone tends to remove exactly the items that carried the relationship.

Buying power arrives before the systems do

Combined spend is the fastest available benefit and the easiest to overstate. Suppliers will consolidate prices willingly, but only where the two sites genuinely buy the same thing to the same specification — and specifications usually differ in small, deliberate ways somebody once had a reason for. Harmonising them means engineering work and re-validation, which is why the negotiated saving lands later than the announcement. Supplier rationalisation carries its own exposure: cutting the acquired company's vendors can eliminate precisely the alternative source the network needed. Sequencing helps: consolidate first where specifications already match, and treat harmonisation of the remainder as an engineering programme with its own timeline and budget.

Two quality systems, one certificate

Merging management systems is not a documentation exercise. Procedures reflect how each plant actually works, and imposing one site's manual on the other produces compliance on paper and improvisation in practice. Certification scope has to be extended formally, customer approvals transferred or renewed, and any move of a validated process treated as a change requiring notification and evidence. The characteristic failure is announcing a single system before either site has adopted it, then discovering mid-audit that the shop floor follows documents nobody updated. Running both systems formally until one is genuinely implemented is slower, more expensive and considerably safer than an announcement followed by improvisation on the floor.

Where the synergy case stalls

Savings assumed at completion usually depend on closing capacity, and closing capacity is slow: customer approvals are site-specific, equipment relocation is disruptive, and the site with the better assets is not always the one with the better people. Capital sits in the wrong places for a while. Systems integration is the other long pole — a single item master requires mapping two numbering schemes and reconciling bills of materials built on different assumptions, while running both systems in parallel meanwhile costs more than either did alone. Naming an owner for each promised benefit, with a date and a measure attached, separates the savings that materialise from the ones quietly forgotten.

Frequently asked questions

How quickly can we move a product from one plant to another after a merger?

Physically, sometimes within weeks; contractually, often far longer. The pacing item is customer and regulatory approval, since many specifications name the manufacturing site, and a transfer usually needs notification, sample approval and occasionally full re-qualification. Build the sequence around those approvals rather than around the equipment move, and begin the notifications before operational planning is finished, because they are the genuine long lead item.

Should we standardise on one site's processes or take the best from each?

Choosing the best of each sounds obvious and proves much harder to execute, because every hybrid procedure needs writing, training and validating from scratch. Adopting one site's way is quicker and demoralises the other. A workable compromise standardises wholesale on one system for administrative and quality processes, while allowing genuinely justified technical differences to persist where a customer approval or a piece of equipment demands it, with each exception documented and reviewed.

What do we do about customers who buy from both companies at different prices?

Expect the discrepancy to surface quickly, usually raised by the customer. Decide in advance whether prices converge upward, downward or over an agreed period, and treat it as a commercial project with named owners rather than letting individual account managers improvise. Where contracts differ in terms as well as price — lead times, quality agreements, liability caps — those differences matter more than the number and deserve deliberate reconciliation.