DPMBG — Dapur Pintar MBG

Highlights

• ★Each kitchen's data stays isolated, verified by 96 automated tests
• ★Full ownership: I built the backend, frontend, deployment, and ongoing operations
• ★Updates ship without taking the system offline

Problem

Indonesia's school nutrition programme serves millions of meals every day, yet kitchen operators run on spreadsheets — menu planning, ingredient variance, delivery routing, and coordination across multiple kitchens all break the moment one operator runs more than a single kitchen.

Approach

• —One platform handling three layers — the programme, each operator (foundation or company), and each kitchen — with cleanly separated permissions so no one sees data they shouldn't
• —Built-in optimisation engines for menu planning and delivery routing, instead of manual scheduling on a whiteboard
• —Automated price-checking for ingredients, refreshed on a schedule, so costs stay current without manual lookups
• —QR-code scanning for receiving deliveries, plus thermal-printer support for kitchen tickets
• —Live updates push to a mobile-friendly dashboard that installs on operator phones and works offline
• —96 automated tests across realistic multi-kitchen scenarios — verifying every kitchen's data stays separate, even with mixed foundation + company operators sharing the platform

Stack

Outcome

• —Live in production for the pilot kitchen (SPPG Paseh)
• —Variance reporting replaces manual reconciliation between planned menus and actual deliveries
• —Foundation for the GiziGuard on-site AI nutrition layer (next project)

Tags