What is a warehouse management system (WMS)?

What a warehouse management system does

A WMS is the system of record for physical stock. Accounting software knows what inventory is worth. An online store knows what customers ordered. The WMS knows that the 240 units of olive oil OIL-008 are really 180 units in bin A-01-02 from lot LOT-0826, 48 units on a pallet still at the receiving dock, and 12 units in quarantine because two cartons arrived crushed.

The second job is directing work. A spreadsheet records what already happened. A WMS tells people what to do next: which bin to put a delivery away to, which lot to pick for an order, which bins to count today, which order has to leave before the carrier cut-off. Each task is confirmed with a scan, so the record updates at the moment the stock moves, not at the end of the shift.

Put together, those two jobs answer the questions a warehouse gets asked all day. Can we ship this order today? Where did this lot go? Why does the count not match? A good WMS answers them from data rather than from someone walking to the shelf.

Core WMS functions

Most warehouse management systems cover the same flow of work, from the truck that arrives to the parcel that leaves. The depth of each step is where products differ.

• Receiving: check deliveries against a purchase order or advance shipping notice, capture lots, expiry dates and serial numbers, and record shortages, overages and damage.
• Putaway: direct each pallet or carton to a storage location and confirm it with a location scan.
• Inventory control: track stock by location, lot, serial, license plate, owner and status (available, quarantine, damaged, on hold), with moves and adjustments recorded against a reason.
• Order allocation: reserve specific stock for each order according to rules such as first expired, first out, and create backorders when stock is short.
• Picking: produce pick lists in walk order and confirm each pick by scan, one order at a time or in batches.
• Packing and shipping: verify items at the pack station, choose cartons, capture weights, print labels and packing slips, and dispatch parcels or truck loads.
• Counting: run cycle counts continuously instead of shutting down for an annual count.
• Returns: receive returned units, grade them and decide whether they go back to stock, to repair or to disposal.
• Reporting: show what needs a decision now and measure performance over time.

How a WMS tracks inventory: locations, lots and the ledger

Inventory in a WMS is not one number per product. Stock is identified by a combination of warehouse, location, SKU, lot, serial or license plate, owner and status. Two cartons of the same serum are different stock if they came from different lots, and a pallet on hold is not available to sell even though it is on the shelf.

The best systems keep an append-only movement history. Every change in quantity is a movement with a reason, a reference and a user: received against a purchase order, moved from A-01-02 to B-04-01, adjusted down by two for damage. The on-hand balance is the sum of those movements. That gives you an audit trail for every unit and makes it possible to trace a lot forward to the customers who received it.

Types of warehouse management systems

The label WMS covers several kinds of software. Knowing which kind you are looking at saves time in evaluation.

A standalone WMS does warehouse execution in depth and connects to your store, ERP and carriers through integrations and an API. An ERP warehouse module lives inside a larger business system; it shares one database with finance and purchasing, but its floor workflows are often thinner. The trade-offs are covered in WMS vs ERP. Inventory management software tracks quantities and reorder points but usually stops short of bins, lots, scanning and directed tasks.

Two other distinctions matter. A multi-client WMS, built for third-party logistics providers, keeps each client's stock, orders and billing separate inside one warehouse. And deployment: cloud WMS runs in a browser and is updated by the vendor, while on-premise WMS runs on your own servers. For a new operation, cloud usually wins on practicality: there is no server to maintain and the floor can work from phones and scanners over Wi-Fi.

WMS vs OMS, TMS and shipping software

A WMS is often confused with the systems on either side of it. An order management system (OMS) collects orders from every channel, decides which warehouse fulfills each one and tells the customer where the order is. The WMS takes that order and turns it into physical work inside one building. The split is covered in more depth in WMS vs OMS.

A transportation management system (TMS) plans and buys freight: which carrier, which route, which truck. Parcel shipping software buys labels and tracks parcels. A WMS usually produces the data those tools need, such as package weights, dimensions and pallet counts, and prints the labels at the pack station. Small operations often run a WMS with a shipping tool and no separate OMS or TMS at all, adding them only when channels or freight volumes grow.

Who needs a WMS (and who does not yet)

You probably need a WMS when the answer to "how many do we have?" depends on who you ask. A common trigger is going from one person who knows where everything is to a team that has to be told. The signs below are more reliable than any order-count threshold.

If you have one room, a few dozen SKUs, no expiry dates and one person who picks everything, a well-kept sheet can still work. The comparison of a WMS vs spreadsheets lays out where that breaks down.

• The same SKU sits in more than one location, and pickers search for it.
• You sell products with lots, expiry dates or serial numbers and need to trace them.
• Counts regularly disagree with the system, and nobody can explain why.
• Mis-picks and short shipments generate customer complaints or credit notes.
• You fulfill both parcel orders and pallet or B2B orders from the same stock.
• You hold stock for more than one owner, as a 3PL does.
• Someone has to walk the floor before you can promise a delivery date.

How to evaluate a WMS

Feature lists look alike, so evaluate with your own scenarios. Write five or six scripts from real days in your warehouse and ask each vendor, or your own trial account, to run them end to end. For example: receive a delivery that is two cartons short and contains two lots; pick an order that needs stock from two bins; count a bin with a variance while someone picks from it; return a damaged unit; recall one lot.

Then score what you saw against the criteria below. For a longer checklist and the questions to ask, see how to choose a WMS.

• Stock model: does it handle your lots, expiry, serials, license plates, owners and statuses without workarounds?
• Floor usability: can a new picker learn the scanner flow in an hour? Does it work on the devices you already have?
• Rules: can allocation apply FEFO, prefer pick faces, and handle shortages the way you want?
• Data in and out: bulk import with validation, an API with documentation, webhooks and CSV export.
• Visibility: an exceptions view, alerts, an activity history per record, and KPI reports.
• Security: how tenant data is isolated, how permissions work, and who can see what.
• Commercials: pricing model, contract length, and what counts as a billable user or order.
• Time to first order: how long before a real order ships through the system.

WMS implementation: a step-by-step outline

Implementation is mostly data and discipline, not software. The order of steps below keeps the go-live small and reversible. If you are moving off spreadsheets, the spreadsheet-to-WMS migration guide goes through the data work in detail.

• Scope: pick the warehouse, the order channels and the workflows for go-live. Leave nice-to-haves for month two.
• Master data: clean the catalog first (one SKU per sellable variant, units of measure, pack sizes, barcodes).
• Locations: name every bin with a consistent code, print and fix labels, and set a walk sequence.
• Rules: set allocation, receiving tolerances, count tolerances and user permissions.
• Opening stock: count into the system rather than importing old balances you do not trust.
• Training: rehearse each script on the floor, including the exceptions (short pick, damaged item, wrong barcode).
• Cutover: go live on a quiet day, stop using the old sheet the same day, and keep a supervisor on the floor.
• Stabilize: review exceptions daily for the first weeks and start cycle counting from day one.

Common WMS implementation mistakes

Importing dirty data is the most expensive mistake, because every later report inherits it. Duplicated SKUs, missing barcodes and guessed opening balances turn into mis-picks within a week. Count first, then import.

The second is going live at peak. A new system slows people down for the first days, so choose a quiet week. The third is over-customizing before you have run the standard workflow; most requests for custom fields disappear once people see the flow working. The last is training only the happy path. Pickers learn scanning quickly; what they need rehearsed is what to do when the bin is empty.

How NextStock approaches warehouse management

NextStock is a cloud WMS for brands, 3PLs and B2B distributors, currently in open beta and free to use. It covers receiving with lot, serial and license plate capture, directed putaway, FEFO allocation, walk-sorted discrete and batch picking, scan-verified packing, parcel and pallet dispatch, cycle counts, holds, recalls and returns. Every quantity change is a movement in an append-only ledger, and every record carries its owner, so a 3PL and a single brand use the same model.

The office runs in a web browser and the floor runs as an installable web app on phones or scanners, so there is nothing to install on a server. You can create an account and set up a warehouse yourself. Native store connectors and live carrier label purchase are on the roadmap, not available yet; today orders arrive through the UI, CSV import or the API.