Smart Rannaghor
Cook Smart. Save More. Live Better.
Created on 7th September 2025
•
Smart Rannaghor
Cook Smart. Save More. Live Better.
The problem Smart Rannaghor solves
Globally, one-third of food produced is wasted, resulting in substantial financial losses for families and environmental degradation as the planet suffers from increased carbon emissions and resource depletion. Households frequently forget expiry dates, overbuy groceries, and lack effective inventory management, leading to unnecessary discarding of edible items. In India, this issue is particularly acute, with average households wasting 50-70 kg of food annually, and 40% of urban food waste stemming from poor storage and expiry oversight. Simultaneously, communities grapple with paradoxical challenges of food surplus in some areas leading to waste, while others face shortages, exacerbating inequality and sustainability concerns. This inefficiency not only drains household budgets—potentially costing ₹15k–20k per year—but also hinders eco-friendly practices, highlighting the urgent need for innovative tools to minimize waste, optimize grocery planning, and foster community sharing for a more sustainable kitchen ecosystem.
Challenges we ran into
While building Smart Rannaghar, our team faced a few technical and logical hurdles:
1.Expiry Date Tracking Bug
Initially, we had issues with storing and comparing expiry dates in the database. Dates were being saved as plain strings, which caused errors when calculating “days left.”
Solution: We switched to using proper date formats (DATE type in Supabase) and added a check to calculate expiry using JavaScript’s Date object.
2.Inventory Update Errors
When adding new grocery items, our frontend sometimes showed “function not defined” errors (e.g., addInventoryItem is not defined).
Solution: We refactored the code so all functions were properly imported and ensured event listeners were bound after DOM loading.
3.Price Compare
We could not find the API to compare the price of the online shop.
Team Collaboration & Merge Conflicts
While pushing code to GitHub, we often faced merge conflicts because multiple members were working on frontend and backend simultaneously.
Solution: We adopted a branching workflow (feature/branch) and resolved conflicts by frequent pulls and proper code reviews.
Technologies used