The problem
NAZAFAT-IMS was built for a cleanliness committee that needed to keep track of supplies across different areas. Administrators maintain the product list and available stock, while area heads request materials for their teams. The application brings those requests, the resulting stock movement, and reusable-item returns into one place.
What I built
I worked on a Next.js application with separate admin and area-head interfaces. The repository includes inventory, request, return, and area-wise reporting screens, with Supabase supporting application data and authentication. The role-based structure matters because the people requesting materials need a simpler view than the staff responsible for stock control and approvals.
- The role-based workflow replaced scattered supply records with a shared view of stock, requests, and returns.