Written by Takayama — Paddy & Water Inc. / Supply Chain

WMS Explained

― Warehouse Management System Functions, Selection, and a Comparison of Leading Vendors ―

Functional Framework / Deployment Types / Manhattan, Blue Yonder, SAP, Oracle, Körber, and Others

July 2026

This report provides an overview of Warehouse Management Systems (WMS) in general, organizing their role, core functions, deployment types, and selection criteria, and offers a cross-vendor comparison of leading providers (Manhattan Associates, Blue Yonder, SAP EWM, Oracle, Körber (Infios), Infor, and others). The primary intended readers are SCM, logistics, and IT planning practitioners considering a WMS implementation or renewal.

Chapter 1　What Is a WMS?

A WMS (Warehouse Management System) is a system that manages and optimizes in-warehouse operations from receiving through putaway, storage, picking, and shipping. It integrates with ERP, OMS (order management), and TMS (transportation management) systems to track, in real time, “where things are, how much there is, and in what condition,” and to direct work accordingly.

System	Role	Relationship to WMS
ERP	Core system for order management, inventory, and accounting	Issues shipment instructions to the WMS and receives inventory results from the WMS
OMS	Order intake, inventory allocation, cross-channel management	Passes shipping orders to the WMS
WMS	Management and optimization of in-warehouse work	Directs and tracks putaway, picking, and shipping
WCS/MFS	Control of automated equipment	Converts WMS instructions into equipment actions (can be integrated via MFS in EWM)
TMS	Transportation planning and execution	Coordinates WMS shipments with dock scheduling and load planning

Chapter 2　Core WMS Functions ― What It Can Do (In Detail)

• Receiving and Putaway: ASN matching, inspection, and optimal shelf placement based on putaway strategy

• Inventory Management: Real-time inventory by bin, lot, serial number, and handling unit (HU); cycle counting; traceability

• Picking and Shipping: Wave/batch/zone picking, packing, shipping inspection, label issuance

• Labor Management: Standard work times, productivity measurement, staffing plans

• Slotting: Designing and re-arranging optimal shelf placement based on shipping frequency

• Automation Control: Integration with AS/RS, conveyors, sorters, AGV/AMR, and GTP robots (via WCS/MFS)

• Value-Added Services (VAS): In-warehouse processing such as kitting, labeling, and assembly

• Visibility and Analytics: KPI (productivity, accuracy, throughput, OTIF) dashboards

2-1　Receiving and Putaway (Inbound)

• ASN Matching: Reconciles advance shipping notices and purchase orders against actual receipts, detecting discrepancies in quantity, item, and lot

• Inspection and Receipt: Quantity inspection, quality inspection (integrated with QM), damage checks; routes to putaway or hold based on pass/fail results

• Putaway Strategy: Automatically determines the optimal storage location based on item characteristics, available space, temperature zone, and turnover rate (fixed location, floating location, proximity storage, etc.)

• HU Generation on Receipt: Assigns handling unit numbers by pallet or case, enabling subsequent inventory and movement management at the unit-load level

• Cross-Docking: Moves received goods directly to shipping without storage, reducing storage costs and lead time

2-2　Inventory Management and Cycle Counting

• Real-Time Inventory: Immediate visibility of inventory by bin, HU, lot, serial number, and quality status

• Stock and Bin Transfers: Controls internal transfers, replenishment, and movements between storage types via work instructions

• Physical Inventory: Cycle counting and full physical counts, with discrepancy logging and accounting adjustments

• Traceability: Tracking by lot, serial number, and expiration date (FEFO), and recall support

2-3　Picking and Shipping (Outbound)

• Wave/Batch/Zone/Multi-Order Picking: Groups shipping orders to optimize routing and resources

• Picking Strategies: FEFO/FIFO, shortest-route picking, single-order (discrete) picking, and batch picking with downstream sortation

• Picking Support: RF handhelds, voice picking (Pick-by-Voice), picking carts, Pick-to-Light/Put-to-Light

• Packing and Shipping Inspection: Packing, weight/dimension checks, shipping label/delivery note issuance, load building

• Shipping and Dock Scheduling: Shipping door assignment, truck loading, and coordination with TMS/transportation

2-4　Returns, Value-Added Services, and Other Processes

• Returns Processing: Returns receipt, inspection, and restock/disposal decisions — important for e-commerce reverse logistics

• Value-Added Services (VAS): In-warehouse processing such as labeling, kitting, assembly, and repackaging

• De-consolidation: Re-sorting consolidated handling units by destination

• Yard Management: Positioning and movement of trailers, vehicles, and dock assignments on-site

• Billing: Warehouse service billing for 3PLs based on storage and labor volume

2-5　Labor Management, Slotting, and Automation Control

• Labor Management: Setting standard work times, performance measurement, productivity analysis, staffing plans, and incentives

• Slotting: Designing and periodically re-arranging optimal shelf placement based on shipping frequency (ABC analysis), weight, and size

• Automation Control: Integration with AS/RS, conveyors, sorters, AGV/AMR, and GTP (Goods-to-Person) robots; equipment controlled via WCS/WES/MFS

• Material Handling Equipment Integration: Connectivity with DPS (digital picking systems), automated packing machines, and weight-check systems

2-6　Visibility, Analytics, and Management

• KPI Dashboards: Productivity (units/hour), shipping accuracy, inventory accuracy, throughput, OTIF, and space utilization

• Work Monitoring: Real-time monitoring of progress, delays, and exceptions, with dynamic work reallocation

• AI/Forecasting: Demand-driven work planning, slotting optimization, anomaly detection, and peak-period forecasting

💡 WMS functionality is easiest to grasp when understood along the logistics flow of “receiving → putaway → storage → picking → shipping.” What differentiates one WMS from another lies in the capabilities layered on top of this foundation — labor management, slotting, automation control, and analytics — and the sophistication of these capabilities increasingly determines productivity as warehouse scale and automation levels rise.

Chapter 3　WMS Deployment Types and Selection

3-1　ERP-Embedded vs. Best-of-Breed

• ERP-Embedded (e.g., SAP EWM, Oracle WMS): Tightly integrated with the core ERP system, making master data and inventory consistency easier to maintain, and simplifying operations by using the same vendor as the ERP

• Best-of-Breed (e.g., Manhattan, Blue Yonder, Körber): Advanced, WMS-specialist functionality and automation support; ERP-independent, and well-suited to environments running multiple ERPs

3-2　Cloud vs. On-Premises, by Scale (Tier)

• Cloud (SaaS): Excels in deployment speed, updates, and scalability; increasingly the mainstream choice in recent years (Manhattan Active, Blue Yonder Luminate, etc.)

• By Tier: Tier 1 = large scale, highly automated (Manhattan/Blue Yonder/SAP/Oracle); Tier 2 = mid-size; Tier 3 = small scale, lightweight. Selection should be based on scale and complexity

Chapter 4　Comparison of Leading WMS Vendors

The WMS market has matured: Gartner’s 2025 Magic Quadrant evaluated more than 80 vendors, of which 17 were included in the quadrant. SAP has been named a Leader for 12 consecutive years, and Oracle for 10 consecutive years. The characteristics of the leading vendors are summarized below.

Vendor / Product	Type	Strengths	Best Fit
Manhattan Associates (Manhattan Active WM)	Specialist, cloud	Depth of functionality, omnichannel, automation; long-standing top Leader and the leading WMS specialist	Large-scale retail, 3PL, e-commerce, high automation
Blue Yonder (Luminate WMS)	Specialist, cloud	Unified with end-to-end SCM (planning through execution); AI/ML	Retail, manufacturing, 3PL
SAP EWM	ERP-embedded/distributed	Tightly coupled with S/4HANA; direct automation control via MFS; Gartner Leader for 12 consecutive years	SAP-centric manufacturing and logistics operations
Oracle (Fusion Cloud WMS)	ERP-embedded, cloud	Integrated with Oracle’s core systems; cloud-native; Gartner Leader for 10 consecutive years	Companies running Oracle as their core system
Körber (Infios)	Specialist	Broad scale coverage, automation, voice	Manufacturing, 3PL, mid-to-large scale
Infor (WMS/CloudSuite)	Specialist/industry-specific	Industry-specific templates, 3D visualization	Distribution, manufacturing, 3PL
Softeon / Made4net / Tecsys	Specialist	Flexibility, cost, industry specialization	Mid-size, specific industries

💡 Vendor selection tip: If SAP is your core system, EWM offers the strongest integration advantage; if Oracle is your core system, Oracle WMS does. On the other hand, if your primary requirements are a multi-ERP environment, advanced automation, or omnichannel capability, specialist best-of-breed solutions such as Manhattan, Blue Yonder, or Körber are the stronger choice. The trade-off between “ERP affinity” and “depth of WMS functionality” is the central axis of selection.

Chapter 5　Companies Best Suited to WMS Adoption

A WMS is not necessary for every company. For operations that can be run with manual processes, spreadsheets, or an ERP’s standard inventory features, implementing a WMS can be over-investment. On the other hand, companies exhibiting several of the following signals tend to see a high return on investment from WMS adoption.

5-1　Signals That a Company Is a Good Fit for WMS

• High Shipment Volume and SKU Count: A high number of daily shipments and an SKU count in the thousands to tens of thousands, where manual, paper-based processes have hit their limit for inventory accuracy and productivity

• Low Inventory Accuracy: Chronic cycle-count discrepancies, mis-shipments, and stockouts/overstock, where the root cause is not knowing “what is where”

• Large Seasonal or Demand Fluctuations: Staffing cannot keep pace at peak times, requiring staffing plans and work optimization

• Omnichannel/E-Commerce: Inventory is shared across stores, e-commerce, and wholesale channels, requiring same-day/next-day shipping and returns handling

• Traceability Requirements: Lot/serial/expiration-date (FEFO) tracking and recall support are mandatory (food, pharmaceuticals, chemicals, automotive parts)

• Plans to Advance Warehouse Automation: Planning to introduce AS/RS, AMR, GTP, sorters, and the like, which requires a control platform (WCS/MFS)

• 3PL/Multiple Warehouses: Operating multiple sites and multiple clients under standardized processes, requiring usage-based billing and cross-site visibility

• Expansion or Global Rollout: Adding sites or expanding overseas requires standardized operations rather than operations dependent on individual expertise

5-2　Fit by Industry

Industry	Why WMS Is Effective	Especially Important Functions
Retail/E-Commerce	Many SKUs, omnichannel, same-day shipping, high return volume	Wave/multi-order picking, returns, inventory visibility
3PL/Logistics	Multiple clients, usage-based billing, cross-site operations	Billing, multi-client support, KPI visibility
Food and Beverage	Freshness (FEFO), lot tracking, temperature zones	FEFO, lot/expiration-date tracking, temperature management
Pharmaceuticals/Medical Devices	Regulatory requirements, serial tracking, traceability	Serial number management, GxP compliance, audit trails
Manufacturing (Parts/Finished Goods)	Production supply synchronization, inbound/outbound timing, high product variety	Production integration, kanban replenishment, cross-docking
Automotive Parts/Aftermarket	High-mix, low-volume, supply commitments, service parts	Multi-tier inventory, RF automation, supply accuracy

5-3　Rough Guidelines by Scale (Tier)

• Large Scale, Highly Automated (Tier 1): Tens of thousands of order lines or more per day, multiple sites, automation-driven. Manhattan/Blue Yonder/SAP EWM/Oracle

• Mid-Size (Tier 2): One to a few sites, moderate automation. Körber/Infor/mid-tier specialists

• Small Scale (Tier 3): Single warehouse, lightweight needs. Lightweight cloud WMS, or an ERP’s built-in simplified inventory features (e.g., SAP Stock Room Management)

5-4　Cases Where Adoption Should Not Be Rushed

• SKU count and shipment volume are low, and inventory accuracy is being maintained with an ERP’s standard inventory features or simple tools

• Master data (items, bins, locations) is not yet organized, and data cleanup needs to come first

• Business processes are not yet settled, and the standard work to be modeled in the WMS has not been defined

⚠ Prerequisite: A WMS is a tool that accelerates a warehouse that is already well-organized — it is not magic that automates chaos as-is. Organizing location, bin, and item master data, and designing standard work (receiving through shipping) beforehand, are prerequisites for a successful implementation.

💡 Rule of thumb: If inventory accuracy, shipping accuracy, or productivity has hit a limit under manual processes, spreadsheets, or standard ERP functionality, and if SKU count, shipment volume, number of sites, or automation plans are expanding, the ROI of WMS adoption is likely to be high.

Chapter 6　Criteria for Selecting a WMS

Selecting a WMS based on “breadth of functionality” alone tends to lead to failure. It is important to weight and compare candidates against evaluation criteria centered on your own company’s requirements. The following outlines the selection process, key evaluation criteria, tips for requirements definition, and pitfalls to avoid, in a systematic way.

6-1　Selection Process (RFP through PoC)

①　Requirements Definition: Quantify shipment volume, SKU count, sites, automation plans, omnichannel needs, and traceability requirements, and organize them into “must-have” and “want” categories

②　Long List: Narrow candidates based on ERP affinity, scale (Tier), and industry fit

③　RFP/Demos: Request scenario-based demonstrations for key use cases (peak-period picking, returns, automation integration)

④　PoC/Fit Verification: Confirm fit and gaps using your own real data and real business processes (assess the amount of add-ons — i.e., the degree of customization — required)

⑤　TCO Evaluation and Final Selection: Decide based on the 5-year TCO — license, implementation, maintenance, and automation investment — together with scalability and support structure

6-2　Key Evaluation Criteria (Weighted Comparison)

Evaluation Criterion	What to Look For	Matters Most For
Functional Fit	How much can be covered by standard functionality (fewer add-ons is better)	Companies with unusual operations
Scale/Throughput	Daily shipment line volume, SKU count, resilience to peak fluctuations (Tier)	Large scale, high seasonal variation
Automation Support	Integration with AS/RS, AMR, GTP, sorters; depth of WCS/WES/MFS integration	Companies planning automation investment
ERP Affinity	Integration cost and master-data consistency with the existing ERP (SAP/Oracle, etc.)	Single-ERP-oriented organizations
Cloud/Deployment	SaaS scalability, updates, multi-site/multi-language/multi-currency deployment	Global, expanding organizations
Omnichannel	Cross-channel inventory visibility, allocation, and returns across stores/e-commerce/wholesale	Retail, e-commerce
Extensibility/API	Ease of external integration and robot/equipment connectivity; development flexibility	Organizations prioritizing an ecosystem approach
Support/Track Record	Vendor/partner implementation capability, industry track record, roadmap	Organizations prioritizing long-term operation
TCO	Total cost of ownership including implementation, maintenance, upgrades, and automation	Cost-disciplined organizations

6-3　Tips for Requirements Definition

• Size to Peak, Not Average: Judge scale based on whether the system can handle peak-period shipment volume and staffing, not average levels

• Build In an Automation Roadmap: If AS/RS or AMR will be introduced in the future, choose a WMS with deep WCS/MFS integration from the start

• Minimize Customization: Choose a product that can be covered by standard functionality and keep add-ons to a minimum (to avoid upgrade debt)

• State of Master Data and Process Readiness: A WMS is a tool for accelerating an already-organized warehouse; if master data is not ready, prioritize getting it ready first

6-4　Pitfalls to Avoid

⚠ Common Failure Patterns: ① Choosing based on the sheer number of features, resulting in poor adoption on the floor; ② Failing to consider future automation, leading to painful integration later; ③ Excessive customization that makes upgrades impossible; ④ Implementing without organizing master data first, so accuracy never improves; ⑤ Misjudging peak-load resilience. All of these stem from insufficient rigor in requirements definition and PoC work.

💡 The essence of selection is not choosing “the product with the most features,” but choosing the product that best fits your company’s requirements, scale, ERP environment, and automation plans, that can be covered by standard functionality, and whose TCO makes sense. Weighting evaluation criteria and validating with real data in a PoC is the key to a selection you won’t regret.

Chapter 7　Automation and AI Trends

WMS is evolving from “a system that records and directs warehouse work” into “a platform that orchestrates the entire warehouse — people, robots, and equipment — in real time.” The major recent trends are summarized below.

7-1　Warehouse Robotics and GTP

• AMR (Autonomous Mobile Robots): Transport robots that reduce human travel distance; includes shelf-carrying (GTP, Goods-to-Person) and collaborative types

• Piece-Picking Robots: Automated picking that grasps individual items using AI image recognition; adoption is growing in e-commerce and high-SKU-variety environments

• Automated Storage/AutoStore: High-density storage (cube-based grid systems) that achieves both storage efficiency and picking speed

• Multi-Vendor Integration: WMS is evolving into an “orchestration layer” that integrates and controls robots and equipment from multiple vendors (via standardized APIs/robot integration platforms)

7-2　Convergence of WMS × WES × WCS (Layer Consolidation)

Traditionally, WMS (inventory/task management), WES (execution optimization), and WCS (equipment control) were separate layers. In recent years, these layers have been converging toward a single platform that controls inventory, work, and equipment as one.

Layer	Role	Direction of Convergence
WMS	Inventory and task management	Oversees the whole from the top layer
WES	Execution optimization and wave/flow control	Trending toward absorption into WMS
WCS/MFS	Direct control of automated equipment	Controlled directly by the WMS (e.g., MFS in SAP EWM)

• Effect: Simplified architecture through fewer layers, and real-time, unified optimization of inventory, work, and equipment

7-3　Use of AI/Machine Learning

• Demand-Driven Work Planning: Optimizing staffing and wave planning based on shipment forecasts

• Slotting Optimization: Learning shipment patterns to continuously redesign shelf placement for the shortest travel routes

• Picking Optimization: AI dynamically assigns tasks based on travel routes, congestion, and priority

• Anomaly Detection and Forecasting: Early detection of signs of delays, stockouts, or equipment trouble, and advance countermeasures based on peak-period forecasting

• Generative AI Assistants: Natural-language support for work instructions, inquiries, and report creation

7-4　Cloud Adoption and “Versionless” Operation

• SaaS/Cloud-Native: Excels in deployment speed, scalability, and multi-site rollout; increasingly the mainstream in recent years (Manhattan Active, Blue Yonder Luminate, etc.)

• Versionless: Continuous updates provide constant access to the latest features and eliminate the burden of major upgrades

• Microservices/APIs: Makes loosely coupled integration with external systems, robots, and equipment easier

7-5　Sustainability and Visibility

• Energy Efficiency/CO2: Visualizing energy reductions from shorter travel routes, optimized load planning, and equipment control

• Supply Chain Visibility: Connecting WMS data to control towers and digital twins for end-to-end visibility of inventory and shipments

💡 The core of these trends is that WMS is becoming an orchestration platform that ties together people, robots, and equipment. When selecting a WMS, evaluation should account not only for current functionality but also for “future headroom” — robotics integration, AI optimization, and ongoing cloud evolution.

Chapter 8　AI in the WMS Domain — Leading Case Studies

This chapter compiles leading case studies of AI adoption in the WMS domain, drawn from public information — official vendor case studies, announcements from adopting companies, product documentation, and academic papers. At present, the areas with the highest maturity and the clearest visible ROI are “picking optimization” and “orchestration of WMS-WCS-robotics.” Demand forecasting and inventory optimization have fewer documented cases but deliver large impact. Natural language interfaces, anomaly detection, predictive maintenance, and reinforcement learning remain at the “entry point to production use” stage.

8-1　Picking and Robotics (Most Mature, Most Documented Cases)

Company/Technology	Key Results
Semir (Manhattan WMS)	Picking efficiency +60%, fulfillment labor cost −40%
Eroski (AutoStore)	Picking efficiency +400% (5x), required space −25%
Bergfreunde (AutoStore)	Picks per hour up from 45 to 175, shipping lead time under 3 hours, ROI of roughly 2 years
Toranoana (AutoStore)	Picking efficiency +70% (roughly 1.6x)
TEPCO Logistics (Mujin RCP)	90% of case-handling volume automated; picking staff reduced from 4 to 1
Hitachi LogiRiSM	Sorting productivity roughly 4x the previous level
Suning / Walmart Shenzhen / Sandman	Processing capacity 3–7x / 3.5x / +500% respectively

💡 AMR/AS-RS systems tend to deliver simultaneous gains in “reduced walking, high-density storage, and 24-hour operation,” making ROI easy to demonstrate through floor-level KPIs (picks per hour, walking distance). Improvement rates tend to cluster in the range of roughly 1.6x to 5x, making this the leading entry point for a PoC.

8-2　Demand Forecasting and Inventory Optimization (Fewer Cases, but Large Impact)

• Dole Food & Beverage (Blue Yonder): Reduced inventory by 40% while improving fill rates in key markets to above 95%

• Summit (Hitachi’s AI-driven demand-forecasting automatic ordering system): Applied across all 123 stores, operating with a 95% suggestion-adoption rate while improving stockouts and reducing inventory

• McKinsey’s Analysis: AI-driven improvements in demand forecasting and inventory optimization can reduce inventory levels by 20–30%

8-3　Image Recognition and Inspection

• iSCAN / NEC: Inspection using image recognition. The scope of the task is easy to constrain, and once cameras, training data, and lighting/imaging conditions are in place, results can be confirmed quickly — making it well suited as an entry point for a PoC

8-4　Orchestration (Integration of WMS-WES-WCS-Robotics)

• Blue Yonder Robotics Hub: Standardizes robot connectivity. New-vendor connection time reduced by 50%; new-site rollout cost for existing vendors reduced by 60%. Integrations built once can be reused across additional sites

• Dematic: A unified WMS/WES/WCS software layer delivering predictive maintenance and throughput optimization

• Hitachi LogiRiSM: Dynamically recalculates overall priority via WCS, providing real-time visibility, prediction, and control across all material handling equipment

8-5　Natural Language and AI Agents (Entry Point to Production Use)

• Oracle WMS: Task Management Assistant (identifying and prioritizing at-risk orders and assigning tasks) and Inventory Expiry Assistant (monitoring near-expiration inventory), both operated via natural language

• SAP Joule: Beginning to connect natural-language interaction to WMS operations such as goods receipt, goods issue, task handling, and physical inventory

⚠ Key Consideration for Natural Language Systems: What matters more than “what can be asked” is “how much can be executed automatically.” Without access controls, approval workflows, audit logs, and rollback design for mis-operations, floor-level adoption will not progress. It is safest to start by using these tools mainly for inquiries, summarization, and search, and to require approval for any execution-capable functions.

8-6　Predictive Maintenance, Reinforcement Learning, and Digital Twins (Long-Term Themes)

• Reinforcement Learning on SAP LE: A reported 95% task-optimization accuracy and a 60% reduction in processing time using 300,000 synthetic transaction records (academic research)

• KION / NVIDIA / Accenture: Integrating digital twins to train warehouse robots to adapt to changes in demand, inventory, and layout

💡 For reinforcement learning and predictive maintenance, since live logistics operations cannot be halted, inserting a digital twin/simulation step before production deployment is, in practice, a prerequisite.

8-7　Implementation Roadmap for Japanese Companies

• Short Term: Establish event-level granularity, inventory location accuracy, work-performance logs, and exception reason codes within the WMS to set a baseline for floor-level KPIs. Focus PoCs on “image-based inspection,” “demand-forecast-driven automatic ordering,” and “picking-support AMR/AS-RS”

• Medium Term: Standardize WMS-WCS-AMR/AS-RS connectivity. Rather than building custom integrations for each individual robot, standardize locations, transport tasks, exception events, and priority rules via APIs

• Long Term: Expand in stages from AI agents (accelerating exception handling via natural language) → equipment monitoring and predictive maintenance → digital-twin training → dynamic scheduling via reinforcement learning

8-8　The Biggest Risk — Insufficient Integration

A common thread among successful cases is that AI was not introduced in isolation — it was designed together with the WMS’s business process design, master data, exception handling, and robot control.

⚠ Integration Is the Biggest Bottleneck: In Kardex’s 2025 survey, 75% of respondents considered integration a prerequisite for realizing automation benefits, yet only 23% said they had achieved full integration. Introducing AMR alone, image AI alone, or a generative AI chatbot alone will hit a local optimum if the WMS’s priority logic, inventory location design, and WCS exception handling remain outdated.

💡 In practice, what matters most is not “which AI to introduce” but deciding in advance “which KPI, using which data, achieved through which operational change.” For inventory reduction, the Dole/Summit pattern; for reduced walking distance and processing capacity, the Eroski/Bergfreunde/Toranoana/Mujin pattern; for inspection quality, the iSCAN/NEC pattern; for reusability of overall control, the Hitachi/Blue Yonder pattern; for the floor-level UI, the Oracle/SAP pattern — organizing the choice by objective in this way is effective.

Chapter 9　Conclusion ― A Selection Guide

WMS is a core system that determines a warehouse’s productivity, accuracy, and throughput, and selection comes down to a balance between “ERP affinity” and “depth of functionality and automation support.” For SAP-centric manufacturers, EWM is compelling (with automation integration through MFS as its strength); where the primary requirements are multiple ERPs, advanced automation, or omnichannel capability, specialist best-of-breed solutions (Manhattan, Blue Yonder, Körber) are the stronger candidates.

💡 Final Message: There is no single correct answer for WMS selection. Translate your company’s scale, automation level, ERP environment, and omnichannel requirements into a requirements matrix, and compare candidates based on Tier fit and TCO. In recent years, cloud adoption and robotics integration have advanced, and the competitive axis has shifted from “the functionality of the WMS alone” to “integrated orchestration capability spanning automation and execution systems.”

(This report was prepared based on general WMS methodology, the 2025 Gartner Magic Quadrant for WMS (in which SAP has been a Leader for 12 consecutive years and Oracle for 10 consecutive years, among other findings), and publicly available vendor information. Vendor positioning may vary depending on evaluation criteria and point in time.)