Most WMS buying guides are written for a business choosing its first serious system with nothing in place. An SAP business is in a different position. The ERP already holds the stock, the orders and the finance, and whatever runs the warehouse has to agree with it every minute of every shift. That narrows the field before a single demo, and it changes what a good selection looks like. We work only on SAP-run warehouses, so read this knowing where we stand: if the honest answer is not SAP, we will say so.
The four real options.
Stay on inventory management, or move to Stock Room Management.
SAP inventory management knows what you own, its value, and the plant and storage location it belongs to. It does not run the building. If the operation is small, simple and well run, that can be enough, and the honest first question is whether a warehouse system is needed at all. Our note on why inventory management is not a WMS sets out the signs that it is.
For a site coming off classic SAP WM, Stock Room Management is the lighter path: the continuation of WM with a reduced function set, part of the S/4HANA core since release 1909. It leaves out task and resource management, the automation interface, waves, cross docking, yard, value-added services and decentralised WM. SAP positions it for small warehouses with low automation. When it fits, it is a smaller project and a smaller cutover, and Stock Room Management or EWM goes through how to judge that.
Basic EWM, in the S/4HANA core.
Basic warehouse management sits in the S/4HANA core under the Enterprise Management licence. It covers inbound and outbound processing, internal movements, physical inventory, the warehouse monitor, resource management, and integration to quality, production and transportation, plus an IDoc interface to a third-party material flow system. For a site that receives, stores, picks and ships without heavy automation or yard control, it is often the honest middle, and it is the option buyers most often do not realise they may already be licensed for. Exact scope varies by release and contract.
Advanced EWM.
Licensed separately, and the right answer when the floor depends on what it adds: direct control of conveyors, sorters and shuttles, wave management, labour management, yard, cross docking, value-added services, slotting and cartonisation, among others. The dividing lines are set out in basic or advanced EWM, and the architecture question that follows (in the S/4HANA system or beside it) in embedded or decentralised EWM.
A third-party WMS beside SAP.
A real option, and sometimes the right one: an operation with unusual processes that no SAP product handles well, or an automation supplier whose own warehouse software is part of the equipment. The cost is not the licence. It is two systems that both believe they know where the stock is, an interface that has to stay healthy through every upgrade on both sides, and a support model split between two vendors who will each suspect the other first. Price that for the life of the system, not the first year, before deciding it is the cheaper path.
What decides it is the floor.
Every one of the four options can be made to sound right in a workshop. What separates them is a short list of questions about how the building actually runs, asked shift by shift:
Does any equipment on site need the warehouse system to drive it, or does the automation vendor run its own control layer? Do supervisors release work in waves against carrier cut-offs, or does the floor pick as orders arrive? Does anyone measure who is doing what against a standard? Is there a yard with trailers queuing, stock that crosses the dock without touching a bin, or kitting and labelling done on site? Is a second site or a group template coming? And when does the S/4HANA programme land, because the warehouse decision and the ERP timeline have to agree.
Answer those honestly and most selections narrow to one or two options before anyone sees a demo. If the site is coming off classic WM, do the same exercise on the functions the floor uses today, as set out in classic WM on S/4HANA after the Compatibility Pack. A function that is configured but unused is not a requirement.
How the selection should run.
In this order, and the order matters more than the method. First, map the operation as it runs today, by shift, including the workarounds. Second, list the functions it depends on now and the ones the next three to five years will ask for. Third, map that list to the four options and drop the ones that cannot carry it. Fourth, cost the survivors to live with, not just to buy: licence, integration, hardware, support, and the retraining and cutover each one implies. Our note on what an EWM rollout really costs shows where that money usually goes.
Only then go to market, with requirements written around operator outcomes rather than a feature catalogue. The integrator is chosen after the system, and interviewed about the floor, not the slide deck. We have written down the questions that separate floor people from slide people.
A function that is configured but unused is not a requirement. A function the floor runs on a spreadsheet is.
Who should help you pick.
Everyone in this market has a reason to prefer an answer. A software vendor sells its own product. An integrator sells the build of the product it implements. Some logistics consultancies that run selections also sell or implement a warehouse system of their own. None of that makes their advice wrong, but it is worth asking every adviser, directly, what they earn if you pick each option.
The adviser you want has stood on warehouse floors, knows your ERP well enough to see where the integration will hurt, and earns the same whichever option you choose. That is how we work on SAP-run sites: we sell no licences, no software and no build. If the floor points away from SAP, we will tell you and suggest who is better placed.
Where Luminar fits.
Usually at the start, with the Floor Audit: one day on your floor and a plain-language memo within five working days that says which of the four options fits and why. From there, the work runs into the position you are in, whether that is a new distribution centre, a move off SAP WM, or a broader conversation with a warehouse management consultant about where to start.