SAP EWM in intralogistics.

Streamlined warehouse management across two locations – SAP EWM implementation at Ultra-Pharm.

How a mail-order retailer of medical supplies moved its warehouse management from Sage to a decentralised SAP EWM – close to standard, paperless and scalable.

Get a no-obligation consultation now.

The SAP EWM implementation at Ultra-Pharm began with a legacy system: warehouse management and ERP had been running on Sage for over 20 years. For a mail-order retailer of medical supplies serving both B2C and B2B customers – a business that depends on speed, reliability and complete documentation – this had become a brake on growth. Together with status C, it was replaced by a deliberately lean SAP warehouse management solution built on a decentralised SAP EWM – close to standard, paperless and spanning two warehouse sites. The ambition sounds like a contradiction, yet it ran through the entire project as its guiding principle: to think a system with a reputation for complexity so simply that it remains manageable in day-to-day operations – and still grows with the business.

Project

  • Replacement of warehouse management and ERP after more than 20 years on Sage

  • Implementation of a decentralised SAP EWM across two warehouse sites

  • Digitalisation of the paper-based picking process (RF UI / mobile data entry) incl. goods receipt area.

  • Parallel ERP implementation on SAP S/4HANA (by partner PIKON)

Industry

  • Mail-order retail of medical supplies, e-commerce (B2C & B2B)

Time period

  • November 2025 – May 2026

Achievements

  • Lean, standard-based EWM operation – deliberately kept slim and designed to scale

  • Picking performance at the Hilter site almost doubled

  • Paperless picking process via mobile data entry (RF UI)

  • Four delivery types distinguished (standard, single-line, one-piece, B2B); orders can be prioritised

  • HU completion via a purpose-built RF enhancement with just a few scans instead of the time-consuming /SCWM/PACK

  • Two sites separately analysable in the EWM monitor via shipping office assignment

Starting point: paper-based warehouse management and stock discrepancies.

What had worked for years had become a brake. Significant stock discrepancies had built up in the legacy Sage system. Picking was paper-based, using printed lists – batch numbers written by hand on the pick slip, and the slips then archived in a box. On top of that, storage bins appeared unsorted on the pick lists, and single-item orders ran through the warehouse alongside standard orders – with no optimised pick path. Anyone who records batches by hand on paper knows the risk: every transcription error costs time and, particularly in pharmaceutical and healthcare fulfilment, traceability. A process that neither scales with growing order volumes nor delivers the transparency this market demands.

Added to this was the structure: Ultra-Pharm operates two warehouse sites with different requirements – one with a high share of bulky goods, the other with a classic product range. Both needed different process variants, yet were to converge in a shared, future-proof SAP warehouse management system.

Objective: implement a decentralised SAP EWM the lean way – in parallel with SAP S/4HANA.

At first, the objective sounds like a contradiction: a lean, highly scalable warehouse process – and this on the basis of SAP EWM, of all systems, one that many label “powerful and complex”.

This is exactly where status C came in. The approach: think EWM consistently lean – set up as close to standard as possible, with processes kept as simple as possible for the people on the warehouse floor, and an architecture designed so operations can grow later. A decentralised EWM was deployed, decoupling warehouse operations from the ERP migration running in parallel.

That migration was the real reason for the project duration from November 2025 to May 2026: at the same time, partner PIKON was implementing a new ERP based on SAP S/4HANA. Two fundamental system changes under one roof – tightly scheduled, with a clear division of responsibilities.

Approach: fit-to-standard workshop and SAP EWM implementation in three sprints.

Rather than reinventing the warehouse from scratch, the project started where SAP already provides answers. In a fit-to-standard workshop, status C presented the standard scope items and worked with the key users to establish where the standard holds – and where genuine gaps exist. The approach was documented throughout:

  • Signavio: scope items mapped as processes and transferred to Jira.

  • Jira: GAPs assigned to the relevant process as user stories and tracked to completion.

  • Three sprints: two up to go-live, a third for process optimisation afterwards.

This kept it visible at all times which processes run on standard and where deliberate refinements were made. That is the essence of the lean approach: start by addressing each requirement through customising, and then check where further refinement is needed.

Fabian Schlisio

Logistics Planner, Ultra-Pharm

“Replacing our Sage system, which had grown over more than 20 years, was a big step. The fact that this led us to a decentralised SAP EWM solution that cleanly maps our two warehouses with their very different requirements convinced us. The batching processes in particular (one-piece, single-line) have had a positive effect on picking performance.”

Picking in SAP EWM: single-line, one-piece and B2B – prioritised and RF-based.

A lean EWM must not mean sacrificing performance. Despite the standard-based implementation, Ultra-Pharm was not to forgo high-performance picking processes – and it didn’t have to.

Ultra-Pharm distinguishes four delivery types: standard deliveries as well as the single-line and one-piece (OnePiecer) processes and B2B deliveries. Orders can also be prioritised – Amazon orders, for example, leave the warehouse faster. The pick cart is also mapped via SAP EWM RF. None of this required custom development – it was achieved by configuring queues and warehouse order creation rules – using the system’s own tools, cleverly parameterised.

The mobile data entry processes (RF UI) replaced the paper process and increased picking performance. A standard RF enhancement was used here: wThe picking process was therefore modelled within the system using a picking trolley. In future, staff will thus be guided through the process independently and systematically.

What this means in operation is most evident in the so called volume batching: Instead of processing OnePiecer orders alongside standard orders, EWM groups them by type, limits them by volume and guides the pickers through the warehouse along an optimised route. Although performance could not be measured in the legacy system, the comparison based on Ultra-Pharm’s many years of experience is clear: at the Hilter site, picking performance has roughly doubled, and it has risen noticeably at the Füchtorf site as well.

The lean approach also shows in packing. The SAP standard provides for packing via transaction /SCWM/PACK and completing the handling unit (the shipping carton) there – for the customer, this was too time-consuming in daily operations. So a standard RF enhancement was created that lets staff complete HUs with just a few scans directly on the scanner. Only special cases – such as recording serial numbers or batches – still run via /SCWM/PACK.

The special thing: there is nothing special – everything stays within the SAP standard.

Perhaps the most important point of this project sounds unspectacular: nothing was built outside the standard. SAP EWM ships with over 800 BAdIs, plus RF enhancements, the Post Processing Framework (PPF) and monitor enhancements – all standard tools for adapting the system to a customer’s processes. Those who know them adapt EWM without leaving the standard. That is the difference between “adapting to the system” and “developing around it”.

For Ultra-Pharm, this meant in concrete terms:

  • EAN logic: Since several companies use the same EWM, a standard class was replaced so that articles are found correctly under all relevant EAN types – not a BAdI, but the replacement of a standard class provided for exactly this purpose.

  • Completeness Check: Before a handling unit is completed, the system checks whether the associated outbound delivery order has been fully picked – a safeguard that matters particularly in pharmaceutical and healthcare fulfilment.

  • RF and Packaging Extensions: As described above, implemented as standard RF enhancements.

No middleware, no special path: that is exactly what keeps the system maintainable, reduces sources of error and makes future updates easier.

Two warehouse sites, separately analysable in one SAP EWM.

One system for two warehouses of opposite character – bulky goods here, a classic range there – only works if each site still retains its own view. That was precisely the requirement, and it was solved without a second system landscape.

The key lies in the master data: Here, too, the tried-and-tested EWM approach has proved its worth. By setting up a second dispatch centre, the two sites were able to be systematically separated. In the SCU hierarchy, these shipping office SCUs are assigned as subordinates of the warehouse SCU (business attribute “Warehouse”). As a result, each site can filter the outbound deliveries relevant to it in the warehouse management monitor via its shipping office. The actual separation of work control is achieved through separate queues per site with distinct naming – so the warehouse orders and waves of the two sites run separately and without affecting each other. In practice this means: each site sees at a glance where backlogs are forming, processes its own queues independently and carries clear responsibility for its throughput – without disrupting the other site’s processes.

The result is a warehouse operation that delivers three things at once: close to standard and therefore low-maintenance, lean and therefore manageable for users, and scalable – the architecture is designed so that further processes, volumes and, in future, a third site can grow with it without re-laying the foundations.

What the SAP EWM implementation at Ultra-Pharm shows for other projects.

The concern that SAP EWM is “too big” for one’s own operation often leads to the wrong alternative – a smaller stand-alone solution that blocks the path to S/4HANA. The Ultra-Pharm case shows: this calculation doesn’t add up if you frame it wrongly. Whether the legacy system is an older warehouse software such as Sage here or an existing SAP WM – EWM can be deliberately implemented lean and still run high-performance processes such as batching, prioritisation and mobile picking, entirely within the standard.

The transferable lesson lies less in the technology than in the approach. Anyone planning an EWM implementation should run two questions against their own core processes: Which of them does the SAP standard already cover? And where does a standard enhancement tool – BAdI, RF enhancement, PPF or monitor – suffice instead of custom development? Those who implement this way keep complexity low and remain future-ready.

  • Elisabeth Seber

    SAP Consulting, status C AG

    “The art lay not in exhausting EWM’s full potential, but in deliberately keeping it slim. We first looked at what the standard can do – and only where Ultra-Pharm’s processes genuinely required it did we tailor it to the customer with standard enhancements. Among them BAdIs, RF enhance-ments and PPF actions – all 100% standard-based enhancement concepts, no special path. That keeps operations main-tainable and lets the system grow with the business.”

  • Sergei Püschel-Schlotthauer

    SAP Development and Consulting, status C AG

    “Two system changes under one roof – the EWM implementation and, in parallel, the S/4HANA migration by PIKON – demand a clear division of responsibilities. That is exactly what the collaborative partnership in this project made possible.”

Are you planning an SAP EWM implementation and wondering how lean it can be?

Let's discuss this during a no-obligation initial consultation.

For a no-obligation initial consultation.

Frequently Asked Questions About SAP EWM Implementation.

SAP WM vs. SAP EWM – What's the Difference?

SAP WM (Warehouse Management) is the older warehouse management module, while SAP EWM (Extended Warehouse Management) is its more powerful successor with more granular process control. During a migration—such as Ultra-Pharm’s switch from Sage to a decentralized SAP EWM—EWM can be intentionally set up in a streamlined manner without utilizing the full range of functions from the outset.

What does a decentralized SAP EWM mean?

A decentralized warehouse management system (WMS) decouples warehouse operations from the ERP system. This is particularly useful when an ERP migration is taking place at the same time—in Ultra-Pharm’s case, the S/4HANA implementation by PIKON. This allows both system changes to be implemented in parallel with a clear division of responsibilities.

What is the process for implementing a "Fit-to-Standard" solution in SAP EWM?

In the Fit-to-Standard workshop, the standard scope items are presented, and the gaps (GAPs) are identified in collaboration with the key users. These are documented (at Ultra-Pharm in Signavio and Jira) and implemented in sprints. The goal is to stay as close as possible to the SAP standard and to make only targeted enhancements.

Is it possible to speed up order picking in SAP EWM without custom development?

Yes. Batching methods such as single-line and OnePiecer processes, the distinction between B2B shipments, the prioritization of individual orders, and the picking cart logic via SAP EWM RF can all be implemented through the configuration of queues and warehouse order creation rules—all within the standard system. Standard extensions such as BAdIs, RF apps, or PPF supplement this only where customer processes require it.