How to add a mobile app to Infor VISUAL
Short answer
A mobile app for Infor VISUAL talks to a gateway service in front of the VISUAL database and API Toolkit. It handles barcode scanning, labor tickets, inventory moves and approvals on phones or rugged scanners, with offline queuing where Wi-Fi is weak.
VISUAL was built around a Windows desktop client. That works at a desk, but receiving docks, stockrooms and machine cells need something a person can use standing up, with a scanner in hand. Many shops end up with paper travelers, clipboards and end-of-shift data entry, which delays labor and inventory records by hours.
A mobile app closes that gap. Operators scan a work order, start and stop an operation, report quantity complete, and move material between locations. Receiving staff scan a PO and receive against it. Managers approve requests from their phones.
The decisions that matter are device type, how the app reaches VISUAL without exposing it to the internet, and how writes are validated. Getting those right is more important than the screen design.
What teams use it for
Shop floor labor reporting
Operators scan a work order and operation to clock on and off, and enter quantity good and scrap.
Receiving against PO
Scan the PO, confirm quantities and location, and print or generate labels for the received material.
Inventory transfers and cycle counts
Move parts between warehouses and locations, and count by scanning location and part barcodes.
Issue material to jobs
Scan a work order and a part to issue material, with a warning when the part is not on the requirement list.
Approvals and look-ups
Supervisors approve overtime or expedites and look up part availability while walking the floor.
Infor VISUAL integration surface
- VISUAL API Toolkit: the supported way to post labor, inventory transactions and receipts under business rules, where your version and license include it.
- Database reads: part, work order, operation and inventory location data are read from SQL Server or Oracle for display. Verify table names in your own version.
- Labor and inventory transaction logic: tables such as labor tickets and inventory transactions are written by the application, so avoid inserting into them directly.
- Barcode and label support: VISUAL reports and label tools can generate barcodes for work orders, parts and locations, depending on your configuration.
- Existing shop floor modules: some VISUAL versions and partner add-ons include shop floor data collection, so compare before building.
How it works
- 1
Pick devices
Choose between rugged Android scanners, shared tablets and employee phones. Rugged devices scan faster and tolerate gloves and cleaning.
- 2
Deploy a gateway
Run an API service in a DMZ or behind a VPN. It validates requests and talks to VISUAL, and the app never connects to the database.
- 3
Authenticate users
Use badge scan plus PIN for the floor and single sign-on for office roles. Map each user to a VISUAL employee or user.
- 4
Build transactions
Implement the few that matter first: labor, receipt, move, issue. Validate on the server against VISUAL rules.
- 5
Handle weak Wi-Fi
Queue transactions on the device with a unique ID, and replay them safely so a retry never posts twice.
- 6
Pilot in one area
Start with one cell or the dock, watch the exceptions for a few weeks, then widen.
Example flows
Operator reports a finished operation
Trigger: An operator scans the traveler barcode at the machine.
- The app loads the work order and the open operations.
- The operator selects the operation and enters good and scrap quantities.
- The gateway validates sequence and quantity limits.
- The labor and quantity are posted through the supported interface.
Result: WIP is current within minutes instead of at the end of the shift.
Dock receiving
Trigger: A truck arrives and a clerk scans the PO barcode.
- Open PO lines are shown with expected quantities.
- The clerk enters counts and the receiving location.
- Over-receipt beyond tolerance is blocked or sent for approval.
- The receipt posts and labels are printed.
Result: Material is available to planners the same hour it arrives.
Keeping data on-prem
A mobile app does not have to put VISUAL on the internet. Host the gateway inside your network and reach it over plant Wi-Fi or a VPN, with a reverse proxy in a DMZ only if you need access from outside. Keep the app private through a mobile device management tool or an internal app catalog. If you add voice or photo features, such as reading a label or defect photo, run those models on a local server so part and customer data stay in-house. Offline mode matters in metal-clad buildings, so test Wi-Fi coverage at the machines, not just in the office.
Security checklist
- Never connect the app straight to the VISUAL database.
- Validate every transaction on the server and enforce roles per transaction type.
- Use device management to enforce screen lock and remote wipe on phones.
- Make offline queues idempotent so retries cannot double post.
- Log device, user and time for every transaction.
Ways to get it done
Packaged shop floor or WMS add-on
Effort: Weeks, plus license cost
Best when a vendor already supports VISUAL with tested transactions and your processes are fairly standard.
Build in-house
Effort: Several months for a solid first version
Possible with mobile developers and someone who knows VISUAL transactions well. Maintenance is the long-term cost.
Partner build with Netray
Effort: Weeks to a few months depending on scope
Suited to custom flows, an on-prem gateway, and adding AI features such as photo reading under approval.
Pitfalls
- !Inserting into transaction tables directly and skipping VISUAL rules.
- !Assuming Wi-Fi is good on the floor and having no offline queue.
- !Using shared logins that make labor records meaningless.
- !Building too many screens before one flow is proven.
- !Barcodes that differ between VISUAL labels and what the app expects.
Frequently asked questions
Does Infor VISUAL have a mobile app?
Mobile and shop floor options have existed through Infor and partner products, but what is available depends on your version and licenses. Check with your reseller. Where nothing fits, shops build a custom app over a gateway that uses the API Toolkit.
Can the app work offline?
Yes, with limits. The device can cache part and work order lookups and queue transactions with unique IDs, then replay them when connected. Anything that depends on live inventory, such as issuing the last units, should be validated when the transaction finally posts.
Do we need the API Toolkit?
For writing transactions safely, it is the recommended route if your version includes it. Without it you may be limited to read-only lookups, or to partner tools with their own posting logic. Inserting directly into tables is risky because it can bypass costing and validation.
Which devices should we use?
Rugged Android scanners suit docks and stockrooms. Shared tablets work at machine cells, and phones suit supervisors and approvals. Choose based on scan speed, glove use, cleaning needs and how many people share a device, not on price alone.
Can we add AI features later?
Yes. Typical additions are photo capture of labels or defects, voice notes turned into text, and natural-language lookups. Run the models on a local server if the data is sensitive, and keep a person confirming anything that changes records.
Want Mobile app working on your Infor VISUAL?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment