Grubhub Clone Business Model: The Delivery Fee Is the Line You Can Improve
Commission is a percentage of somebody else's price. The delivery fee is the only revenue line whose cost side you also control, which makes it the one number on the platform that gets better because you got better. Six lines ship here, and this one is first, because assignment quality, zone density and orders per partner hour move it every single week.
Design My Revenue Model →See PricingWhy Cost per Delivery Decides Everything
Most delivery businesses fail on a number that no revenue line can rescue.
A delivery order carries a fixed operational cost that arrives whether or not the order was profitable: a rider is paid for the run, a processor takes a component of a small basket, and somebody answers the phone when it goes wrong. Raising commission is the obvious response and the wrong one, because a higher rate is exactly what makes restaurants leave for the aggregator you were competing with. The number that actually moves is what a delivery costs you to complete, and it is decided by three things: assignment quality, zone density and orders per partner hour.
All three are visible in this build rather than inferred. Partners are filtered by zone before assignment so dispatch cost tracks the area rather than the fleet. Every transition writes its own named column, so time-to-assign and time-to-door are queries rather than an analytics project. And delivery pricing is set per zone, so a dense area and a sparse one are not forced to share a fee. That is why the delivery fee margin sits first on this page: it is the line that rewards operational work rather than pricing power.
Commission remains the largest line for most operators. The argument is that it is the line you defend, and delivery margin is the line you improve.
Six Revenue Lines, One You Improve Rather Than Raise
Every one of these is built. Which are switched on, and at what rate, is yours.
Delivery fee margin
The difference between what the customer pays for delivery and what the run costs you, set per zone. Because you control assignment, zone geometry and fleet utilization, this is the only line that improves when you operate better rather than when you charge more, and it is the reason dispatch quality is a commercial subject.
Commission per order
A percentage of every order, set platform-wide or negotiated per restaurant, with each rate frozen onto the transaction at settlement. The largest line for most operators and the one restaurants are most sensitive about, which is exactly why it should not be the lever you reach for when margins are thin.
Store subscription plans
A monthly fee instead of commission, with plans you build and price and the store panel gated by plan entitlement. It suits the restaurant with volume that resents a percentage, and it can run alongside commission for the restaurants that have none yet.
Customer membership
A recurring line carrying free or reduced delivery, which on a delivery-led platform does something beyond revenue: it smooths demand by making repeat ordering feel free at the point of decision, and predictable demand is cheaper to dispatch than spiky demand.
Placement and advertising
Featured positions and promoted campaigns sold to restaurants on surfaces you control and price yourself. A secondary line on a dispatch-led platform, worth opening once a listing page has enough restaurants for position to be worth something.
Service and packaging charges
Per-order charges you configure, including the small fixed lines that are invisible individually and material across volume. On thin delivery economics these are often what turns a marginal order into a positive one, which is also why they need modelling rather than copying.
Miracuves takes no percentage of any of these and nothing is charged per rider, per restaurant or per delivery. Every efficiency you win on cost per delivery stays entirely with you.
How Delivery-Led Operators Actually Earn
The shapes that recur, and what each one genuinely requires before it produces anything.
| Approach | What it needs first | Where it breaks |
|---|---|---|
| Delivery fee margin | A tight zone and riders in it | Sparse areas where the run costs more than the fee |
| Commission per order | One restaurant and one customer | Raising it is what sends restaurants to the aggregator |
| Store subscriptions | Restaurants with volume worth a fixed fee | Meaningless before order volume exists |
| Customer membership | Customers ordering more than weekly | Waives the fee on your most improvable line |
| Placement | More restaurants than fit a screen | Nothing to outrank in a thin category |
| Raising the fee to fix margin | Nothing, which is the temptation | Demand falls, density falls, cost per delivery rises |
The last row is the trap specific to this model. Raising the delivery fee to repair margin reduces order frequency, which reduces density, which raises cost per delivery, which is the number you were trying to fix.
Monetization Ranked by What You Already Have
Density comes before every revenue decision on this list, which is unusual and is the whole argument for dispatch-led thinking.
| What has arrived | What starts earning | Why it works at this point |
|---|---|---|
| A tight zone with riders in it | Delivery fee margin | Priced against local rider cost, measured per zone |
| A first restaurant taking orders | Commission on every order | Frozen at settlement, so the rate can be corrected later |
| Counter and phone trade | Commission on till orders too | The built-in till puts walk-ins in the same books |
| Orders per partner hour rising | Better margin on the same fee | Cycle-time data comes from timestamps you already have |
| Restaurants earning steadily | Subscription plans beside commission | A stored setting, and both can run together |
| A crowded listing page | Placement, then service charges | Position is worth something once there is competition for it |
Row four is the one no other model has. Your margin improving without any price changing, because the same fee now covers a cheaper run, is the payoff for treating dispatch as the product.
What Renting the Dispatch Layer Costs
Six costs of running deliveries on somebody else's platform. None of them appear on an invoice.
Here the delivery application, the dispatch surface, the lifecycle timestamps, the cash controls and the disbursement scheduler all transfer with the source.
Which Lever to Switch On First
A launch order that assumes one tight zone, a handful of riders and no density yet.
| Stage | Turn on | Leave off |
|---|---|---|
| Launch week | One tight zone, commission, a delivery fee you can defend | Membership, placement, service charges |
| Weeks two to six | The till, cash ceilings, one disbursement schedule | A second zone before the first is dense |
| Timestamps accumulating | Cycle-time review as a weekly habit | Guessing at lateness from complaints |
| Orders per partner hour rising | Delivery margin retuned, fee unchanged | Raising the fee to repair margin |
| Repeat customers visible | Membership, priced against repeat value | Waiving delivery for customers who order monthly |
| Restaurants earning steadily | Subscription plans, then placement | Selling position with four restaurants listed |
Row four is the discipline that separates operators. When margin is thin the instinct is to change a price; the platform exists so you can change the run instead.
Three Ways Operators Run This Platform
The same deployment with a different revenue emphasis, not three different builds.
The dense-city marketplace
One tightly drawn zone where density does the work. Delivery margin and commission carry the model, and the operational habit is watching orders per partner hour rather than watching the revenue line.
- A small area with enough restaurants beats a large one
- Cycle time reviewed weekly from the order timestamps
- Cash ceilings tuned per partner as the fleet settles
The delivery-as-a-service operator
A fleet carrying for restaurants that take their own orders, where the delivery fee is close to the whole business. Commission is secondary and dispatch efficiency is the entire margin, which makes the timestamps the most important thing in the platform.
- Delivery margin priced per zone against rider cost
- SLA reporting straight from named columns
- Proof of delivery matters commercially, not just operationally
The multi-category fleet
Restaurant orders at the two peaks, and groceries, pharmacy or parcels in the hours between them. The same riders, the same assignment surface and one demand curve instead of two spikes, which is the cheapest way to raise orders per partner hour.
- One fleet spread across several categories
- Peaks filled rather than staffed around
- Margins set per category as well as per zone
These are illustrative operator shapes rather than forecasts or observed results. Every rate, fee and plan in the model is one you set yourself.
Common Delivery Operator Mistakes
Five that are expensive to undo
Drawing the first zone generously. The most common and the most expensive. A wide area looks like more market and behaves like less, because rider time between drops rises faster than order volume, and restaurants signed inside it are hard to un-sign.
Raising the delivery fee to repair margin. It reduces frequency, which reduces density, which raises the cost per delivery you were trying to fix. The fee is a demand lever, not a margin lever, and treating it as the latter is a spiral.
Recruiting riders before restaurants. Partners with nothing to deliver leave within a fortnight and tell everyone. Supply on both sides has to arrive close together, and the restaurant side is the one to lead with.
Launching membership early. Free delivery for your most frequent customers waives the fee on exactly the runs that were paying. It is a good line once you know what a weekly customer is worth over a quarter, and a quiet loss before that.
Ignoring the timestamps for six months. The data is there from the first delivery. Operators who start reading cycle time in month one improve; operators who wait for a reporting project spend that time guessing which part of the run is slow.
The first two are the ones we raise on day zero, because both are decided before a single delivery happens and both get harder to reverse every week afterwards.
Frequently Asked Questions
Why lead with delivery fee margin rather than commission?
How do I set the delivery fee?
What does the platform actually tell me about performance?
Can I run deliveries for restaurants that take their own orders?
Does carrying groceries or parcels help the economics?
Does Miracuves take a share of delivery revenue?
Model it against your rider cost, not a competitor's fee
Bring what an hour of rider time costs you and how tight your first zone can be. We will work the delivery margin from there and tell you which of the other five lines to leave off.
Explore the Grubhub Clone
Every efficiency you win stays yours.
Six revenue lines built, one of them improving whenever your dispatch does, inside a platform you own outright with no percentage routed anywhere else.
Talk to Us →Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by Grubhub.
“Grubhub Clone” is used descriptively. It is how the software industry refers to building a platform with functionality similar to Grubhub, and how clients search for it.
The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the Grubhub website or applications.
Grubhub and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.
