Al-Aqsa Multi-Store E-Commerce
Online grocery ordering for a five-location US supermarket chain. One storefront, per-store delivery zones, live admin alerts and order updates delivered automatically over WhatsApp.
Problem
Five stores, zero ordering. Everything came in by phone. Orders, questions status updates. And staff spent hours calling customers back. Each location had delivery areas and pickup schedules so one shared system had to behave differently per store without becoming five separate codebases.
Key Highlights
- ZIP-code delivery validation per store. Customers only order what their location can deliver.
- Scheduled home delivery and in-store pickup with time windows.
- Dynamic offers engine. Tiered discounts, minimum-order thresholds, automatic free-item giveaways.
- Real-time admin alerts the moment an order lands.
- Automated WhatsApp updates: placed, processing, out for delivery delivered.
- Stripe checkout, cash on delivery and guest checkout.
What I built
A Next.js storefront, a Node.js/Express backend with MongoDB and Redis and an admin analytics dashboard. One codebase running isolated instances per store. Background job queues drive the WhatsApp notification engine so messaging never slows the store down and financial calculations use fixed-precision types end to end because groceries can't be off, by a cent.
Measurable Impact & Outcomes
- Fulfillment turnaround dropped by ~45% with live alerts
- +20% average order value lifted by dynamic offers
- 5 locations running unified on one codebase
Need a similar performance turnaround?
Whether you are rebuilding a legacy slow site or building a conversion-first funnel from scratch, let's discuss your timeline and technical specs.