Last Updated: April 2026
Maybe this sounds a bit familiar? A company rolls out a new ERP system and the office team loves it. Then someone hands a warehouse worker or a field technician a phone and says “you can do your timesheets in here now.” The worker opens the app, sees a screen built for a desktop user with a dozen fields they’ve never touched, and goes back to writing things down on paper.
That’s not a people problem. That’s a design problem. But with Acumatica’s mobile app customization you can quickly fix that.
See, Acumatica’s mobile app isn’t just a shrunken version of the desktop interface. It’s a configurable tool, and when you set it up right, it gives field workers exactly what they need and nothing they don’t. The difference between a mobile screen that gets used and one that gets ignored almost always comes down to how much thought went into building it.
What Acumatica’s Mobile Framework Actually Does
Acumatica’s mobile app runs on a framework that lets you define custom screens, control which fields appear, set their order, and determine what actions are available. You’re not locked into Acumatica’s default mobile layout for every screen. You can build views that match how your people actually work in the field.
The configuration happens through the Acumatica Mobile Application Framework, which uses a declarative markup language to define screens. If you’ve done any customization work inside Acumatica before, the approach will feel familiar. You define what a screen contains, and the framework handles rendering it on iOS or Android.
The most important thing to understand going in: mobile screens in Acumatica are separate from desktop screens. Changing the desktop layout doesn’t change the mobile layout, and vice versa. That’s a good thing – it means you can build a direct field view without touching anything else your office team relies on. Acumatica’s mobile framework documentation covers the full structure in detail.
How to Build Field-Friendly Screens
Before you open your customization editor, spend time with the people who will actually use the screen. This sounds obvious, but it’s skipped constantly. A field technician completing a service order has different needs than a warehouse worker confirming a receipt. Build for the specific job, not for a generic “mobile user.”
A few questions worth answering before you start:
What’s the one thing this person needs to do on their phone? Start there. If it’s logging time against a project, every other field on that screen is secondary. If it’s confirming a shipment quantity, that number needs to be front and center.
What information do they need to see, versus what do they need to enter? Read-only context fields (customer name, job number, site address) take up space but support accuracy. Don’t strip them out entirely just to simplify the screen. Make them visible but secondary.
What DON’T they need? Financial fields, internal reference numbers, system-generated data – these belong on the desktop view, not the mobile one. Removing them from the mobile screen isn’t limiting your workers, it’s respecting their time (and eyesight).
Once you know what the screen needs to do, you can start defining it in the mobile framework. Screens are built using YAML-style markup that specifies containers, fields, actions, and selectors. Acumatica’s Open University has course material on mobile customization that walks through building screens from scratch if you’re new to the framework.
Common Field Scenarios Worth Customizing
Here are a few examples of the mobile screen types we see come up for many manufacturing and distribution companies.
- Time entry. The default time entry screen works, but it’s built for completeness, not speed. A custom mobile time entry screen can default the project, task, and date based on context, leaving the worker to confirm or adjust the hours. That turns a five-minute process into thirty seconds.
- Inventory receiving. Field workers confirming purchase order receipts don’t need to see vendor payment terms or landed cost allocations. A custom mobile receiving screen shows the PO number, expected items, quantities, and a confirm action. That’s it. Acumatica’s purchase order and receiving functionality supports mobile receiving natively, and customization lets you tighten the interface around that workflow.
- Service order updates. Field technicians need to update job status, log materials used, and capture signatures. A well-built mobile service screen handles all three without requiring the technician to navigate multiple screens or scroll past irrelevant fields.
NOTE: If you’re using Acumatica for manufacturing or distribution and your field teams aren’t taking advantage of the mobile app, it’s usually because the default screens don’t fit their workflow. Customization can solve that issue—reach out to us and we’ll be happy to help.
Testing Before You Deploy
This can be a crucial step. The screen might look fine when someone tests it in the office on a clean wifi connection. But, it looks totally different when a warehouse worker is using it on a cellular signal, with gloves on, under a loading dock light.
Test your mobile screens in real conditions. Have actual users walk through the workflows before you push anything to production. Pay attention to which fields require too much scrolling to reach, which actions aren’t obvious, and where people hesitate. Those friction points are your revision list.
Acumatica’s mobile framework lets you iterate quickly. Adjusting field order, adding a default value, or removing a container that’s creating confusion is straightforward once the screen is built. Build, test with real users, adjust, and repeat. A little extra time here goes a long way in the end.
Connecting Mobile Customization to Your Broader Acumatica Setup
Mobile screens don’t exist in isolation. They pull data from and push data to the same records your desktop users work with. That means your Acumatica security roles and user permissions apply to mobile screens too. A field worker who can’t edit a record on the desktop won’t be able to edit it on mobile either. Before you roll out custom screens, make sure the users who need them have the right access configured.
Make sure to coordinate mobile customization with workflow and approval automations. If a field technician submitting a service order kicks off an approval process, validate that the mobile screen gives them the context they need to submit accurately. A well-configured mobile screen that feeds bad data into a workflow defeats the purpose.
Getting Acumatica Mobile Customization Right
The mobile app is one of the most visible parts of Acumatica for field-based teams, and it’s often the most underbuilt. Companies that take the time to customize mobile screens for specific workflows see real adoption. Companies that ship the defaults and hope for the best usually end up with people working around the system instead of in it.
If you’re implementing Acumatica for the first time or trying to improve mobile adoption for an existing installation, getting the screen design right is worth the investment. CAL Business Solutions works with mid-sized manufacturing, distribution, and professional services companies to configure Acumatica so it works for the people using it, in the field and in the office. Reach out to our team to talk through what your field workflows need.
