 |
The Operator’s Edition |
|
|
★ FOLLOW-UP TO YESTERDAY · A DEEPER LOOK
★ Play II · Going Deeper
The Margin Lever You Own
The single biggest margin lever in your marketplace. And why most operators leave it on the table.
A deeper look at Play II from yesterday’s playbook.
Hi there — yesterday we sent five plays for marketplace operators. Play II got the most replies. "Show me the actual math" was the most common follow-up. Fair. Let’s do that.
This email is a deeper look at one specific thing: how delivery economics quietly decide which marketplaces survive year one — and why the operators who get this right are running fundamentally different businesses than the ones who don’t.
It’s a longer read than yesterday. But if you’re running delivery (or about to), the 8 minutes here might be worth more than anything else we send you this month.
|
|
|
|
★ SECTION I · THE PROBLEM
Why most marketplaces silently bleed margin on delivery.
Here’s what we see all the time. A founder launches a delivery marketplace. They price the food competitively. They absorb delivery cost on the operator side because "the customer won’t pay for it." Three months in, they look at their margin and realize they’re losing $1.50–$4.00 per order, depending on city and order size.
Their reaction is almost always one of two things. Either they raise menu prices (which kills conversion and erodes their pitch to vendors), or they cut driver pay or service quality (which kills retention and brand). Both fixes make the business worse. The third option — pass logistics costs transparently to the customer at checkout — doesn’t even occur to most operators, because they assume customers won’t accept it.
Customers will accept it. They already do. Uber Eats charges a delivery fee. DoorDash charges a delivery fee. Rappi charges a delivery fee. Independent marketplaces are the only category where founders consistently leave this revenue line empty.
|
The mental model shift: delivery is not a cost you absorb to be competitive. Delivery is a service you provide, and customers expect to pay for services. The question isn’t "will they tolerate a fee" — the question is "what’s the right fee structure for my market."
|
|
|
|
|
★ SECTION II · THE OPTIONS
The four configurations operators actually use.
There’s no single "right" answer here. The configuration that fits depends on your vertical, your customer’s price sensitivity, your fleet model, and how aggressive your growth targets are. The four patterns we see most often:
|
Config 1 · The full pass-through
Customer pays 100% of delivery.
A flat fee equal to (or slightly above) your average delivery cost. Simplest to implement, cleanest on the P&L, most aggressive on customer perception. Works well when your vertical is high-value (groceries, premium food, B2B) and the customer expects logistics to cost something.
Best for: high-AOV verticals, B2B, premium positioning
|
|
Config 2 · The distance-based fee
Fee scales with delivery distance.
$2 base + $0.50/km, or similar. Customer sees the fee adjust in real time as they pick their address. Feels fair (longer trip costs more). Operationally clean because your actual fleet cost also scales with distance.
Best for: city-wide marketplaces, mixed urban/suburban zones
|
|
Config 3 · The threshold model
Free delivery above $X. Fee below.
"Free delivery on orders over $25." Massively under-rated. Drives average order value up (customers add an item to hit the threshold), kills your worst-economics orders (the $8 single-item ones), and feels like a benefit to the customer. Mathematically elegant.
Best for: food delivery, groceries, low-AOV verticals trying to push AOV up
|
|
Config 4 · The membership model
Monthly fee unlocks free (or cheap) delivery.
$9.99/month, unlimited free deliveries. DoorDash DashPass, Uber One, Amazon Prime. The play that fundamentally changes your business model: you stop selling individual transactions and start selling a subscription. The hardest to set up, but the highest-leverage long-term.
Best for: established marketplaces with proven repeat-purchase behavior
|
Most operators we work with end up running a mix — e.g., Config 3 (threshold) for restaurants, Config 2 (distance-based) for groceries, Config 4 (membership) layered on top once they hit scale.
|
|
|
|
★ SECTION III · THE CUSTOMER QUESTION
Will customers tolerate a delivery fee? (Data, not vibes.)
This is the question every operator wrestles with before turning fees on. Here’s what we’ve observed across hundreds of marketplaces that flipped the switch:
|
• Conversion rate impact is usually small — or zero.
In most A/B tests we’ve seen, a transparent delivery fee at checkout produces a conversion drop of less than 3%. In some verticals (groceries, B2B) the impact is statistically zero. Customers expect it.
|
|
• AOV often goes up, not down.
Customers who see a $3 delivery fee will sometimes add a second item to "make the fee worth it." Threshold models (Config 3) lean into this directly — we’ve seen AOV jumps of 15–25% in the first 60 days.
|
|
• Transparency matters more than the number.
A $3 fee shown clearly at checkout outperforms a $1 fee buried in the order total. Customers don’t mind paying for delivery. They mind feeling deceived. Show the line item early in the checkout flow, label it clearly, and don’t round it weirdly.
|
|
• Repeat purchase rate stays flat.
This is the one we get asked about most. The answer: in nearly every case we’ve tracked, 30/60/90-day repeat purchase rate is statistically unchanged after introducing fees. Customers come back because of product quality and convenience, not because of a $3 line item.
|
Numbers above reflect general patterns we’ve seen across operators on our platform. Your results will vary based on vertical, market maturity, and competitive landscape. Run your own A/B test before committing to a full rollout.
|
|
|
|
★ SECTION IV · EXECUTION
The setup, in under an afternoon.
Whether you’re on our platform or another one, the operational rollout follows the same pattern. If your tool supports it, the technical setup is usually a few hours. The harder work is the analysis. Here’s the order we’d run it in:
|
1 · Pull your last 90 days of delivery costs.
Average cost per order. Distribution by zone. Distribution by order size. You can’t set the right fee until you know what you’re actually spending.
|
|
2 · Pick a configuration (one of the four above).
Match it to your vertical and customer base. If you’re unsure, Config 3 (threshold) is the safest first move — it benefits the customer narrative and your AOV.
|
|
3 · A/B test it on 20–30% of traffic for 2–4 weeks.
Measure: conversion rate, AOV, repeat purchase rate at 30 days. If two of the three hold or improve, roll it out fully. If one drops meaningfully, tweak the configuration before rolling out.
|
|
4 · Communicate to vendors.
This step gets skipped and it shouldn’t. Your restaurant or store partners need to understand the fee structure so they can answer customer questions consistently. Send a one-pager. Run a 30-minute call.
|
|
5 · Review monthly. Adjust quarterly.
As your fleet costs shift, as your zone mix evolves, as competition changes — your fee structure should too. The operators who get the most out of this lever treat it as a living configuration, not a one-time setup.
|
|
★ The honest version
Most operators we talk to know they should be doing this. Most haven’t set aside the afternoon to actually run the numbers. If that’s you — pick a date this week. Block 90 minutes. Do step 1. The rest follows.
|
|
|
★ Want help running the numbers?
Bring your numbers. We’ll model the configurations with you.
If you’re running a marketplace and want to figure out which fee configuration fits your business — book a free 15-minute consultation. Bring your average delivery cost, your AOV, and your repeat purchase rate. We’ll walk through which of the four configurations is realistic for your setup and model the margin impact.
No pitch unless you ask for one. We’ve done this exercise with operators across 60+ countries. If we can save you a quarter of trial-and-error, we’ve earned your time.
|
|
|
★ Tools that make this easier
• Customer Fees — the configurable engine all four configurations run on
• Shipday Integration — auto-dispatch + branded tracking, the layer underneath
• 3rd-party delivery — Uber Direct, DoorDash Drive, Lalamove, Yango, Pickerexpress
|
|
|
10k+
Live stores
|
|
50M+
Orders processed
|
|
60+
Countries live
|
|
0%
Order commission
|
|
|
| ★★★★★ |
Rated Excellent · 350+ reviews on Trustpilot · 5,000+ founders |
|
|
Thanks for sticking with the deep dive. Tomorrow we’ll likely return to a shorter format. — The Ordering.co team
|
|
Catch up on the rest:
All features → · Pricing overview → · Integrations → · 52 business models →
|
|
The same enterprise codebase powering 10,000+ stores across 60+ countries. 50M+ orders processed. Trusted by 5,000+ marketplace founders. ★★★★★ Rated Excellent on Trustpilot.
You’re receiving this email because you signed up through one of our forms on our website to receive updates, insights, and occasional offers from Ordering.co.
Unsubscribe · Visit ordering.co
|
|