Share this case study

Grandma's POS & franchise operations

Copy link

Case-study QR code

QR code linking to the Grandma's POS & franchise operations detailed case study Download QR

Scan to open the detailed case study.

Share with an app

Detailed case study · Operations · Food service

Grandma's POS & franchise operations

I built a branch-aware operations platform for a food-service business that needed point-of-sale, inventory, supply orders, and staff access to work across locations, including when internet connectivity was unreliable.

Role
Solo full-stack developer
Period
October 2025–May 2026
Status
Deployed on Cloudflare Workers
Supply order screen with branch selection, raw-material search, and quantity controls

01 / The problem

Daily operations crossed branches and workflows

This was more than a checkout screen. Staff needed to process sales, manage ingredients, move supplies between locations, verify payments, and hand work over through preparation and pickup. Branches also needed their own users, stock, and reports.

The system had to remain useful through internet outages and replace manual coordination across spreadsheets and separate operational tools.

02 / The approach

Treat offline use and branch context as core requirements

I built the point-of-sale client to store sales locally with IndexedDB and Dexie, then synchronize them with the backend when connectivity returns. User sessions are scoped to a branch so staff work with the location’s own operational context.

I organized supply orders around a traceable lifecycle: create the order, review and verify payment, prepare it, confirm pickup or receipt, and retain an activity log. A custom transaction wrapper keeps multi-step backend operations atomic.

03 / The solution

Connect sales, stock, orders, and access control

I built the application with SvelteKit, TypeScript, and Hono, backed by Cloudflare Workers and D1. Product recipes connect sales to ingredient deductions; branch staff can manage supply orders, attach payment proof, and follow preparation and receiving status.

The wider system includes audit logs, order chat, inventory and production tools, and configurable roles with more than 30 permissions. Payment-proof files are queued locally and synchronized to Google Drive through its API in the background.

04 / What changed

One deployed platform supports the branch workflow

The application is deployed on Cloudflare Workers. Its documented capabilities include offline sales with later synchronization, recipe-based stock movement, branch-scoped operations, payment verification, configurable access, and an order history staff can trace.

The screenshots show the branch selector, supply-order and payment-verification screens, preparation progress, order logs, and role management.

Project evidence

Interfaces and workflows from the work.

Selected project screens and diagrams support the details in this account.

A useful place to start

What is slowing your
business down?

Tell me about the workflow, the friction, and what a better version would look like.

Schedule a call