Cirebon Kuring Cafe - Cafe Management System

Project Overview

A complete operating system for Cirebon Kuring Cafe — covering everything from the moment a customer scans the QR code on their table to the owner closing the month's payroll. Instead of stitching together separate POS, inventory and HR tools, everything lives on one Supabase (PostgreSQL) backend and is served through four purpose-built applications.

The Four Applications

Architecture

The repository is a Turborepo + pnpm monorepo. Shared packages keep the four apps consistent:

• shared-types — one source of truth for orders, menu, payments, inventory and employees
• utils — currency, tax, discount and payroll calculations plus Indonesian-specific validators
• ui-components — shared React components
• database — typed query helpers

Business rules that must not be bypassed by any client — order validation, payment verification, stock deduction, attendance validation and report generation — run as Deno Edge Functions on Supabase, while Row-Level Security policies make sure each role can only read and write what it should.

Order Flow

Scan table QR → Browse & customize menu → Checkout
      ↓
Payment (cash / QRIS / transfer with proof upload)
      ↓
Cashier verifies → Kitchen display → Waiter serves → Completed
      ↓
Ingredients auto-deducted · Receipt printed · Customer can rate

Every status change is pushed in realtime, so the customer's order-status page, the kitchen tablet and the owner's live orders view always show the same state.

Inventory That Costs Itself

Menu items are linked to their ingredients, so completing an order automatically deducts stock at the database level. Purchases are recorded as batches with expiry dates, and the unit cost of each ingredient is recalculated with a moving-average cost method (including delivery-fee allocation). That means gross margin per menu item is based on what the cafe actually paid, not a fixed estimate. Expired batches are written off automatically and low-stock alerts are sent to the owner.

People Operations

• Attendance — clock-in is validated against the cafe's configured location radius, with rules for lateness and early leave set by the owner.
• Scheduling — shift templates and a weekly schedule builder.
• Requests — leave and overtime requests flow from the employee portal to the owner for approval.
• Payroll — monthly payroll computed from attendance and overtime, exported as PDF payslips.

Key Takeaways

• Putting critical rules in the database and edge functions, not the UI, kept four different clients consistent.
• A monorepo with shared types caught breaking changes across apps at compile time.
• Real operational data (stock, cash, attendance) forced careful handling of edge cases that tutorials rarely cover — partial payments, expired batches, missed clock-outs.

Repository: CirebonKuringCafeApp · Period: June 2025 – March 2026