How to build a shop-floor mobile app for Business Central
Short answer
Start with the standard Business Central mobile app and its camera barcode scanning, then build a custom app over API v2.0 or custom API pages only where task-specific screens, rugged handhelds or offline tolerance demand it. Keep screens narrow and let Business Central remain the system of record.
Warehouse and production staff do not want the full Business Central client on a small screen. They want to scan a bin, a lot and a quantity, confirm a pick or report output, and move on. The question is how much of that the standard app does for you, and where a purpose-built app earns its keep.
Business Central offers a mobile app for phones and tablets, supports camera scanning and role-centred pages, and has warehouse features such as directed put-away and pick. Many sites run well on that. Others need rugged scanners, fast keystroke flows, offline use in dead zones, or labor reporting that does not map to standard pages.
A custom app is a product you maintain: devices, updates, authentication and support. Treat that cost honestly before building.
What teams use it for
Receiving against purchase orders
Scan a PO barcode, confirm quantities per line and lot, and post a warehouse receipt or update the receive quantity, with over-receipt tolerance rules.
Picks and put-aways
Work through warehouse pick or put-away lines in bin sequence, scanning bin and item to confirm each move.
Production output and scrap reporting
Operators report output and scrap against a released production order through a simplified screen that posts to a consumption or output journal.
Physical inventory counts
Count by bin on a handheld, writing to the physical inventory journal with a recount workflow for variances.
Field service and delivery
Technicians and drivers view assigned work, capture signatures and photos and attach them to the related document.
Microsoft Dynamics 365 Business Central integration surface
- The Business Central mobile app for iOS and Android, with barcode scanning via the device camera, and the web client in a mobile browser for lighter use.
- Warehouse management features such as warehouse receipts, picks, put-aways and movements, plus inventory pick and put-away for simpler setups.
- REST API v2.0 and custom API pages for a custom app, with Entra ID OAuth 2.0 and mobile-friendly flows like MSAL.
- Journals (item, consumption, output, physical inventory) as controlled write paths for production and counting events, with batch templates restricting what can post.
- AL page extensions and role centres to simplify what the standard mobile app displays; third-party handheld products from AppSource are another route.
How it works
- 1
Test the standard app first
Configure role centres, simplified pages and camera scanning on real tasks with real operators. Document exactly what fails before building anything.
- 2
Choose the device
Phones with cameras suit light scanning. High-volume warehouses usually want rugged scanners with hardware triggers, which pushes toward a purpose-built or partner handheld app.
- 3
Design narrow screens
One task per screen, large targets, scan-first inputs. Remove anything the operator should not decide.
- 4
Expose a minimal API surface
Create custom API pages for exactly the reads and writes the app needs, rather than handing the app broad table access.
- 5
Authenticate properly
Use Entra ID with conditional access, or kiosk-style sign-in for shared devices, mapped to Business Central users and permission sets.
- 6
Plan for connectivity
Decide whether the app needs offline queueing. If so, design idempotent operations and conflict handling before writing UI code.
- 7
Pilot on one process
Roll out receiving or counting first, measure scan errors and time per task, then expand.
Example flows
Scan to receive a PO line
Trigger: A receiving clerk scans a PO label at the dock.
- App loads open lines through a custom API page.
- Clerk scans the item and enters or scans a lot.
- App validates quantity against outstanding and tolerance.
- It writes the receive quantity on the warehouse receipt line.
- A supervisor posts the receipt in Business Central.
Result: Receiving is faster and errors are caught at the dock, while posting stays controlled.
Operator reports output
Trigger: An operator finishes a batch at a work center.
- App lists released production orders for that work center.
- Operator enters good quantity and scrap with a reason.
- Entry goes to an output journal line for review or auto-post per policy.
Result: Production progress is visible in near real time without operators learning the full client.
Keeping data on-prem
On-premises Business Central supports the mobile app and APIs if the service tier is reachable from devices, typically through a VPN, reverse proxy or Wi-Fi inside the plant. Authentication options depend on version, so confirm whether Entra ID or another supported method is available. For sites with weak or no connectivity, a local gateway service on the plant network can queue transactions, but that is custom engineering. Any AI features such as photo-based part recognition can run on a local server rather than in a cloud service.
Security checklist
- Enforce device management (MDM) and screen locks, and use conditional access for Entra ID sign-in.
- Give mobile users narrow permission sets and journal batches that cannot post to unrelated areas.
- Do not embed credentials or client secrets in the app package; use user sign-in or a secure token broker.
- Wipe or revoke access quickly when a device is lost, including shared scanners.
- Log scans and journal writes with device and user for traceability.
Ways to get it done
Standard Business Central mobile app
Effort: Configuration measured in days
Phone or tablet users, camera scanning, light warehouse and field tasks.
AppSource warehouse or handheld product
Effort: Weeks including device setup
High-volume scanning with rugged devices and a vendor-supported UI. Check licensing and update cadence.
Custom app over APIs, built in-house or with Netray
Effort: Typically eight to sixteen weeks for a first release
Unique processes, offline needs or local AI features such as photo-based checks.
Pitfalls
- !Building a custom app before testing the standard one often duplicates what already works.
- !Offline mode without idempotent writes produces duplicate postings after reconnect.
- !Giving the app broad API access turns a lost device into a data breach.
- !Warehouse setup (bins, locations, item tracking) problems get blamed on the app, so fix master data first.
- !OS and Business Central release cycles require ongoing testing of custom apps.
Frequently asked questions
Does Business Central have a mobile app?
Yes, there are apps for iOS and Android, supporting phones and tablets, with camera barcode scanning. Functionality and form-factor support evolve with releases, so test the pages your operators use on real devices before deciding you need something custom.
Can I use rugged barcode scanners?
Often yes, either through the standard app with Bluetooth scanners that act as keyboards, or through an AppSource handheld product or custom app that supports hardware scan triggers. Evaluate scan speed and ergonomics in the real environment.
Does the app work offline?
Do not assume so. Standard capabilities depend on connectivity. Offline operation in a custom app means queueing writes locally and syncing later, which requires careful conflict and duplicate handling. Confirm current behaviour in Microsoft documentation for your version.
How should a custom app write to Business Central?
Through custom API pages or standard API v2.0, targeting journals or warehouse documents with controlled posting. Avoid direct posting from the device when a supervisor review step makes sense, and make every call idempotent.
Can this run on-premises?
Yes if devices can reach the service tier securely, and your version supports the authentication you need. Plan network access, certificates and device management, and consider local servers for any AI features so images and data stay inside the plant.
More for Microsoft Dynamics 365 Business Central
Want Mobile app working on your Microsoft Dynamics 365 Business Central?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment