Your warehouse has grown and the off-the-shelf WMS has started to pinch: it won't sync with SAP in real time, it can't handle the way you schedule deliveries, and every non-standard operation is a spreadsheet workaround. Before you swap one box for another, see when a custom WMS genuinely pays off, and how not to overpay for custom where a box would do fine.
A WMS runs the warehouse: intake, storage, picking and dispatch. An off-the-shelf system handles a standard process; custom makes sense when the process is your edge or no ready-made product covers it end to end.
A clear sign you've outgrown the product is that key operations run in a spreadsheet beside the system, while the SAP or carrier integration you need "can't be configured".
Price a custom WMS by the cost of risk and downtime, not by a licence fee. The real cost is a warehouse that stops when one system goes down.
A custom WMS isn't a one-off rollout; it's a system for years. The right question is who runs it when SAP changes an API five years from now.
Not every warehouse needs a custom system. If your process is standard and an off-the-shelf product handles it without workarounds, buy that product.
A WMS (Warehouse Management System) is the software that runs the warehouse: goods in, where they're stored, order picking, dispatch and stock counts. An off-the-shelf WMS (a big-name suite, a module inside SAP, a smaller vendor's product) comes ready-made: you install it, configure it, go live. For a typical warehouse that's often the best call, and there's no sense writing one from scratch.
The trouble starts where your warehouse stops being typical. An off-the-shelf product assumes a certain way of working. As long as your process fits, everything runs. The moment you start bending it, the workarounds appear: spreadsheets for every unusual delivery, macros, re-keying data between systems, and "that can't be configured" from the vendor. You're paying for a licence while part of the warehouse runs outside the system.
The second pressure point is integrations. A boxed WMS connects the way its vendor planned for. If you need real-time SAP, your own delivery scheduling, the carrier and invoicing wired into one flow rather than a loose export once a day, you hit a wall fast. That's where custom territory begins.
| Custom WMS | Off-the-shelf WMS | |
|---|---|---|
| Process | Software shaped to your warehouse | Your warehouse shaped to the software |
| Integrations | Real-time SAP, carrier, scanner, invoicing in one flow | As much as the vendor planned for |
| Non-standard operations | Handled inside the system | End up in a spreadsheet beside it |
| Cost | Higher up front, priced by the cost of risk | Lower up front, paid back in workarounds |
| A year on | You extend the system to a new process | You wait for the vendor's roadmap |
| When something breaks | The partner who built it picks up | A ticket in the support queue |
From the Rulewave delivery: a global logistics operator's WMS.
“You don't buy a custom WMS to have a "more modern" system. You buy it when your warehouse is your edge, and no box will handle it.”
For a global logistics operator, we built and run a WMS that no off-the-shelf product could support. Real-time SAP, a warehouse scanner, supplier delivery scheduling, DHL and invoicing are wired into one flow. It handles hundreds of thousands of operations a year, with no critical failures or data loss. When the process changes, we extend the system; we don't wait for a vendor's roadmap. With low turnover, the engineers who built it are still supporting it.
You don't assess the cost of a custom WMS the way you assess the cost of a licence. A box has a price on the invoice; custom is a build plus years of upkeep. But there's a cost the box's invoice never shows: the hours in spreadsheets, the picking errors, the numbers that don't match between systems, and the warehouse that stops when one integration goes down.
Count it honestly, both ways:
If the answers point to a custom system, you're not looking for a one-off rollout. You're looking for a partner who'll run that WMS when SAP changes an API five years from now, or a new carrier comes in. And the other way round: if the process is standard and the box handles it without workarounds, custom will only burn budget. See what a custom WMS looks like in practice: our case studies.
Software that manages the warehouse at the operational level: intake, put-away, order picking, dispatch and stock counts. It tells the picker where the stock sits and how to get a shipment out, and it gives the business real-time data on what's happening on the floor.
An ERP runs the whole company: finance, sales, purchasing. A WMS manages the warehouse itself at the operational level: locations, picking, dispatch. In practice we connect the two: the WMS reports warehouse movements to the ERP or SAP in real time, instead of a once-a-day export.
SAP is first and foremost an ERP. It has a warehouse module (SAP EWM/WM), but that's not the same as a WMS fitted to your warehouse. More often we connect a custom WMS to SAP as the source of truth, in real time, the way we do it at Rulewave.
When the warehouse process is your edge, when you need integrations a box won't give you (real-time SAP, the carrier, invoicing), or when non-standard operations run on a spreadsheet beside the system anyway. For a standard warehouse, a box does the same job for less.
It depends on scope and integrations, but the real question is different: what does the risk and downtime cost when the warehouse stops? Custom is priced by the cost of risk and workarounds, not by the licence alone. We give a concrete figure for your scope after we've talked through the process.
Real-time SAP, delivery scheduling, the carrier, the scanner: a warehouse your operations depend on. Let's talk through the process before we mention technology.
Let's talk about your processOne hard integration or a narrow module with a clear scope. We'll price it quickly and clearly, with no open-ended "let's add one more thing".
Get your scope priced
