How to add a mobile app to Microsoft Dynamics GP
Short answer
GP has no modern mobile client, and the web client is not built for scanners. The usual approach is a thin mobile app or web app that reads from SQL views, scans barcodes, and sends transactions through an eConnect-based API service, with a queue to survive weak Wi-Fi.
Dynamics GP was designed for a desktop. The Web Client exists and works for office users, and Microsoft once offered mobile experiences for GP, but warehouse and shop-floor staff who need to scan a barcode and move stock need something faster and simpler than a full GP window.
That gap is why many GP sites still run clipboards, spreadsheets and end-of-day keying. Receipts are posted the next morning, inventory is wrong during the day, and cycle counts are painful.
A small mobile layer can fix specific tasks without replacing GP. The key decisions are which transactions to support, how to keep GP's integrity intact, and what happens when the warehouse Wi-Fi drops.
What teams use it for
Barcode receiving against POs
The receiver scans a PO barcode and then items, enters quantities, and the app stages a purchase receipt. Over-receipts are blocked or flagged.
Bin-to-bin and site transfers
Scan an item and locations to move stock, using inventory transfer transactions, with live availability checked first.
Cycle counts
Counters see a list of items for their zone, scan and enter counts, and variances are staged for supervisor approval before adjustments are posted.
Pick confirmation for sales orders
Pickers confirm quantities against SOP lines and mark shipping ready, feeding fulfillment and invoicing.
Manager approvals on the go
Approvers get requisitions or large POs on their phone with the key facts and approve or reject.
Field service stock lookup
Technicians check van or warehouse stock and part cross references before visiting a customer.
Microsoft Dynamics GP integration surface
- SQL Server views provide fast reads for items, quantities by site (IV00102), bins if enabled, open POs (POP10100/POP10110) and open sales lines. Build views so the app never touches base tables.
- eConnect is the supported write layer for inventory transactions, purchase receipts and sales documents. Wrap it in a REST service so mobile devices never talk to eConnect directly. Procedure names depend on your release.
- Web Services for Dynamics GP and, depending on version, newer REST-style endpoints might cover some of the same ground. Confirm what your build supports and its lifecycle status.
- GP Web Client is HTML-based and can be reached from a tablet, but it is not tuned for scanning or small screens.
- Manufacturing modules and third-party warehouse add-ons have their own tables and APIs. If you run them, the app must write through those layers, not around them.
How it works
- 1
Pick the first transaction
Start with receiving or cycle counts. They are well bounded, high value and easy to validate against GP data.
- 2
Choose the client
A progressive web app works on Android scanners with a camera or built-in scan engine. Native apps suit rugged devices needing deep hardware access.
- 3
Build the API service
A small server inside your network with endpoints like get PO, post receipt, adjust count. It does validation, calls eConnect and returns GP's error text on failure.
- 4
Secure the access
Authenticate with your identity provider or device-bound credentials. Expose the API through a VPN or reverse proxy, not directly.
- 5
Add offline queueing
Store scans locally with timestamps and sync when connected. Every queued action needs an idempotency key so a retry cannot double-post.
- 6
Reconcile and report
Show supervisors what was posted, what failed and what is waiting. Failed items need a clear resolution path.
Example flows
Dock receiving with a handheld
Trigger: Truck arrives; receiver scans the PO barcode
- App fetches remaining quantities for the PO from the open lines view.
- Receiver scans each item and enters the received count.
- App blocks quantities above the open amount unless a supervisor override is entered.
- On submit the API posts a receipt through eConnect and returns the receipt number.
Result: Stock appears in GP while the truck is still at the dock rather than the next morning.
Cycle count with variance approval
Trigger: Supervisor releases a count list for a zone
- Counters see the items for their zone without seeing expected quantities, if you want blind counts.
- They scan and enter counts; the app stages results.
- Variances above a threshold go to a supervisor for recount.
- Approved adjustments are posted with a reason code.
Result: Counts finish without printing sheets, and inventory adjustments carry an approval trail.
Keeping data on-prem
A GP warehouse commonly sits on a local SQL Server with devices on in-building Wi-Fi, which is the easy case: the app and API can run entirely inside the plant with no cloud dependency. Host the API on an internal server and publish it to the Wi-Fi VLAN only. For remote or field users, provide access over VPN or a zero-trust gateway. Offline-first design matters more than cloud design here, since dead spots in racking and trailers are real. If you add voice or natural-language features, run the speech and language models on-prem so receiving data and part numbers do not leave the building.
Security checklist
- Never expose SQL Server or eConnect to the device network; only the API service.
- Use per-user authentication and device registration so lost scanners can be revoked.
- Enforce permissions in the API: who may receive, adjust or approve.
- Use idempotency keys and server-side validation to prevent duplicate postings.
- Log device id, user, action and GP document number for every transaction.
Ways to get it done
Third-party warehouse or mobile add-on for GP
Effort: Weeks to months plus license
Fits sites needing full WMS features like bins, waves and label printing. Check version support and how it posts to GP.
Custom PWA with an eConnect API
Effort: Two to four months for a first release
Best for focused workflows like receiving and counts, with a developer who knows GP.
Netray with a GP partner
Effort: Pilot in weeks, scope dependent
When you want mobile tasks plus AI assistance, such as voice queries or exception explanations, with models kept on-prem.
Pitfalls
- !Letting devices post directly with no staging; one bad scan changes inventory.
- !No offline plan, so staff revert to paper when Wi-Fi drops.
- !Ignoring GP rules like closed periods, locked batches and site or bin restrictions.
- !Using the GP Web Client on a small scanner screen and expecting adoption.
- !Not testing with real barcodes: item numbers, vendor part numbers and UPCs differ and need a cross reference.
Frequently asked questions
Does Dynamics GP have an official mobile app?
Microsoft has offered mobile experiences for GP in the past, but I would not plan around an official scanning-capable app today. Check Microsoft's current documentation. In practice sites use a third-party warehouse add-on or a custom app.
Can mobile devices connect straight to the GP database?
They should not. Put an API between the device and SQL Server, read through views and write through eConnect. Direct database access from a device is a security risk and bypasses GP validation.
How do we handle poor warehouse Wi-Fi?
Queue actions locally on the device with unique ids and sync later. The server must reject duplicates. Also make the app clear about what is saved locally versus posted in GP.
Which transactions are safest to start with?
Receiving against open POs and cycle counts. Both are bounded, can be validated against GP data, and can be staged for review. Start there before touching sales invoicing or financial postings.
Can we use phones instead of scanners?
Yes for low volume, using the camera for barcodes. For heavy scanning, dedicated devices with built-in scan engines are faster and more durable, and the same web app can run on both.
Want Mobile app working on your Microsoft Dynamics GP?
A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.
Get a free assessment