Case study · live production system

One gym, one system,
zero downtime.

A neighbourhood gym was running daily sales on a legacy browser POS — sales in one place, member records in another, month-end reconciliation rebuilt by hand. The shop could not afford to close, so “migrate the system” kept being postponed. I moved it live without losing a single trading hour.

2,643
transactions migrated and processed
RM 139,887.90
revenue handled on the system
0 min
trading downtime at cutover
30 min
automated reconciliation cycle
Figures read from the live database, not estimated.
The situation

Two systems, one spreadsheet, and no way to stop selling.

Checkout lived in an ageing web POS, and every sale was then keyed a second time into a shared Excel workbook — one tab per trading day. At month end the owner re-added those rows by hand to get a total per product, per payment method and per trainer, then carried the figure into the accounts.

The obvious answer — “just switch systems” — ignored the real constraint: the counter is the business. Any migration had to happen while staff kept taking payments, and the historical sales had to come across without a single duplicated or missing ringgit.

The before

One Excel tab per trading day. Then the maths.

Every sale keyed in by hand, each category ticked, and at month end every row added up again — per product, per payment method and per trainer, as the tally block on the right shows.

Excel workbook used before the migration: one tab per trading day, rows of hand-keyed sales with category ticks, and a manual monthly tally by product and trainer
Actual workbook · October 2026 · staff names redacted
What I built

One system for the counter, the books and the back office.

01

POS & inventory

Single-screen checkout, receipts, stock movements, shift records and a category-based catalogue built for counter speed.

Operate
02

CRM & memberships

Members, plans, renewals, class scheduling, leads and staff permissions in one record instead of three.

Operate
03

Reporting that adds up

Revenue by day, category and payment method — computed from the same rows the counter writes, so the numbers always reconcile.

Monitor
04

Data migration

An idempotent importer pulled 2,643 historical sales out of the old system; re-running it never duplicated a row.

Cutover
05

Automated sync & monitoring

Incremental reconciliation every 30 minutes with verification and failure alerts — instead of silent drift discovered at month end.

Operate
06

Production hardening

Domain and SSL migration, locked-down database tooling, debug mode off, and a commission-calculation mismatch found and fixed.

Rescue
Inside the product

Real screens, from the live system.

Executive dashboard with month-to-date revenue, sales trend and category mix
Executive dashboard. Month-to-date revenue, sales trend and revenue split by category — the view the owner opens first.
POS catalogue and checkout panel with PT packages and custom-priced services
POS & inventory. Catalogue, stock, PT packages and custom-priced services, with one-screen checkout.
Sales report broken down by payment method and item
Sales report. Payment-method totals and item-level breakdown for the selected period.
The result

What changed for the owner.

MeasureBeforeAfter
Daily sales recordkeyed by hand into Exceltyped once at the counter
Month-end tallyevery row re-added by handautomatic · 30 min
Historical sales in one placesplit across systems2,643 records
Revenue visibilityend of monthlive
Trading downtime at cutoverfeared0 minutes
Failed syncs noticednever checkedalerted in minutes
Most developers hand over a repository and disappear. The part that actually matters is what happens after launch — the migration that has to be exact, the monitoring nobody set up, and the phone call when a number doesn’t add up. Fyxed Lab

Running a gym on a system you don’t trust?

Tell me how the counter actually works. First call is free.