Why ecomm replatforming isn’t always the answer

The question underneath all of it is whether the infrastructure is holding the store back, and whether fixing that is simpler than starting over.

Before the vendor calls

The Shopify Plus pitch tends to come first. The rep is well-prepared: compliance handled at the platform level, no more infrastructure decisions, a migration team that’s run hundreds of them.

You walk out thinking about the custom work in your current build. The B2B pricing logic, the multi-warehouse routing, the checkout flow that took the better part of two years to tune.

Your developer’s read is direct: rebuilding those features isn’t impossible, but producing an honest estimate of what it costs in developer time and calendar months requires assumptions neither of you can stand behind. The number is not going to be small.

When the developer runs the numbers

As of early 2026, Shopify Plus starts at $2,300 per month on a three-year term. Above a certain revenue threshold it shifts to a percentage of monthly GMV, which for a mid-market retailer can reach tens of thousands per year in platform fees alone before you factor in transaction costs, app licensing, and the migration itself.

The developer’s reframe: the application is paid for. You don’t need a new platform. You need better infrastructure underneath the one you already have. That’s usually when this shifts from a replatforming conversation to an infrastructure one.

What the decision comes down to

Two things tend to drive it.

The first is compliance. PCI DSS v4.0.1 Requirements 6.4.3 and 11.6.1, mandatory since March 2025, require payment page scripts to be inventoried, integrity-checked, and monitored for unauthorized changes. On dedicated infrastructure with a documented responsibility model, the question of who owns that work has a written answer before an auditor asks for it. On shared virtual infrastructure, that same question tends to produce a conversation rather than a document.

The second is cost predictability. The CFO’s requirement is simple: an invoice that doesn’t change when December traffic does. On fixed-cost dedicated infrastructure, it doesn’t.

When the evaluation gets to those specifics rather than staying at the platform-features level, the replatforming case tends to lose momentum. The ecomm application isn’t the problem, the infrastructure underneath it is, and that’s a different kind of fix.

The vendor calls that follow

Once the conversation shifts to infrastructure, the questions change. Not which platform, but what the responsibility model covers, who owns the compliance work when an auditor asks, and whether the invoice holds when December traffic doesn’t.