WMS Functions

A Warehouse Management System (WMS) is far more than a digital inventory list. It controls every physical step in the warehouse – from receiving a delivery to booking the shipment and restocking a return. Understanding individual WMS functions helps you define requirements precisely, compare systems and optimize processes in a targeted way.

This guide explains the most important functional modules of a modern WMS, shows how they work together in day-to-day fulfillment, and helps you prioritize: what is mandatory, what is nice-to-have – and at what volume does which feature pay off?

Why WMS functions are more than inventory counting

Many retailers start with inventory management in their shop system. That is sufficient for small product ranges but does not replace operational warehouse control. A WMS knows not only how many units of a SKU are available, but also where they are located, in which batch, with which expiration date and in which status (available, reserved, blocked).

The central task: every warehouse movement is recorded, validated and reported back to connected systems. This creates a seamless data flow between digital orders and physical execution – the foundation for reliable availability displays, low pick error rates and measurable KPIs.

WMS function chain in day-to-day operations

Eight modules in the operational workflow – with a return channel from returns and inventory back to inventory management:

1
Master data & warehouse structure
2
Goods receipt
3
Put-away
4
Inventory management
5
Order reservation
6
Picking
7
Packing & shipping
8
Returns & inventory – return channel to inventory management

The ten core modules in detail

001. Master data and warehouse structure

Before operational processes run, the WMS sets up the physical and logical structure of the warehouse:

  1. Warehouse zones – goods receipt, picking, shipping, quarantine, cold storage area
  2. Storage locations – unique addresses (aisle-bay-level-bin)
  3. SKU master data – dimensions, weight, EAN, packing instructions, ABC class
  4. Rules – put-away logic, pick priorities, FIFO/LIFO requirements

Without clean master data, all other WMS functions are ineffective. Storage locations must be physically labeled and identically maintained in the system – otherwise incorrect bookings and unnecessary walking distances occur.

Important: Master data is not a one-time setup. With every new product, every layout change and every seasonal restructuring, the WMS and physical warehouse must remain synchronized.

002. Goods receipt (inbound)

The goods receipt function controls the acceptance of incoming deliveries:

  • ASN import – pre-import advance shipping notices from suppliers and detect discrepancies
  • Scan-supported booking – capture each line item by barcode instead of manual entry
  • Quality inspection – blocking for damage or quantity discrepancies
  • Quarantine workflow – blocked inventory is not released for orders

The WMS reconciles delivered quantities with purchase orders and automatically generates complaint notices for discrepancies. For more on the operational workflow, see Put-away and booking.

003. Put-away

After goods receipt, put-away distributes goods to optimal storage locations. The WMS applies rules:

  1. Place fast movers (A items) close to the shipping area
  2. Heavy pallets on lower rack levels
  3. Batches with earliest expiration date first in accessible zones
  4. Bundle items of the same category for efficient picking

Put-away reduces walking distances during later picking and uses warehouse capacity efficiently – especially relevant with limited space in small warehouses.

004. Inventory management and reservation

Inventory management at storage location level is the heart of every WMS:

Inventory status
Meaning
Available for sale
Typical WMS action
Available
Free on storage location, not reserved
Yes
Shop sync, order reservation
Reserved
Bound to open order
No
Pick list, picking
Blocked
Quarantine, B-stock, quality defect
No
Manual release after inspection
In transit
Between storage locations or in pick
No
Movement booking, scan confirmation

When an order is received, the WMS automatically reserves inventory – only when availability is insufficient does a backorder or partial shipment occur. This prevents overselling across multiple sales channels.

005. Picking

Picking is the most resource-intensive process. WMS functions here:

Pick strategies:

  1. Single-order picking – one order, one route, ideal for beginners
  2. Batch picking – multiple orders in parallel, sorting at packing station
  3. Wave picking – time-controlled waves by cut-off or carrier pickup
  4. Zone picking – employees stay in their zone, handoff to next zone

The WMS creates pick lists, optimizes walking routes and requires scan confirmation at each storage location. Discrepancies (wrong item, empty location) are reported immediately and can trigger an automatic inventory spot check.

Criterion
Single-order
Batch
Wave
Zone
Effort per order
Medium (one route per order)
Lower per order
Low at high volume
Low per zone
Error susceptibility
Low
Medium (sorting required)
Medium
Medium (handoff between zones)
Throughput
Limited
High
Very high
Very high
Suitability from volume
From day 1
From 100+ orders/day
From 500+ orders/day
From 500+ orders/day

006. Packing and shipping preparation

After picking, the WMS routes to the packing station:

  • Packing instructions per SKU – box size, filler material, inserts
  • Weight check – plausibility check against master data
  • Shipping label creation – carrier API or connection to shipping software
  • Shipment booking – tracking number, carrier, ship date

Every scan at the packing station confirms a process step. If an item is missing or the weight does not match, the WMS blocks shipment – before the package leaves the warehouse.

007. Returns management

Returns are a full WMS process, not an add-on:

  1. Return registration and label assignment
  2. Return goods receipt with scan and condition check
  3. Decision logic: restocking, B-stock, disposal
  4. Inventory reversal and shop sync

Without a returns workflow, shadow inventory occurs – physically present goods that are invisible in the system.

008. Inventory counting and stock correction

Inventory functions differ by maturity level:

  • Perpetual inventory – every movement books stock; discrepancy only on spot check
  • Cycle countingABC analysis determines counting frequency (A more often than C)
  • Full physical inventory – annual requirement or during system change
  • Ad-hoc correction – after pick error or empty location report
Inventory without scan discipline in day-to-day operations is worthless. Those who do not consistently scan during pick and put-away fight systematic discrepancies during inventory counting.

009. Reporting and KPI dashboards

A WMS delivers operational metrics in real time:

KPI
WMS data source
Typical target value
Action on deviation
Pick accuracy
Scan confirmations vs. target positions
Over 99.5%
Training, pick verification, review layout
Inventory accuracy
System vs. spot count
Over 99%
Scan requirement, tighten cycle counting
Throughput time
Order receipt to shipment booking
Under 4 hours (standard)
Adjust wave picking, staffing, cut-off
Pick performance
Lines per hour per employee
Individual, increasing
Optimize route, introduce batch picking
OTIF
Shipped complete and on time
Over 98%
Check reservation, inventory, carrier

WMS function benefits by module

Average error reduction and efficiency gains with consistent use:

Scan picking

Approx. 70% fewer pick errors

Reservation

Approx. 90% fewer oversells

Put-away

Approx. 25% shorter walking distances

Inventory

Approx. 50% less counting effort

010. Integration and interfaces

WMS functions only deliver their value through connectivity:

Input (orders and master data):

  • Shop systems and marketplace connectors
  • OMS for multi-channel routing
  • ERP for product master data and purchasing
  • EDI/ASN from supplier

Output (execution and feedback):

  • Barcode scanners and mobile devices
  • Label printers and carrier APIs
  • Inventory feedback to shop and marketplaces

WMS interfaces – data flow

Shop / OMS

Order intake and master data

WMS

Central hub – control of all warehouse processes

Scanner / hardware

Operational execution in the warehouse

Packing station / label

Packing, weight check, shipping label

Carrier

Tracking, shipment booking

Inventory feedback

Sync back to shop and OMS

Bidirectional data flows: WMS as hub between sales, operational execution and inventory feedback.

Mandatory vs. nice-to-have: functions by maturity level

Not every warehouse needs all modules from day one. This prioritization helps with system selection:

Function
From day 1 (mandatory)
From 100+ orders/day
From 500+ orders/day
Storage location inventory
Yes
Yes
Yes
Scan picking
Yes
Yes
Yes
Order reservation
Yes
Yes
Yes
Put-away rules
Basic
Advanced
Automated
Batch/wave picking
No
Recommended
Mandatory
Batches/expiration date
As needed
As needed
Standard
Returns workflow
Basic
Full
Full
Multi-channel sync
Single channel ok
Yes
Real-time
Tip: Start with single-order picking and clean scan discipline. Introduce batch and wave picking only when the base process is stable below 0.5 percent pick errors.

Practical example: function chain for a standard order

A typical e-commerce order passes through all WMS modules in minutes:

  1. Order intake – shop transmits order to WMS via API
  2. Reservation – WMS checks inventory at storage location level, reserves line items
  3. Pick list – system creates optimized route, employee receives order on scanner
  4. Picking – scan at each storage location confirms removal
  5. Packing – packing instruction, weight check, label print
  6. Shipment booking – tracking back to shop, inventory reduced
  7. Customer notification – shop triggers shipping email

Standard order in the WMS – timeline

0 min
Order – order intake
1 min
Reservation – inventory check and binding
15–45 min
Pick – picking with scan confirmation
5 min
Pack – packing instruction and weight check
1 min
Label – shipping label creation
Immediately
Booking – shipment booking in WMS
1–5 min
Sync – inventory feedback to shop

Checklist: WMS functions for vendor selection

Use this list in demos and quote comparisons:

  • Inventory management at storage location level (not just SKU total)
  • Automatic reservation on order intake
  • Scan requirement for goods receipt, pick and pack
  • Configurable put-away rules
  • At least single-order and batch picking
  • Shipping label integration for your carriers
  • Returns workflow with restocking
  • Cycle counting by ABC classification
  • Real-time inventory feedback to shop/marketplaces
  • KPI dashboard (pick accuracy, throughput time, OTIF)
  • API or ready-made connectors for your shop system
  • Roles and permissions concept for warehouse staff

Common mistakes when using WMS functions

  1. Activating features, ignoring processes – wave picking without stable single-order picking
  2. Neglecting master data – packing instructions and storage locations incomplete
  3. Bypassing scans – team enters manually, inventory shows chaos
  4. No reservation – oversells despite WMS use
  5. Returns outside the WMS – shadow inventory and incorrect availability
  6. Reporting not used – KPIs exist but nobody responds to deviations

Frequently asked questions (FAQ)

  • Is shop inventory without storage locations sufficient? – No, insufficient from medium volume onward.
  • Do I need wave picking immediately? – No, only after process stabilization.
  • What is the most important scan point? – Pick confirmation at storage location.
  • How often inventory counting? – Perpetual booking plus cyclical spot checks.
  • Which function saves the most? – Reservation plus scan picking.

Conclusion: use functions strategically instead of activating everything

WMS functions form an interconnected system – from goods receipt through put-away and reservation to pick, pack, shipping and returns. Thinking module by module allows gradual introduction: first master data and scan picking, then put-away rules and batch picking, finally advanced reporting and multi-channel sync.

What matters is not the number of activated features, but consistent use in day-to-day operations. A lean WMS with end-to-end scan discipline beats an enterprise system whose functions the team bypasses. For the overall system overview and introduction, see WMS Warehouse Management System.

Related topics

Last updated: July 7, 2026