SAP EWM
How a Food and Beverage Distributor Cut Warehouse Handling Costs by 24% with Embedded SAP EWM
At a glance
Our client was a US food and beverage distributor, who moved its main warehouse from SAP WM to embedded SAP EWM on S/4HANA in 8 months.
Handling cost per order fell by 24%, and inventory accuracy rose from 91% to 99.2%.
| Project detail | Summary |
| Client | US food and beverage distributor |
| Location | Midwest, USA |
| Warehouses | 4 in total; this project covered the main distribution centre |
| Previous system | SAP WM on S/4HANA, compatibility pack |
| New system | Embedded SAP EWM on S/4HANA |
| Connected to | SAP TM, and the [AS/RS] through SAP MFS |
| Duration | 8 months from assessment to go-live, followed by 6 weeks of hypercare |
| Headline results | Handling cost per order down 24%; inventory accuracy up from 91% to 99.2% |
About the client
The client is a food and beverage distributor based in the Midwest, USA. It operates 4 warehouses, ships around 6,000 orders a day and carries about 18,000 SKUs. A large share of that range is chilled and frozen stock with expiry dates, so releasing the right batch first is a daily operating requirement.
All four sites ran on SAP WM. The system had served the business well for years, but the business had grown considerably since it was set up, and the warehouse application had not kept pace.
The challenge
In short, the stock in SAP no longer matched what was on the shelves, and too many orders were going out wrong. Four issues stood out.
Unreliable stock data. Cycle counts put inventory accuracy at about 91%. Planners did not trust what SAP showed them, so they carried extra safety stock as a precaution.
Picking errors. Around 2.8% of order lines went out wrong, mostly the wrong item or the wrong batch. Each error meant a return, a re-ship and, sometimes, an unhappy customer.
A fragile AS/RS interface. The AS/RS passed data to SAP through a custom interface that failed [a few times a month]. Every failure left someone correcting stock by hand.
A fixed deadline. The client’s WM compatibility pack usage rights were due to expire on December 31, 2025. Staying on SAP WM was not an option, so the real question was how to move.
Why we chose embedded EWM
We chose embedded SAP EWM because all of the client’s sites run on a single S/4HANA system, and the warehouse did not need to keep operating independently if that system went down. We also assessed decentralised EWM, which suits very high-volume warehouses and sites that must keep shipping while the central ERP is unavailable. Neither profile applied here.
| Decision factor | What we found | Effect on the decision |
| ERP landscape | All sites run on one S/4HANA system. | Embedded EWM fits the existing landscape. |
| Volume | The busiest site ships about [3,500] orders a day | Not the very high-volume profile that points to decentralised EWM |
| ERP downtime | The client already had a downtime plan | No need for a warehouse that runs independently of the ERP |
| IT capacity | Small IT team | One system, fewer interfaces and less hardware to support |
| Automation | The AS/RS could connect to EWM directly through SAP MFS | Confirmed before the decision, and it settled the question |
Field Note - If S/4HANA goes down. The AS/RS finishes the moves already sent to its controller. After that, the team switches to a written downtime procedure until the system is back.
What SCM Champs implemented
We replaced SAP WM with embedded SAP EWM at the main distribution centre, connected it to SAP TM, and linked the AS/RS directly to EWM through SAP MFS.
Warehouse processes
| Area | Scope |
| Inbound | Receiving with RF scanners; putaway rules based on temperature zone and product size |
| Outbound | Wave picking by [delivery route and truck time], followed by packing and loading |
| Inside the warehouse | Replenishment, cycle counting, and batch and expiry tracking on a first-expired, first-out basis |
| Labour | Simple labour tracking, so supervisors can see picks per hour by shift |
Integrations
| System | Role |
| S/4HANA | Orders, stock and finance. Because EWM is embedded, it runs on the same system rather than a separate one. |
| SAP TM | Shipment planning. The warehouse now knows which truck leaves when and picks in that sequence. |
| [AS/RS] through SAP MFS | Replaced the old custom interface entirely. |
Future Scope - SAP Yard Logistics and BN4L were left out. The client wanted the warehouse stable first and will look at both later.
Project timeline
The project ran for about 8 months, from the first workshop to go-live, followed by 6 weeks of hypercare.
| Phase | Duration | Key activities |
| Assessment | 3 weeks | Site walk-through, review of the WM setup and custom code, and the embedded versus decentralised decision |
| Design | 6 weeks | Storage types, putaway and picking rules, wave setup, and the TM and MFS interfaces |
| Build | 4 months | Configuration, master data clean-up, and the MFS link to the AS/RS |
| Testing and training | 6 weeks | The client’s own team ran the test scripts; key users trained on real orders, not demo data |
| Go-live | 2 weeks | Cutover over a weekend, with our consultants on the warehouse floor |
| Hypercare | 6 weeks | Daily check-ins at first, then twice a week |
Little Hiccup - The Go-live moved by 2 weeks because the AS/RS vendor needed more time on their side of the MFS setup. That delay is already counted in the 8 months. We used the time for an additional round of testing, and we were glad we did.
Results
Once operations settled after go-live, handling cost per order dropped 24%, and inventory accuracy rose from 91% to 99.2%.
| Metric | Before (SAP WM) | After (SAP EWM) | Change |
| Inventory accuracy | 91% | 99.2% | +8.2 points |
| Handling cost per order | $2.10 | $1.60 | −24% |
| Picking errors (share of order lines) | 2.8% | 0.6% | −2.2 points, about 79% fewer errors |
| Picks per labor hour | 62 | 81 | +31% |
| Manual stock fixes per month | about 40 | fewer than 5 | more than 85% fewer |
How we measured this. The before figures are the average of the 6 months before go-live. The after figures are the average of months 2 to 7 after go-live; we left out the first month on purpose, because performance is always unsettled right after a go-live.
Inventory accuracy comes from the client’s own cycle counts, and cost per order comes from their finance team. Handling cost covers warehouse labour, equipment and overhead. Order volume rose about 10% over the same period, and that is already reflected in the numbers.
Trade-offs. The results were not all upside. Picks per hour fell about [15%] in the first [3 weeks] while people adjusted to RF scanning and wave picking. EWM also added [license and support costs] that WM did not carry. [The savings still covered those costs within the first year.]
What the client said
“We had to move off SAP WM, but we did not want to simply swap one system for another. SCM Champs rebuilt how our warehouse runs, and it shows in the numbers: inventory accuracy is above 99%, our AS/RS now feeds SAP without constant manual fixes, and handling cost per order is down by almost a quarter. Their consultants were on our warehouse floor through go-live, and that made all the difference.”
[VP, Operations]
Lessons learned
Some parts of the project went smoothly, and some did not. For teams planning a similar move, four lessons stand out.
Bring the automation vendor in early. Our 2-week delay came from the AS/RS side. Next time we would involve the vendor in design from week one, not week six.
Clean your master data before you build. We spent about 3 weeks correcting product dimensions and storage data. It is unglamorous work, but putaway rules fail without it.
Let the client run their own testing. It takes a little longer, but by go-live the key users already know the system, and support calls dropped off after week 2.
Start with one site. Getting the main distribution centre right gave us a template for the other three, which are being rolled out now.
Technologies used
| Technology | Role in the project | Impact |
| SAP S/4HANA | Single core system for orders, stock and finance | Running EWM inside it kept the warehouse on the same data as the rest of the business and avoided a second system and its interfaces. |
| Embedded SAP EWM | Replaced SAP WM as the warehouse management engine: putaway, wave picking, replenishment, cycle counting, and batch and expiry control | Behind the gains in inventory accuracy and picking accuracy |
| SAP MFS (Material Flow System) | Direct, standard connection between EWM and the AS/RS | Replaced the custom interface that failed few times a month; manual stock fixes fell from about 40 to fewer than 5 a month |
| AS/RS | Automated storage and retrieval at the main distribution centre | Its movements now flow to EWM through MFS, so automated and manual stock sit in one system of record. |
| SAP TM | Shipment planning | Tells the warehouse which truck leaves when, so wave picking follows the actual loading plan. |
| RF scanning | Handheld scanners for receiving and picking | Confirms each transaction at the point of work and supported the drop in picking errors from 2.8% to 0.6%. |
| Batch and expiry management | Lot and expiry tracking within EWM | Enforces first-expired, first-out in the system, which matters most for the chilled and frozen range |
| Labour tracking | Simple labour tracking within EWM | Gives supervisors picks per hour by shift |
Planning a move from SAP WM to embedded EWM?
If your warehouse is struggling with unreliable stock data, picking errors or a fragile automation interface, SCM Champs can help you work out the right EWM model for your sites. Book a Free Warehouse Assessment to get started.