Does this replace SAP EWM?

No. SAP keeps the stock, status and rules. The app is a faster front end that posts to SAP through released APIs.

Does it work without EWM?

Yes, on SAP IM with QM as well.

Does it change the SAP core?

No. It is a clean-core, side-by-side extension.

Are you an SAP partner?

No. We are an independent studio. We build beside SAP using its released APIs and work with your SAP partner, who stays responsible for SAP itself. If you need the integration certified by SAP, we scope that into the project.

A studio service

GMP warehouse floor app for SAP EWM & IM SAP's rules, on a screen the floor can use.

SAP already enforces quarantine through QM usage decisions, FEFO through shelf-life rules and storage conditions through EWM. What slows the floor is the screen. We build scanner-first apps that sit on top of SAP, show operators exactly the step in front of them, and post every movement back to SAP, so the rules stay in SAP and the work gets faster.

See the packages →All supply chain modules

GMP warehouse floor app for SAP EWM & IM

The facts behind this module

21 CFR 211.82(b)

“Components, drug product containers, and closures shall be stored under quarantine until they have been tested or examined, whichever is appropriate, and released.”

Source: US FDA, 21 CFR 211.82(b).

21 CFR 211.150(a)

Distribution procedures shall include “a procedure whereby the oldest approved stock of a drug product is distributed first.”

Source: US FDA, 21 CFR 211.150(a).

21 CFR 211.184(c)

Records shall include “an individual inventory record of each component, drug product container, and closure and, for each component, a reconciliation of the use of each lot.”

Source: US FDA, 21 CFR 211.184(c).

Quoted from the sources linked. We add no estimates of our own.

What it looks like

Put-away — handheld view

To put away

To pick

Counts due

Blocked lots

Lot	Material	Storage condition	Bin	Expiry	Status
L-55120	Cell culture medium	2–8 °C	CR-02-14	03/2027	Quarantine
L-55118	Buffer salt	15–25 °C	AM-11-03	09/2028	Released
L-55103	Filter capsule	15–25 °C	AM-07-21	01/2029	Released
L-55091	Resin	2–8 °C	CR-01-06	11/2026	Rejected

Interface concept with invented sample data, shown to illustrate the design. It is not a screenshot of a live system.

How it connects

SAP S/4HANA

Batches, QM, EWM, planning
Stays the system of record
Core left standard, nothing changed inside

⇄released APIs only

The app, in your tenancy

SAP BTP, Azure or AWS, your region
Audit trail, roles, single sign-on
Read-only in a Pilot; write-back by agreement

⇄scoped access

People and plant systems

Your teams, by role
Sponsors, each to their own data
MES, LIMS, QMS and logger platforms

SAP's clean-core rule, quoted: “Extensions must be developed using only released local or remote public SAP APIs, BAdIs, or ABAP RESTful application programming model business object (BO) extension points.” SAP PRESS, SAP S/4HANA Clean Core: Principles, Benefits, and Best Practices.

N° 01What SAP already covers

We start from SAP, not against it.

SAP EWM and IM with QM enforce stock status, shelf life and FEFO. This module adds a scanner-first screen and floor-specific steps such as status labels and storage-condition checks at the bin. This module is a side-by-side extension: it reads and writes SAP only through released APIs and leaves the core standard.

N° 02Where it helps

Four situations this module is built for.

Transactions built for the office

Multi-screen SAP transactions on a handheld. We reduce each task to scan, confirm, done.

Status not visible on the pallet

Status labels printed from SAP status at receipt and on every change.

Wrong-zone put-away

Storage condition checked at the bin scan before SAP is posted.

Counts typed in later

Cycle counts scanned against live SAP stock, variances routed for review.

N° 03What the module covers

Scope, in plain terms.

Receipt & put-away

Scan, label, check storage condition, post to SAP.

Picking & issue

FEFO picks proposed from SAP, issued against the process order.

Counts

Scanned cycle counts with variance review.

Labels & devices

GS1 labels and handhelds such as Zebra and Honeywell.

N° 04For each person in the decision

One page, six readers.

Supply chain lead

The scope above, three fixed-scope packages with prices, and a read-only Pilot you can run on one site before committing.

QA and validation

GAMP 5 Category 5 development documents, executed developer IQ/OQ evidence, Annex 11 and Part 11 controls in the GxP-ready package. You run and sign validation.

IT and your SAP team

Released SAP APIs only, no changes inside SAP, one least-privilege technical user, deployed in your own tenancy and region.

Sponsor-facing teams

Each sponsor sees only their own data, enforced in the data layer, with every access logged.

Procurement

Fixed scope and price per package, a written not-included list, and our vendor questionnaire answered in full on request.

Finance

The price shown is ours. SAP licences, including any SAP Digital Access for documents created in SAP, hosting and validation effort are yours and are listed as not included.

N° 05The Pilot, week by week

Eight to ten weeks, read-only from SAP.

Weeks 1–2: scope and access

Requirements workshop, the list of SAP APIs to be read, a technical user from your SAP team, and sample data agreed.

Weeks 3–5: build

The module built in your tenancy against your SAP test system, with a working demo every week.

Weeks 6–7: your data

Connected to the agreed SAP data, tested by your users, findings fixed.

Weeks 8–10: live on one site

Go-live for up to 25 users, a handover session, and a written decision paper for the Production package.

N° 06Your three options

Inside SAP, packaged, or beside SAP.

Customise inside SAP

Done by your SAP partner. SAP's clean-core rule limits extensions to released APIs and extension points, and each change follows your SAP change and validation process.

Buy a packaged product

A vendor's standard product and roadmap, with its own licence, validation package and integration to your SAP.

Build beside SAP (this page)

An app scoped to your process, in your tenancy, connected through released SAP APIs, with the source code and documentation handed to you.

N° 07AI assists

Where AI helps, and where a person decides.

Designed to the draft EU GMP Annex 22: predictive models are static, versioned and show their confidence; generative tools only draft for a person to confirm. No assist releases, rejects or ships a lot.

Label and document reading

Supplier labels and delivery notes read at receipt and pre-filled for the operator to confirm. Generative, non-critical, human confirms.

Count anomaly flag

A static model flags counts unlike the item's history, with confidence, for review before posting.

N° 08Investment

Pilot, production, or GxP-ready.

Pilot

From $48,000

One site, read from SAP through released APIs, live in 8–10 weeks.

Receipt, put-away and status labels for one warehouse
Read and post through SAP APIs
Read-only connection to SAP S/4HANA (OData APIs and CDS views), no core changes
Audit trail on every record, role-based access, SSO with your identity provider
One site, up to 25 named users
Not included: write-back to SAP, electronic signatures, validation documentation, SAP BTP licences

Start the project

Recommended

Production

From $78,000

Two-way with SAP and one more plant system, across sites.

Everything in Pilot
Picking, issue and cycle counts
Label printers and handhelds across sites
Two-way integration through SAP APIs or SAP Integration Suite, clean-core compliant
Digital Access check with your SAP licence team before any write-back is switched on
Up to three sites and 250 users
60 days of hypercare after go-live
Not included: validation documentation, SAP or BTP licences (including any SAP Digital Access your contract requires for documents created in SAP), SAP-side configuration by your SAP partner

Start the project

GxP-ready

From $118,000

Built and documented for GMP use.

Everything in Production
21 CFR Part 11 / EU Annex 11 electronic signatures and record controls
GAMP 5 Category 5 SDLC pack: URS trace matrix, FS/DS, code review records
IQ/OQ scripts with executed developer evidence; change control for later releases
Not included: validation execution and QA sign-off (your CSV team), hosting qualification, SAP licences

Start the project

Before you buy

What you get

An independent build that connects to SAP only through SAP's released APIs
A read-only Pilot that creates nothing in SAP, so it carries no SAP licence exposure
Delivery alongside your SAP partner and IT, who keep control of SAP itself

What we don’t do

SAP licences, or SAP Digital Access for documents a two-way build creates in SAP
Changes to your SAP configuration or custom code inside SAP
SAP certification of the integration, unless you ask us to scope it in

DesignKompanie is an independent studio and is not affiliated with, endorsed by or a partner of SAP SE. SAP and SAP S/4HANA are trademarks of SAP SE.

N° 09Questions

The answers we give most often.

Does this replace SAP EWM?: No. SAP keeps the stock, status and rules. The app is a faster front end that posts to SAP through released APIs.
Does it work without EWM?: Yes, on SAP IM with QM as well.
Does it change the SAP core?: No. It is a clean-core, side-by-side extension.
Are you an SAP partner?: No. We are an independent studio. We build beside SAP using its released APIs and work with your SAP partner, who stays responsible for SAP itself. If you need the integration certified by SAP, we scope that into the project.

N° 10Related

Start your book

Planning the GMP warehouse floor app for SAP build?

Tell us your sites, the systems you run and what has to change. You'll get a scoped plan and a fixed price within two business days.

Start the project See the process