Case study · Food ordering · Loyalty
KFC Pakistan
Loyalty, scheduled ordering and QR dine-in for KFC Pakistan's ordering platform.
- Role
- Software Engineer at Simplex, working on backend services and the features below from requirements to production.
- Company
- Simplex Technology Solutions
- Stack
- NestJS · Node.js · React · MySQL · Redis
01Project
What the system is
KFC Pakistan takes customer orders online. I work on its ordering platform as part of the engineering team at Simplex Technology Solutions, mostly on the backend and its integrations.
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.
03Contribution
What I worked on
- Turned business requirements for loyalty and ordering into backend modules and APIs.
- Worked with the mobile and marketing teams on frontend integrations.
- Integrated third-party services and built the reporting around them.
04Engineering
What shipped
- 01
Configurable loyalty engine
Point management that the business can configure, with third-party integrations and reporting on top.
- 02
Future ordering
Customers can schedule an order for later, constrained to the store's operational hours.
- 03
QR dine-in ordering
Diners scan a QR code at the table and order directly from their own device.
05Stack
How the pieces fit
Client
- React
Services
- Node.js
- NestJS
Data
- MySQL
- Redis
Integrations
- Third-party loyalty services
06Complexity
What made it non-trivial
- 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.