# How to add a mobile app to Dynamics 365 Finance and Supply Chain > Source: https://netray.co/integrations/dynamics-365-fscm-mobile-app > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Integrations ## Short answer Start with Microsoft's own Warehouse Management mobile app and production floor execution before building anything. For gaps such as approvals, inspections or field tasks, add a Power Apps or custom app over OData data entities and custom services, and plan separately for offline use. ## System Microsoft Dynamics 365 Finance and Supply Chain ## Capability mobile-app ## Intro Most Dynamics 365 Finance and Supply Chain users sit at desks, but the people who create inventory truth do not: receivers, pickers, machine operators, inspectors and field technicians. If they cannot record events at the point of work, transactions are batched at the end of the shift and the ERP is a record of what was believed, not what is. Microsoft supplies a Warehouse Management mobile application that runs mobile device menu items on Android, iOS and Windows, and a production floor execution interface for touch devices on the shop floor. Those cover core flows well, and they should be the first choice because they follow the system's own validation and security. This page is for the remaining gaps: the flows Microsoft does not ship, the ones where you need a different user experience, or environments where the network is unreliable. It describes the integration surface, an honest view of offline, and a build path. ## Use Cases ### Warehouse receiving, picking and counting **Description:** Use the warehouse management mobile app with mobile device menu items for receiving, put away, picking, movement and cycle counting, with barcode scanning and work-based directing. ### Production floor labor and job reporting **Description:** Operators clock on to jobs, report progress, scrap and consumption through the production floor execution interface or a tailored app that calls the same journals. ### Mobile approvals **Description:** A lightweight app or Power App lists pending workflow items for managers with the key fields and a complete action under their identity. ### Quality inspections on the floor **Description:** Inspectors enter test results against quality orders from a tablet, with photo capture attached through document handling. ### Field service and delivery confirmation **Description:** Technicians and drivers confirm delivery, capture signatures and record parts used, posting to the relevant order or journal. ### Asset and tool tracking **Description:** Scan asset or tool tags to log location changes or maintenance requests in asset management. ## System Surface Warehouse Management mobile app and mobile device menu items, configurable without code (menu item, display fields, steps), extendable with X++ for custom steps and work-order types. Production floor execution interface (touch, shop-floor oriented) for job registration, with configuration of what operators see and report. OData v4 data entities and custom services under /data and /api/services for any custom app, authenticated by Entra ID. For user-level security, use delegated sign-in and do not funnel everyone through one service identity. Power Apps with the Finance and Operations connector or Dataverse virtual entities for forms such as inspections and approvals, subject to connector limits and licensing. Barcode handling: GS1 and custom barcode setups in the ERP resolve scans to items, lots and serials, which a custom app should reuse rather than reinvent. Offline: the standard warehouse app requires connectivity. Offline capable behavior generally needs a custom store-and-forward design with conflict handling, since the ERP expects online validation. ## How It Works ### Inventory the flows **Detail:** List each task by role, frequency and network quality. Mark which are covered by the warehouse app or production floor execution. ### Configure the standard app first **Detail:** Set up mobile device menu items, work-user profiles and barcode rules, test on rugged scanners, and capture what is truly missing. ### Pick the app technology **Detail:** Power Apps for forms and approvals, a native or cross-platform app for scanning-heavy or offline needs, or a web app on tablets for shop-floor kiosks. ### Design the API layer **Detail:** Expose only the operations needed as custom services (for example report operation progress) instead of letting the app write raw journals. ### Authenticate users **Detail:** Use Entra ID sign-in with the user's own security roles, and handle shared devices through quick badge or PIN flows mapped to individual users. ### Handle poor connectivity **Detail:** Queue actions locally with idempotency keys, show clear status, and reconcile when online. Decide in advance which actions are never allowed offline, such as inventory reservations. ### Pilot and instrument **Detail:** Run one line or one warehouse zone, log every failed call, and measure scans per minute and error rate before rollout. ## Example Flows ### Operator reports progress on a production job **Trigger:** An operator scans a job card at a station. **Steps:** - The app resolves the production order and operation from the barcode. - It shows quantity expected and routing instructions. - The operator enters good and scrap quantities. - A custom service posts the route card journal under the operator's identity. - The screen shows the updated remaining quantity. **Result:** Production status and labor are posted at the time of work, so planning and costing use current data. ### Inspector records a quality result with a photo **Trigger:** A quality order is assigned for an incoming lot. **Steps:** - The inspector opens the assigned order on a tablet. - The app lists the tests and acceptable ranges. - Values are entered, a photo is taken and attached. - The service writes results and the quality order outcome follows the configured logic. **Result:** Results and evidence are on the quality order in the ERP, and failed lots are blocked before use. ## On Prem Shop-floor networks are often segmented, and in Local Business Data deployments the app must reach the on-premises AOS endpoints with AD FS authentication, usually over a VPN or a reverse proxy. Keep device management (MDM) local, scope the app to the plant network and cache read-only reference data (items, locations) on the device. Any AI feature in the app, such as reading a label or answering a question, can call a model hosted in the plant so images and queries never leave the site. Plan for downtime procedures if the network or the ERP is unavailable. ## Security - Sign users in individually and enforce ERP security roles; avoid shared service accounts for postings. - Use MDM, device PINs and remote wipe on scanners and tablets. - Validate every request server-side, not just in the app UI. - Idempotency keys on postings stop duplicate journals after retries. - Limit offline caches to non-sensitive reference data and encrypt them. ## Options ### Standard warehouse app and production floor execution **Fit:** Core receiving, picking, counting and job reporting flows. **Effort:** Configuration measured in days to weeks, plus device rollout. ### Power Apps over the connector **Fit:** Approvals, inspections and simple field forms with moderate volumes. **Effort:** Weeks, with licensing and throttling to review. ### Custom or partner-built app **Fit:** Heavy scanning, offline needs, custom UX or AI features such as label reading. Netray can build the AI layer and integration with your app partner. **Effort:** Typically several weeks to a few months depending on flows. ## Pitfalls - Building custom screens before configuring the standard app duplicates work and diverges from future updates. - Offline requirements are costly; confirm they are real before committing. - Mobile menu items and work user setup are per warehouse or legal entity and are easy to misconfigure. - Direct writes to inventory journals skip the work logic that warehouse management relies on. - Rugged scanner browsers and OS versions lag; test on actual devices. ## Faq ### Does Dynamics 365 Finance and Supply Chain have a mobile app? **Answer:** Yes, for specific areas: the Warehouse Management mobile app and the production floor execution interface are the main shop-floor options. Other older or general mobile experiences are less central, so check what your release currently supports. ### Can I build my own app on the ERP? **Answer:** Yes, using OData entities and custom services with Entra ID authentication, or Power Apps. Use custom services for postings so business logic and validation run server-side. ### Does it work offline? **Answer:** The standard warehouse app needs a connection. Offline behavior requires a custom store-and-forward design with careful limits on what can be done without a live ERP check. ### Can operators share a tablet? **Answer:** Yes, with a badge scan or PIN that maps to an individual ERP user so postings are attributed correctly. Avoid a single generic login. ### Where does AI fit in a mobile app? **Answer:** Typical uses are reading labels or documents from a photo, answering questions from procedure documents, or suggesting a putaway location. Run it on a plant-hosted model when images or procedures are controlled data. ## Search terms dynamics 365 mobile app, dynamics 365 warehouse management mobile app, d365 fo shop floor app, dynamics 365 production floor execution, dynamics 365 barcode scanning mobile, power apps dynamics 365 finance and operations, dynamics 365 supply chain mobile offline, custom mobile app for dynamics 365 f&o --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json