How to Cap Food Delivery Costs with a 3‑Number Menu‑Fees‑Tip Rule

Food delivery is weirdly good at turning a “quick dinner” into a checkout surprise.

Not because you’re bad with money—because the pricing is layered. A delivery fee here, a service fee there, a small‑order fee if you didn’t hit a minimum, maybe a location-based surcharge, and then the tip screen at the end. The FTC has even alleged a “pricing shell game” where the price you think you’re paying only becomes real once you reach the all‑in total at checkout. The takeaway is simple: treat the final checkout total as the truth, and treat line‑items as variable—not fixed. (Source 1)

So instead of trying to “be disciplined” every time you’re hungry, use a tiny rule that does the thinking for you.

Here’s the micro‑experiment: cap delivery with three numbers you choose once, then reuse.

The 3‑Number Rule (M‑F‑T)

You set:

M = Menu number (markup tolerance): how much higher you’re willing to pay for menu prices in the app versus ordering direct or in‑store.
F = Fees number (fee ceiling): the maximum you’ll accept for all app fees combined (delivery fee, service fee, small‑order fee, surcharges).
T = Tip number (tip default): a tip percentage you can live with, consistently.

Why separate them? Because recent enforcement and reporting reinforce that “sticker prices” don’t mean much until you see the itemized checkout total, and that “service,” “small order,” and other fees can materially change what you pay. (Source 1)

And because in NYC data (Q1 2024), consumer fees rose while tips fell—proof that fees and tips move differently, and your system should treat them differently. (Source 3)

Mini‑experiment: The 30‑second cart-screen pause

This is the whole habit.

When you’re at the cart screen (not after you’ve ordered, not when you’re already hungry-angry), do a quick check:

M check: Are the menu prices within your markup tolerance?
F check: Are total fees (all fee line items) within your fee ceiling?
T check: Is your tip set to your default number?

If any one fails, you don’t “try harder.” You switch the method: pickup, direct order, or a simpler basket.

That’s it. No guilt. Just a consistent decision rule.

DoorDash itself has emphasized applying savings and understanding fees through clearer visibility at the ordering stage, reinforcing that your decision point should be before checkout. (Source 6)

Pick your numbers (without overthinking)

A good rule is one you’ll actually reuse.

M: Menu markup tolerance

This is your “I refuse to pay that much extra for the same food” number.

The sources you were given flag a core trend: menu prices may differ from in-store/direct ordering. (Source list “Core trends,” #1)

If your sources don’t provide a universal “normal” markup percentage (they don’t), don’t invent one. Use a personal tolerance that matches your budget and how much you value convenience.

Micro‑experiment: For one order, compare one item in-app vs direct/in-store. If it feels annoying, set M lower. If it feels fair for convenience, set M higher. Repeat only when you notice drift.

F: Fee ceiling (include the sneaky ones)

Your fee ceiling should include everything that isn’t food but shows up before tip:

delivery fee
service fee
small order fee
regulatory response fee / location-based fee / surcharges (labels vary)
other checkout add-ons

The “multi-part fee” structure is a key trend in your source set—and it can change by city and regulation. (Source list “Core trends,” #2)

NYC’s policy landscape also shows rules can shift over time, which can shift platform economics and lead to location-linked pricing changes. Translation: your F number should be flexible by city. (Source 4)

Micro‑experiment: Write two fee ceilings: F-home and F-campus/work. You may accept different fees depending on your context and energy.

T: Tip default (pre-commit to reduce tip-screen pressure)

Tipping norms are in flux, and people feel frustrated—some describe tipping as a “hidden tax.” The practical move is to pre‑commit so you’re not negotiating with yourself while the app stares at you. (Source 14)

Your provided sources also include consumer research suggesting many people tip in a 10%–19% band. If you want a budget-friendly default, pick a stable number inside that range and stick to it. (Source 13)

Important gap: the sources provided here don’t tell us what tip is “right” for your city or what couriers earn. So this rule isn’t about morality—it’s about consistency and predictability.

Micro‑experiment: Pick a tip default you can repeat without resentment. If you notice you’re always overriding it, your default is wrong (for you).

The template (copy/paste)

Use this once per order—ideally at the cart screen.

The M‑F‑T Checkout Checklist

My numbers

M (menu markup tolerance): ____ (e.g., “I’m okay with small differences, not big ones.”)
F (fee ceiling): ____ (your max for delivery/service/small-order/surcharges combined)
T (tip default): ____% (your consistent tip percentage)

Before I place the order

Compare menu pricing (M): If it breaks M, I switch to pickup or direct.
Scan all fees (F): Add delivery + service + small order + surcharges. If total breaks F, I switch to pickup/direct.
Set tip (T): I set my tip to T (inside my budget), then stop revisiting it.
Promo check (10 seconds): I check for an eligible promo code/discount before paying. (Source list “Core trends,” #3; Source 13)
Stop at the all‑in total: I trust the final total at checkout as the real price. (Source 1)

How to make the rule work in real life (without becoming a spreadsheet person)

1) Default to pickup when fees break F

NYC’s delivery data suggests a practical lesson: treat fees as something you can cap—and when they exceed your cap, pickup becomes your automatic alternative. (Source 3)

Mini‑experiment: Keep one “pickup-safe” option saved (a place you actually like). The point is reducing decision fatigue when you pivot.

2) Batch orders to dodge small-order fees (and meet minimums)

Your source set highlights small-order fees and subscription minimums. The simplest lever is batching: order a bit more at once (when it fits your life), or pair up with a roommate/partner.

Mini‑experiment: Next time your cart triggers small-order logic, test one of these:

add a staple you’ll eat tomorrow
coordinate a shared order
switch to pickup

3) Use subscriptions only as an optimization layer

DashPass, Uber One, Grubhub+—memberships can reduce certain fees, but they come with terms and minimum subtotals. Your source set warns against treating “$0 delivery” marketing as a guarantee and stresses eligibility rules. (Source 1; Source 5; Source 9; Source 10)

Mini‑experiment: Add a “membership reality check” to your rule:

If the order is eligible and meets minimums, apply the benefit.
If not, don’t chase the benefit by adding random items you don’t want.

4) Audit memberships like any other recurring expense

The FTC case page (as summarized in your sources) frames subscription disclosures and cancellation practices as enforcement priorities—meaning it’s on you to keep subscriptions from silently becoming “default spending.” (Source 2)

Mini‑experiment: Add a lightweight “membership audit” moment to your budgeting system: confirm renewal date + cancellation path. No shame—just awareness.

5) Check bundled perks before buying another subscription

Your sources point out that bundled memberships exist (like Prime-linked Grubhub+ benefits), which can reduce delivery fees—so you should check what you already have before stacking new subscriptions. (Source 11; Source 12)

Mini‑experiment: If you’re about to subscribe, pause and ask: “Is this already included somewhere else?”

A realistic example (with minimal math)

Let’s say you’re ordering dinner after a long day.

You pick your three numbers (M‑F‑T).
You build your cart.
At the cart screen, you scan the fees and see the total fees exceed F.

Under the rule, you don’t argue with yourself. You switch to pickup or direct ordering.

That’s not “being strict.” That’s saving your future self from checkout regret.

If you want a euro-based cap example (optional): some students find it calming to set F as “I won’t pay more than €X in fees tonight”—but your sources don’t specify what an appropriate €X is, so keep it personal and adjustable.

What this post can’t answer (because the sources don’t)

A few things you might want a definitive answer on aren’t actually settled by the provided sources:

A universal “normal” menu markup percentage across apps/cities
A single “correct” tip percentage for fairness across regions
A promise that regulation will eliminate delivery fee complexity everywhere (your sources even note junk-fee rulemaking doesn’t automatically apply to restaurant delivery) (Source 16)

That’s exactly why a personal cap rule helps: it works even when pricing is messy.

If you try one thing today

Open your delivery app, go to the cart screen, and run the M‑F‑T checklist once. Even if you still order, you’ll start building a tiny reflex: pause, scan, decide.

That reflex is the whole win.