Skip to content
Work

Online Food Ordering · Web Product

Andhra Spice Cloud Kitchen

A direct-ordering website for a cloud kitchen in Dinnedevarapadu, Andhra Pradesh: menu, cart, delivery or pickup, a PhonePe payment integration, and an owner dashboard.

What changedCustomers now order directly from the kitchen’s own website and pay online, and the owner runs every order from one dashboard.

Andhra Spice Cloud Kitchen menu: Fries And Snacks with prices, veg and non-veg markers, a Bestseller tag and Add buttons

Overview

This is a direct-ordering website for Andhra Spice Cloud Kitchen. It is built so customers can browse the menu, build a cart, choose delivery or pickup and pay online, and so the kitchen can manage orders, the menu, party enquiries and store settings from a sign-in protected dashboard. I built the site as a web product.

The ordering flow

  1. 01

    Browse the menu

    Sections with prices in rupees, veg and non-veg markers, Bestseller tags and a Veg filter.

  2. 02

    Build a cart

    Add items from any section. The cart keeps an item total and notes that offers and delivery are applied at checkout.

  3. 03

    Choose delivery or pickup

    Delivery is limited to a configured service area. Customers can optionally share their location to help the rider find them.

  4. 04

    Pay online

    The payment step is an integration built using PhonePe Standard Checkout. The order is saved before the customer is sent to pay, and the code marks it paid only after the server’s own status check confirms the payment.

  5. 05

    Follow the order

    A private order link opens after payment and updates as the status changes. A failed payment can be retried from the same page.

Under the hood

  1. 01

    Prices are set on the server

    The browser never decides what an order costs. Every order is priced again from the database, and a stale total is rejected instead of charged.

  2. 02

    Payments are checked, not trusted

    In the code, redirects and PhonePe callbacks only trigger a check. An order is marked paid after the server confirms the order and amount, and a reconciliation job covers missed callbacks.

  3. 03

    Emails survive failures

    Customer confirmations and kitchen alerts go through an outbox with retries, so an email problem never touches a paid order.

  4. 04

    An owner dashboard

    Sign-in protected screens for orders, menu items, party enquiries and store settings.

  5. 05

    Party and bulk enquiries

    A separate enquiry form that takes no payment. Enquiries are emailed to the kitchen and listed in the dashboard.

  6. 06

    Tested end to end

    Unit and database tests (Vitest) and mobile and desktop browser tests (Playwright) cover the cart, checkout, payments, admin and party orders.

My Role

Built as a web product: the ordering site, the payment integration and the owner dashboard.

Screens

03 frames

  • Menu
    Andhra Spice Cloud Kitchen menu showing Fries And Snacks with prices, markers and Add buttons
  • Menu, continued
    Andhra Spice Cloud Kitchen menu showing Chicken Specials and Fried rice with prices
  • Party orders
    Andhra Spice Cloud Kitchen party-order enquiry form

Specification

From the live site and source

Product
Andhra Spice Cloud Kitchen
Category
Online food ordering · Web
Fulfilment
Delivery or pickup
Delivery
Limited to a configured service area
Payment
PhonePe Standard Checkout integration
Dashboard
Orders, menu, party enquiries, store settings
Stack
Next.js · TypeScript · Tailwind CSS · Postgres (Drizzle)
Live site
andhraspicecloudkitchen.online
Next projectC24 Cardio

Have a business problem that needs software?