How to Consolidate Shipping Systems after Healthcare M&A

Kris Gösser
October 20, 2026
Product
See how Shipium completes your Manhattan implementation.

Every healthcare acquisition brings a product line, a set of facilities, and usually its own shipping system. A few deals later, the parent company is rating the same carrier's shipments under separate contracts, with separate rules, in separate systems, and nobody can see the total. When leadership asks how to consolidate shipping systems, the conversation often turns into a multi-year post-merger TMS integration program.

Our view is that parcel can be fixed first. Parcel decisions can move into one shared layer that every subsidiary's WMS or ERP calls: one set of carrier contracts, one rulebook, one carrier network, one shipment record. The TMS consolidation can then follow on its own schedule.

The tell is the quarterly review where finance asks what parcel cost by business unit, and the answer takes a week and three spreadsheets.

Key highlights:

  • Healthcare and life sciences companies often run several shipping systems at once, inherited from acquired subsidiaries that kept their own WMS, ERP and TMS.
  • Fragmentation costs show up as split carrier volume, inconsistent service selection, slow carrier onboarding, and spend that finance can't attribute.
  • Consolidating parcel means centralizing contracts, rules, carrier connections and shipment data, while each site keeps its system of record and local workflows.
  • Shipium's Console and Rules Engine centralize shipping configuration across subsidiaries, with business-unit-specific logic and cost allocation by business unit.

Why do healthcare companies end up with multiple shipping systems?

Healthcare companies end up with multiple shipping systems because acquisitions bring their systems with them, and shipping is wired into each subsidiary's WMS and ERP. Those core systems often don't merge on day one, so the shipping system attached to each one stays too.

The pace of dealmaking makes this more pressing in 2026. PwC's Pharmaceutical and life sciences: US Deals 2026 midyear outlook found that U.S. pharma and life sciences deal value passed $65 billion in the first quarter, the strongest quarter since 2020, with 16 biopharma deals above $1 billion. Each deal can bring its own sites, systems and carrier contracts into a parent company that now has to ship as one.

Two shifts make the fragmentation more expensive for healthcare and life sciences shipping now. Direct-to-patient models are pushing parcel volume into networks built for shipping to distributors and dispensers, so parcel operations are growing. And carriers are courting healthcare volume: Supply Chain Dive reported that FedEx has been chasing more profitable segments such as healthcare. New healthcare-capable services only help if every subsidiary can actually use them.

What do fragmented shipping systems cost?

Fragmented shipping systems cost money in five places, and much of it is spread across contracts that were never combined, rules that drifted apart, and data nobody can join.

Symptom What it costs Who feels it
Separate carrier contracts per subsidiary Volume split across agreements, so no single contract reflects the parent company's combined spend with that carrier Procurement, transportation
Different rules for the same decision One site ships a refill overnight while another sends the same order ground, with no shared logic for when speed is worth the cost Operations, patients
Carrier onboarding repeated per system Adding a regional or healthcare-capable carrier means a separate integration and test cycle in every subsidiary's system IT, transportation
Shipment data in separate schemas Finance can't see parcel cost by business unit, lane or service without stitching exports together Finance, leadership
Invoices audited separately, or not at all Each subsidiary reconciles its own carrier bills, so the same billing error can repeat across sites unnoticed Finance

The first row deserves the most attention. Carrier pricing is negotiated on volume, so a parent company that ships through three subsidiaries, each with its own contract, is effectively negotiating as three smaller shippers.

Say three subsidiaries each spend $3 million a year with the same national carrier. At renewal, each one negotiates as a $3 million account. Think about what that means: the parent company is a $9 million customer that the carrier never has to price as one. Combining the contracts is how that volume starts counting.

Figures are illustrative.

What should you centralize, and what should stay local?

Centralize the parcel decisions and the data they produce; keep the systems of record and the physical workflows local. That split gives a parent company centralized shipping operations, acting as one shipper while each subsidiary keeps its own WMS.

Layer Centralize Keep local
Carrier contracts and rates One view of every contract, rated on fully loaded cost Site-specific accounts where a contract requires them
Selection rules One rulebook for service and carrier choice, with business-unit overrides where the business genuinely differs Cutoff times and operating days for each site
Carrier connections One carrier network that every site can use Which regional carriers serve each site's lanes
Shipment data One shipment record, so cost and performance roll up by business unit, lane and service Nothing; local copies are where reconciliation goes to die
Invoice audit and cost allocation Audit every carrier bill against the shipment record and allocate cost to each business unit Business-unit sign-off on its own allocated spend
WMS, ERP and TMS Nothing yet The system of record at each subsidiary, on its own migration timeline

Gartner's latest research points the same way. Its 2026 Market Guide for Multicarrier Parcel Management Solutions notes that most ERP, TMS, OMS and WMS providers do not specialize in parcel capability. That's what makes the sequence possible: parcel can live in its own layer and be consolidated while the TMS consolidation is still underway.

The last row is the point. Your freight TMS program can take whatever time it needs, and parcel stops waiting on it.asdw

How to consolidate shipping systems across subsidiaries

Consolidating parcel across subsidiaries works best as six steps, one business unit at a time. The early steps cost little and tell you whether the later ones are worth it.

  1. Inventory every system and contract. List each subsidiary's WMS, ERP, TMS and shipping tool, every carrier account and contract, and who can change rules in each. Expect to find at least one account nobody remembered signing.
  2. Model the combined network before changing anything. Run historical shipments from each business unit through one rating model to see what combined contracts and consistent rules would have cost. This is the business case procurement and finance will ask for.
  3. Write one rulebook with explicit overrides. Agree on how service and carrier get chosen for each order type, such as refills, new prescriptions, clinic orders and samples. Where a business unit truly needs different logic, make it a named override in the shared rulebook, so the difference is deliberate.
  4. Connect sites one at a time. Point each subsidiary's WMS or ERP at the shared parcel layer, starting with the site where the business case is clearest. Each connection reuses the same carrier network, so the second site should go faster than the first.
  5. Unify shipment data and invoice audit. Once sites share a shipment record, audit every carrier invoice against it and allocate cost by business unit. This is where the quarterly-review question gets a fast answer.
  6. Renegotiate with the combined volume. Bring a single, defensible view of total spend by carrier, service and lane to carrier negotiations, so the parent company negotiates as one shipper.

How Shipium consolidates parcel shipping across subsidiaries

Shipium is built to be that shared parcel layer: each subsidiary's WMS, OMS or ERP calls one platform for rating, labeling and carrier selection, and one Console holds the contracts, rules and data.

Step How Shipium supports it
Model the combined network Simulation models a newly acquired business unit, a new carrier mix or a network change against your real shipment history, to build the business case for procurement and finance
One rulebook with overrides The Rules Engine holds global and business-unit-specific logic, which your supply chain team changes from the Console without an IT ticket
Connect sites one at a time Configuration-ready integration frameworks for the WMS, OMS and ERP systems HLS companies run, plus a pre-integrated carrier network where new regional or healthcare-specific services can be added in days
Unify data and audit Orca AI Analytics shows carrier performance and shipping cost by business unit; Invoice Management matches carrier bills against shipment-time rates
Allocate cost Billing Management generates cost allocations from shipment data, tying shipping spend back to finance by business unit

The same consolidation pattern shows up outside healthcare. Nurture Life moved shipping that was spread across multiple systems into Shipium and now manages carriers, contracts, surcharges and rules from one place. For a broader comparison with older platforms, see Shipium vs. legacy shipping systems.

Book a demo and we'll model what your subsidiaries would cost to ship as one network, before anything in production changes.

Frequently asked questions

How do you consolidate parcel shipping while keeping your existing TMSs?

You consolidate parcel shipping by moving it into one shared platform that each subsidiary's WMS, ERP or TMS calls for rating, labeling and carrier selection. Each system of record stays in place, and any TMS consolidation can run on its own timeline.

What should be centralized first when consolidating shipping systems?

Carrier contracts and shipment data should be centralized first. A single view of every contract and every shipment shows what combined volume and consistent rules would be worth, which is the business case for the rest of the project.

How do you handle business units that need different shipping rules?

You handle different business-unit needs with named overrides inside one shared rulebook. The default logic applies everywhere, and each override documents where a business unit genuinely ships differently, such as temperature-sensitive products or clinic deliveries.

How do you allocate shipping costs across business units?

You allocate shipping costs by tying every shipment, and every carrier invoice line, to the business unit that generated it in a single shipment record. Allocations then come from real shipment data, so each business unit can review its own spend.

Why does M&A make healthcare shipping more expensive?

M&A makes healthcare shipping more expensive when each acquired subsidiary keeps its own carrier contracts, rules and systems. Carrier volume gets split across agreements, carrier onboarding is repeated system by system, and finance loses a clear view of spend by business unit.