CUSTOMER
identity · store credit · debt
01 / RETAILA / PRODUCTION SYSTEM
Retail operations, connected to the money.
A production multi-tenant retail management platform built to run day-to-day operations and financial workflows for retail businesses.
production statuslive
5
SHOPS · running on the platform
- MULTI-TENANT
- BUSINESSES · data isolated per tenant
- PRODUCTION
- USED IN THE REAL WORLD · live operations
production case study · fig 01multi-tenant · financial core
02 / Real product demo
See it in action
A full point-of-sale workflow, recorded from the real product — the cursor moves the way an operator does: sale, payment, and the inventory and financial effect each one leaves behind.
retailla · point of salerecording
POS → SALE → PAYMENT → INVENTORY → LEDGERfig 02 · desktop
03 / A sale's path
One transaction. The whole system moves.
A sale at the counter is not a single screen — it is a chain that ends in the ledger. Scroll, and the system draws itself the way a checkout actually runs.
CART
session state
CHECKOUT
atomic Postgres RPC
ORDER
order + items + payment method
INVENTORY
stock moves with the order
PAYMENT
cash · card · store credit
CASH LEDGER
append-only financial event
REPORTS
derived from the ledger
04 / Financial system
More than a POS.
Operational activity is connected to financial state. Sales, refunds, expenses, and store credit all converge on one cash ledger — and history is append-only.
operations
every flow feeds the money- SALES
- REFUNDS
- EXPENSES
- VENDOR PAYMENTS
- OWNER FLOWS
- STORE CREDIT
the ledger
CASH LEDGER
append-only · never rewritten
financial ledgers
three more, append-only- store_credit_pool_ledgershared credit balances
- store_credit_ledgercredit issued and used
- customer_debt_eventsdebt history
CASH LEDGERfig 04 · live ledger
05 / System map
The domains, and how they connect.
Ten domains inside one tenant boundary. Select a domain to trace how it connects to the rest of the system.
SYSTEM MAPselect a domain to trace its connections
06 / Mobile product demo
The system, beyond the counter.
The same tenant, the same ledger — recorded on the floor, where the register fits in a pocket.
The register in a pocket
Operators run the same store data from a phone — sales, store credit, and the cash ledger in hand.
One system, both ends
The counter and the floor work the same tenant data — no second product, no separate sync.
retailla · on the floor
07 / Foundations
Built as a real product.
Not a demo, not a dashboard mock — the architecture underneath the counter.
TENANCY
Multi-tenant architecture
Tenancy is derived from the authenticated context — every query is scoped and isolated per business.
BACKEND
Backend-driven core
FastAPI services orchestrate the business logic, with complex rules executed as atomic database routines.
LEDGER
Financial integrity
Money movement is append-only — a ledger event is never rewritten, only balanced.
INFRA
Production infrastructure
Dockerized services on managed infrastructure, with authentication and operational tooling built in.
08 / Technology
Everything the platform runs on.
The stack the production system actually runs on.
- Stack
- PYTHON
- FASTAPI
- POSTGRESQL
- SUPABASE
- REDIS
- DOCKER
- RENDER
- GEMINI·OCR
- Layering
ROUTER → SERVICE → SCHEMAS → POSTGRES RPC / SUPABASE
- Year
- 2025
- Role
- Backend Engineer & Architect
09 / Proof & open source
The open-source core.
The repository is the open-source core the platform runs on — services, schemas, and ledger logic you can read in the open.