UrsaCode

Case study · Client work

ZingnCrisp

The ordering site and the in-store point of sale for a fast-food cafe in Peshawar.

  • BuiltFrom August 2025
  • What we didWebsite, point of sale, kitchen screen, staff app
  • ClientZingnCrisp, Peshawar
The point of sale on a staff phone: menu categories for dine-in, takeaway and delivery.
Taking an order
The kitchen screen: 2 order tickets with Start cooking and Mark ready buttons.
The kitchen screen
Taking payment: cash, card or wallet, with the change worked out.
Payment and change
The staff app offline, showing one order waiting to sync.
Working offline
3,000+orders through the point of sale
190trading days in daily use at the counter
3staff roles: cashier, kitchen, manager
1install on the shop's PC

01The brief

ZingnCrisp is an evening fast-food cafe in Peshawar. It needed 2 things: a site where customers can see the menu and deals and order straight away, and a system for the shop itself to take orders at the counter, send them to the kitchen, take payment and close each day's books.

02What we built

  • The ordering site. Menu and deals online, where every "Order now" opens a WhatsApp chat with the cafe.
  • A point of sale for the counter. PIN sign-in for cashiers, kitchen staff and the manager, each seeing only what their job needs.
  • A live kitchen screen. New orders appear the moment they're taken; cooks start and finish them with a tap.
  • Payments and receipts. Split payments, refunds and 80 mm thermal receipts.
  • Reports by business day. The cafe trades from 4 pm to 1 am, so a sale at half past midnight counts toward the evening it belongs to.
  • A staff app for phones. It pairs with the shop's PC by scanning a QR code, and keeps taking orders when the network drops.

03The hard parts

Orders that survive a dropped connection

When the shop's network drops, the staff app queues orders on the phone and sends them when it reconnects, without ever creating the same order twice.

A day that ends after midnight

Reports follow the cafe's trading day, 4 pm to 1 am, not the calendar, so each night's takings close as one day.

Moving the database mid-service

The system moved from MySQL to SQLite to run as a single install on the shop PC, and the menu's photos were recovered from the old data along the way.

04In use

The point of sale ran the counter and the kitchen every evening: more than 3,000 orders across 190 trading days.

05Built with

  • FastAPI
  • React
  • SQLite
  • WebSockets
  • Expo (Android)
  • Thermal printing

Related service: Business systems.

Running a shop that's outgrown paper?

Point of sale, kitchen screens and ordering, built around how you trade.

Start a project