# How to build a mobile app for MRPeasy > Source: https://netray.co/integrations/mrpeasy-mobile-app > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Integrations ## Short answer Check what MRPeasy's own mobile and shop floor options cover first. For gaps, build a small web or native app over the MRPeasy REST API for barcode scanning, work order reporting and stock moves, with a local queue for poor connectivity. ## System MRPeasy ## Capability mobile-app ## Intro MRPeasy has its own mobile and shop floor features, and for many small shops they are enough. The reason people search for something more is specific: a scanner workflow that matches how their warehouse really works, a simpler screen for operators, a count process, or a way to capture photos and quality notes at the machine. Because MRPeasy is a cloud system with a REST API, a custom app is a realistic project. It reads and writes the same data, so the office sees reports as they happen. The risks are not the screens. They are connectivity in the back of a factory, scanning accuracy and keeping the app within what the API allows. ## Use Cases ### Scan to receive **Description:** Scan a purchase order barcode, confirm quantities per line and post the receipt from a handheld or phone. ### Pick for manufacturing order **Description:** Show the materials to pick for a work order and confirm each pick by scanning item and location. ### Report production progress **Description:** Operators start, pause and finish operations and report good and scrap quantities from a tablet at the machine. ### Stock transfers and counts **Description:** Move items between locations and run cycle counts by scanning, with variance review before adjustments. ### Quality checks with photos **Description:** Record an inspection result and photo against a work order or lot, for later review. ### Manager approvals on the go **Description:** Review and approve purchase orders or order changes from a phone with only the data needed to decide. ## System Surface - MRPeasy's built in mobile and shop floor options should be evaluated first; confirm current capabilities on your plan before building anything. - REST API with API key and secret; these are account level credentials, so a mobile app should call your own backend, not embed the key in the app. - Resources for items, stock, manufacturing orders, operations, purchase orders and locations; support for each action varies by API version, so verify in a test company. - Barcodes are your design: use item codes, order numbers or lot numbers printed as Code 128 or QR, and keep the format consistent. - Hosted SaaS: the app needs internet, so offline behaviour is something your app adds, not something MRPeasy provides. ## How It Works ### List the gaps **Detail:** Compare the native features to what operators actually do. Build only what is missing, such as a count flow or a pick screen. ### Put a backend in front of the API **Detail:** Create a small service that holds the MRPeasy credentials, authenticates users and exposes only the few endpoints the app needs. ### Choose the client **Detail:** A progressive web app on rugged phones or tablets is quickest. Native is justified for hardware scanner SDKs or heavy offline use. ### Design for scanning **Detail:** Large buttons, immediate audio and haptic feedback, and a rule that scan confirms the item before quantity entry. ### Handle offline **Detail:** Queue transactions locally with a unique id, sync when the connection returns, and show clearly what is pending. ### Resolve conflicts **Detail:** Check stock and order status at sync time; reject or flag transactions that no longer apply. ### Pilot on one process **Detail:** Roll out receiving or counting first, measure errors and time, then add the next. ## Example Flows ### Cycle count **Trigger:** A counter opens the count task for one aisle. **Steps:** - App lists locations and expected items. - Counter scans location and item and enters quantity. - Differences above a tolerance are flagged. - Supervisor approves and the adjustment is posted. **Result:** Counts are done with a scanner, with a clear approval before the stock changes. ### Operator reports a finished operation **Trigger:** An operator finishes a job at a workstation. **Steps:** - Scan the work order barcode. - Select the operation and enter good and scrap quantities. - App posts the report through the backend. - Next operation shows as ready. **Result:** The planner sees progress without anyone walking the floor. ## On Prem MRPeasy is cloud hosted, so there is no on-prem ERP database, but the mobile backend can still live inside your network or private cloud, with devices on factory Wi-Fi or VPN. Photos, notes and any AI features such as reading labels or summarising inspection notes can run on local models, so only the transaction data goes to MRPeasy. ## Security - Never embed the MRPeasy key in the app; use a backend and per user login. - Enrol devices in mobile device management and enable remote wipe. - Give operators only the actions their role needs, enforced by your backend. - Encrypt the offline queue on the device and clear it after sync. - Log device, user and transaction id for every posting. ## Options ### Use MRPeasy's own mobile features **Fit:** Best when they already cover receiving, picking and reporting for your shop. **Effort:** Hours to days ### Custom PWA over a small backend **Fit:** Good for specific flows, quick to iterate. **Effort:** 4 to 8 weeks ### Partner build such as Netray **Fit:** Useful when you want AI features on the device and an on-prem backend. **Effort:** 6 to 10 weeks ## Pitfalls - Replacing working native screens with a custom app adds maintenance with little gain. - Offline queues that replay old transactions can post against changed stock. - Labels that fail to scan in dirty or dim conditions stall adoption; test barcodes in place. - API rate limits matter when many operators sync at shift change. - Forgetting a rollback path for a bad posting leaves supervisors editing records by hand. ## Faq ### Does MRPeasy have a mobile app? **Answer:** MRPeasy provides mobile and shop floor options, but their scope changes between versions and plans, so check the current feature list. A custom app is worth considering only for flows those options do not cover. ### Can I scan barcodes with a phone? **Answer:** Yes. A phone camera works for light use, while rugged scanners with a hardware trigger are faster and more reliable for warehouse volumes. Either can feed a web or native app that calls your backend. ### Will it work offline? **Answer:** MRPeasy needs internet, so offline support has to be built into your app with a local queue and a sync step. Keep offline actions simple, such as counts and reports, and check conflicts when they sync. ### Is it safe to call the MRPeasy API from a phone? **Answer:** Not directly with the shared key. Route calls through a backend you control, authenticate each user and expose only the needed operations, so a lost phone does not expose the whole account. ### How long does a first version take? **Answer:** A single flow such as receiving or counting can be piloted in a few weeks if the API supports the needed transactions. The time goes into testing on the floor, not into the screens. ## Search terms mrpeasy mobile app, mrpeasy barcode scanning, mrpeasy shop floor app, mrpeasy inventory app, mrpeasy api mobile, mrpeasy handheld scanner, mrpeasy work order mobile, custom app for mrpeasy, mrpeasy cycle count app, mrpeasy offline --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json