How to add a mobile app to SYSPRO
Short answer
Start by checking what SYSPRO's own mobile offering (Espresso and related tools) already covers. For gaps, build a thin mobile front end that calls e.net business objects through a gateway you control, with barcode scanning, queued writes for weak connectivity and strict operator mapping.
Warehouse staff, shop-floor operators and field engineers need to scan, count, report time and approve things where they stand. Running the full SYSPRO desktop client on a tablet at a machine is awkward, and paper travellers get keyed in later.
SYSPRO has its own mobile approach, so the first question is what already works for you. A custom app earns its place for specific scanner-driven tasks, unusual screens or offline needs, not for rebuilding what Espresso already offers.
What teams use it for
Goods receipt by barcode
Scan a PO barcode and item, confirm quantity, record lot or serial, and post the receipt without returning to a desktop.
Job labor and material reporting
Operators start and stop operations on a job, record quantities complete and scrap with reason codes, and issue materials by scan.
Stock transfers and bin moves
Scan from-bin, item and to-bin to move stock between warehouses or bins, with immediate validation against on-hand quantity.
Cycle counts
Present count lists on a handheld, capture counts by scan, and submit variances for supervisor approval before adjusting inventory.
Pick, pack and ship confirmation
Guide pickers through dispatch lines, confirm picks by scan and capture proof of delivery from drivers.
Mobile approvals
Managers approve requisitions, timesheets or expense items from a phone, with the same limits that apply in the SYSPRO client.
SYSPRO integration surface
- SYSPRO Espresso, SYSPRO's mobile and tablet-oriented offering, and the barcoding and warehouse features in your edition. Capabilities vary by version and licence, so confirm what you already own.
- SYSPRO e.net business objects for inventory movement, goods receipt, WIP labor and material posting, and dispatch. Object names and parameters vary by release.
- SYSPRO web services and, in newer releases, REST-style access through the e.net layer, which suits mobile clients better than COM.
- SQL Server tables for lookups such as bins, lots and serials, stock codes and open jobs, accessed read-only via your gateway, never directly from the device.
- SYSPRO operator security and warehouse or bin restrictions, which should drive what each mobile user can do.
How it works
- 1
Audit the standard options first
List the tasks you need and test whether Espresso or your barcoding module covers them. Only build for the gaps.
- 2
Choose the device and form factor
Rugged Android handhelds with built-in scanners are common in warehouses, tablets suit machine-side use, and phones suit approvals.
- 3
Build a gateway between app and SYSPRO
The app talks only to your gateway over HTTPS. The gateway authenticates, maps the user to an operator, validates input and calls business objects.
- 4
Design for scanning speed
Use keyboard-wedge or intent-based scanning, validate each scan instantly against cached masters, and give clear audible and visual feedback.
- 5
Handle weak connectivity
Cache open picks, jobs and masters on the device, queue transactions with idempotency keys, and replay in order when back online, flagging conflicts.
- 6
Roll out in stages
Pilot one process on one shift, measure scan errors and time per transaction, then add processes. Provide a fallback to the desktop for exceptions.
Example flows
Dock receipt with lot capture
Trigger: A truck arrives with a supplier delivery.
- The receiver scans the PO barcode and the app lists open lines.
- Each item and quantity is scanned and a lot label is printed.
- The gateway posts the receipt through the goods receipt business object.
- Exceptions such as over-receipt are blocked and sent to a supervisor.
Result: Stock appears in SYSPRO at the dock, with lot traceability from receipt.
Operator job reporting offline
Trigger: An operator completes an operation in an area with poor Wi-Fi.
- The tablet records quantity, scrap and reason offline.
- The transaction is queued with a unique key and timestamp.
- On reconnection the gateway posts it and returns any rejection reason.
Result: WIP reflects shop-floor reality without paper travellers or double entry.
Keeping data on-prem
Keep SYSPRO and SQL Server inside the plant network and publish only the gateway, either on a plant Wi-Fi VLAN for devices on site or through a VPN or reverse proxy for remote staff. Authenticate devices and users, and avoid exposing e.net directly. Mobile device management should control enrolment and remote wipe. If you want voice or natural-language entry, run a speech and language model locally so shop-floor audio and part data do not leave the site. Plan for Wi-Fi coverage surveys, since dead zones cause more problems than software.
Security checklist
- Never connect devices directly to SQL Server or e.net; use an authenticated gateway.
- Map each user to a SYSPRO operator and enforce warehouse and bin restrictions server-side.
- Use device certificates or MDM enrolment and disable the app on lost devices.
- Validate all input and use idempotency keys to prevent duplicate postings on retries.
- Log device, user and transaction details for audit.
Ways to get it done
SYSPRO Espresso and standard barcoding
Effort: Configuration and training, depending on licensed modules.
Common tasks that the standard tools already cover, with minimal custom screens.
Third-party warehouse or shop-floor app
Effort: Weeks to configure, plus licence and support costs.
You need mature scanning workflows and the vendor supports SYSPRO.
Custom app with Netray
Effort: Scoped per process, commonly a pilot in weeks and a full rollout in months.
Unique processes, offline needs or on-prem voice and AI features that standard tools lack.
Pitfalls
- !Building what Espresso already provides, then maintaining it forever.
- !Posting synchronously on bad Wi-Fi, causing duplicates when users retry.
- !Ignoring unit of measure conversions between scan labels and SYSPRO stock units.
- !Letting a shared login hide who made inventory adjustments.
- !Skipping a bin or label standard, so barcodes are inconsistent across suppliers.
Frequently asked questions
Does SYSPRO have a mobile app?
SYSPRO offers Espresso for mobile and tablet use, and barcoding capabilities depending on edition. Exact features vary by version and licence, so check with your SYSPRO partner. A custom app is justified mainly for specific scanner workflows, offline use or screens the standard tools do not provide.
Can a mobile app work offline with SYSPRO?
Yes, by caching reference data on the device and queuing transactions with unique keys, then replaying through the gateway when connectivity returns. You must design conflict handling, such as stock that changed meanwhile, and decide which transactions are safe to accept offline.
How should devices connect to an on-prem SYSPRO?
Through a gateway you control, not directly to SYSPRO or SQL Server. On site, devices join a plant Wi-Fi network that can reach the gateway. For remote use, use a VPN or reverse proxy with strong authentication, and manage devices with MDM.
Which SYSPRO interface should the app use?
Prefer e.net business objects through the web service or REST-style layer your release provides, because they enforce SYSPRO business rules and security. Use SQL only for read-only lookups. Writing directly to tables risks corrupting data and is not supportable.
Can I add voice or AI to the mobile app?
You can, for example voice entry of counts or asking where a part is stored. For plant data, run speech recognition and a language model on local servers, and keep the model read-only unless a person confirms the action. Test in real noise before relying on it.
Want Mobile app working on your SYSPRO?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment