Contact person: Business Client

Phone:Show

Email:Show

Location: Thiruvalla, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"ZUPPR – BARE MINIMUM MVP (Developer Brief)

Goal:

Build a simple, stable, cluster-based food delivery MVP that allows customers to place orders, restaurants to receive them, and riders to deliver — with basic fees, basic tracking, and no extra frills.
This version should work for 0–500 orders/day and survive until seed funding.

⸻

1. USER TYPES
1. Customer
2. Restaurant
3. Rider
4. Admin (Founder Panel)

⸻

2. CORE FEATURES (ABSOLUTE MUST-HAVES)

These are the ONLY features required before investment.

⸻

A. Customer App (MVP)
• Onboarding: Mobile OTP login
• Cluster-Based Restaurant List: Show restaurants only within user’s cluster
• Menu View: Basic menu with item name, price, add/remove
• Cart + Order Summary
• Delivery Fee Logic:
• Below ₹499 → customer sees the split fee (e.g., ₹12.50 or ₹35 depending on your model)
• Above ₹499 → free delivery or whatever model you finalize
• Payment Options:
• Cash on Delivery (CoD) first release
• Online payment integration can be added after stability
• Order Confirmation Screen
• Order Status Updates: Accepted → Picked → Delivered (manual rider updates)

⸻

B. Restaurant App (MVP)
• OTP Login
• Receive Orders: Simple “Accept / Reject”
• Order Dashboard: Active orders, completed orders
• Edit Menu: Only basic text + price (no photos needed in MVP)
• Payout Summary: Show what they owe or pay per order (delivery fee + platform fee)

⸻

C. Rider App (MVP)
• Login with OTP
• Order List: Show assigned orders only
• Update Order Status:
• Picked
• Delivered
• Earnings Summary: Per order earning shown simply
• Navigation: Deep link to Google Maps (no in-app map needed)

⸻

D. Admin Panel (Critical MVP)

Minimal dashboard for the founder:
• Live Orders
• Restaurant Management: approve/disable stores
• Rider Management: onboard/disable
• Cluster Management: Assign pin codes to clusters
• Manual Reassign Orders
• Order History + Basic Reports

⸻

3. SYSTEM REQUIREMENTS
• One Flutter app split into 3 logins:
Customer / Restaurant / Rider (all in one codebase, different UI after login)
• Backend: Node.js or Firebase (developer chooses cheapest & fastest)
• Database: Firestore / MySQL
• Notifications: Firebase push
• Hosting: Cheapest scalable cloud (Render, Railway, or Firebase)

⸻

4. NO NEED IN MVP

Remove all the following until funding:

❌ Live GPS rider tracking
❌ Wallets / refunds
❌ Discounts, coupons, offers
❌ Restaurant photos / item photos
❌ Search & filters
❌ Ratings / reviews
❌ Subscriptions (999 plan etc.)
❌ Analytics
❌ Notifications to admins (manual monitoring is fine)
❌ Multiple clusters auto-assign (do manually in admin)

Keep it super lightweight.

⸻

5. ORDER FLOW (Developer Must Know)
1. Customer places order
2. Restaurant accepts
3. Admin or system assigns rider
4. Rider updates picked → delivered
5. Customer pays COD (online later)
6. Restaurant settles weekly with Zuppr

⸻

6. DELIVERY FEE LOGIC (Developer-Ready)

Developer must build a simple fee engine where:
• They see two values:
• Restaurant side fees (e.g., 50 + 12.50 platform fee)
• Customer side fees (e.g., 12.50 platform fee or 0 on >499)

Fee rules will be stored in backend and editable later.

⸻

7. TIMELINE TARGET

3–4 weeks for full MVP (if developer is decent).
This is NOT a complex build.

⸻

8. SUCCESS METRIC FOR MVP

If it can handle:
• 100 restaurants
• 50–100 riders
• 500 orders per day

WITHOUT crashing → MVP is successful." (client-provided description)