Looking for a WMS alternative? Work through this first

Before you shop for a WMS alternative, label each complaint as a product, setup, training, commercial or support gap, because only product gaps and some commercial gaps are solved by leaving. People search for "alternatives to" a system when something has gone wrong. Sometimes the system is the problem. Sometimes the setup is. Sometimes the contract is. Swapping one WMS for another fixes only the first.

This page is a short diagnosis you can do in an afternoon. It names no products, because the diagnosis comes first and the shopping second.

Step 1: say what is actually wrong

Write one sentence for each complaint. Then label it.

• Product gap. The system cannot do the thing, even with configuration.
• Setup gap. The system can do it, but nobody set it up that way.
• Training gap. The feature exists and your staff do not use it.
• Commercial gap. The price or terms no longer suit you.
• Support gap. Problems are raised and not fixed in a useful time.

An example, clearly made up: a warehouse says "the system cannot handle our kits." After a call with the vendor, it turns out kits are supported but were never configured. That is a setup gap, and moving to a new system would have meant paying to learn the same lesson again.

Only product gaps and some commercial gaps are solved by leaving.

Step 2: test whether it can be fixed where you are

Before you go shopping, ask your current vendor, in writing:

1. Can this be done with the current version? Show us how.
2. If not, is it planned? Give us a date or tell us there is no date.
3. What would a change to our contract cost, if the price is the issue?

Keep the answers. If the vendor cannot help, you now have evidence for your search. If it can, you have saved a migration.

Step 3: price the move honestly

Switching has costs that rarely appear in brochures:

• Moving item, location and customer data and checking it afterwards
• Retraining every user
• Time when you run slower while people learn
• Rebuilding integrations with other systems
• A period of overlap if you run both systems
• Any exit fee, notice period or data export charge in the old contract

Add your own staff hours to the list, because that time is real even if no invoice shows it. A cheaper monthly fee can lose to the cost of moving.

Step 4: list what you must carry across

Make an inventory of what your current system holds and does that you cannot lose:

• Item masters and location maps
• Open orders and open receipts at the moment of cutover
• Customer or client rules, such as labelling and shipping preferences
• Reports people rely on, including the ones nobody remembers asking for
• Integrations, with who owns each connection
• Scanner screens that your team has memorised

Every item on this list becomes a test for a new product. The unglamorous items, such as that one report the finance person uses on the last day of the month, cause most of the pain after go-live.

Step 5: define a fair alternative

An alternative qualifies only if it meets three tests:

1. It fixes the complaint you labelled in step 1.
2. It covers everything in your step 4 inventory, or you have a workable plan for what it does not.
3. The total cost, over a period you choose, is lower or the benefit clearly outweighs the difference.

The options usually fall into four groups, and it helps to know which you are comparing:

Cargohold, which we make, is a one-time custom build, no per-seat, per-truck or per-client fees. Put every quote through the same tests.

Step 6: run the same trial on everything

Create a test pack from your real data: ten items, three locations, five orders including one awkward one, and one inbound shipment. Ask every candidate to process it. Record the steps, the time and what had to be worked around.

Do not accept "we can do that" in place of the run. Ask for a recorded session or a trial account.

Step 7: plan the cutover before you sign

• Choose a quiet week, not a peak
• Decide how open orders move across
• Name one person on your side who owns the project
• Agree what "done" means: for example, a full week of orders shipped without workarounds
• Keep the old system available for a defined period, in a read-only state if possible

A quick decision grid

What to expect from this site next

We will publish named comparison and alternatives pages after this. Each will cite public pages for every fact about another product, show the date we read them, and invite corrections. Until then, the steps above work against any product.

Questions people ask

What are the signs I should replace my WMS?

A product gap, where the system cannot do the thing even with configuration, or a commercial gap, where price or terms no longer suit you. A setup or training gap would follow you to a new system.

Is a WMS alternative always the answer?

No. Only product gaps and some commercial gaps are solved by leaving. A setup or training gap would follow you to a new system.

What does switching cost beyond the new price?

Moving and checking data, retraining users, slower running while people learn, rebuilding integrations, a period of overlap, and any exit fee, notice period or data export charge in the old contract.

What should I list before switching?

Item masters and location maps, open orders and receipts at cutover, client rules, reports people rely on, integrations with their owners, and scanner screens your team has memorised.

How do I test candidates fairly?

Build a test pack from your real data: ten items, three locations, five orders including one awkward one, and one inbound shipment. Ask every candidate to process it and record the steps, the time and what had to be worked around.