Point-of-Sale Toolchain Modernisation for Web & Mobile POS

Overview

A national retail group runs its stores on a pair of point-of-sale systems — a web POS for counter terminals and a hybrid mobile POS used on the floor. Both are business-critical: when the POS is down, the store cannot trade.

The mobile app was built on an ageing hybrid stack whose build toolchain had drifted badly out of date. New Android requirements loomed, the existing build process was fragile, and the team needed the app modernised without a disruptive rewrite. We were contracted to bring the build system current, verify the app end-to-end, and ship improvements alongside.

The Challenge

• An outdated hybrid toolchain. The Cordova-based build system was several major versions behind, blocking Android target-SDK updates required for continued Play Store distribution.
• No appetite for a rewrite. The POS logic was proven in production across many stores. The mandate was modernise-in-place, not replace.
• Regression risk. POS flows — sales, returns, payments, end-of-day — had to keep working exactly as before. Any change to the build pipeline had to be verified against real hardware and real store workflows.
• Structured release discipline. Changes shipped through UAT and production release trains on Azure DevOps, aligned with store operations.

What We Did

Build toolchain modernisation

Upgraded the Cordova build tooling and Android build chain across the mobile POS project — new CLI, updated platform targets, plugin compatibility resolution, and Gradle/SDK alignment. The output: the same app, buildable on a current toolchain, meeting current store requirements.

End-to-end functional verification

With the toolchain replaced underneath the app, everything needed re-verification: transaction flows, receipt printing, barcode scanning and offline behaviour, tested against physical devices via Android Studio. Issues found in the upgrade were triaged and fixed as part of the engagement.

Delivery through the release train

Work landed through the client's Azure DevOps process — feature branches, PR review, UAT deployment, sign-off, then production release on the store schedule. We also completed a set of functional tasks on the web POS (Angular) alongside the mobile work.

• Angular
• Ionic / Cordova
• TypeScript
• Java EE
• Android Studio
• Azure DevOps
• Node.js

Outcome

• The mobile POS builds on a current, supported toolchain — unblocking Android platform requirements without a rewrite.
• Core store workflows verified working across the upgrade, with fixes shipped where the toolchain change surfaced issues.
• All work delivered inside the client's existing Azure DevOps release process, with UAT and production releases on schedule.
• A contained, fixed-scope engagement: in, modernised, verified, out — the kind of surgical contract work legacy systems often need.