[ ← back to projects ]
> cat case-studies/lovedoner.md

LoveDoner Kebab KMS and POS

Client
LoveDoner (franchise kebab/döner restaurant organization)
Engagement
2024 – 2025
Role
Sole/lead developer — built both systems from scratch
Stack
Angular (frontend), .NET Core Web API (backend)
Systems delivered
Enhanced POS (per-franchise) + Factory Manager KMS (factory/HQ)
Status
Completed build; a follow-on hardening phase is scoped as future work
< KMS />< POS />< Full Stack />
LoveDoner Kebab KMS and POS screenshot 1
LoveDoner Kebab KMS and POS screenshot 2
LoveDoner Kebab KMS and POS screenshot 3
LoveDoner Kebab KMS and POS screenshot 4
LoveDoner Kebab KMS and POS screenshot 5
LoveDoner Kebab KMS and POS screenshot 6
LoveDoner Kebab KMS and POS screenshot 7
LoveDoner Kebab KMS and POS screenshot 8
LoveDoner Kebab KMS and POS screenshot 9
LoveDoner Kebab KMS and POS screenshot 10
LoveDoner Kebab KMS and POS screenshot 11
01 / 11
> the situation

LoveDoner runs a central production factory supplying multiple franchise locations, each running point-of-sale. Before this engagement, the franchise-level POS processed orders but had no historical tracking, no fraud/discrepancy detection, and no link between what the factory produced/spent and what individual locations sold. Nothing connected factory-side costs (ingredients, transport, labor) to franchise-side sales, and nothing flagged when something in the order record didn't add up.

As daily transaction volume reached 200-300 per location, that gap stopped being theoretical. The client came to Shees with a specific, concrete suspicion: they believed employees might be manipulating or deleting orders at the POS level, but had no way to confirm it or quantify the impact.

> what was built

Two connected systems, both built from scratch on the same stack. POS (per-franchise level) — the front-line order system each location uses, rebuilt with structured historical tracking so every order leaves a persistent, queryable trail rather than disappearing once completed or cancelled.

Factory Manager KMS (factory/HQ level) — a knowledge-management/oversight system for the production side of the business, handling production cost tracking, full expense and employee-management records, and detailed financial reporting down to granular line items — including transportation costs for ingredients moving from the factory to individual POS locations.

The investigation that produced the $18,000 finding: the client reported a suspicion that employees might be creating and then deleting orders. Shees investigated directly against the order records and surfaced a set of orders that had existed at some point but were missing from the active order set — evidence the deletions were really happening. Working from what could still be reconstructed, Shees compiled a full report: total revenue tied to the missing orders, broken down monthly across a twelve-month period, totaling $18,000 — turning a vague suspicion into a concrete, evidence-based finding the client could act on.

> results
$18,000
Revenue leakage identified
12-month period, reconstructed from order records
2
Franchise locations scaled
~$15,000/mo each, ~$180K annualized
200-300
Daily transactions per location
now with structured historical tracking
Full
Inventory traceability
factory production through to franchise-level sale
> the lesson

The most valuable part of this engagement wasn't a feature — it was turning a client's vague suspicion into a defensible, dollar-figure finding they could act on. Most operators sense something is off long before they can prove it or put a number on it; the value delivered was closing that gap between "we think something's wrong" and "here's exactly what it cost you, broken down by month."