$ cat /work/subscription-operations-platform.md
industry
D2C meal subscription
region
Türkiye
year
2025–2026
status
●In development
# at a glance
Two-service platform with a typed API contract, token-based payment ledger, and a kitchen prep schedule on a fixed weekly cadence.
# problem
Subscription operations sit awkwardly between e-commerce and operations software. Orders, recurring billing, prep, packaging, and delivery all run on a shared cadence — but most off-the-shelf systems treat each as a separate silo with their own database.
The brief asked for a system that could be operated by floor staff during shifts and audited cleanly at month-end without spreadsheet reconciliation.
# approach
Split into two services that share a typed API contract: a FastAPI backend owns the operational ledger; a Next.js frontend handles ordering, customer self-service, and admin views.
Token-based payment ledger — every credit, charge, and refund is an immutable entry, never a mutated balance. Reconciliation reads the ledger; it doesn't recompute it.
Redis caches the per-shift prep schedule so the kitchen view stays responsive while the ledger keeps long-term truth in PostgreSQL.
# outcome
In active development. Operational schema and ledger contracts locked; ordering and admin surfaces shipping iteratively.
# stack