System
WarungKit
Intro
A practical operating layer for UMKM: catalog, orders, and daily flow in one place.
Problem
There are two recurring friction points in UMKM operations. First, when too many features are introduced at once and paid from day one, teams often feel overwhelmed and end up paying for capabilities they do not actually use. Second, when businesses start from traditional or separated workflows, migration becomes heavy: catalog, orders, and reporting stay fragmented across chat, spreadsheets, and manual notes.
Solution
WarungKit is designed to grow with the user. It starts from a focused core, then expands progressively through modules that can be adopted step by step, so teams can move from traditional workflows without operational shock or feature overload.
Impact
From this foundation, rollout will continue in practical increments: keep shipping useful modules, grow with real user behavior, and sustain long-term fit for daily UMKM operations.
Tech / Architecture
WarungKit is currently built as a monolithic fullstack application on Next.js, with Supabase as the primary database layer. This is the foundation: a stable base to move fast during launch, while keeping a clear path toward modular boundaries as usage deepens across different UMKM contexts.