Famous Recon

QSR operations platform: multi-store reconciliation, fleet telemetry, daily-ops automation for a multi-brand QSR franchisee operator.

Visit the live product

The problem

A franchisee operator running 20 outlets across Steers, Debonairs, Fishaways, and Milkylane brands faced a daily back-office crisis. Aura POS data lived on a local server inside each store, so the owner had to log into 20 separate machines to compare yesterday's takings. Mr D, UberEats, Yumbi, TJ Speedpoints, Capitec Speedpoints, and Deliveree Tribe each provided no API access. The daily reconciliation work was done by hand, 20 times over, with no consolidated view of the fleet.

Famous Recon login screen — Famous Recon sign-in — the single front door that replaced logging into 20 separate store machines

Why custom over SaaS

No off-the-shelf platform exists for this. SaaS platforms assume API access to the systems they ingest from. None of the systems feeding a QSR franchise in South Africa provide that access. The only way to consolidate the data was to build the bridge ourselves, store by store, platform by platform.

Owner Recon Insights dashboard with KPI cards, sales volume chart, and tender mix by location — Owner Recon Insights — the cross-business dashboard no SaaS could deliver without API access to Aura, Mr D, UberEats, Yumbi, TJ, Capitec and Deliveree Tribe

What we built

We started as a reconciliation app. One month in, we realised the underlying infrastructure was a bigger problem than the recon itself. Store servers had no backup discipline and no monitoring. We pivoted: built a custom fleet monitoring and cloud backup layer first. The owner now gets a single morning briefing covering missing Windows updates, low storage, and backup failures across all 20 stores. With infrastructure stable, we returned to the recon engine: ingestion connectors for every platform feeding the business, plus a unified daily reconciliation view that exposes 20 stores at a glance.

IT Management Overview screen with per-store service status cards — IT Management Overview — the fleet monitoring layer we built first, before returning to the recon engine

The hardest part

Every platform feeding a QSR franchise has its own way of not giving you the data. Some only offer manual CSV exports. Others require resilient web automation against anti-bot defences. Aura itself is a local-only POS with no remote API, sitting on a server inside each store. Getting all of these to feed into a single consolidated view, every day, automatically, with no manual intervention, is not work that gets done casually. The ingestion engine took months to harden across all six data sources and is the kind of integration most operators would never get built.

Sales reconciliation screen with Aura POS sales matched against platform tenders — Daily sales reconciliation — Aura POS sales (left) matched against delivery and tender platform feeds (right), per store, every day

Outcomes

20 outlets reconciling daily through one platform. Owners now compare stores in seconds instead of hours. The morning monitoring briefing catches infrastructure problems before they cause a trading-day outage. The franchisee operator has avoided hiring a full-time back-office operator to maintain fleet visibility.

Daily Action Report PDF showing 69 total devices, 18 needs attention, 51 healthy, with per-server breakdown — Daily Action Report — the IT fleet status briefing auto-generated and emailed to the owner each morning

Want one like this?

Tell us about your operation and we will follow up to schedule a discovery call.

Book a Discovery Call