Almost every EWM project I join has the same debate early on. Do we run EWM inside S/4HANA, or as a separate system next to it? Both work. The right answer depends less on the software and more on one question about your warehouse.
The First Question: How Long Can the Warehouse Stand Still?
Ask the operations manager what happens if the warehouse system is down for four hours on a Saturday. If the answer is “we load the trucks on Monday”, embedded EWM is a strong option. If the answer is “the cranes stop, the conveyors stop and the customers do not get their deliveries”, you need to think hard about decentralised.
With embedded EWM, the warehouse runs in the same system as finance, sales and production. Every planned outage of S/4HANA is also an outage of the warehouse. Patches, upgrades and system copies all have to fit around warehouse shifts. For a site that works 24/7, that becomes a real constraint.
With decentralised EWM, the warehouse has its own system. You can plan its maintenance around the warehouse, and the warehouse can often keep working for a while when the ERP is unavailable. You pay for that with an extra system to run and an interface to look after.
Then the Other Factors
Volume. High transaction volumes, with many RF confirmations per hour and waves released all day, put load on the system. A separate warehouse system keeps that load away from the rest of the business.
Automation. In automated warehouses with cranes, conveyors and AGVs, EWM talks to the equipment through the Material Flow System. Both deployment options can run MFS. But a crane waiting for a telegram does not care why the system is down, so automation usually pushes the uptime question up the list.
Number of ERP systems. A decentralised EWM can serve more than one ERP. That helps during a long migration, or when warehouses serve business units on different systems. Embedded EWM belongs to one S/4HANA system.
Upgrade cycles. With embedded EWM, the warehouse is upgraded when S/4HANA is. Decentralised lets you upgrade the warehouse on its own timeline, which can be a relief or an extra project, depending on how you look at it.
Licence and deployment. Basic warehouse management in embedded EWM comes with S/4HANA, but advanced functions such as MFS need an additional licence. Decentralised EWM has its own licence terms. Check the details of your own contract with SAP early. I have seen designs change late because nobody did.
Do Not Decide It per Site
If you run several warehouses, pick one approach for each type of site and put it in your template. When I worked on a European template across food-manufacturing sites, the value came from doing things the same way everywhere. A different deployment choice per site undoes that quickly.
Write the Decision Down
Whatever you choose, record why. In three years someone will ask again, usually during an upgrade. A one-page note with the uptime requirement, the volumes and the automation plans saves you the whole debate a second time.
