An enterprise-grade, Cloudflare-native blueprint to launch a Swiggy/Zomato & UrbanClap-class platform across five verticals: restaurant & hotel food, grocery & goods home delivery, in-stay hotel service, errands & courier, and on-demand home professionals — starting in Bhubaneswar & Odisha, designed to scale nationally.
SREE already operates a multi-sector business with live hyperlocal infrastructure (Saptahik Bazar, vendor network, battery-vehicle delivery, an agent earning program). SREE Delivery unifies these into a single consumer super-app that monetises the same delivery fleet and merchant relationships across five demand streams instead of one — maximising orders per rider, per kilometre, per day.
Tier-2/3 Odisha is underserved by national aggregators. Local trust, Odia-first UX, lower commissions and an existing fleet are a defensible moat.
One logistics backbone, five revenue verticals. Shared identity, wallet, address book, and rider pool — each new vertical adds margin without new fixed cost.
Cloudflare-native: Pages frontends, Workers APIs, Durable Objects for live order/GPS state, D1 for transactional data, Queues for dispatch. Low ops, global edge, pay-per-use.
Each vertical reuses the same accounts, payments, dispatch and tracking core. They differ only in catalog shape, fulfilment SLA and merchant type.
Browse nearby restaurants & hotels, dish-level menus, customisations, live prep + delivery tracking. The classic Swiggy/Zomato flow. SLA: 30–45 min.
Kirana, daily essentials and Saptahik Bazar produce delivered home. Slotted & express. Reuses the existing 207-item catalog & vendor portal.
B2B2C: partner hotels offer room-service, amenities & local errands to checked-in guests via QR menu. Hotel-branded, commission per order.
On-demand pickup-and-drop, parcel, document & "buy-me-this" tasks. Distance-priced. Monetises idle rider capacity between food peaks.
Plumber, electrician, AC repair, cleaning, salon-at-home, appliance service. Scheduled bookings, vetted pros, fixed/quoted pricing, ratings.
Pharmacy, meat/fish express, B2B restaurant supply and ticketing slot in as new "catalog types" — no re-architecture.
Every vertical is served by the same four actors and four product surfaces. Build the surfaces once; configure per vertical.
Installable PWA + web. Discover → cart/booking → pay → live-track → rate. Wallet, saved addresses, SREE Card discounts, Odia/English/Hindi.
Restaurants, hotels, kirana, Bazar vendors. Menu & stock management, accept/reject, prep status, payouts, hours & availability. Extends existing vendor-portal.
Delivery riders & service pros. Go-online, receive assignment, navigate, OTP-verified handoff, earnings & payout ledger, ratings.
Onboarding & KYC, live ops console (map of orders/riders), commission & pricing config, disputes & refunds, analytics, zone management.
Chosen to match SREE's existing stack (Pages + Workers + KV + R2, as used by samparana.com and bazar.samparana.com). No servers to manage, global low-latency edge, and pay-per-use economics that suit a hyperlocal launch.
CUSTOMERS / MERCHANTS / RIDERS / ADMIN (installable PWAs + web) │ ▼ ┌──────────────────────────────────────────────────────────┐ │ Cloudflare Pages — 4 frontends, one design system │ │ customer · merchant · rider · admin (sub-paths/sub-apps) │ └──────────────────────────────────────────────────────────┘ │ HTTPS / WebSocket ▼ ┌──────────────────────────────────────────────────────────┐ │ Cloudflare Workers — API gateway + business logic │ │ /api/auth /api/catalog /api/orders /api/dispatch │ │ /api/payments /api/track /api/admin │ └──────────────────────────────────────────────────────────┘ │ │ │ │ │ ▼ ▼ ▼ ▼ ▼ Durable D1 KV R2 Queues Objects (SQL: orders, (sessions, (menu/dish (dispatch + live order merchants, rate-limit, images, notify + state + menus, config, KYC docs, settlement rider GPS payments, geo-cache) invoices) jobs) + WS hub riders…) │ ▼ external integrations Razorpay (UPI/cards/payouts) · Google Maps/Ola Maps (geo, ETA, routing) WhatsApp Cloud API + SMS (MSG91) · Workers AI (support bot, reuse from samparana.com)
| Primitive | Role | Why it fits |
|---|---|---|
| Pages | 4 frontend apps + this site | Already the SREE deploy pattern; per-app projects + subdomains. |
| Workers | Stateless API + auth + routing | Edge-fast, scales to zero, same model as existing functions/api/*. |
| Durable Objects | One object per live order; rider GPS hub; WebSocket fan-out | Strongly-consistent, single-threaded state — perfect for an order state machine + real-time tracking without Redis/Socket.io. |
| D1 (SQLite) | Transactional system-of-record | Relational orders/menus/payments with SQL; cheap; edge-replicated reads. |
| KV | Sessions, rate limits, config, geo cache | Already used for visitor counter + rate limiting on samparana.com. |
| R2 | Images, KYC docs, invoices | Zero-egress object storage; same pattern as planned VENDOR_DOCS bucket. |
| Queues | Async dispatch, notifications, settlement | Decouple slow work (assign rider, send WhatsApp, compute payouts) from the request. |
| Workers AI | Support chatbot, menu tagging | Llama 3.3 already wired on samparana.com — reuse. |
Polymorphic merchant_type + vertical columns let one schema serve food, goods, hotel, errands and services. Live, fast-changing state lives in Durable Objects; D1 holds the durable truth.
| Table | Key columns | Notes |
|---|---|---|
users | id, phone, name, role, wallet_balance, locale | One identity across all verticals & roles. |
merchants | id, vertical, type, name, geo(lat,lng), zone_id, status, commission_pct, open_hours | Restaurant, hotel, kirana, vendor, service-firm. |
catalog_items | id, merchant_id, name(en/od), price, category, veg_flag, prep_time, stock | Dishes / goods / services / errand types. |
orders | id, user_id, merchant_id, vertical, status, total, payment_id, rider_id, addr, slot, otp | DO mirrors the live status; D1 is the ledger. |
order_items | order_id, item_id, qty, unit_price, customisations | Snapshot of price at order time. |
riders | id, user_id, vehicle, status, current_zone, kyc_status, rating | Riders + service professionals. |
service_bookings | id, user_id, pro_id, service_id, scheduled_at, quote, status | UrbanClap-style scheduled jobs. |
payments | id, order_id, gateway, amount, status, settled_at | Razorpay txn + reconciliation. |
payouts | id, party_id, period, gross, commission, net, status | Merchant + rider settlements. |
zones | id, name, polygon, surge_pct, sla_min | Per-area pricing, surge, serviceability. |
reviews | id, order_id, target, stars, text | Two-way ratings. |
One Durable Object per active order owns the transitions; every change is broadcast over WebSocket and persisted to D1.
Side-paths: REJECTED, CANCELLED, REFUNDED. Service jobs use a parallel set (BOOKED → ASSIGNED → EN ROUTE → IN PROGRESS → COMPLETED).
payouts ledger + invoice PDFs in R2Phone-OTP login, JWT sessions in KV, role-based access (customer/merchant/rider/admin), signed Razorpay webhooks.
Cloudflare WAF + Bot Fight Mode + Turnstile (already on samparana.com), per-IP rate limits, strict CSP, HSTS — extend existing _headers.
IT Act 2000 & DPDP Act 2023 privacy, GST-compliant invoicing, FSSAI display for food merchants, KYC for riders/merchants in R2.
PCI handled by Razorpay (no card data touches us), server-side amount recompute, idempotency keys, refund audit trail.
Edge-distributed, scales to zero, DO single-writer consistency, Queue retries with DLQ, structured logs + alerts.
Two-way ratings, OTP-verified handoff, SOS button, fraud heuristics on refunds/cancellations, merchant & rider vetting.
Timeline assumes a small focused team (see resourcing). Dates are indicative from a Phase 0 kickoff.
samparana-delivery Pages project + delivery.samparana.com (this site)| Role | Phase 1 |
|---|---|
| Full-stack lead (Workers/DO/D1) | 1 |
| Frontend (PWA × 4 surfaces) | 1–2 |
| Ops / city launcher (merchants, riders) | 1 |
| Designer / QA (shared) | 0.5 |
| Product owner (SREE) | 1 |
Grows with verticals; Cloudflare's serverless model keeps DevOps near-zero.
| Service | Indicative |
|---|---|
| Cloudflare Workers Paid + DO + D1 + R2 + Queues | ~$5–$30/mo at launch scale |
| Razorpay | ~2% per txn (no fixed) |
| Google/Ola Maps | usage-based, free tier covers MVP |
| WhatsApp Cloud API + SMS | per-message (paise) |
Infra scales with revenue — no upfront server spend. Major cost is people + rider incentives, not technology.
samparana-delivery Pages project + DB bindingsNon-technical, business-focused deck for SREE stakeholders. 12 slides. Download as PDF (opens anywhere) or editable PowerPoint.
This blueprint is approved-architecture and ready to execute. The next command starts Phase 0: provisioning the platform and scaffolding the MVP.
← Back to Samparana Discuss on WhatsApp