How do we know we've outgrown our ERP's warehouse module?
The usual answer is a list of symptoms: spreadsheets running alongside the system, an exception process that keeps growing, overtime that scales with order volume rather than with revenue, chargebacks absorbed as a cost of doing business. Those are worth writing down. They just don't settle the question, and the reason has less to do with the symptoms than with what the module is.
It was never chosen. It arrived bundled with the ERP, already licensed, and nobody in the building evaluated it against an alternative. That matters more than it sounds. When an operation outgrows a system it selected, there's a record of what the system was selected for — a scope, a set of requirements, things it was supposed to do — and outgrowing it means measuring against that record. A bundled warehouse module has none. There is no agreement to have exceeded, which is why the question usually ends up answered by feel.
The second difficulty is that the module's inadequacy never presents as a system cost. It presents as labor, as a spreadsheet somebody maintains by hand, as a customer-specific process one supervisor owns and no one has written down, as chargebacks booked against freight. Every one of those has an owner and a budget line, and none of them says "warehouse module" on it. So the module reads as free and adequate at the same time, and each impression reinforces the other.
Then there's the comparison itself, which has no reference point. Nobody on the team has operated a purpose-built WMS, so the question is this the amount of manual work this should take? has no available answer. Availability bias normally pushes a buyer toward the vendors they've heard of. Here it runs backward: the most visible option is the one already installed, and it wins by being the only thing anyone can picture.
None of this means the module is the problem. Plenty of distribution operations are well served by it, and one shipping company-owned inventory to a predictable customer base, on its own terms, usually is. What distinguishes the operations that have genuinely outgrown it is where the friction sits: against a retailer's routing guide, against a traceability requirement carrying legal weight, against inventory in the building the company doesn't own.
Every warehouse carries friction — what settles this question is whose rules produced it.
Related questions
System Fit Sprint
Before this becomes a vendor problem, it's an operational one.
The System Fit Sprint surfaces what your operation actually needs before any vendor conversation starts — so the workarounds you've stopped seeing don't become the gaps that disqualify systems in implementation.
Reserve your sprint