Overview
DashCart is a complete delivery platform, and you get the full source code. One installation runs any number of independent delivery brands. Each brand has its own web address or custom domain, logo, colours, currency, stores, riders, customers and settings, and PostgreSQL row-level security keeps each brand's data apart. Two business models are built in: quick-commerce grocery, with dark stores, stock, pick and pack and short delivery times; and restaurant delivery, where restaurants hand over their orders, riders collect and deliver them on planned routes, and each restaurant is invoiced per delivery.
It suits operators who want to launch their own grocery or food delivery service, agencies building delivery apps for clients, and teams who want to run several local brands on one system. Everything is one installable Next.js web app with separate areas for customers, store pickers, restaurant staff, riders, brand admins and the platform operator, plus a background worker for dispatch, billing, notifications and payouts. The seed script creates four demo brands (two Indian grocery brands, a UK grocery brand with VAT, and a London restaurant delivery brand) so you can try every role on day one.
Features
Customer store
- Location first: Customers set a delivery point by GPS or address search. The nearest serviceable store, delivery time and fees are worked out on the server.
- Browse and search: Category rails, category pages, product pages with pack sizes, search with synonyms, and voice search where the browser supports it.
- Cart and checkout: Online payment or cash on delivery, coupons and offers, delivery notes for the store or kitchen, scheduled delivery slots and takeaway (each behind an admin switch).
- Multi-store orders: One checkout can include items from several stores when the brand turns it on.
- Order tracking: Live order status, a delivery code to give the rider, a shareable tracking link, reorder, ratings and a printable tax invoice.
- Customer money: Wallet, part-payment, loyalty rewards, referrals, cashback and a paid membership, each switchable per brand.
- Engagement: Wishlist, product reviews, flash sales with a countdown, targeted banners and an optional AI shopping assistant.
- Account: Phone sign-in with a one-time code, optional Google and Apple sign-in, saved addresses, and privacy controls.
- Installable app: PWA with web push notifications and an offline page, plus a dark theme.
Store pickers
- Shared-device login: Pickers sign in with a staff PIN on a shared store device.
- Live order queue: New orders appear as they come in.
- Pick list: Barcode scanning with the device camera, substitutions, packing and hand-over to the rider.
Restaurant portal
- Request a delivery: Type the order in, or upload a screenshot of an order from another platform and let AI fill in the form for review.
- App orders: Accept orders placed in the customer app and mark them ready.
- Follow deliveries: Active deliveries, drafts and history, live rider tracking and chat with the rider.
- Cancellations: The cancellation charge is shown before the restaurant confirms.
- Billing: Invoices per location, pay by saved card or report a bank transfer.
- Partner sign-up: New restaurants apply online with documents; an admin approves them and they receive a login.
Rider app
- Onboarding: Riders sign up and upload identity, right-to-work and insurance documents. They cannot go online until the required documents are approved.
- Offers and routes: Go online, accept single deliveries or orders added to a route, and follow numbered stops.
- Proof of delivery: Photos at pickup and drop-off and a delivery-code check.
- Chat: Order chat and a support chat with the operations team.
- Money: Earnings, payout statements as PDF or CSV, bank details, cash on hand limits and early payout requests.
- Optional extras: Shifts, bonuses and incentives, and refer-a-rider.
Brand admin console
- Dashboard: Today's orders, sales, on-time rate, items needing attention and low stock.
- Catalogue: Products and variants, categories, brands, collections, banners, CSV import with history, search synonyms and search insights.
- Stock: Stock per store, goods received, reorder levels and a change log with reasons.
- Stores: Stores, delivery areas, opening hours and promised delivery times.
- Orders and dispatch: Order desk with filters, an order side panel, and a live dispatch board for deliveries in flight.
- Routing and rider pay: Bundling and routing rules, vehicle types, versioned rider pay tables and a cancellation policy.
- Riders and staff: Rider list, document review, shifts, incentives, cash, payout runs and bank details; staff with custom roles.
- Restaurant accounts: Vendors with plans and delivery rates, applications, per-store invoices, payments, bank statements, disputes and payment reminders.
- Incidents and evidence: Log incidents and refunds, and review delivery photos.
- Marketing: Coupons, offers, flash sales, banners, reviews and customer attributes for targeting.
- Communication: Announcements to staff and riders, and a chat inbox.
- Insights: Funnel and promotion analytics and downloadable reports.
- Settings: Branding, custom domains, WhatsApp, maintenance windows, API keys, audit log and a two-factor sign-in policy.
Platform console
- Brands: Create, configure and suspend brands; a new brand can also be created from a JSON file with a script.
- Payments: Split payments with a platform commission (Razorpay Route or Stripe Connect) and a finance view.
- Operations: Feature flags, health and alerts, maintenance windows, security settings and an audit log.
- Support access: Audited impersonation of brand staff.
Integrations and API
- Versioned JSON API:
/api/v1 with an OpenAPI 3.1 document and API keys for integrations.
- Webhooks: Razorpay, Stripe, Twilio delivery receipts and WhatsApp.
- Security: Personal data (names, phones, e-mails, addresses) is stored encrypted, admins use authenticator-app two-factor sign-in, and a check script confirms every brand table is protected by row-level security.
Good to know
- Restaurant delivery brands have no menu editor yet, so products for in-app restaurant orders must be created outside the admin.
- Coupons and the wallet do not apply to multi-store checkouts.
- There is no customer-to-rider chat; chat covers riders, restaurants and the operations team.
- Rider payouts are recorded and exported as a bank file; the transfers are sent from your bank.
- The admin, platform and rider screens are in English. The customer store has one English message file, ready for translation.
- Third-party integrations are tested against recorded vendor responses and run on mocks locally. Check each one with your own test-mode keys before going live.
- The seeded rider pay rates are placeholders and are labelled as such in the admin.
Tech stack
- Next.js 15 (App Router), React 19, TypeScript (strict), Tailwind CSS 4
- Auth.js v5, Zod schemas shared by server and client
- PostgreSQL 16 with PostGIS, Drizzle ORM, row-level security per brand
- Redis and BullMQ for live data and background jobs
- Serwist service worker, Web Push, MapLibre maps
- S3-compatible object storage
- Vitest and Playwright, pnpm workspaces and Turborepo, Node 22, Docker
What's included
- Full monorepo:
apps/web (every screen and the API), apps/worker (about 50 background jobs), and the core, contracts, providers, routing, ui and config packages
- Database migrations and row-level security policies
- Seed script with four demo brands, stores, catalogue images, riders, restaurants and past deliveries
- Docker Compose for Postgres, Redis, S3-compatible storage and Mailpit, plus
Dockerfile.web and Dockerfile.worker
- Railway configuration, a Fly.io example and GitHub Actions workflows for checks, end-to-end tests and deploys
- Docs: product specification, about 50 architecture decision records, service references and runbooks for deploys, backups, encryption keys and custom domains
- Unit, integration and Playwright end-to-end tests
.env.example documenting every setting
Requirements and third-party costs
You need Node 22.12 or later, pnpm 9 and Docker for local development. In production you need PostgreSQL 16 with PostGIS, Redis, S3-compatible storage and a wildcard domain (one subdomain per brand). Locally every third-party service is replaced by a mock, so the app runs without any keys.
- Hosting, database, Redis and storage (required): Any Docker host, such as Railway, plus managed or self-hosted Postgres, Redis and S3-compatible storage.
- Payments (required to take online payments): Razorpay or Stripe per brand. Cash on delivery works without them.
- Stripe (optional): Card billing for restaurant invoices, and Stripe Connect or Razorpay Route for platform commission.
- SMS (required for phone sign-in in production): MSG91 for India or Twilio elsewhere.
- Maps (required for address search): Google Maps, Mapbox, Ola Maps, Mappls or OpenStreetMap. Google is also used for road distances in dispatch if you turn it on.
- E-mail (required in production): Resend or any SMTP server.
- Anthropic (optional): Reads order screenshots and powers the shopping assistant. Manual entry works without it.
- WhatsApp Business (optional): Meta Cloud API, set up per brand.
- Google and Apple sign-in (optional): For customer sign-in.
- Web Push (free): Uses VAPID keys you generate with an included script.
- Sentry, PostHog and an OpenTelemetry collector (optional): Error reporting, product analytics and tracing.
The purchase covers the source code only. Service fees are billed by the providers listed above.