How to build a mobile app for Infor M3
Short answer
Build a mobile app for Infor M3 by creating a thin client that calls M3 API programs (MI programs) through the ION API gateway or an internal gateway. Focus on a few high-frequency tasks such as picking, stock moves, receiving, labor and approvals, use device barcode scanning, and keep business rules in M3. Check first whether Infor's own mobile or warehouse offerings already cover the task.
M3 runs the plant, the warehouse and the sales desk, but the people doing the work are standing at a pallet or a machine, not at a PC. Typing item numbers on a small screen or walking back to a terminal to report a movement costs time and produces mistakes. Companies end up with spreadsheets, paper travelers or rekeying at the end of the shift.
Infor provides the H5 client, which is responsive but built for general use, and mobile and warehouse offerings that vary by version and license. Before building anything, see whether they cover the transaction you need. Custom apps make sense when the workflow is specific: your label formats, your inspection steps, your approval chain, or a device not supported by the standard tooling.
A good M3 mobile app is small. It does three or four jobs well, validates early, and writes through the same API programs as the rest of the system so M3 business rules still apply.
What teams use it for
Goods receiving against purchase orders
Scan the PO or item barcode, confirm quantity and location, and post the receipt through the PO receiving API with lot and serial capture.
Stock moves and cycle counts
Move stock between locations and perform counts by scanning location and item, using inventory transaction and count programs.
Picking and shipment confirmation
Show pick lists for a delivery, confirm picks by scan, and finish with delivery confirmation, including partial picks and short-pick reasons.
Production reporting and labor
Report quantities, scrap and time against a manufacturing order operation by scanning the order barcode at the work center.
Mobile approvals
Let managers approve purchase requisitions, orders and time with a summary and link, tied to M3 approval steps.
Field service and maintenance tasks
Technicians view service or maintenance orders, record parts used and time, and capture photos or signatures attached to the order.
Infor M3 integration surface
- M3 API (MI programs) for inventory, manufacturing, purchasing and sales transactions. Typical program families cover item balance, stock transactions, PO receipts, MO reporting and customer order delivery, but names and fields vary by version; use the API metadata to find them.
- ION API gateway with OAuth 2.0 for external or cloud-hosted apps; for on-prem, an internal API endpoint and VPN or MDM-managed devices.
- Infor H5 client and mashups: configurable, responsive panels that can sometimes cover simple screens without custom code.
- Infor mobile and warehouse offerings (for example mobile warehouse functions): check licensing and version; these may already handle scanning workflows for standard processes.
- M3 database for reporting views only (for example MITBAL for balances); writes must go through MI programs. Event publishing through ION can notify the app of changes such as new picks.
How it works
- 1
Pick the tasks and users
Shadow people on the floor for a shift. List the five most frequent transactions and the errors they make. Choose one or two to start, such as receiving and moves.
- 2
Choose the app type
A progressive web app is fastest to deploy and works on most Android scanners. Native or cross-platform apps help with hardware scanning SDKs, background sync and complex offline needs.
- 3
Design the API layer
Put a small backend between devices and M3 to combine calls, enforce limits, cache masters and hide credentials. Avoid devices calling raw M3 APIs with broad rights.
- 4
Authenticate and authorize
Use SSO via Infor OS identity or your IdP, with per-user authorization so M3 transaction logs show the actual person. Scope permissions by warehouse and function.
- 5
Handle scanning and validation
Support GS1 and your own label formats, validate item, location and lot against M3 before submit, and give immediate feedback for wrong scans.
- 6
Plan for connectivity
Warehouses have dead spots. Queue transactions locally with idempotency keys, show sync state clearly, and prevent negative stock or double posts on retry.
Example flows
Receiving a purchase order
Trigger: A receiver scans the PO barcode on a delivery.
- The app loads open lines for that PO and warehouse from M3.
- The receiver scans each item and enters or scans quantity and lot.
- The app flags over-delivery or wrong items before submit.
- On confirm, the backend posts the receipt through the PO API and prints labels.
Result: Receipts are posted at the dock, and stock is available sooner and with fewer data errors.
Reporting production at a work center
Trigger: An operator scans the manufacturing order traveler.
- The app shows the operation, remaining quantity and required components.
- The operator enters good quantity and scrap with reason.
- The backend reports the operation via the MO reporting API.
Result: Production and scrap are reported in near real time rather than at the end of the shift.
Mobile requisition approval
Trigger: A manager gets a push notification for a pending requisition.
- The app shows requester, cost center, items and total.
- The manager approves or rejects with a comment.
- The backend advances the approval step and records the user.
Result: Approvals no longer wait for a desk visit.
Keeping data on-prem
On-prem M3 works well with a mobile app if devices reach your network via Wi-Fi or VPN. Host the backend inside your network, expose it to managed devices only, and keep M3 API credentials on the server. Where devices must work in poor coverage, use local queueing and sync. An AI assistant in the app, for example voice or free-text lookups, can use a locally hosted model so item and stock data stay inside the site network.
Security checklist
- Use MDM-managed devices, device PINs and remote wipe, particularly for shared scanners.
- Authenticate each user, avoid shared logins, and map to M3 users so transaction history is accurate.
- Keep M3 credentials only on the backend and restrict it to the specific MI programs used.
- Use TLS everywhere, certificate pinning where practical, and rate limits on the backend.
- Log every transaction with device, user and idempotency key for audit and troubleshooting.
Ways to get it done
Infor's standard mobile or warehouse offerings and H5 mashups
Effort: Configuration, days to weeks.
Standard receiving, picking and moves where licenses are already in place.
Third-party warehouse or shop-floor mobile product with M3 connector
Effort: Two to four months including process changes.
Specialised warehouse operations that need mature scanning workflows.
Custom app, in-house or with a partner such as Netray
Effort: Six to twelve weeks for a first release on one or two transactions.
Workflows specific to your plant, on-prem constraints, or an AI-assisted interface with approval-gated writes.
Pitfalls
- !Building a mobile copy of the whole M3 menu instead of a few focused tasks.
- !Posting offline transactions without idempotency, creating duplicates after reconnect.
- !Giving the app a single powerful M3 user, which hides who did what.
- !Neglecting scanner hardware and label quality; bad barcodes defeat a good app.
- !Calling MI programs one field at a time from the device instead of through a backend that bundles calls.
Frequently asked questions
Does Infor M3 have a mobile app?
Infor provides a responsive H5 client and, depending on version and license, mobile and warehouse functionality. Capabilities differ between cloud and on-prem releases, so check your documentation and account team. Custom apps fill gaps in workflow and device support.
Should we call M3 APIs directly from the device?
Usually no. Put a backend in between to hold credentials, bundle calls, enforce permissions and handle retries. Devices then talk to one stable API, and changes to M3 programs are absorbed in one place.
How do we handle offline use?
Queue transactions locally with unique keys, show sync status, and have the backend reject duplicates. Avoid offline for transactions that depend on live availability, such as allocation, unless you accept the conflicts.
Can we scan barcodes with a phone?
Yes, camera scanning works for low volumes, but rugged scanners are faster and more reliable in warehouses. Choose the device based on scan volume and environment, then pick the app framework that supports its scanning SDK.
How does AI fit into a mobile app?
Possible uses include voice or free-text lookups, photo-based document capture and suggested corrections. Keep AI read-only or approval-gated for writes, and use a local model if the data cannot leave the site.
Want Mobile app working on your Infor M3?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment