WMS Buyer's Guide 2025 | SC Radar Reports

10 min readSC Radar Intelligence ReportPreview

Executive Summary

Warehouse management is now one of the few supply chain software categories where the buyer conversation has clearly moved up a level. A WMS project used to be framed as a warehouse-system replacement: better inventory control, better RF workflows, better task management. In 2025, the category is being bought as an execution platform for labor, automation, and service-level resilience. The question is no longer just whether the system can run the building. It is whether the platform can help the business absorb e-commerce volatility, support returns, orchestrate robotics, and improve site-level throughput without creating another decade of customization debt.

That is why the market remains attractive even while other software budgets are tighter. The demand drivers are concrete: labor pressure, omnichannel complexity, more automation on the floor, and the need to manage forward and reverse flows with the same system of record. At the same time, the vendor field is splitting. Enterprise incumbents still dominate the most complex networks, especially where ERP coupling, labor engineering, or material-handling integration is deep. But cloud-native challengers are winning attention because they promise faster go-lives, cleaner APIs, and lower upgrade pain.

For a supply chain director or VP, the buying criteria in 2025 are sharper than they were even two years ago. Buyers need to evaluate implementation speed, automation readiness, integration ownership, upgrade economics, and the degree of customer-specific code required to make the product fit. They also need a clearer view of total cost of ownership. A low headline subscription can still become an expensive program once ERP integration, parcel connectivity, robotics orchestration, testing, and change management are included.

What changed in 2025 is not that every warehouse suddenly became autonomous. It is that WMS vendors started selling more credibly into three high-priority problems: cloud modernization, human-plus-robot orchestration, and returns complexity. The best buying process now treats WMS as both an operational system and a capital-allocation decision.

Market Snapshot

The WMS market remains large and durable. MarketsandMarkets sizes the category at roughly $4.57 billion in 2025, with continued expansion expected through the end of the decade. Demand is not being created by software fashion. It is being created by operating pressure. U.S. e-commerce keeps pushing more order lines through warehouse networks, while reverse logistics has become a margin-management issue rather than a back-room afterthought. NRF and Happy Returns estimated $890 billion in retail returns for 2024, which matters because many warehouse environments still handle returns through fragmented workflows, separate tools, or manual workarounds.

Three trends matter most for buyers in 2025:

Cloud-native adoption is now the default buying conversation. Buyers want faster upgrade cycles, fewer custom-code traps, and stronger API connectivity to ERP, OMS, TMS, parcel, and analytics layers.
Robotics integration has moved from edge case to mainstream requirement. AMRs, AS/RS, goods-to-person systems, cobots, and voice workflows are no longer separate innovation projects; they increasingly need to plug into the WMS operating model.
Returns and omnichannel complexity are reshaping selection criteria. A system that is strong on outbound picking but weak on reverse logistics, store replenishment, or order prioritization will underperform in modern retail and DTC environments.

There is also a practical capital-markets angle. MHI and Deloitte reported that 55% of supply chain leaders increased technology investment in 2025, and WMS continues to benefit because it sits close to hard operating metrics: labor utilization, inventory accuracy, cycle time, and fill rate. For buyers, that means the right WMS can still win budget, but the evaluation bar is higher. Boards and CFOs are more willing to fund execution software when the ROI logic is tied to service, labor, and throughput, not just digital transformation language.

Vendor Landscape

Enterprise Tier

Manhattan Associates

Best fit for large enterprises with complex distribution networks, high automation density, and low tolerance for execution risk. Strengths include workflow depth, strong labor and automation credibility, and a mature cloud story through Manhattan Active. The main watchout is cost and program complexity; Manhattan is rarely the cheap or fast option. Pricing is typically custom enterprise subscription plus implementation services. Recent signal: Manhattan used Momentum 2025 to unveil agentic AI positioning around its platform, reinforcing its push from system-of-record to execution-intelligence layer.

Blue Yonder

Best fit for large retailers, manufacturers, grocers, and logistics-heavy enterprises that want warehouse optimization tied to a broader planning-and-execution estate. Strengths include resource orchestration, robotics-friendly positioning, and strong credibility in brownfield improvement programs. Weaknesses include integration and transformation complexity if the buyer wants a fast, clean-slate WMS rollout. Pricing is generally enterprise quote-based. Recent signal: Blue Yonder introduced its Warehouse Operations Agent and kept building its robotics and orchestration narrative, signaling a stronger AI-in-the-shift story rather than dashboard-only intelligence.

SAP EWM

Best fit for enterprises already standardized on SAP and unwilling to create a separate warehouse stack unless the value is overwhelming. Strengths include deep SAP alignment, strong fit for manufacturing and regulated environments, and a credible path for buyers who care more about ERP continuity than best-of-breed UX. Weaknesses include heavier implementation effort and a less flexible greenfield story than many cloud-native challengers. Pricing is usually bound to broader SAP commercial structures and is not transparently published. Recent signal: SAP keeps adding capability in S/4HANA EWM releases, especially around labor, Advanced Shipping and Receiving, and cloud deployment options.

Mid-Market Tier

Korber / Infios

Best fit for distributors, manufacturers, and 3PLs that want broad warehouse functionality with more flexibility than a mega-suite. Strengths include warehouse depth, voice and labor heritage, and a portfolio that can stretch from SMB to complex operations. Weaknesses include brand transition risk and product-family complexity across the installed base. Pricing is quote-based and varies by deployment model and scope. Recent signal: Korber's supply chain software business rebranded to Infios in 2025, a notable move because it reframes the company as a broader supply chain platform rather than only a classic WMS vendor.

Infor WMS

Best fit for companies already invested in Infor CloudSuite or those wanting a practical, operations-heavy WMS inside a broader ERP relationship. Strengths include strong manufacturing and distribution fit, solid workflow coverage, and a realistic path for buyers who prioritize ecosystem fit over category flash. Weaknesses include less market buzz than the leaders and less momentum in greenfield warehouse narratives than cloud-native challengers. Pricing is typically custom and sold as part of broader Infor commercial bundles. Recent signal: Infor has kept pushing AI and workflow acceleration through its Velocity Suite positioning, which helps existing customers modernize without changing their software stack.

Tecsys

Best fit for healthcare, complex distribution, and regulated environments where operational nuance matters more than sleek demos. Strengths include strong domain depth, especially in healthcare and high-service distribution, plus credible warehouse execution in environments where traceability and service levels matter. Weaknesses include narrower brand visibility outside its strongest verticals and a smaller ecosystem than the largest suites. Pricing is custom and usually tied to scope, users, and deployment. Recent signal: Tecsys continues to emphasize cloud WMS and robotics-ready execution, with the market still treating it as a specialist operator's choice rather than a mass-market default.

Cloud-Native Challengers

Deposco

Best fit for retailers, ecommerce operators, and upper-mid-market networks that want a faster deployment profile without giving up warehouse execution depth. Strengths include time to value, solid omnichannel posture, and practical automation readiness. Weaknesses include less credibility than Manhattan or SAP in the most customized multi-site enterprise environments. Pricing is quote-based SaaS plus implementation. Recent signal: Deposco used ProMat 2025 to highlight Order Fulfillment Profiles, smarter Directed Putaway, and preconfigured automation integrations, which reinforces its pitch around flexibility without a massive implementation program.

Logiwa

Best fit for high-growth DTC, ecommerce, and digitally native operators that care about fast rollout, multi-channel inventory visibility, and API-first extensibility. Strengths include cloud-native architecture, ecommerce fit, and implementation speed. Weaknesses include a lighter fit for highly engineered enterprise distribution environments with deep legacy coupling. Pricing is typically subscription-based but not broadly published for large deployments. Recent signal: Logiwa keeps leaning on rapid go-live and fulfillment-efficiency customer stories, which supports its position as a speed-first option for modern commerce operations.

Extensiv

Best fit for 3PLs, multi-client warehouses, and SMB-to-mid-market fulfillment operators that need practicality more than transformation theater. Strengths include 3PL workflow fit, ecosystem breadth, and operator-friendly release cadence. Weaknesses include limited fit for the largest enterprise distribution programs and less strategic gravity in executive shortlist processes. Pricing is generally SaaS-style and quote-based depending on warehouse count and scope. Recent signal: Extensiv's recent Warehouse Manager releases focused on practical workflow upgrades such as item aliasing and serial-number handling, which is exactly the kind of incremental product shipping its core customer base values.

Evaluation Framework

Use these ten questions to force differentiation during demos, reference calls, and commercial negotiations:

How fast can one site go live and stabilize? Ask for first-site timing, not enterprise-program slides.
What percentage of workflows require customer-specific code? This is the fastest proxy for future upgrade pain.
Who owns ERP integration? Get explicit answers on middleware, master data, write-back, and upgrade testing.
How does the system connect to robotics and automation vendors? Ask for real connectors, not roadmap language.
How are returns, reverse logistics, and quality holds handled? Many demos stay too outbound-centric.
What does peak-season exception management look like? The system needs to be credible under stress, not just in steady state.
How are labor planning, task interleaving, and supervisor workflows supported? WMS buying is still labor buying.
What is the release cadence and customer upgrade burden? Cloud claims only matter if upgrades are actually lightweight.
What customer references look like our network? Industry match matters less than complexity match.
What does the vendor's first-year ROI model assume? Force the vendor to show where labor, service, or inventory gains actually come from.

Score vendors on five dimensions:

Operational fit (30%): workflow coverage, site complexity, labor model, returns, and automation support.
Time to value (20%): first-site speed, implementation burden, and internal resource requirements.
Integration and architecture (20%): ERP connectivity, APIs, robotics interfaces, data model quality, and upgrade path.
Commercial efficiency (15%): subscription economics, implementation scope, and expected support burden.
Vendor momentum (15%): product shipping cadence, customer traction, and clarity of roadmap.

Total Cost of Ownership

The most common WMS buying error is to compare software subscription numbers while underestimating the delivery program around them. In practice, the first-year cost stack usually includes five buckets: software, implementation services, integration, internal project labor, and post-go-live support. For a straightforward single-site cloud deployment, buyers should expect the real first-year program cost to land well above the headline license. For multi-site enterprise rollouts with robotics, parcel, ERP, and change-management requirements, the true number often becomes a seven-figure program before the second site is even discussed.

SC Radar planning shorthand:

Straightforward cloud mid-market deployment: often lands in the high six figures once implementation and integration are included.
Complex enterprise or multi-site rollout: often moves into the low-to-mid seven figures.
Automation-heavy program: budget additional integration, testing, and orchestration spend above the core WMS program.

Cost categories to pressure-test:

Licensing or subscription: named users, site count, transaction volume, or modular add-ons.
Implementation services: configuration, data migration, training, testing, and cutover support.
Integration: ERP, OMS, TMS, parcel, EDI, and robotics or material-handling interfaces.
Change management: site champions, SOP redesign, labor-training time, and temporary productivity loss during stabilization.
Ongoing support: vendor support tier, managed services, enhancement backlog, and regression testing for upgrades.

The right commercial question is not "Which vendor is cheapest?" It is "Which option gives us the cleanest path to measurable service and labor improvement with the least future rework?"

The Cloud-Native vs. Legacy Decision

Choose cloud-native when speed, flexibility, and lower customization debt matter most. This is usually the better path for greenfield warehouses, fast-growing ecommerce and omnichannel operations, 3PL expansions, or teams that need cleaner API connectivity across storefronts, OMS, parcel, and analytics systems. Cloud-native vendors tend to win when the buyer wants repeatable deployment, lighter upgrade burden, and a more modern integration model.

Choose legacy or enterprise incumbent platforms when the warehouse network is genuinely complex: many sites, heavily customized workflows, deep SAP or enterprise-ERP dependency, unionized or highly engineered labor models, expensive automation already installed, or regulated process requirements. In those environments, the risk of replacing process depth with implementation speed can outweigh the benefits of a cleaner modern stack.

Migration questions to settle early:

Is the target state a full replacement, a site-by-site modernization, or a coexistence model?
Which legacy customizations are real competitive requirements and which are historical baggage?
Can the business tolerate standardization if it gets a faster upgrade path in return?
Will robotics, voice, or AS/RS integrations be rebuilt, reused, or mediated through a separate layer?

In most cases, this is not a pure architecture debate. It is a risk-allocation decision between speed now and complexity later.

Buyer's Checklist

Define the first-site success metrics before the RFP starts.
Separate must-have workflows from inherited preferences.
Require every vendor to map ERP, parcel, returns, and automation integration ownership.
Ask for two customer references that match your operational complexity, not just your industry.
Demand a clear first-year cost model that includes implementation, integration, and internal labor.
Force vendors to show upgrade mechanics, not just promise a cloud roadmap.
Test returns, exceptions, and peak-season scenarios in the scripted demo.
Ask what percentage of the delivered solution will be customer-specific code.
Identify which sites should modernize first and which should wait.
Align procurement, IT, warehouse operations, and finance on the same scorecard before final negotiation.

Conclusion & Recommendations

The WMS market in 2025 rewards clear-eyed buyers. Manhattan, Blue Yonder, and SAP EWM still matter because complexity still matters. Deposco, Logiwa, and Extensiv matter because speed, flexibility, and lower upgrade drag now matter more than they used to. Korber, Infor, and Tecsys remain credible because many buyers do not need the loudest story; they need the best fit for the operating model they actually run.

SC Radar's recommendation is straightforward. Start with the operating environment, not the vendor brand. If the first site needs to go live fast, the system must integrate broadly, and the business can live with more standardization, bias toward the strongest cloud-native options. If the network is heavily automated, deeply ERP-coupled, or operationally ugly in ways demos hide, keep the enterprise incumbents in the process. Above all, price the whole program, not just the subscription. The winner is the platform that improves throughput and service without creating a second modernization project three years from now.