Mobile Data Capture for Sage 200 (Evolution) with Power Apps

Sage Evolution's Mobile Gap

Sage Evolution is an excellent desktop accounting and ERP system, but it was built for office use. Warehouse staff doing stock counts, drivers confirming deliveries, technicians logging service calls, and sales reps capturing orders in the field have no native way to interact with Sage data from a mobile device. The result? Paper forms, WhatsApp photos, and end-of-day data entry back at the office - a workflow that introduces delays, errors, and data gaps.

How Power Apps Extends Sage to Mobile

Power Apps connects to Sage Evolution's SQL Server database through the on-premises data gateway or direct SQL connector. A Canvas App can read from Sage tables (StkItem for stock items, Client for customers, Vendor for suppliers) and write captured data to staging tables or SharePoint lists. Power Automate then processes this data and, where appropriate, feeds it back into Sage - all without modifying the Sage application itself.

Use Case 1: Mobile Stock Counting

Build a Power Apps stock count app that loads item master data from Sage's StkItem table. Warehouse staff scan barcodes with their phone camera, enter counted quantities, and submit the count. The app calculates variances against Sage's on-hand quantities in real time. Completed counts are reviewed in a Power BI dashboard before adjustments are posted. This replaces printed count sheets and eliminates the post-count data entry step entirely.

Use Case 2: Delivery Confirmation and Proof of Delivery

Drivers receive their delivery schedule from Sage's InvNum (invoice/delivery note) table in the Power App. At each drop-off, they capture the recipient's signature, photograph the delivered goods, record any damages or shortfalls, and mark the delivery as complete. This data syncs back to SharePoint and triggers a Power Automate flow that updates the delivery status and notifies the dispatch team.

Use Case 3: Field Service and Inspections

Technicians access customer details from Sage's Client table, view service history, and log new service calls directly from site. The app captures photos of equipment, records meter readings, logs parts used (from StkItem), and collects customer sign-off. A completed job triggers invoicing preparation in the back office.

Use Case 4: Sales Order Capture

Field sales reps browse the product catalogue from StkItem, check available stock levels, and capture orders on their tablet. The app pulls customer-specific details from the Client table and applies the correct terms. Submitted orders flow into a review queue where the sales admin can verify and create the formal Sage sales order.

Offline Capability

Many South African field environments have unreliable connectivity - rural areas, underground parking, large warehouse structures. Power Apps supports offline data caching, allowing users to continue working without a connection. When connectivity returns, the app automatically syncs captured data back to the server. Design your app with offline scenarios in mind: pre-load reference data, queue submissions locally, and handle sync conflicts gracefully.

Architecture and Data Flow

The recommended architecture keeps Sage as the system of record. Power Apps reads reference data from Sage (customers, stock items, accounts) but writes captured data to a staging layer - typically SharePoint lists or Dataverse tables. Power Automate validates and processes this staged data before it enters Sage, ensuring data integrity. This approach protects your Sage database from direct mobile writes while still providing real-time integration.

Getting Started

Choose one high-impact use case - typically stock counting or delivery confirmation - and build a focused app that solves that specific problem well. Start with read-only Sage integration (loading item and customer data) before adding write-back capabilities. Most organisations can deploy their first Sage-integrated Power App within a few weeks, with immediate productivity gains for field staff.