How to add a mobile app to IFS Cloud
Short answer
For IFS Cloud mobility, first check IFS's own mobile and native Aurena options, then fill gaps with a custom app that calls IFS projections through an authenticated gateway. Design around scanning, short transactions and offline queues, and keep business rules in IFS rather than in the app.
IFS Cloud customers in manufacturing, maintenance and field service need people away from a desk to do real work in the system: receive goods, move stock, report labor on a shop order operation, close a work task, capture a meter reading or an inspection result. Aurena works in a browser, and IFS has offered mobile and native client options for areas like field service, warehouse and maintenance, so the first question is always what you already own.
Custom mobile becomes relevant when the standard apps do not match a process: a specific inspection flow for a regulated product, a rugged scanner with a different workflow, a subcontractor portal, or a very simplified screen for operators who should not see the whole ERP. Then you build a thin app over IFS projections.
The sections below cover how to decide, how the integration works, and the problems that show up on real shop floors: bad Wi-Fi, gloves, scanners and the 6 a.m. shift change.
What teams use it for
Goods receipt with barcode scanning
Scan the PO and part label, enter quantity and lot, and create a purchase receipt with an inspection flag where required.
Shop order labor and quantity reporting
Operators clock on to an operation, report good and scrap quantities and reasons, and clock off, from a screen designed for the work center.
Inventory moves and cycle counts
Scan location and part to move stock or count, with variance thresholds that require a supervisor before posting.
Field work task completion
Technicians see assigned tasks, log time and parts, capture a signature and photos, and close the task on site.
In-process and final inspection
Inspectors record measurements against an inspection plan, attach photos and raise a nonconformance from the device.
Approvals and notifications for supervisors
Supervisors approve overtime, requisitions or scrap from push notifications without opening a laptop.
IFS Cloud integration surface
- Projections: the OData REST layer under the projection/v1 path is the supported route for custom apps, including actions for reporting, receiving and moving stock. Confirm names for your release in API Explorer.
- IFS-delivered mobile and native clients: IFS has offered mobile options such as Aurena Native and applications for warehouse and field service. Their scope and names depend on version, so review what you license before building.
- Authentication: OpenID Connect against IFS's identity layer, often federated to Entra ID, with mobile apps using authorization code with PKCE and managed device policies.
- IFS Connect and Business Events: useful to push tasks and alerts to devices, and to receive offline queue submissions as messages.
- Barcode and label data: part catalog, handling units and lot data in IFS define what a scan can resolve to, so label formats must match.
How it works
- 1
Audit what IFS already provides
List the processes you need and match them to IFS native and mobile apps you license. Build only the gaps.
- 2
Define the screens around tasks
Design one job per screen: receive, report, move, inspect. Cut every field that can default from IFS.
- 3
Set up the API gateway
Place a gateway or backend-for-frontend in front of the projections to shape payloads, enforce rate limits and hide IFS URLs from devices.
- 4
Implement sign-in and device trust
Use the authorization code flow with PKCE, short-lived tokens and mobile device management, and map users to IFS permission sets.
- 5
Add scanning
Use camera scanning for casual use, or vendor SDKs for rugged scanners, and resolve codes against IFS data before posting.
- 6
Plan offline behavior
Queue transactions locally with idempotency keys, and decide what can be posted late and what must be online, such as stock moves of scarce items.
- 7
Pilot on one line or route
Run a pilot with real scanners and shifts, measure time per transaction and error rate, then expand.
Example flows
Scan to receive
Trigger: A delivery arrives at the receiving dock
- Receiver scans the PO barcode and the part label
- App retrieves expected lines through the projection
- Receiver enters quantity and lot, and photographs damage if any
- App posts the receipt, flags inspection if required, and prints a put-away label
Result: Receipts post at the dock in seconds, and shortages and damage are logged at the source.
Operator labor reporting
Trigger: An operator starts an operation on a shop order
- Operator scans the shop order traveler barcode
- App shows the operation and the part
- Operator clocks on, later enters good and scrap quantity with reason code
- App posts the report; failures queue with an idempotency key
Result: Shop order progress reflects reality within the shift, not the next morning.
Field task close-out
Trigger: A technician finishes work in an area with poor signal
- App stores time, parts, photos and signature locally
- Connection returns and the queue syncs in order
- Gateway posts each item through the projection
- Conflicts, such as a task already closed, appear for the dispatcher
Result: Work is closed with evidence even when the site had no signal.
Keeping data on-prem
For customer-managed IFS Cloud, host the gateway in your DMZ and let devices reach only it, over VPN or a private APN. Mobile device management keeps tokens and cached data protected. Offline caches should hold the minimum data, encrypted on device. If you add assistants to the app, such as voice commands or a question box for work instructions, run the model on your own servers with open weights and retrieval over approved IFS data and documents, so shop floor questions are never sent to a public AI service.
Security checklist
- Use PKCE authorization code flow with short-lived tokens, and revoke on device loss.
- Encrypt the local offline store and wipe it on logout or MDM unenroll.
- Enforce IFS permission sets per user, so the app never has more rights than Aurena.
- Rate-limit and validate at the gateway, and never expose IFS projection URLs directly to the internet.
- Log device id, user and idempotency key for each posted transaction.
Ways to get it done
Use IFS-delivered mobile and native apps
Effort: Weeks of configuration and rollout
Standard warehouse, maintenance and field service processes
Custom app on projections with a gateway
Effort: Roughly three to five months for a first app
Unique inspection or shop floor flows, simplified roles
Partner build with Netray and your IFS partner
Effort: Phased, starting with one workflow
Mobile plus voice or assistant features on a private model
Pitfalls
- !Rebuilding what IFS already ships as a mobile app, then maintaining it across upgrades.
- !Designing offline mode last; retrofitting idempotency and conflict handling is painful.
- !Putting business rules in the app, so the web client and mobile behave differently.
- !Ignoring label quality and scanner settings, which causes most scan errors.
- !Testing on office Wi-Fi only, not in the corners of the plant or the field.
Frequently asked questions
Does IFS Cloud have a mobile app?
IFS has offered mobile and native client options, such as Aurena Native and applications for warehouse and field service, though availability depends on your version and licenses. Review these first. Build a custom app only for processes they do not cover or where simplification matters.
Can we scan barcodes into Aurena in a browser?
Many scanners work as keyboard input and fill fields in Aurena, which suits simple cases. For guided workflows, camera scanning, offline use and simplified screens, a native or purpose-built app is usually better. Test with your actual scanners and labels.
How should offline transactions be handled?
Queue them on the device with unique idempotency keys, post them in order when connected, and surface conflicts to a supervisor. Decide up front which transactions may be delayed, because stock moves of constrained parts or already closed tasks can conflict.
Which authentication should a custom app use?
Authorization code flow with PKCE against IFS's OpenID Connect capable identity layer, often federated to Entra ID, with short token lifetimes and device management. Avoid embedding client secrets in the app or using shared accounts for the shop floor.
Can an AI assistant be added to the mobile app?
Yes. Common additions are voice entry for quantities and a question box over work instructions and IFS data. Run the model privately with retrieval, enforce the user's IFS rights, and keep any posting behind a confirmation step in the app.
Want Mobile app working on your IFS Cloud?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment