D2C Franchise Inventory Platform
Budget: ₹12,500 – ₹37,500 INR
I need a single, end-to-end system that keeps every franchise outlet, manager and customer on the same page—from stock availability to final payment. Today our stores work in silos; the goal is to replace those patch-ups with a streamlined inventory + e-commerce solution that scales nationally.
Core workflow
• A cloud back office maintains one source of truth for product data and real-time stock levels. Every inward or outward movement instantly updates so that managers, regional leaders and HQ can act on accurate numbers.
• Automated restocking alerts must trigger when any SKU approaches its reorder point, reducing manual checks.
• A role-based dashboard gives franchise managers the ability to transfer, reserve or write-off stock while leadership views consolidated analytics.
Customer touchpoints
• Android app and responsive web storefront show only the items physically available at the shopper’s chosen location.
• Shoppers place new orders or raise product-request tickets that flow straight to the outlet’s queue.
• Integrated payment gateway processes cards, wallets and UPI, yet staff can still mark cash or offline transactions as “paid,” keeping the status log unified.
Billing & fulfilment
• On confirming payment, the system should generate an invoice that staff can share or print instantly as PDF or JPEG—handy for mobile stalls and events.
• Order history, delivery status and refunds all stay visible to both customer and staff.
Desired deliverables :
0. Most Important tech stack and code base should only use open source and self coded stuff , no paid plugins or complex frameworks. only popular/common libraries/languages and frameworks allowed (good examples : Android : Java/kotlin, native platform, libraries like retrofit, okhttp, compose,etc . bad examples : react native, flutter, maverics, etc)
1. Source code for back-end, Android app and web front : Android: native app, kotlin (view/compose both are fine) | web backend: REST+json based apis , expo/js/ts acceptable. springboot preferred , django/python/others not acceptable | web frontend : vanilla preferred, though react also works. DB : AWS,firebase.
2. Deploy scripts / CI-CD notes so we can spin up staging and production quickly.
3. Database schema and API documentation. Try to add maximum optimisation for api calls/costing. use as much caching as possible without impacting real time updates
4. Short hand-off session plus 30-day defect-fix window.
If you’ve built multi-location retail or franchise tools before—especially anything that mixes automatic and manual payment flows—let’s talk.
Core workflow
• A cloud back office maintains one source of truth for product data and real-time stock levels. Every inward or outward movement instantly updates so that managers, regional leaders and HQ can act on accurate numbers.
• Automated restocking alerts must trigger when any SKU approaches its reorder point, reducing manual checks.
• A role-based dashboard gives franchise managers the ability to transfer, reserve or write-off stock while leadership views consolidated analytics.
Customer touchpoints
• Android app and responsive web storefront show only the items physically available at the shopper’s chosen location.
• Shoppers place new orders or raise product-request tickets that flow straight to the outlet’s queue.
• Integrated payment gateway processes cards, wallets and UPI, yet staff can still mark cash or offline transactions as “paid,” keeping the status log unified.
Billing & fulfilment
• On confirming payment, the system should generate an invoice that staff can share or print instantly as PDF or JPEG—handy for mobile stalls and events.
• Order history, delivery status and refunds all stay visible to both customer and staff.
Desired deliverables :
0. Most Important tech stack and code base should only use open source and self coded stuff , no paid plugins or complex frameworks. only popular/common libraries/languages and frameworks allowed (good examples : Android : Java/kotlin, native platform, libraries like retrofit, okhttp, compose,etc . bad examples : react native, flutter, maverics, etc)
1. Source code for back-end, Android app and web front : Android: native app, kotlin (view/compose both are fine) | web backend: REST+json based apis , expo/js/ts acceptable. springboot preferred , django/python/others not acceptable | web frontend : vanilla preferred, though react also works. DB : AWS,firebase.
2. Deploy scripts / CI-CD notes so we can spin up staging and production quickly.
3. Database schema and API documentation. Try to add maximum optimisation for api calls/costing. use as much caching as possible without impacting real time updates
4. Short hand-off session plus 30-day defect-fix window.
If you’ve built multi-location retail or franchise tools before—especially anything that mixes automatic and manual payment flows—let’s talk.