Should I customize my WMS or change my processes?

If you're asking this after vendor selection, the answer is harder than it should be — and the reason has less to do with the question than with when it's getting asked.

Customization tolerance is an operational lever. How much your processes can flex to match a system, how much a system needs to flex to match your processes, where the line sits between the two — these are inputs to vendor fit, not outputs of it. They determine which vendors can support your operation and which ones will require expensive customization or process compromise to make the relationship work. Settled in advance, they shape the shortlist. Settled after the fact, they become a forced choice between two bad options: customize the system you bought, which is expensive, fragile, and often vendor-dependent — or restructure operations to fit a system that wasn't selected for fit, which is operationally disruptive and sometimes impossible without losing what made the operation work in the first place.

The reason this question gets asked too late isn't carelessness. It's that customization tolerance is exactly the kind of operational lever that's hard to see clearly from inside the operation. The processes that can flex and the ones that can't — and why — are bound up in workarounds, exceptions, and operational habits proximity blindness has made invisible. When you run a solo evaluation, you typically don't surface customization tolerance as a vendor-selection criterion because you don't have a documented picture of what your operation can and can't bend on. The question you should be answering at selection — which processes are load-bearing and which are habits I could change — gets deferred to implementation, where the answer is no longer free.

By the time the customize-or-change question is being asked, the choice is between bad options and worse ones. The path to better choices was upstream.