Warehouse Management System: the complete guide

A warehouse management system manages four things at the same time: where something is, how much of it there is, who needs to act on it, and in what order. Every action is confirmed with a scan, so recorded stock and physical stock cannot drift apart between counts.

That is the whole idea. Everything below is a consequence of it.

• Inbound and receiving. Arrivals are checked against the purchase order, discrepancies are captured at the dock instead of discovered later, and batch or expiry data is registered at the moment of receipt.
• Directed putaway. The system decides the storage location based on velocity, dimensions and storage conditions — not the operator's habit.
• Replenishment. Pick faces are topped up before they run empty, driven by thresholds rather than by someone noticing a gap.
• Picking. Optimised walking routes, batch and zone picking, scan validation on every line.
• Packing and shipping. Carrier selection, labels and shipment data without rekeying into a carrier portal.
• Counting. Cycle counts per location, continuously, instead of one annual shutdown.
• Returns. A registered assessment step, so returned goods re-enter available stock deliberately rather than sitting in a tray.

WMS, OMS and ERP — who owns what

These three are constantly confused, and the confusion is expensive because it leads to buying the wrong layer.

• ERP owns the financial and administrative truth: purchasing, sales, invoicing, article master data, stock value.
• OMS (order management system) owns the commercial promise across channels: which order goes to which location, what is available versus committed, what the customer was promised and when.
• WMS owns the physical execution: the location, the sequence, the scan, the pick.

An ERP knows you hold 240 units. It does not know that 180 sit on a pallet in racking, 40 in the pick face and 20 in a returns bin awaiting assessment. The moment an operator has to search, or several channels draw on the same stock, that gap starts costing real money.

There is no magic order volume that triggers the need for a WMS. Complexity weighs far more than throughput: number of SKUs, number of channels, batch or serial requirements, seasonal peaks. Recognise three or more of these and the delay is almost certainly costing more than the system would.

• New staff need weeks before they can pick unsupervised, because the knowledge lives in people rather than in the process.
• You consistently find variances at the annual stock count, and nobody can reconstruct where they came from.
• Mispicks and returns are managed with an extra checking step instead of better direction.
• You sell through several channels and hold safety buffers purely to avoid overselling — cash sitting in racking.
• Peak season is absorbed with overtime and temporary staff rather than with capacity.
• One person knows where everything is, and their holiday is a risk to the operation.
• Someone rekeys shipment data into a carrier portal every day.

Where you sit changes the answer

BizBloqs frames this by company size, because the pain is genuinely different at each stage rather than being a bigger version of the same thing.

• SME — one location, growing SKU count, the first channel beyond your own webshop. The priority is getting direction and scan validation in place at all.
• SME+ — multiple channels, more complex flows, and specific requirements such as batch tracking or value-added services. Modules are added on top of the base platform against a monthly and implementation fee.
• Enterprise — multi-site, multi-entity, deeper integration and governance requirements. Includes the SME+ modules; 3PL billing and MHE integration remain separately priced add-ons.

Read the detail for your stage: SME, SME+ or Enterprise.

Vendor feature lists look remarkably alike, which is why comparing them line by line rarely separates the candidates. A small set of capabilities decides whether the system works on the floor.

1. Scan validation on every action. If an action can be confirmed without a scan, it will be, and your accuracy has a hole in it.
2. Directed picking with route optimisation. The system decides the sequence. Walking distance is the largest single cost in most pick operations.
3. Rule-driven allocation. Which stock is assigned to which order, per channel, per priority — without a human arbitrating.
4. Batch, serial and expiry tracking where your sector requires it, enforced rather than optional.
5. Pre-built connectors to your ERP, your channels and your carriers. Every connector you have to build is a project with a maintenance tail.
6. Process change without development. The ability to change a flow yourself, as a configuration, is the capability that determines your cost of ownership three years in.

The full capability list is on the features overview, and the platform itself is described under warehouse management and order management.

Configuration or custom development

This is the single most consequential question in any selection, and it is worth asking in every demo, about every deviation you request. A configured WMS goes live in weeks and a process change is a setting. A programmed system takes quarters, and every change afterwards is another project with a quote attached. BizBloqs delivers warehouse and order management as a service — Business Process as a Service — where processes are configured, not built.

The business case for a WMS is rarely about software cost. It is about picking hours, mispick handling, stock accuracy, safety buffers and the overtime you no longer need at peak. Those are your numbers, not ours, so the honest way to present a return is to let you enter them.

The calculator below runs on your own volumes and shows payback in months, in euros or dollars. Nothing is sent anywhere until you choose to ask for the summary.

WMS pricing has three components, and vendors differ mostly in how much of the third they hide. There is a recurring subscription, usually driven by users, locations or volume; a one-off implementation and configuration fee; and the change cost afterwards — what you pay each time a process needs to move. That third component is where a cheap-looking quote turns expensive, because in a custom-developed system every change is a new project.

Budget realistically for integrations, hardware (scanners, access points, label printers) and the internal time your team will spend on data preparation. A WMS quote that omits those is not a lower price; it is an incomplete one.

Full breakdown, with the questions to ask a vendor about each line: WMS cost.

Most failed selections go wrong before any vendor is contacted, because the requirements were written as a feature list instead of as a description of the flows that actually have to run. Start from your own processes: map the ones that cause pain today, quantify them, and score vendors on whether they can run those flows as configuration.

• Score on your flows, not on a generic requirements matrix.
• Demo with your own article data and your own orders, not the vendor's demo dataset.
• Ask, for every deviation you request: configuration or development?
• Check the connector to your specific ERP version, not to the product family.
• Ask what a process change costs in year two.
• Speak to a reference in your sector, at your size.

Side-by-side method and scoring model: compare WMS software. Structured requirements list to work through: WMS selection checklist.

A configured implementation follows the same shape regardless of size; what changes is how long each phase takes, not which phases exist. In order: process mapping, configuration, integration, data migration and cleansing, testing with real orders, key user training, and a controlled go-live with hypercare.

Two phases decide the date. Data quality is the first — article master data, dimensions, locations and stock positions are almost always worse than assumed, and cleaning them is your work, not the vendor's. Integration is the second, particularly when an ERP is older or has been customised. Neither is solved by adding people late.

Phase-by-phase plan, with what you own versus what the vendor owns: WMS implementation.

A WMS only delivers if it sits in the flow rather than beside it. In practice that means a bidirectional exchange with your ERP — article data, purchase orders, sales orders and stock corrections down; receipts, picks, shipments and adjustments back up — plus channel and carrier links so nothing is rekeyed.

BizBloqs maintains pre-built connections across the ERP, ecommerce, PIM, carrier and forecasting landscape. A selection:

• ERP and finance — Exact Online, Business Central, SAP Business One, Sage, Uniconta, AFAS, King.
• Ecommerce and marketplaces — Shopify, Magento, WooCommerce, Shopware, ChannelEngine, Channable.
• Carriers and shipping — Sendcloud, nShift, DeliveryMatch, ShippyPro.
• Planning and forecasting — Optiply, Slimstock.

The complete list is on the integrations page and the partner overview.

The core flow is the same everywhere; the constraints are not. Food and pharma are driven by batch, expiry and traceability. Fashion is driven by size and colour variants and by return rates. Technical wholesale is driven by serial numbers and long-tail SKUs. Ecommerce fulfilment is driven by peaks and by same-day cut-offs. 3PL is driven by client separation and by billing.

Sector-specific detail, including the flows that typically need configuring, is on the industries overview.

Three solutions, depending on how far along you are. If you are still framing the problem, run your own numbers through the calculator above. If you are building requirements, work through the selection checklist. If you want to see the platform run on your own orders, book a working session — thirty minutes, your flow, no slide deck.