Frollie OS

Frollie OS — the agentic operating system Frollie runs on.

Started as a recipe costing tool. Now it is the operations backbone for an Indonesian FMCG snack business — orders, kitchen production, inventory, multi-channel sales, and a full accounting layer, all on one real-time backend. Open-sourced as product_master (the repo README calls it Frollie Pro); on this site it is Frollie OS.

What it does

The app is laid out the way staff actually use it — orders front and center, then kitchen, ops, finance, and config behind that.

• Orders & fulfillment. A real-time kanban across the whole lifecycle, Draft through Complete. Build an order item by item with live pricing and a bank-transfer reference number; capture payment; print a branded invoice.
• Kitchen production. A touch screen for the production floor. Balls get produced into trays and auto-allocate to the oldest pending orders, so the kitchen works the queue without anyone assigning it.
• Recipes & costing. An ingredient catalog drives cost-per-gram; products sit on a unified Bill of Materials that resolves into COGS and contribution margin. Bulk-update ingredient prices and the margins recompute everywhere downstream.
• Inventory. Stock with FIFO batch tracking, reserved on order confirmation and consumed on fulfillment, across multiple locations.
• Sales channels. Pulls platform sales from Shopee, BigSeller, GoFood, and GrabFood incrementally and reconciles them into the ledger, attributing revenue to the actual platform rather than the aggregator. K3Mart runs as a consignment partner with its own sales-sync cockpit. Units are counted as BOM-resolved balls — a 3-ball hamper counts as 3 — so per-ball unit economics are real.
• Finance & accounting. A double-entry layer, not just reports: income statement off the ledger, expenses with an approval queue, payroll, an editable chart of accounts, bank reconciliation, and a fixed-asset register with depreciation.

How it works

Everything is live over Convex. Changes push to every connected screen the moment they happen — no refresh, no cache to bust. Kitchen staff see new orders as order staff type them; managers see margins move as ingredient prices change.

Login is PIN-based, and roles decide what you can touch: kitchen, order_staff, manager, admin. Each role lands on its own home screen, and the kitchen sees orders cost-stripped.

Stack

Convex for the serverless backend and real-time database, React 19 and TypeScript on the front, Vite for the build, Tailwind 4 and shadcn/ui for the interface. The whole thing is Claude-Code-deployed.