How to add a mobile app to SAP Business ByDesign
Short answer
Start with the mobile apps SAP offers for ByDesign for common roles, then fill gaps with a custom app that calls ByDesign web services or custom OData services, handles barcode scanning on the device, and queues work when offline. Keep the app narrow: a few scans and confirmations, not the whole ERP.
ByDesign's browser UI is built for a desk. Warehouse staff, production operators, service technicians and sales reps need a tool that works with gloves, a scanner or a phone camera, and that asks for three taps rather than a screen of fields. When the system does not offer it, they write on paper, text a supervisor, or keep a spreadsheet that someone types in later.
SAP has historically offered mobile apps for ByDesign for roles such as sales and approvals, and these should be your first check. For anything specific to your floor, such as moving stock between bins, reporting production quantities or logging service time, you will likely build or buy a small app over the supported web services.
The design constraint is that ByDesign is SaaS: connectivity is required and customers have no database access. The mobile app needs to cope with poor signal and make writes safe to retry.
What teams use it for
Goods receipt by barcode
Scan the PO or delivery note, confirm received quantities per line, and post a goods receipt. Over-receipt alerts appear immediately.
Stock transfers and picking
Scan source and target locations and the material to move stock, or confirm picks against an outbound delivery.
Production confirmation
Operators report quantity produced, scrap and time against a production order, with a scan of the order barcode.
Cycle counts
Count by location with the expected quantity hidden, then submit counts as inventory count documents for review.
Service technician work orders
View assigned tickets, record time and parts used, capture a customer signature and photos.
Sales rep order entry
Look up stock and prices, draft a quote on site, and send it for approval.
SAP Business ByDesign integration surface
- SAP-provided mobile applications for ByDesign for some roles, available for certain platforms; availability and capability depend on the release and have changed over time, so check what is current for your tenant.
- SOAP web services through Communication Scenarios and Arrangements for inventory, production, purchasing, sales and service documents.
- Custom OData and web services from the Cloud Application Studio, which are a good way to create mobile-specific endpoints returning only the few fields a scan screen needs.
- Report-based OData feeds for lookups such as stock by material and location, with filters for speed.
- Add-ins and mashups in the SDK that extend the browser UI, useful for tablets used in a kiosk style.
How it works
- 1
Inventory the tasks
Walk the floor and list the five or six actions that happen most. Time them. Pick the one with the most paper or double entry.
- 2
Check what SAP already offers
Review the mobile apps and any partner solutions for your release before building. A prebuilt app covering 80 percent beats a custom one.
- 3
Choose the client
A progressive web app is quick and avoids stores, but camera and scanner access varies. A native or cross-platform app suits rugged scanners and background sync.
- 4
Build a thin backend
Do not call ByDesign directly from the device. Put a small API in between to hold credentials, shape payloads, enforce idempotency keys, and log.
- 5
Handle identity
Sign users in with your identity provider, map to ByDesign users, and apply role checks in the backend before posting.
- 6
Plan for offline
Cache lookups such as open POs and locations, queue scans locally, and sync with retry and conflict messages when connectivity returns.
- 7
Pilot with one shift
Run beside the old method for a week, compare postings, fix scan edge cases such as damaged labels, then roll out.
Example flows
Receiving against a purchase order
Trigger: A truck arrives and the clerk opens the receiving screen.
- The clerk scans the PO barcode; the app fetches open lines through the backend.
- They scan each item or key a quantity; over-delivery beyond tolerance triggers a warning.
- On submit, the backend posts the goods receipt with an idempotency key.
- A label print is requested for putaway.
Result: Receipts post on the dock rather than hours later, and stock is visible to sales immediately.
Technician closes a service job
Trigger: A technician finishes work at a customer site with weak signal.
- They log hours, parts and a note, and capture a signature on the screen.
- The app stores everything locally with a pending flag.
- When signal returns, the queue syncs and the backend updates the service confirmation.
Result: Billing no longer waits for paper job cards to reach the office.
Keeping data on-prem
The ByDesign side is SaaS only, so there is nothing to install on-prem there. The mobile backend, scan processing and any AI features can sit in your own network or private cloud, with the device reaching them over VPN or a private access gateway. If you add features such as photo-based part recognition or voice notes converted into confirmations, run those models locally so photos of products, labels and customer sites do not go to a third-party API.
Security checklist
- Use mobile device management for company devices and block jailbroken or rooted ones.
- Never store ByDesign credentials on the device; use short-lived tokens issued by your backend.
- Encrypt the local offline queue and wipe it on logout or remote wipe.
- Authorise by role in the backend, for example only stores staff can post goods movements.
- Make writes idempotent and logged with device ID and user to survive retries and support audit.
Ways to get it done
SAP mobile apps or partner apps
Effort: Days to weeks for setup and training.
Best for standard roles such as approvals and sales if features match.
PWA over a thin backend
Effort: 3 to 6 weeks.
Cheap and quick for tablets and phones with camera scanning and modest offline needs.
Native app with rugged scanner support (Netray or another partner)
Effort: 6 to 12 weeks.
Warehouses and plants needing hardware scanners, robust offline sync and optional private AI features.
Pitfalls
- !Direct device-to-ByDesign calls expose credentials and make retries messy; use a backend.
- !Poor signal in warehouses and plants is the norm. Without a queue, scans are lost and users revert to paper.
- !Label quality drives scan success; poor barcodes will sink adoption faster than any software bug.
- !Posting authorisations in the mobile role may differ from those in the UI, so test with real user profiles.
- !Overbuilding the first release: a three-screen app people use beats a twenty-screen app they avoid.
Frequently asked questions
Does SAP Business ByDesign have a mobile app?
SAP has offered mobile apps for ByDesign for certain roles and platforms, but the portfolio has changed across releases. Ask your SAP partner what is supported in your tenant today, and test it before planning a custom build.
Can I use a handheld barcode scanner?
Yes, with a custom or partner app. Most rugged scanners run Android and can emit scans as keyboard input or through an SDK. The app should handle scan, validate against ByDesign data, and post through your backend.
Will the app work offline?
Only if you design it to. ByDesign needs connectivity, so the app caches reference data and queues transactions locally, then syncs. Decide up front which actions can be queued and how conflicts are shown to the user.
Which ByDesign interfaces should the app use?
Use the supported web services and custom OData or web services from the Cloud Application Studio, via a backend you control. Avoid screen scraping or unsupported calls, which break on upgrades.
Can AI be added to the mobile app?
Yes, for example voice-to-text for notes or photo capture of delivery notes feeding OCR. Keep a human confirmation before posting, and consider hosting the model privately if photos include sensitive customer or product information.
Want Mobile app working on your SAP Business ByDesign?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment