POS / Restaurant · 2026

Restaurant POS System

A restaurant point-of-sale with the back office built in: orders for dine-in, takeaway and delivery, a kitchen display, cash shifts, recipes and item costing, stock, staff and a daily profit and loss.

Client: Tech Solutions product, deployed for restaurants in Pakistan including Hidden Bites and Mad Max
Hidden Bites
Mad Max
Role: Product design, build, deployment and support
Stack: Next.js 14 (App Router) · TypeScript · Prisma · PostgreSQL · Railway · Embedded PostgreSQL (offline build)

Updated 14 Nov 2026

Restaurant POS System — Order screen: dine-in, takeaway, delivery and Foodpanda tabs, menu by category, bill with discount, tax and payment mode (demo restaurant)

The problem

Restaurants were running a till that recorded sales and a set of spreadsheets for everything else: recipes, purchases, stock counts, staff attendance and the month-end profit figure. The two never agreed, food cost was a guess, and the owner learned how a week went a month later.

What I built

One application covers the counter and the office. An order placed on the till prints a receipt, appears on the kitchen display and reduces stock through the item's recipe. Purchases update the cost of each ingredient, so the recipe cost sheet shows the margin on every menu item at today's prices. Cash shifts compare what the drawer should hold with what was counted. It ships two ways: a cloud build where every screen shares one hosted database, and an offline build that runs the same app and its database on a single PC at the counter.

Order screen for dine-in, takeaway, delivery and Foodpanda, with tables, waiters, discounts, vouchers and tax
Order queue and kitchen display with elapsed time per ticket
Cash shifts: opening float, expected against counted cash, day close
Menu, price rules and deals
Recipes and recipe cost sheet with margin per item
Products, purchases, purchase orders, opening and closing stock, consumption
Sales, item, comparison and void reports; sales forecast and item targets
Profit and loss with fixed expenses and charge rules
Employees, attendance and payroll
Customers by phone number
Users and roles with an activity log
Cloud build on Railway, and an offline Windows package with install, start, stop and check scripts

Outcome

The owner reads margin per item and profit per day from the same system the cashier sells on, and stock counts start from what the recipes say was used instead of from zero.