"100% of assortment planning implementations historically fail."
That's not a provocation. That's a quote from one of our implementation partners who has watched more retail tech projects go sideways than they can count. And in conversations across the industry, it comes up more than it should.
So what does "fail" mean in practice? It means a retailer invests 12 to 18 months, somewhere between $500K and several million dollars, and a significant amount of organizational goodwill -- and ends up either abandoning the project or running parallel systems indefinitely because the implementation never fully landed.
The planning team is still in Excel. The system isn't trusted. The vendor relationship is strained. And someone has to explain to the CFO why the ROI conversation has been pushed out another fiscal year.
There is a subset of implementations that don't end this way. The question worth asking is what they do differently.
Why Retail Planning Implementations Fail (And What It Actually Costs)
The retailers who end up in implementation purgatory share a few common traits. They chose a vendor based on feature depth rather than deployment model. They agreed to a roadmap that stretched 18 months before any planner would touch a live system.
Responsibilities between client, vendor, and systems integrator were loosely defined -- everyone assumed the other party owned the hard parts. And success was framed as "go live" rather than as something measurable planners actually cared about.
When those projects stall, the compounding cost is real. There's the direct spend: implementation fees, SI hours, internal time.
There's the opportunity cost: another season of decisions made on bad data.
And there's the morale cost, which rarely makes it into the financial model -- planning teams who went through one failed implementation are harder to rally for the next attempt.
What Successful Implementations Do Differently
The implementations that work tend to have three things in common.
Responsibility is Divided Clearly and Enforced
The client owns data quality and stakeholder alignment. The vendor owns configuration and product functionality. The Systems Integrator, if one is involved, owns integration and change management. When those boundaries blur, accountability disappears.
The implementations that succeed usually have someone willing to say, out loud, who owns what and what happens if that work isn't done.
Why the Cost of a Failed Implementation Is Riskier Right Now
The current environment makes the cost of a failed implementation higher than it's ever been.
Tariff volatility is reshaping sourcing decisions mid-season.
Margin pressure is forcing CFOs to scrutinize every tech line item.
Retailers who are mid-project and miserable don't have the luxury of waiting another year for an implementation to turn around.
The business case for merchandise planning has never been easier to make: 2 to 3 points of gross margin improvement, 5 to 10 percent reduction in excess inventory, faster response to demand signals. But that case falls apart completely if the implementation doesn't actually land. The ROI math only works if the system gets used.
How to Evaluate a Planning Vendor Before You Sign
Before signing anything, ask the vendor how many customers went live in under six months.
Ask what percentage of their customer base is actively using the system versus technically implemented.
Ask what happens in month four if the integration isn't working; who owns that, and what does it cost you.
The answers will tell you more than any feature demo.
The retailers who pick well are the ones who found the platform most likely to be running, trusted, and delivering value by the time they need it.
