How to add a mobile app to Sage X3
Short answer
Either use Sage's own mobile and warehouse options if your version includes them, or build a purpose-made app that talks to X3 web services for scanning, stock moves, receipts and approvals. Keep each screen to one task, and plan for weak Wi-Fi on the floor.
Sage X3 is a capable back-office system, but its standard web client is built for a desk. On the shop floor and in the warehouse, people hold a scanner or a phone, wear gloves, and have ten seconds. When they cannot do their task from there, they write it down and someone keys it later, so stock is wrong by lunchtime.
Sage has offered mobile and warehouse capabilities for X3 in some versions, and third-party scanner apps exist. They fit standard processes well. Where your process is unusual, such as lot-controlled aerospace parts, multiple units per item, or custom inspection steps, a tailored app is often simpler than bending the standard one.
This page treats the app as a thin client over X3 web services, with the business rules staying in X3.
What teams use it for
Goods receipt against purchase orders
Scan the PO or packing slip barcode, confirm quantities per line, capture lot and expiry, and post the receipt to PRECEIPT through services.
Stock transfers and bin moves
Scan source location, item and destination location to post a stock transfer without a trip to a terminal.
Cycle counts
Assign count sheets by zone, scan items and locations, and submit counted quantities for review before adjustment.
Work order labor and material reporting
Operators start and stop operations on a work order (MFGHEAD) and report completed quantity and scrap, with an optional reason code.
Pick and ship confirmation
Scan to confirm picked quantity against the delivery, and print the shipping label on completion.
Approvals for managers
Approve purchase requests or time entries on a phone with the key facts on one screen.
Sage X3 integration surface
- Web services: SOAP through the Syracuse web services pool (CAdxWebServiceXmlCC) and REST/SData endpoints for reading and posting transactions. Which objects are published and how depends on your configuration and version.
- Sage mobile and warehouse options: some X3 versions offer mobile or warehouse management components; availability, licensing and capabilities differ, so confirm with your reseller before building.
- Syracuse: the web server layer handles authentication and sessions; a custom app should use its supported auth rather than storing passwords.
- Database: STOCK, STOJOU, ITMMVT and MFGOPE tables can be read for lookups, but writes belong in services to keep X3 rules and journals correct.
- Hardware: Zebra or Honeywell scanners with Android run browser or native apps; Bluetooth label printers are driven through your own print service.
How it works
- 1
List the five tasks that matter
Observe the floor. Pick receive, move, count, report labor and pick. Do not build a full ERP in a handheld.
- 2
Choose app style
A progressive web app is quickest to deploy. A native Android app handles hardware scanning, offline queues and kiosk mode better.
- 3
Design a thin API layer
Put a small backend between the app and X3 that combines multiple X3 calls into one task-level endpoint and returns short, device-friendly responses.
- 4
Handle auth and device trust
Use SSO or per-user tokens, with shared-device quick login by badge if required, and device registration.
- 5
Plan for offline
Queue scans locally with timestamps, then replay with conflict checks. Do not allow offline posting of high-risk transactions such as adjustments.
- 6
Pilot in one area
Run receiving on one dock for two weeks, compare book quantity to physical counts, then roll out.
Example flows
Dock receipt with lot capture
Trigger: A truck arrives with goods for open POs.
- Receiver scans the PO barcode; the app lists open lines.
- For each line, they enter quantity and scan the lot label.
- The backend posts the receipt through X3 services and returns the receipt number.
- A putaway task with the target location appears on the same device.
Result: Stock is visible and allocatable in X3 minutes after the truck is unloaded.
Operator reports an operation complete
Trigger: An operator finishes a work order operation.
- Scan the work order traveller barcode.
- Enter good and scrap quantities and a scrap reason.
- The backend posts the production reporting transaction.
- Next operation's work centre is shown.
Result: WIP status and costs update during the shift rather than the next morning.
Keeping data on-prem
A shop-floor app is a natural on-prem fit. Host the thin backend inside the plant network next to X3, reachable over the plant Wi-Fi or VPN, with no internet dependency. Handhelds talk only to the backend. If you add voice or natural-language entry later (for example saying a count), run speech and language models locally so floor data never leaves the site. Design for outages: the app should still queue scans when the network drops.
Security checklist
- Use per-user authentication even on shared devices; badge login beats a shared password.
- Restrict mobile function profiles to the specific services needed, never general admin.
- Enrol devices in MDM, enforce screen lock and the ability to remote wipe.
- Validate all scanned input server side; a scanned barcode is untrusted data.
- Log device, user and timestamp with each posting.
Ways to get it done
Sage mobile or warehouse components or a scanner add-on
Effort: Weeks of configuration; licence and version dependent.
Standard receiving, picking and counting in supported versions.
Build a custom app in-house
Effort: Typically 8 to 16 weeks for a five-task app.
Unusual processes and a team with mobile and X3 skills.
Partner build such as Netray with an X3 partner
Effort: Pilot on one task, then add tasks.
Custom workflows plus AI assistance, on-prem hosting.
Pitfalls
- !Copying the desktop screens onto a phone; floor users need one task per screen.
- !Letting the app post inventory adjustments offline, creating conflicts that are hard to reverse.
- !Underestimating Wi-Fi dead zones in racking and metal buildings.
- !Slow web service round trips: batch calls in the backend so each scan responds in about a second.
- !No master data hygiene; bad barcodes and unit setups make scans fail on day one.
Frequently asked questions
Does Sage X3 have a mobile app?
Some X3 versions include or offer mobile and warehouse components, and third parties sell scanner apps. What exists depends on your version, licence and region, so confirm with your reseller before deciding to build.
Can a custom app run offline?
Yes for queued scans and low-risk transactions, with timestamps and conflict checks on sync. Avoid offline posting of adjustments or anything that needs live availability.
Native or web app?
A progressive web app deploys fastest and suits phones. Native Android is better for hardware scanners, kiosk mode and robust offline queues. Many sites start with web and move to native if needed.
How does the app talk to X3?
Through X3 web services, SOAP or REST depending on your version and publishing, behind a small backend that turns several X3 calls into one task-level call. Direct database writes are not recommended.
Can we add AI to a shop-floor app?
Yes, for example photo capture of labels, voice entry, or a question box that answers from X3 data. Run models locally if shop-floor data must stay on site, and keep a person confirming any posted transaction.
Want Mobile app working on your Sage X3?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment