Retail POS & back office

The problem

Enterprise retail runs on point-of-sale software that cannot be down and cannot be slow. Each retailer needed the platform customised to their own store operations, and the back office that configured those stores had grown slow enough that rolling out a change across the estate was a whole day of work.

What I did

1. 01Delivered customisations on the Flooid POS platform for enterprise retailers including Marks & Spencer, Woolworths, and Whole Foods Market, across roughly 200 locations in the UK, Canada and the US.
2. 02Rebuilt the back-office store management system with cleaner Spring workflows and revised data models, so configuring a store stopped being a manual crawl.
3. 03Profiled and refactored around fifty slow iBatis SQL queries that were timing out under peak retail load — the periods when the system matters most.
4. 04Mentored three junior developers through code review and pairing.

Outcome

Store configuration time fell about 25% and report generation about 45%, with the peak-load timeouts eliminated. Sprint velocity rose roughly 20% and post-release defects dropped as the review habit took.

Stack

Java Software Engineer · Uworx / Flooid

Retailer systems are internal — the schematic shows the architecture rather than a screenshot.