DELIVERY TEMPLATE
Get in touch

Food delivery · Multi-tenant · Open architecture

One codebase.
Every delivery business model.

Three applications and one backend, built to run a real delivery marketplace: a super-admin console for onboarding restaurants and regions, a seller panel for running the kitchen, and a customer app for ordering — switchable between marketplace and inventory ownership models per restaurant.

Next.js FastAPI MongoDB / Beanie Redis Celery Tailwind
RESTAURANT ONBOARDING #0421
Name
Green Leaf Kitchen
Model
Marketplace · Owner-Seller
Commission
12.5%
Region
H3 · Sector 8C29
Status
Approved

How it works

From first login to a placed order

  1. 01

    Super admin, seeded on first boot

    A seeder script creates the super-admin account the moment the backend starts — no manual database setup before the first login.

  2. 02

    Regions and admins

    From the admin website, the super admin defines regions and creates admin accounts, assigning each admin to the regions they cover.

  3. 03

    Restaurants onboard, in person

    Admins visit restaurant owners directly, negotiate a commission percentage, and register them with phone verification via OTP.

  4. 04

    Approve or reject

    Every registration is reviewed — a restaurant only goes live once its status is changed to approved.

  5. 05

    Sellers build the menu

    Once approved, sellers manage restaurant details, staff, and full menu CRUD — searching the super admin's global catalog to fill in item details instantly instead of typing them from scratch.

  6. 06

    Customers discover nearby

    The customer app surfaces restaurants inside the user's delivery radius, filterable by veg-only, takeaway available, table booking, and open-now.

  7. 07

    Cart, table, or checkout

    Customers add menu items with variants, request table bookings, and check out with delivery or takeaway — takeaway orders are kept to a single restaurant — choosing a saved address and paying cash on delivery.

Per-restaurant configuration

Marketplace or inventory — your call, per restaurant

Marketplace

The restaurant keeps an owner-seller role — an independent business running its own menu and staff on your platform, paying the commission negotiated at onboarding.

Inventory

The restaurant is run by a store manager instead — suited to a single operator managing several branded locations directly, like a company-owned chain.

Everything else, included

Built for running the business, not just the orders

Access & Identity

  • JWT authentication with refresh tokens
  • Super-admin credentials seeded on startup
  • Last-active tracking updated on every token refresh

Configuration

  • Theme colour, takeaway, and table-booking toggles
  • Marketplace or inventory model, per restaurant
  • Franchise operators supported

Commerce & Growth

  • Coupons — create, update, delete from the admin panel
  • Gift cards — created by one user, claimed by another
  • Coupon and gift-card discounts applied and claimed before checkout
  • User wallet with wallet-balance discounts at checkout
  • Order reviews from customers

Discovery

  • Global search across restaurants and menus
  • Delivery-radius matching by customer location
  • H3 hexagonal geo-indexing for region assignment

Infrastructure, your way

  • File storage: Docker, Cloudinary, AWS, Azure, or GCP
  • Redis & Celery: local containers or dedicated external servers
  • Background email delivery via Celery

Marketplace-ready

  • i18n support, translated and documented for CodeCanyon
  • Admin-controlled feature visibility on admin & user sites

Right now

Actively maintained, worked on in the open

In progress

Payment gateways

Direct integrations for PayPal, Razorpay, and Stripe — a large piece of work, underway now.

PayPal Razorpay Stripe

Being verified

Coupon eligibility cron job

A scheduled job that updates user tags used for coupon assignment — implemented, currently under test.