Our own productCustom softwareAutomationHospitality and restaurants

A single-station point of sale system that ties cafe orders to stock and loyalty

Our own product, built for the cafe we own in Islamabad. March to June 2026, 4 months.

A link is coming soon.

from the first commit to a point-of-sale MVP, March 2026
1 week
tables in one PostgreSQL schema, from orders to loyalty
20
workflow maps over a 22-entity domain model
22

Point of sale system at a glance

Challenge
The cafe's till ran on a third-party point of sale, so nobody could answer what was sold against what was used.
Solution
A point of sale with a barista queue, recipe-linked stock, shifts and loyalty, on one 20-table PostgreSQL schema.
Result
A working point of sale a week after the first commit, so the cafe runs tills, stock and loyalty on one system instead of three.

The point of sale system challenge

The cafe runs its till on a third-party point of sale, and its stock, recipes, shifts and loyalty live outside it, so nobody can answer what was sold against what was used. The owner wanted operations tooling the cafe could run itself, on one schema where a sale draws down stock through its recipe and a void leaves a trail. 93 Brew OS is that system, built as our own product.

What went into the point of sale system

Web app

  1. A single-station point of sale and order list, so checkout and preparation progress stay on the cafe's central laptop

  2. Void reversals with an audit trail, so a canceled sale is reversed rather than deleted

  3. A stock record tied to recipes, so each sale draws down the ingredients it used

More of what we built4
  1. Shift management and a loyalty scheme over the same customer records

  2. A 20-table PostgreSQL schema with Drizzle for typed access, Zod validation, JWT auth with bcrypt hashing and a Jest suite

  3. A product requirements document, 22 workflow maps, a 22-entity domain model and a five-wave implementation roadmap

  4. A deliberately bounded MVP scope: one active cash session, ingredient and loyalty ledgers, and paid-order void reversals; no multi-location, offline-sync or separate barista-device workflow

Point of sale system results

The point-of-sale MVP was ready a week after the first commit, and the cafe has an operations system of its own to grow into: one schema where a sale, its stock, the shift it happened on and the customer's loyalty balance are the same record. We walk through it on a call.

Done again today

What this would cost today

Done again today, work like this usually costs $2K to $6K (Operational platform build). The free plan says whether it fits before anything is priced.

  • Operational platform build

    The workflow a department runs on, built as real software with the roles, records and history it needs.

    $2K to $6K, usually fixed-price

    2 to 4 weeks

    Get a quote for this

Your project, next

Have a problem in this shape?

Say so in a few sentences. The free plan comes from the person who built this one.

We usually reply within 2 business days with a free plan for what to do first. No call needed.