Waiting on the ERP

Waiting on the ERP

The Digital Side of the Deal

This is the second issue of The Digital Side of the Deal, a letter I send every other Tuesday to ecommerce, IT and marketing leaders at manufacturers and distributors growing through acquisition. If someone forwarded it to you or you found it here, you can get the next issue by email.

Issue 2 | November 17, 2026 | Sent every other Tuesday

Hi there,

One of our clients decided to launch their new ERP and their new ecommerce platform on the same day. We told them we could do it, and we did, but we also told them it would make the planning of both more complex. After go-live, they told me they wished they hadn’t done it the way they did. Coordinating one launch date made both projects harder, and they should've separated the two.

Their reason for tying the projects together is one I hear in nearly every conversation with companies that are growing through acquisition. If the acquired company is moving to the parent company’s ERP eventually, why are you integrating the current ERP with the parent site now, when you'll need to do it again later?

What’s the Holdup?

It’s a fair question. Your ERP is essential to running your business. What I question is whether customers need to wait until every acquired company is on the same one.

The problem, as you can imagine, is time. We've helped many customers through ERP moves, and they almost always take longer than planned. They can be very worthwhile projects, but they're lengthy, and it can be several years before an acquired company goes live on the new ERP. So if the digital experience waits on that go-live, the acquired company’s customers wait too. Customers keep calling and emailing for pricing, availability, and order status; information they could've looked up themselves.

ERP consolidation and your digital experience can and should be two separate decisions. The cost of integrating now has to be weighed against the cost of leaving customers waiting, potentially for years. Either way, waiting to integrate should be a decision your team makes on purpose rather than by default.

Plan for More Than One ERP

Several years ago, we worked with a manufacturer that was growing through acquisition. They wanted to sell products from any company they acquired, whatever ERP it ran on. We built a data integration layer so their main site connected to one system, and each ERP connected to that integration layer. Every new acquisition still took work to connect, but the ERP stopped being the thing that held them back.

A shared integration layer connects the parent company’s ERP and two acquired companies’ ERPs to one website where customers can find products, see account pricing, check availability, and place orders.

Customers can have one place to buy while the businesses still run on different ERPs.

The data layer we built was one approach, but there are others. They all start the same way: telling your systems implementer up front that you'll be integrating more than one ERP over time. Planning for more than one ERP takes some upfront work, but it can reduce how much you rebuild with each acquisition. 

Why This Matters More Than Ever

Picture a buyer asking an AI assistant to find the replacement part that fits the machine they own, show them the price, and check whether it's in stock.

It brings to mind a technology I'm excited about called WebMCP because it could make tasks like this easier. It gives AI assistants a defined way to use functions on your site, such as looking up specs, checking availability, or adding items to a cart. Though your team will have to make those functions available because they don't happen on their own. WebMCP is still a proposed standard that is only available for experimentation in Chrome, so this isn't something to rush into this quarter, but it could be something to plan for.

For WebMCP and other tools to be useful, your site needs clean, structured product data with clear pricing and availability. All of which comes from your integrations. If an acquired company’s products, pricing, and availability aren't reaching your site, an agent won't find them. Connecting them now helps customers right away and builds the foundation for these tools later.

If you are thinking, “But we have customer-specific pricing,” so does nearly every B2B company that has hired us over the years. Tools like WebMCP don't rule this out, but when it's set up well, an assistant can use the buyer’s signed-in session to get their pricing, and your site can still enforce their account permissions.

Questions to Ask This Month

If you're growing through acquisition, you likely have companies on different ERPs. Pick one acquisition that's waiting on an ERP move and ask yourself:

  1. What can its customers not do online today?
  2. When is its ERP move realistically going to go live? Base this on how long your past ERP moves took compared to the plan.
  3. What would it take to let those customers do one valuable thing online now? How much of that work could be reused after the move?

Two Decisions, Not One

Yes, your ERP is central to running your business. But no, your acquisitions don't all need to be on the same ERP before their customers can get what they need from your site. The ERP migration date shouldn't be what decides when acquired customers get a better online experience. Show these answers to your implementer and ask them what it would take to connect that acquisition now.

Is an ERP move holding up your acquisitions' online progress? Reply and tell me what those customers aren't able to do. If your team has already decided to wait, or maybe decided not to wait, I'd like to hear how it went.

Best,
Lori

Lori McDonald is CEO of Brilliance Business Solutions. The Digital Side of the Deal is written by me and published by Brilliance.

P.S. If another deal is coming, we built a free spreadsheet to catalog the websites, ERPs, payment processors, and other systems of each company you acquire. Download the Acquired Stack Inventory to jump start your planning process.


If this was useful, subscribe here and the next issue will come to your inbox. New subscribers also get the Acquired Stack Inventory spreadsheet.