Why WMS If I Already Have ERP? A Company With 40 Million Euros in Revenue Still Works on Paper

In this episode of Rozmowy Logistyków, Piotr Skobało and Adam Sobolewski explain why a company needs a WMS system when it already has an ERP. They discuss why many Polish family-owned organizations still don't use dedicated warehouse systems, despite the real benefits of deploying one.

ERP RECORDS, WMS MANAGES

ERP systems (Comarch, Microsoft Business Central, and similar) grew out of accounting software — to them, a warehouse is just another "branch" where you can record a receipt or an issue. But they don't manage what's actually happening inside the warehouse: the flow of goods, locations, picking strategies. A WMS (Warehouse Management System) goes down to a level of detail ERP can't reach — batch and expiry-date tracking, multi-level picking strategies, buffering, order consolidation.

TWO SECONDS PER ORDER IS ONE ENTIRE FULL-TIME POSITION

A concrete example from practice: with 12,000 orders fulfilled in a single shift, a difference of just two seconds in the time to pick a single order translates into 24,000 seconds a day — roughly 6.7 effective hours of work, practically an entire full-time position. This shows the leverage of scale: a seemingly microscopic process improvement, multiplied by volume, produces a result counted in tens or hundreds of thousands of złoty a year.

EMPLOYEE ONBOARDING DROPS FROM MONTHS TO DAYS

In a well-organized warehouse with a WMS, a new employee reaches around 70% efficiency after a week to a week and a half, instead of months — because the system "holds their hand": it tells them exactly which aisle and which shelf to go to, and scanning a code (sometimes an EAN plus an additional QR with a serial number) eliminates the need to memorize anything. Without this, warehouses rely on "tribal knowledge" — the legendary employee who can remember 12 order lines at once, while others manage two or three, becomes an irreplaceable bottleneck.

INDIVIDUAL PERFORMANCE TRACKING CUTS BOTH WAYS

Deploying a WMS that enabled a switch from collective to individual bonuses produced a 10% month-over-month productivity increase at one organization. The reverse experiment at another large company — temporarily halting individual productivity feedback to employees (at the request of the union, while keeping quality-error information) — produced a 13% productivity drop within a month. A key caveat: this is about a support tool and feedback, not about accounting for every single second of work.

FEFO VS. FIFO: ACCOUNTING AND THE WAREHOUSE DON'T HAVE TO BE THE SAME

A common organizational mistake: imposing the FIFO rule (first in, first out) from the financial/accounting system onto the physical process of issuing goods in the warehouse, when what actually protects against losses is FEFO (first expired, first out) — issuing goods by expiry date, not by order of receipt. FIFO accounting is a matter of financial methodology, not necessarily the physical warehouse process.

HOW TO TELL IF IT'S WORTH IT

The first question isn't "what ROI," but "can I even run this operation without a system at all" — with a highly fragmented SKU base or a specific product type, this can be a hard requirement, not an option. If the operation can be run without a WMS, only then does return on investment matter — a payback period under a year is a signal to "just take it and don't overthink it," while a four-year payback is a red flag requiring a lot of confidence in the business's stability over that horizon. The real cost of the whole ecosystem (system plus infrastructure) is usually tens to hundreds of thousands of złoty a year — offers advertised as "300 PLN a month per user" usually hide additional costs beyond the license itself.