Two vendors send you a demo. Both show a dashboard, both hold your stock, both print documents, and both describe themselves as the system that runs your operation. One calls itself a WMS and one calls itself an ERP, and nobody explains the difference in a sentence you can act on.
Here is the sentence. A WMS answers questions about the building. An ERP answers questions about the business.
Everything else follows from that.
What each one is actually for
A warehouse management system exists to run the floor. Where is that pallet. Which bin. Which of the four locations holding this product should the picker go to first, and in what order, so the walk is short. Who received it, who counted it, who moved it, and when. It is a system about things and the people handling them, and its unit of work is a movement.
An ERP exists to run the company. What did this job cost. What did we charge for it. What is this customer’s balance. What do we owe that supplier. What did we earn last month, and on which lane. It is a system about money and obligations, and its unit of work is a transaction.
That is why the demos look similar and the products are not. Both can show you a list of stock. Only one of them can tell you whether holding that stock made you any money.
The test: three questions
Ask each question about your own week. The answers point at what you need with no vendor in the room.
1. When something goes wrong, is it lost or is it unpaid? If your bad days are “we cannot find it”, “we picked the wrong one”, “the count does not match” — that is a WMS problem. If your bad days are “we never invoiced that”, “we do not know what that job cost”, “the supplier is chasing us for something we thought we paid” — that is an ERP problem.
2. Do you sell space, or do you sell movement? If customers pay you to hold their goods, you are running a building and you need to know what is in it, to the location. If customers pay you to move their goods, the building is incidental and what matters is the job: its cost, its documents, its margin.
3. Who asks you for numbers? If it is the floor supervisor, a WMS. If it is your accountant, the tax authority or your bank, an ERP. A warehouse system will not produce a VAT return and was never intended to.
When one is enough
A WMS alone makes sense when the warehouse is the whole business and the billing is simple — a fixed monthly fee per customer, raised in an accounting package in ten minutes. You are not trying to work out margin per shipment, because there are no shipments. The floor is the product.
An ERP alone makes sense for most freight forwarders, and this surprises people. A forwarder often holds cargo for a few days between legs, and that is not warehousing — it is a shipment sitting still. It needs a location and a date, not a bin, a pick path and a cycle count. Buying a warehouse system for it is buying a great deal of machinery to answer a question a single field already answers.
The honest line is this: if you cannot remember the last time somebody could not find something, you do not have a warehouse problem yet.
When you need both — and the trap
The moment you charge a customer for warehousing, you need both, because the invoice is built out of facts only the warehouse knows.
Storage is charged per pallet per day. Handling is charged per receipt, per pick, per line, per unit. Every one of those figures is a warehouse event, and every one of them has to arrive in an invoice with the right tax treatment against the right customer. That is a WMS fact becoming an ERP transaction.
And this is where the trap sits. Two systems joined by a spreadsheet exported on the last working day of the month will always drift. Not dramatically — that would get noticed. It drifts the way these things always drift: a customer’s goods arrive on the 29th and the export was taken on the 28th, so two days of storage are never billed. A special handling job is done as a favour and never reaches the sheet. A rate changes in one system and not the other.
Nobody sees any of it, because there is nothing to compare against. The warehouse believes the invoice, and the invoice was built from the warehouse.
What “integrated” has to mean
Every vendor will tell you the two are integrated. The word is worth nothing on its own, so make it concrete with one question:
When the floor records a receipt, does the charge for it exist immediately — against the right customer, at the right rate, ready to be invoiced — without anyone exporting anything?
If the answer involves a file, a scheduled sync, or a person who checks it at month end, the two systems are adjacent rather than integrated, and the drift above is coming. If the answer is that the movement and the billable event are the same record, they are genuinely one system, and the question of which one you bought stops mattering.
Two things that are not what they look like
A WMS bolted onto accounting software is not an ERP. You get stock and you get a ledger, and nothing joins them: the accounts still cannot tell you what a customer cost to serve, because the accounting package does not know what a pallet is.
An ERP with a stock module is not always a WMS. Most ERPs can hold a quantity in a location, which is fine for your own consumables. Running a third-party warehouse needs more: stock owned per customer, batch and expiry, pick sequencing, cycle counting, and a charge attached to every movement. Ask whether it does those specifically, rather than whether it “has warehousing”.
The short answer
If your problem is finding things, you want a WMS. If your problem is knowing what you made, you want an ERP. If you bill people for storage and handling, you need both to be one system — and the test of that is not the word “integrated”, it is whether a movement on the floor produces a charge with no human in between.