Where Deliveroo falls short
Key features to replicate
The core feature set any Deliveroo alternative needs — plus what you can improve on.
Real-time order routing that matches consumer orders to restaurant kitchens and assigns available riders within radius constraints. Batch-matching algorithm reduces dead miles by combining nearby orders for a single rider trip while maintaining ETA accuracy.
Consumer-facing live map showing rider position and estimated arrival time. ETA prediction model using historical delivery times, current traffic, and kitchen preparation time. Automatic ETA re-calculation when delays are detected.
Delivery fee engine that adjusts based on distance, rider supply, demand spikes, and weather conditions. Configurable surge multipliers with consumer-facing transparency. Peak-time fee caps configurable per city or zone.
Monthly subscription program offering free delivery on qualifying orders above a minimum basket threshold. Pre-acquisition Deliveroo Plus priced at £3.49/mo for free delivery on £25+ orders. Managed via Stripe Billing with automatic renewal and usage tracking.
Merchant-facing portal with order management, menu editing, availability toggling, performance analytics, and payout reporting. POS integration via REST API with Toast, Square, and Oracle MICROS for order injection into kitchen systems.
Three-way payment split at checkout: platform take, restaurant payout, and rider payout via Stripe Connect. Supports multi-currency for international operations. Automated 1099/IR35-equivalent tax document generation for rider and restaurant partners.
Country-specific configuration for payment methods, regulatory compliance (GDPR, payment licensing), currency display, VAT calculation, and customer service workflows. Deliveroo operated across UK, France, Italy, and UAE — each requiring distinct compliance and payment stacks.
Dedicated courier mobile app with order assignment, navigation, contact masking via Twilio, and proof-of-delivery photo capture. Configurable contactless delivery flow with GPS-verified drop-off confirmation.
Technical architecture
Consumer and restaurant apps
Recommended:
Order dispatch engine
Recommended:
Geospatial and routing layer
Recommended:
Payments and payouts
Recommended:
Platform and compliance services
Recommended:
Deliveroo vs building your own
Open-source Deliveroo alternatives
Existing projects you can self-host or use as a starting point. Each has trade-offs.
Medusa
Modular open-source commerce platform with order management, split payments via Stripe Connect, and plugin architecture. MIT license, 30K+ stars. Supports custom fulfillment providers and three-sided marketplace logic via custom modules. Active 2026 development.
TastyIgniter
Open-source food ordering and delivery management system built on Laravel. MIT license, 3.5K+ stars. Handles menu management, order dispatch, delivery zones, and restaurant dashboards out of the box — the closest OSS equivalent to Deliveroo's restaurant-side infrastructure.
Bagisto
Laravel-based headless commerce framework with multi-channel, multi-currency, and marketplace module support. MIT license, 26.8K+ stars. Can serve as the commerce backbone for a delivery marketplace with custom rider dispatch extensions. Active 2026 maintenance.
DIY roadmap: build it yourself
- Set up Next.js App Router monorepo with separate consumer, restaurant, and rider app packages
- Design PostgreSQL schema: restaurants, menus, riders, orders, order_items, zones, delivery_fees
- Implement Supabase Auth with role-based access: consumer, restaurant_owner, rider, admin
- Build restaurant onboarding flow: profile, menu creation, delivery zone polygon definition, commission agreement
- Create consumer-facing restaurant listing with geospatial search using PostGIS for radius filtering
- Build order placement flow: cart, checkout, Stripe payment intent, 3-way split via Stripe Connect
- Implement order state machine using BullMQ or Temporal: placed, restaurant_accepted, preparing, rider_assigned, picked_up, delivered
- Build rider assignment engine: nearest available rider within zone using PostGIS distance query and Redis availability cache
- Implement real-time order status updates via Supabase Realtime WebSockets to consumer and restaurant apps
- Build rider app order acceptance flow with push notifications via FCM and timeout re-assignment logic
- Integrate Google Maps Platform for rider route display and ETA calculation on consumer tracking screen
- Build rider location update pipeline: React Native GPS at 10-second intervals writing to Supabase with upsert
- Implement Twilio masked phone number proxy for consumer-rider and consumer-restaurant communication
- Add proof-of-delivery photo capture in rider app with S3/Supabase Storage upload and order record attachment
- Build delivery exception handling: undeliverable order flow, contactless drop-off with photo confirmation
- Configure Stripe Billing for Plus subscription: monthly plan, free delivery threshold, Stripe webhook status sync
- Build dynamic delivery fee engine: base fee + per-km rate + surge multiplier configurable per zone
- Implement automated rider payout schedule via Stripe Connect with weekly settlement and payout history dashboard
- Add restaurant commission reporting: gross order value, platform fee, net payout breakdown by week/month
- Build consumer refund and credit flow for order issues with configurable approval rules
- Build admin ops dashboard: city configuration, delivery zone management, commission tier assignment per restaurant
- Implement fraud detection rules: unusual order patterns, card testing, fake delivery claims flagging
- Add restaurant performance analytics: order volume, acceptance rate, preparation time, customer rating trends
- Build rider supply management tooling: active rider count by zone, surge alert thresholds, bonus incentive configuration
- Implement GDPR-compliant data retention policies: anonymize completed order PII after 90 days per EU/UK requirements
Features you can't get from Deliveroo
This is where a custom build pulls ahead — features impossible or impractical on a shared platform.
Restaurant-owned co-operative model
Structure the platform as a co-operative owned by participating restaurants, charging 8–12% commission instead of Deliveroo's 28–35%. Restaurants buy shares and vote on platform decisions. Several city-level restaurant co-ops have launched with this model in North America and Europe since 2023.
Ghost kitchen marketplace
Build specifically for ghost kitchen operators and cloud kitchens, who lack the street-front presence that benefits traditional restaurant platforms. Offer ghost kitchens lower commission (10–15%) in exchange for exclusive platform listing, creating a supply base competitors cannot easily replicate.
Hyperlocal neighbourhood focus
Launch in a single dense urban neighbourhood rather than a whole city. Lower marketing costs, higher supply density, faster delivery ETAs, and stronger brand recognition than a city-wide rollout. Add community features like neighbourhood restaurant loyalty programs.
Transparent rider pay model
Differentiate from Deliveroo and DoorDash by publishing real-time per-hour earnings for riders and guaranteeing a minimum hourly floor. Publish rider earnings data publicly. This regulatory-forward approach builds rider loyalty and may qualify for preferred treatment under emerging gig economy legislation.
B2B corporate lunch delivery
Target offices, coworking spaces, and corporate parks with group ordering and per-head budget management. Corporate accounts pay monthly invoices rather than per-order card transactions. Delivery volume is predictable, reducing rider idle time and improving unit economics versus consumer-only models.
Alcohol and grocery add-on delivery
Expand beyond food with alcohol-licensed delivery (UK premises licence or equivalent) and convenience grocery integration. Deliveroo Hop (dark grocery stores) operated this model. A custom platform can partner with local off-licences and convenience stores to add high-margin SKUs to existing delivery runs.
Who should build a custom Deliveroo
Skip the DIY — let RapidDev build it
Everything above is doable — but it takes months of full-time work. We build custom Deliveroo alternatives using AI-accelerated development, delivering in weeks what used to take quarters.
Discovery call (free)
30 minWe map your exact requirements: which Deliveroo features you need, what custom features to add, your users, integrations, and compliance needs. You get a detailed scope document and fixed-price quote within 48 hours.
AI-accelerated build
8–14 weeksOur engineers use Claude Code, Lovable, and custom AI tooling to build 3–5x faster than traditional development. You see progress in a staging environment every week — not a black box for months.
Launch + handoff
1 weekWe deploy to your infrastructure, transfer the GitHub repo, set up CI/CD, and walk your team through the codebase. You own 100% of the source code — no vendor lock-in, no recurring platform fees.
What you get
30-min call. Fixed-price quote within 48 hours. No commitment.
Frequently asked questions
How much does it cost to build a Deliveroo alternative?
Building a three-sided food delivery marketplace comparable to Deliveroo costs $250,000–$600,000 with an agency using 4 engineers over 6–10 months. Using TastyIgniter or Medusa as the commerce foundation reduces build time for restaurant management and order processing. Ongoing infrastructure at city scale runs $3,000–$8,000/month covering maps, Twilio, Stripe, and compute.
Is Deliveroo still independent or part of DoorDash?
Deliveroo is a wholly-owned DoorDash subsidiary since October 2, 2025, when the £2.9B (180p per share) cash acquisition closed. Deliveroo was de-listed from the London Stock Exchange at closing. The Deliveroo brand continues to operate in UK, France, Italy, and UAE, but DoorDash's Q1 2026 call confirmed migration to a single global technology platform is underway.
What open-source tools can power a delivery marketplace?
TastyIgniter (MIT, 3.5K+ stars) is the most purpose-built option — it handles restaurant menus, delivery zones, order dispatch, and kitchen dashboards out of the box. Medusa (MIT, 30K+ stars) provides a flexible TypeScript commerce foundation for custom three-sided marketplace logic. Bagisto (MIT, 26.8K+ stars) supports multi-channel and multi-currency operations needed for international rollout.
How do I handle rider classification and compliance?
UK law classifies Deliveroo riders as self-employed following the 2023 Supreme Court ruling, but EU countries (France, Italy) have different gig worker classifications. For any multi-country rollout, engage local employment counsel before onboarding riders. In practice, most platforms use Stripe Connect for rider payouts and issue IR35/1099-equivalent documents for annual income reporting. Consider a transparent minimum earnings guarantee to reduce regulatory risk.
What commission rate should I charge restaurants?
Deliveroo's 28–35% is widely cited as unsustainable for independent restaurants. A 10–15% commission is operationally viable for most city-scale platforms after accounting for payment processing (1.5–2.9%), rider costs (35–50% of delivery fee), and platform overhead. Start at 12–15% to attract restaurant partners, then optimize as order volume scales. Transparency on commission structure is a competitive advantage against incumbents.
Can I build a delivery marketplace for a single city?
Yes — and it is the recommended starting strategy. A single dense urban area with 50–100 restaurant partners and 30–50 active riders generates enough order volume to test unit economics before expansion. City-focused marketing, local PR, and community restaurant partnerships are far more cost-effective than a national launch. Deliveroo itself started in London before expanding to other cities.
How do I handle real-time rider tracking?
Use Supabase Realtime or a dedicated WebSocket server to broadcast rider GPS updates from the React Native rider app (every 10 seconds) to the consumer tracking screen. Store current rider positions in a Redis cache for fast dispatch queries and in PostgreSQL for audit. Google Maps Platform or Mapbox renders the live rider position with animated marker updates on the consumer map.
Can RapidDev help build a food delivery marketplace?
Yes. RapidDev builds three-sided delivery marketplaces using Next.js, Supabase, Stripe Connect, and TastyIgniter or Medusa. We handle rider dispatch, real-time tracking, restaurant dashboard, subscription billing, and multi-country payment compliance. Typical delivery for a city-focused MVP: 6–8 months.
We'll build your Deliveroo
- Delivered in weeks
- You own 100% of the code
- No per-seat fees, ever
30-min call. No commitment.