IntelliGrocer
A multi-role supermarket operations platform with shopper, employee, and manager workflows connected through inventory, pricing, tasks, and reporting.
What the project is solving.
IntelliGrocer is a full-stack supermarket platform built to show how connected systems should behave when different users depend on the same operational data. Shoppers browse products, place orders, and see approved offers. Employees manage tasks, schedules, and shelf activity. Managers control inventory, pricing recommendations, staffing, and reports from one coordinated system.
I built IntelliGrocer to show more than UI polish. The goal was to model a believable retail system where multiple users affect the same data in different ways.
The strongest part of the project is the workflow connection: a manager can approve a price change, inventory can shift, and the shopper experience updates with the live offer instead of pretending the systems are separate.
Capabilities that make the build useful.
These are the parts that make IntelliGrocer feel like a connected product instead of a collection of unrelated screens.
How the system is structured.
A simple breakdown of the data and workflow path that gives the project technical credibility.
Role-based React frontend with dedicated dashboard flows
Express API layer handling auth, inventory, pricing, scheduling, and orders
MongoDB collections shared across shopper, employee, and manager workflows
Pricing logic that evaluates stock, demand, and expiry pressure before manager approval
Tools used
The stack reflects the actual repo and the workflow problems the project is trying to solve.
Interface snapshots
These panels stand in for the shopper, employee, and manager experiences and keep the case study visually scannable.
View 1
Shopper Experience
Product browsing, offers, category browsing, cart flow, and order tracking.
View 2
Employee Workspace
Task management, schedule visibility, stock checks, and cleaner mobile-first operational layouts.
View 3
Manager Operations
Inventory control, pricing approvals, reports, and full oversight of store workflows.
Key engineering lessons
The hardest parts of the build were mostly about coordination, state consistency, and keeping the system believable.
Keeping shopper-facing offers, inventory counts, and manager actions synchronized without fake disconnected logic
Designing three dashboards that felt consistent but still matched each user's job
Improving pricing behavior so approved changes would not immediately loop into opposite recommendations