WMS and ERP: Task Allocation, Interaction, and Boundaries

A Warehouse Management System (WMS) and an Enterprise Resource Planning System (ERP) perform different but closely related tasks within the corporate IT landscape. While the ERP system typically supports the overarching planning and execution of company-wide business processes, the WMS focuses on the operational management, control, and optimization of warehouse and intralogistics processes.

In practice, however, the distinction between the two systems is not always clear-cut. Modern ERP systems offer extensive functions for warehousing and logistics, while WMS solutions are increasingly taking on tasks that go beyond mere storage location and inventory management. This results in overlaps, for example, in inventory management, master data, order management, or replenishment planning.

A clear division of responsibilities between ERP and WMS is therefore less a matter of the names of individual software functions than of system architecture and functional responsibility. The decisive factors are which system serves as the lead system for a given process and what information is exchanged between the systems.

What is an ERP system?

ERP stands for Enterprise Resource Planning. ERP systems support the planning, control, and execution of company-wide business processes. These may include, among others, purchasing, sales, finance and accounting, human resources, production, procurement, and logistics. The goal is to connect different areas of the company through shared data and integrated processes.

In a logistics context, the ERP system typically provides an overarching view of goods, orders, and resources. For example, it tracks sales orders, purchase orders, production orders, product master data, and commercially relevant inventory levels. This information is used to generate specifications for downstream logistics processes.

The ERP system thus primarily maps the business and administrative levels. It answers questions such as:

• What customer orders are pending?
• Which goods need to be procured or produced?
• What quantities are required?
• What delivery dates must be met?
• Which orders must be fulfilled?
• Which goods movements must be recorded for business purposes?

The specific implementation depends on the respective ERP system and the company. Not every ERP system offers the same range of functions in the area of warehousing and logistics.

What is a WMS?

WMS stands for Warehouse Management System. In German-speaking countries, the term “Lagerverwaltungssystem” (LVS) is also used. A WMS is used to manage, monitor, and optimize processes within a warehouse or an in-house warehousing and transportation system.

The VDI Guideline 3601 describes warehouse management as the control, monitoring, and optimization of warehouse and distribution systems. Its tasks include, among other things, inventory and storage location management, internal transport processes, and methods for monitoring and optimizing system statuses.

The focus of a WMS is therefore on the operational level. The system must not only know that—for example—100 units of an item are needed, but also where they are located, which inventory items can be used for an order, and how the goods should be moved within the warehouse.

Typical questions posed by the WMS therefore include:

• In which storage location is a specific item located?
• Which goods should be picked for an order?
• In what order should orders be processed?
• Which storage location is suitable for putaway?
• When must replenishment be provided?
• Which employee or piece of equipment is responsible for a transport?
• Which conveyor system or automated warehouse should be activated?
• Which inventory items are blocked, reserved, batch-pure, or otherwise restricted?

The WMS thus provides a significantly higher level of granularity for warehouse processes than general inventory management.

Basic Principle of Task Allocation

A commonly used simplification is:

ERP = What needs to happen in the company?

WMS = How is the corresponding warehouse process carried out operationally?

This representation is helpful as a basic model but should not be understood as a rigid technical rule. In real system landscapes, responsibilities may be distributed differently.

For example, a sales order can be created in the ERP system. The ERP system transmits the relevant order data to the WMS. The WMS breaks the order down into operational warehouse tasks, identifies suitable inventory and storage locations, plans order picking, and controls the necessary internal transport operations. Once the processes are complete, the WMS reports the relevant results back to the ERP system.

In simplified terms, this results in the following flow of information:

ERP → WMS: orders, item information, order and delivery information, relevant master data, and other specifications

WMS → ERP: confirmed quantities, inventory movements, status information, shipping and inventory information, as well as other process feedback

The WMS is not necessarily just an “executing system.” Modern WMS systems have extensive optimization and control functions and can, for example, independently optimize picking strategies, replenishment processes, storage location allocation, and internal transport.

The specific functions vary depending on the vendor and system configuration. Typically, the following tasks fall within the scope of the ERP system:

Order Management

The ERP system manages customer orders, delivery orders, purchase orders, and, where applicable, production orders. It thus maps out the overarching business context.

Purchasing and Procurement

Ordering processes with suppliers, order quantities, prices, delivery dates, and commercial information are generally managed in the ERP system.

Production Planning

In companies with in-house manufacturing, the ERP system often handles the planning and management of production orders as well as overarching material requirements planning.

Commercial Inventory Management

The ERP system requires inventory information for planning, sales, procurement, valuation, and other business processes. A distinction must be made between inventory relevant for commercial or planning purposes and physical, storage-location-based inventory management.

Master Data

Item, customer, supplier, and order data are often maintained centrally in the ERP system. However, for warehouse operations, the WMS requires additional logistical information, such as dimensions, weights, storage conditions, packaging units, or storage strategies.

The WMS handles the operational mapping of warehouse processes. These include, in particular:

Goods Receiving

The WMS supports the receipt, identification, inspection, and putaway of incoming goods. Depending on the process, for example, shipments can be scanned, quantities verified, quality checks initiated, and appropriate storage locations determined.

Storage Location and Inventory Management

A key feature of a WMS is inventory management at the storage location level. For example, the system can distinguish which item is located in which warehouse, zone, aisle, bin, container, or storage slot.

This provides a much more detailed view of the physical warehouse than inventory management based solely on quantity.

Putaway and Stock Transfer

The WMS determines or supports the operational execution of putaways and stock transfers. In doing so, factors such as storage strategies, storage location types, dimensions, weights, item characteristics, turnover rates, or restricted stock levels can be taken into account.

Picking

Picking is one of the core functions of a WMS. The system generates and prioritizes operational orders and can support various strategies such as single-item, multi-item, or zone picking.

Replenishment

If inventory in a picking area falls below a defined threshold, the WMS can generate corresponding replenishment orders. For example, goods are moved from a reserve area to the picking station.

Packing and Shipping

The WMS can support packing processes, shipping preparation, packaging material allocation, labeling, and other processes up to the handoff of the goods to the carrier. Which tasks are actually handled by the WMS depends on the system landscape and the integrated shipping and transportation solutions.

Material Flow Control

In automated warehouses, the WMS must communicate with conveyor systems, automated storage systems, automated guided vehicles (AGVs), or other technical equipment. This communication often takes place via an additional system layer, such as a material flow computer (MFR or MFC).

The WMS decides, for example, what is to be transported. A subordinate material flow system can then ensure that the transport is technically executed. TUP also describes this separation as a component of a multi-level intralogistics system architecture.

In a typical system landscape, ERP and WMS are not competing systems. They form different levels of a shared information and process network.

An example process begins with a sales order:

1. The sales order is entered into the ERP system.
2. The ERP system checks, for example, availability and delivery terms.
3. The order relevant to the warehouse is transferred to the WMS.
4. The WMS checks the actual physical inventory levels and storage locations.
5. The WMS generates operational warehouse tasks.
6. Employees or automated systems execute the tasks.
7. The WMS documents the actual goods movements.
8. Relevant feedback is transmitted to the ERP.
9. The ERP updates the higher-level business process and can, for example, trigger delivery, invoicing, or other follow-up processes.

This integration need not be limited to sales orders. Purchase orders, production orders, returns, inventory counts, master data, and inventory information can also be exchanged between the systems.

A powerful interface is particularly important when the WMS is connected to other systems such as transportation management systems, automation technology, EDI solutions, or shipping software. VDI 3601 explicitly describes the integration of the WMS into higher- and lower-level IT systems.

Inventory Management: One of the Most Common Points of Distinction

A question that arises particularly often is whether inventory is managed in the ERP or in the WMS.

The answer is: Both systems may require inventory information, but they perform different tasks.

The WMS manages the operational, physical inventory. For example, it must know that 50 units of an item are located at storage location A-01-02 and another 100 units at storage location B-03-01. In addition, information about batches, serial numbers, blocked inventory, reservations, or warehouse statuses may be relevant.

The ERP system, on the other hand, requires a higher-level view of inventory. For planning, sales, purchasing, production, or business processes, it must know, for example, what quantity is available, reserved, or already allocated to an order.

This allows the same physical inventory to be viewed from different perspectives.

The challenge lies in establishing clear rules for data ownership. Otherwise, discrepancies may arise if the ERP and WMS independently modify the same data.

Master Data: Shared Database, Different Requirements

Overlaps also frequently occur with master data.

For example, the ERP system may manage the item, its description, item number, sales data, and commercial attributes. The WMS additionally requires logistical attributes such as:

• Dimensions and weight
• Packaging units
• Loading and handling aids
• Storage conditions
• Hazardous material characteristics
• Stackability or storability
• Picking characteristics
• Storage zones
• Replenishment parameters

This often results in a two-tiered model: The ERP system provides a basic item master, while the WMS supplements it with warehouse-relevant information.

The key factor here is defining clear data ownership. Not every piece of information necessarily needs to be maintained in both systems.

Order Management: Where Does ERP End, and Where Does WMS Begin?

Orders are also a typical area of overlap.

For example, an ERP system can manage a sales order with multiple line items. For the WMS, however, what matters is how this order is executed in the warehouse.

A single sales order can give rise to multiple operational tasks in the WMS. For example, the line items may originate from different warehouse zones. The WMS can generate various picking orders, replenishment orders, and internal transfers from this.

The ERP system thus handles the business order, while the WMS organizes its operational execution in the warehouse.

A similar distinction can be observed in procurement and production processes. The ERP system can trigger a goods receipt or a material requirement; the WMS then organizes the physical processing in the warehouse.

The greatest difficulties usually arise not from the fundamental differences between ERP and WMS, but from overlaps.

Duplicate Data Maintenance

If the same data is maintained independently in both systems, there is a risk of conflicting information.

A classic example is item master data maintenance. If the weight of an item changes in the ERP, it must be clarified when and how this change takes effect in the WMS.

Different Definitions of Inventory

“Inventory” can have different meanings depending on the process. For example, physically available inventory may be blocked, reserved, or already assigned to an order.

If ERP and WMS use different rules for determining the available quantity, apparent inventory discrepancies arise, even though both systems are functioning correctly from their respective perspectives.

Overlapping Warehouse Functions in ERP

Many ERP systems offer integrated warehouse functions. For simple warehouse structures, their range of functions may be sufficient. However, as warehouse complexity increases, requirements may arise that make a specialized WMS solution a sensible choice.

These include, for example, detailed storage location management, complex picking strategies, highly automated material flows, comprehensive resource control, or the optimization of large volumes of parallel warehouse tasks.

The threshold for this should not be determined solely by the number of storage locations or items. The decisive factors are process complexity, the degree of automation, throughput, and the required granularity of control.

Unclear Process Responsibility

Another problem arises when it is not defined which system is responsible for a particular process step.

For example, both the ERP and the WMS can calculate replenishment quantities. If both calculations are used in parallel, this can lead to conflicting orders.

Therefore, the following should be defined for each relevant process:

• Which system is the primary one?
• What data is generated there?
• What data is transferred?
• Which system is authorized to make changes?
• When is a confirmation generated?
• What happens in the event of errors or discrepancies?

In an integrated system landscape, a clear source should be defined for every piece of essential information. The term Single Source of Truth is often used for this purpose.

This does not necessarily mean that information may only technically exist in one system. Rather, it should be clearly defined which system has business authority over the respective information.

For example, the ERP system may be the primary system for the sales order, while the WMS is the primary system for the operational warehouse order.

Such a separation reduces conflicting data sets and simplifies the definition of interfaces.

As automation increases, the distinction between system levels becomes particularly relevant.

An automated warehouse can consist of several levels:

ERP → WMS → Material Flow Control → System Control Level → Conveyor and Warehouse Technology

The ERP provides the higher-level business and logistics orders. The WMS handles warehouse logistics planning and control. A material flow computer or Material Flow Control System can distribute the specific transport orders to the technical infrastructure.

VDI 3601 classifies the WMS accordingly into a higher-level administrative layer and subordinate system layers.

This separation is particularly important because the systems have different requirements. While an ERP, for example, processes business transactions and commercial processes, a WMS must be able to respond to operational events in the warehouse. In automated facilities, there are additional high demands on response time, data quality, and availability.

Despite the division of tasks described above, there is no universal rule stating that a specific function must always reside exclusively in the ERP or exclusively in the WMS.

System boundaries depend, among other things, on the following factors:

Order Management: Where Does ERP End, and Where Does WMS Begin?

• Company Structure and Complexity
• Number and structure of warehouse locations
• Warehouse and picking processes
• Degree of automation
• Number of items and orders
• Traceability requirements
• Production and scheduling processes
• ERP system in use
• Scope of WMS functionality
• Existing automation systems
• Interface architecture

A company with a small, manageable warehouse may, under certain circumstances, be able to map its warehouse processes largely using the functions of an ERP system. In a highly automated distribution center with numerous storage zones, multiple picking methods, and complex conveyor systems, however, simple inventory management is often insufficient.

The question “ERP or WMS?” is therefore often misguided. In complex system landscapes, the question is rather which tasks are best mapped at which system level.

Effective collaboration between ERP and WMS is based on a defined flow of information. Interfaces must not only enable technical data transfers but also accurately map business processes.

Factors to consider include, for example:

• Master data transfer
• Order transfer
• Inventory reports
• Status updates
• Goods Receipts
• Goods Issues
• Inventory Discrepancies
• Returns
• Production Supply
• Shipping Information
• Error and Exception Handling

Exception handling plays a particularly important role here. Under normal circumstances, for example, an order can be fully picked and shipped. In practice, however, shortages, damaged goods, blocked inventory, technical malfunctions, or quantity discrepancies may occur. The system architecture must therefore also define how such situations are handled between the ERP and the WMS.

ERP and WMS fulfill different functions but complement each other within an integrated IT landscape. The ERP system typically handles high-level business and logistics planning as well as business processes. The WMS focuses on the operational management and optimization of warehouse and internal transport processes.

The most important distinction lies not solely in individual software functions, but in the respective process and data responsibilities. For example, the ERP can manage the sales order, while the WMS plans and controls the resulting warehouse tasks. The ERP requires inventory information for planning and business processes, while the WMS manages the physical inventory at the storage location level.

In practice, overlaps often arise—particularly with regard to inventory, master data, orders, and replenishment. Successful system integration therefore requires clear responsibilities, defined data ownership, and reliable interfaces.

VDI 3601 provides an established framework for this purpose. It describes the tasks and functional areas of a WMS, its integration into the system landscape, and its integration with higher- and lower-level systems.

Ultimately, a WMS should not be viewed as a replacement for an ERP, nor should an ERP automatically be considered a complete replacement for a specialized WMS. Both systems fulfill different tasks within a shared information and process network. A well-thought-out system architecture therefore defines not only which functions are available, but above all, which system assumes responsibility for data, decisions, and processes at what point, because: it is not about rigid functional boundaries, but about responsibilities and system leadership.

For a more in-depth look at the topics mentioned above:

What is a Warehouse Management System / WMS?

VDI 3601 – Warehouse Management Systems