Where do you post stock movements: at the shelf or later at a desk? In one warehouse, movements were noted on paper and keyed in later. We built mobile apps with SAP Build Apps that handle goods receipt, transfers, stock counts and shipping right on the handheld. With barcode scanning, offline capable and booked straight into S/4HANA.
Where do you post stock movements: at the shelf or hours later at a desk? And how often does the stock in SAP still match the shelf by then?
At one manufacturer, warehouse movements were noted on paper and keyed in later at a desk. We built mobile apps with SAP Build Apps that handle goods receipt, transfers, stock counts and shipping right on the handheld. With barcode scanning, offline capable and posted to S/4HANA in real time.
In many warehouses there is a gap between what happens at the shelf and what the system shows. Here it worked like this: goods receipt, transfers, stock counts and shipping ran on paper and fixed terminals. Scanning or noting happened at the shelf, and the movement was keyed into SAP later at a desk.
Time is lost between the two, and accuracy along with it. Until it is booked, SAP shows stock that no longer exists in reality. Notes get lost, the desk entry gets postponed, and in a dead spot at the back of the racks the best desktop screen is no help. The warehouse works mobile, but the system only at the desk.
We built a set of mobile apps with SAP Build Apps, the low-code environment on SAP BTP at the time. They handle the core warehouse processes right on the handheld: goods receipt, transfers, stock counting and packing shipments.
Scanning runs by barcode, fast and without retyping. Postings go in real time through OData and REST straight into S/4HANA. If the network drops, the app keeps working offline and syncs automatically later, without losing a record. Validation and error handling sit on the device itself, so wrong entries never reach the system in the first place. And the interface is made for the warehouse floor: high contrast, large touch targets, usable with gloves and on ruggedized handhelds.
From process discovery to rollout on the devices.
Which warehouse processes, which devices, which steps at the shelf?
Build the apps in SAP Build Apps: scanning, validation, offline buffer and OData connection.
Test on the real handhelds, with the warehouse staff, under real conditions.
Roll out the devices, train the staff, hand over cleanly to operations.
Postings now happen where the goods move, not later at a desk. Stock in S/4HANA matches the shelf because the booking runs immediately. Less manual entry means fewer typos and fewer stock errors. And offline capability keeps work going even in a dead spot.
That such apps could be built quickly with SAP Build was backed by a GigaOm study cited by SAP: development with SAP Build was about three times faster than traditional custom development. For the warehouse, though, one thing mattered most: the worker scans, and the system is right.
A warehouse is a harsh environment for IT. Metal racks swallow the signal, it is cold, dusty and busy, and no one walks to a terminal for every posting. Tie warehouse processes to a fixed desk and you defer the data entry and accept stock discrepancies.
Mobile and offline are not extras here, they are the actual requirement. Scan at the shelf, book in real time, keep working without a network: that is the difference between stock you trust and stock you keep correcting.
Part of an honest account is this: shortly after the project wrapped, SAP discontinued SAP Build Apps as a standalone product (as of March 2026, see the SAP deprecation announcement). Existing environments keep running for now, but SAP no longer builds new projects on this tool.
For the project described here, that changes nothing: the apps are built, in use and still posting to S/4HANA. What remains from this case is not the tool but the lesson behind it: warehouse processes belong mobile and offline at the shelf, not at a fixed desk.
We know both sides: the mobile work at the shelf and what has to happen behind it in SAP. Barcode scanning, offline concepts and clean posting into S/4HANA. The processes behind them hold, independent of any single tool. How we integrate larger SAP landscapes is shown in our reference on the S/4HANA integration at an automotive supplier, and you will find an overview of our services under SAP Consulting. In every project, a founder sits at the table, not a pyramid of juniors.
Your warehouse works mobile, your SAP system only at the desk? Let's talk for 30 minutes. Concrete, no sales pressure.
Send us a note or book a short meeting.
