Skip to content
Bilal Ahmad

Case study · Food ordering · Loyalty

KFC Pakistan

Loyalty, scheduled ordering and QR dine-in for KFC Pakistan's ordering platform.

Role
Backend lead at Simplex. I built the loyalty, future ordering and QR dine-in features on the backend, from requirements to production.
Stack
NestJS · Node.js · React · MySQL · Redis
KFC Pakistan ordering website home page

01Project

What the system is

KFC Pakistan's online ordering platform. I work on it at Simplex Technology Solutions as backend lead, owning the services, APIs and integrations behind the features below.

02Problem

What needed solving

On top of standard online ordering, the platform needed a loyalty programme whose point rules the business can configure, orders that can be scheduled for later, and a way to order from the table in the restaurant.

03My role

What I was responsible for

  • Turned business requirements for loyalty and ordering into backend modules and APIs.
  • Built the loyalty engine so point rules are configured by the business instead of hard-coded.
  • Integrated the third-party loyalty services and built the reporting around them.
  • Worked with the mobile and marketing teams on the frontend integrations.

04Engineering

What I built

  1. 01

    Configurable loyalty engine

    Point management that the business can configure, with third-party integrations and reporting on top.

  2. 02

    Future ordering

    Customers can schedule an order for later, constrained to the store's operational hours.

  3. 03

    QR dine-in ordering

    Diners scan a QR code at the table and order directly from their own device.

05Technologies

How the pieces fit

  1. Client

    • React
  2. Services

    • Node.js
    • NestJS
  3. Data

    • MySQL
    • Redis
  4. Integrations

    • Third-party loyalty services
Simplified view of the technologies involved, grouped by layer. Not a full architecture diagram.

06Complexity

Engineering challenges

  • Point rules are configured by the business, so the loyalty engine evaluates rules defined as data rather than hard-coded logic.
  • Loyalty connects to third-party services and feeds reporting, so balances have to agree across every system that reads them.
  • A scheduled order is only valid inside the store's operational hours.
  • QR dine-in ties an order to a table in the restaurant instead of a delivery address.

Contact

Have a project, role or engineering problem in mind?

Tell me about the product, the problem or the role, and how I can help.

Based in
Lahore, Pakistan · UTC+5

All fields are required.