A franchise management platform where outlet managers close each day's cash, sales and expenses, and head office sees every outlet's gaps, payroll, orders and audits in one place.
A multi-outlet cafe franchise needed each outlet's nightly cash close, staff attendance and salary, supplier orders and inspections in one place, with head office able to see across all outlets at once.
The people entering the figures are outlet managers at the end of a long shift, on a phone. Head office needed to know what was wrong today, not to admire totals.
ByteHint built one Next.js app on one Supabase project, with every write going through a server action. Access rules and the day lock are enforced in the database, so a manager only sees their own outlet and a sent day cannot be edited.
Sales by payment channel, purchases and expenses with bill photos, cash count with a required note on any difference, then send and lock. Autosaves every field.
A sent day reopens for 24 hours only after head office approves. Each edit records the field, old value, new value, who and when.
One list of what is wrong today: days not sent in the last week, cash differences past a threshold, pending change requests and overdue audit fixes.
Monthly salary per outlet from attendance, paid leave and overtime. Each row shows its working, and finalised months are stored and locked.
Orders open on set days until a cutoff in local time, checked on the server and in the database. Head office moves orders through dispatch and delivery.
Auditors rate a checklist. Low ratings become problems, which the outlet answers with a cause, an action and a photo. The audit closes when all are answered.
Profit and loss per outlet for any period, plus Excel and two TallyPrime import files, so the accountant never re-types figures.
Every list screen downloads an Excel file built on the server, honouring the screen's filters and the user's role.
Head office invites managers and auditors with one-time links. Sign-in lockout and rate-limited password reset.
Managers open the app on a phone and land on today's close: sales per payment channel, purchases and expenses with bill photos, and a cash count. Every field saves as they go, and once the report is sent the day is locked.
Mistakes go through a change request that head office approves, and every change is recorded. Head office starts from a list of flags, runs salary with the working shown, and downloads Excel and TallyPrime files.
Architecture · Architecture
Infrastructure and delivery · Infrastructure
Data model · Data Model
Nightly close · User Flow
Change request · Sequence
Order window · Sequence
Invite and sign-in · Auth Flow
Chose Postgres row level security on every table, plus a role check in every server action over Checks only in application or API code
The main risk is one outlet's manager seeing another's revenue. With RLS a missed check in one screen still returns no rows, and the day lock holds even if a screen is wrong. A live test suite signs in as each role to prove it.
Chose Next.js server actions for every write, route handlers only for file downloads over A REST or GraphQL layer with a client data library
A form-heavy internal app with one client does not need an API layer. One hand-written validator module per form runs in the browser for inline errors and again on the server, which never trusts the client result.
Chose bigint paise for every amount and business dates resolved in the Asia/Kolkata timezone over Decimals and server-clock dates
Cash differences and accounting vouchers must balance exactly, and a close done after midnight belongs to the previous trading day. Both helpers are unit tested.
Chose Lazy expiry of reopened days and salary runs created on first open over Hourly and monthly cron jobs
Correctness never depends on a job having run: the read path and the database policy both check the reopen deadline. Fewer moving parts to run and monitor.
Chose Store every computed salary figure when a month is finalised; generated columns for cash variance over Recompute on read
A salary sheet finalised in March must read the same in December after the rules change, and a generated column cannot drift from its inputs.
Phase 1
Phase 2
Phase 3
Phase 4
Phase 5
2
Access leaks caught before launch
The live RLS suite found two holes on its first run (drafts visible to head office, salary unlockable by managers). Both fixed.
18 to 1
Migrations squashed, proven identical
Verified object by object against a fresh build of the old files and against the live database.
95%
Line coverage of tested core modules
95.21% lines, 86.16% branches across the 17 library modules loaded by the unit tests, measured 2026-10-09.
80
Row level security policies
Across 27 tables, so outlet isolation and the locked day hold in the database, not just in the screens.
152
Unit tests passing
Money, business dates, order window, salary math and TallyPrime export, run before every push.
3
Roles enforced in the database
Head office, outlet manager and auditor, each seeing only what it should.
The app covers every module in the original spec plus three later client requests: outlet audits, product photos and a finance view with TallyPrime export. The schema is applied to the live project, and the unit and live access-rule test suites pass.
Tell us what you're building and we'll show you how we'd approach it.
Consumer apps and creator economyA studio promised its creator client an AI social app in a month with one developer. We scoped the real need and had four roles working eight days after the first call.
Gaming and PC optimizationA full-stack, design-first e-commerce build for a PC optimization brand, with cart, checkout and key delivery, that reached a client-reported 25% CTR in a low-conversion niche.
Gaming and PC optimizationA Discord bot that pulls the best gaming deals from Amazon through its Product Advertising API and posts them to the community every four hours.