·3 min readBy Adnan AliUpdated

Building Cheezious with Next.js and NestJS

Next.jsNestJSFood orderingProject work

My work on Cheezious covered the customer ordering website and the tools used behind the counter. I built the storefront and admin dashboards, designed APIs for orders across restaurant branches, and worked on connections to POS machines, kitchen displays and delivery tracking. Menu management and marketing campaign tools were also part of the scope.

The website was one part of the application

A customer needs to browse a menu and place an order. Branch staff need a different view: which orders have arrived, what the kitchen needs to prepare and where each delivery stands. That is why I describe this project through its connected workflows, rather than only showing a checkout screenshot.

The stack included Next.js for the website and dashboards, NestJS for the APIs, PostgreSQL for application data, and Redis and Socket.IO for real-time work. Deployment used AWS, Docker and GitHub Actions. The work connected the public ordering journey to the tools branch staff use.

The branch tools changed the scope

POS connections, kitchen screens and delivery tracking introduce interfaces beyond a browser page. For a similar application, I would want to establish which system owns an order, which transitions staff can make, and what the customer should see at each point. Those decisions need to be clear before an integration can be tested usefully.

  • Identify the customer, branch, kitchen and delivery views of the same order.
  • Document the input and expected result for each connected service.
  • Decide what staff should do when a connected service does not respond.
  • Check permissions for menu changes, order actions and branch-level views.
  • Include admin and reporting screens in the scope, rather than treating them as an afterthought.

What I can show from this work

The project demonstrates frontend and backend work on a full ordering application, including APIs designed for thousands of simultaneous orders. The case study shows the delivered features, the stack and the role of the customer and branch interfaces.

See the Cheezious project scope and technology stack →

If you are planning an ordering application

Send the ordering journey, the number of branches involved, the POS or other services it must connect to, and the admin tasks staff need to perform. If there is an existing application, include the part that needs changing. That is enough to start a useful scope discussion and identify which details need investigation.

Discuss a Next.js and NestJS application →