What is a WMS, and when does a warehouse need more than an ERP?

Short answer: a WMS (warehouse management system) is software that runs the physical work in a warehouse: which location holds the stock, who moves it and when, in what order it is issued and what the next task is. An ERP keeps the books — purchasing, sales, invoicing and stock value. A warehouse needs a WMS when staff search for goods, when discrepancies only show up at the stock count and when accuracy depends on people’s memory. NG WMS runs the goods and sends the ERP verified data.

What is a WMS?

A WMS describes the warehouse the way it physically is — zones, racks and locations — and tracks every movement of stock through it. Where an ERP sees “item X, 240 units in the Belgrade warehouse”, a WMS sees 180 units in a reserve location, 60 on the pick face, one pallet on quality hold and part of the stock already reserved for tomorrow’s wave.

That is why a WMS does five things an ERP usually does not:

• Locations — every unit of stock has an exact place, down to rack, level and position.
• Tasks — receiving, replenishment, picking and counting are tasks with an assignee, a status and a history.
• Scanning — location, pallet and item are confirmed by barcode rather than copied from paper.
• Issuing rules — FIFO, FEFO or location sequence decide which stock leaves first.
• Stock by location — inventory is held by location, LPN, lot and expiry date, and changes with every recorded movement.

WMS vs ERP inventory module: what is the difference?

An ERP inventory module is built for accounting accuracy: how much stock there is, what it is worth and which document brought it in or took it out. That matters, but it does not tell an operative where to go or what to pick. A WMS is built for operational accuracy — the right person picking the right goods from the right place, in the right order.

This is not about a better or a worse system. An ERP and a WMS solve different problems, and a growing warehouse needs both.

When does a warehouse need more than an ERP and spreadsheets?

There is no number of pallets or SKUs after which a WMS becomes mandatory. There are signs. If you recognise three or more, the warehouse has probably outgrown its tools:

• Staff search for goods: an experienced operative knows the item is “somewhere at the back”, a new starter has to ask.
• Locations live in a spreadsheet that is updated at the end of the shift — or not at all.
• Stock discrepancies only surface at the stock count, when nobody knows where they came from.
• Customers receive the wrong item or quantity, and the cause cannot be traced.
• Stock with a shorter shelf life stays on the shelf while a newer lot goes out.
• You store goods for several owners or across several sites, and “stock in the ERP” no longer says enough.
• When a lot has to be recalled, the list is put together from memory and paper.
• Work slows down whenever the one person who “knows the warehouse” is away.

The common thread: the information about your stock exists, but in people’s heads and on paper rather than in a system.

What does a WMS do day to day?

Receiving

Goods arrive against an advance notice, and what was received is compared with what was announced while the driver is still at the dock. Lot, serial number and expiry date are recorded straight away, so traceability starts at goods-in. The full process is covered in Goods receiving in a warehouse: checks, discrepancies and putaway.

Locations

The warehouse is divided into areas, sub-areas and locations. A sub-area has a purpose — picking, reserve, receiving, dispatch or quarantine — and a location has dimensions, a level and a picking sequence. In NG WMS this is the warehouse model, with a 2.5D view of occupancy and blocks.

Picking and dispatch

Orders are grouped into waves, stock is reserved, and every line is scanned before it goes into a box. The shipping unit gets a label with an SSCC. When waves pay off and when they do not is explained in Wave picking: when waves pay off.

Stock, replenishment and counts

The pick face is replenished by a min/max rule before it runs empty, stock is blocked with a document and a reason, and counts run by zone, item or LPN without closing the whole warehouse.

Scanning

Operatives confirm location, container and item with a scanner, where the goods are. In NG WMS this is a dedicated scanner app, working on the same orders, waves and tasks the office sees.

How do a WMS and an ERP split the work?

The most common rollout mistake is keeping the same data in two places. So the split has to be clear from day one: the ERP keeps the books, the WMS runs the goods.

Messages flow between the two. In NG WMS the receiving notice arrives from the ERP through the API, and receipts, dispatches, counts and other stock changes go back as webhook events. A message that was not delivered waits in the outbox and can be resent with the same ID, so the ERP can recognise it as a repeat. A count result reaches the ERP only after approval in the WMS, and an order the ERP has stopped carries an “ERP stop” flag with a reason. The mechanism is described on the ERP integration page.

What should you prepare before implementing a WMS?

1. A map of the warehouse — zones, racks and locations, with the purpose of each.
2. The item master — units of measure, barcodes and rules: whether a lot is mandatory, shelf life and the issuing rule.
3. Your flows of goods — how receiving, picking and dispatch run today, and where errors creep in.
4. The split with the ERP — which documents come from the ERP, which go back and who owns which data.
5. Equipment — scanners, label printers and network coverage on the warehouse floor.

In NG WMS, items, warehouses, areas, sub-areas, handling units and quality statuses are imported from Excel, so the model is not entered by hand, location by location. Scanners and printers are checked on your own equipment as part of the rollout.

What does AI change once the warehouse runs on a WMS?

Once every movement of stock is a record, you can ask the warehouse a question. NG Copilot is the AI assistant built into NG WMS: it answers questions such as “What is late for dispatch today?” or “Where is lot L-0915?” and names the document behind the answer. A proposed replenishment or check becomes a task only when a person confirms it. Through the MCP server, the AI assistants your team already uses work with the same data, under the same permissions. More on the NG Copilot and MCP page.

A spreadsheet cannot answer a question about your stock. A WMS with an AI assistant can, because it knows where the goods are, what has happened to them and what the next step is.