Stop Losing 30% to DoorDash: How to Build a 0% Commission Ordering System

Does DoorDash Really Charge Restaurants 30%?

Sometimes—but not every restaurant pays the same rate.

DoorDash's published US pricing for its standard merchant plans currently lists delivery commissions of 15% for Basic, 25% for Plus, and 30% for Premier. Its listed pickup commission is 6% across those plans.

The exact arrangement matters. The charges depend on the plan and order type, and different products have different pricing structures. Before deciding whether to change your ordering setup, check the current terms rather than assuming every DoorDash order costs 30%.

You can review the details on the official DoorDash merchant pricing page.

There's another important distinction: the commission is generally calculated against the applicable order subtotal. It isn't literally 30% of the restaurant's profit margin.

That difference matters when you're working out whether an ordering channel is profitable.

The Math: What Does a 30% Commission Mean?

Let's use a simple example.

Suppose a restaurant processes $10,000 in monthly delivery orders through a marketplace, and every order in that example is subject to a 30% commission.

• Monthly marketplace delivery sales: $10,000
• Illustrative commission rate: 30%
• Monthly commission expense: $3,000
• Annualized commission expense: $36,000, if the same monthly sales and rate continue for twelve months.

The arithmetic is straightforward. The business would incur $3,000 in monthly commissions on those orders, before considering the other costs of preparing and fulfilling the food.

But there's an important limitation to this calculation: it doesn't tell us how much money the restaurant would save by moving those orders elsewhere.

A marketplace can bring new customers to a restaurant, handle delivery logistics, process payments, and provide customer support. Some orders might never have happened without that exposure.

If the restaurant replaces those orders with direct orders, it may need to invest in marketing, online ordering software, payment processing, delivery arrangements, and customer support. Those expenses must be included in the comparison.

I would use the $3,000 example as a reason to investigate the numbers—not as a promise that a custom website will automatically produce $3,000 in monthly savings.

Why a Restaurant Might Offer Direct Online Ordering

The basic idea is simple: instead of requiring every returning customer to order through a third-party marketplace, the restaurant gives people a convenient way to order through its own website.

A direct-ordering website could provide:

• A menu that customers can browse on a phone.
• Pickup ordering and a clear collection-time process.
• A cart and checkout interface.
• Online payment processing.
• Order confirmations and status updates.
• A way to send accepted orders to the restaurant's staff or existing order-management system.

The biggest potential advantage is having a direct ordering channel that is connected to the restaurant's own website and customer journey.

A restaurant can direct returning customers to its menu, let them place an order, and make the collection or delivery options clear without sending everyone through a marketplace checkout.

However, the system must be practical for the restaurant's staff. If orders don't arrive reliably, menu prices are incorrect, or the payment status is unclear, the restaurant has simply replaced one problem with another.

What Does 0% Commission Actually Mean?

This is where I want to be particularly precise.

A direct-ordering system can avoid a marketplace commission on orders placed through that system, depending on the product, contract, and payment arrangement. That does not mean the transaction has no cost.

For example, Stripe's published US standard pricing lists 2.9% plus 30 cents for a successful domestic-card transaction. Other payment methods and additional services may have different charges.

Suppose a restaurant receives 100 direct orders in a month, each worth $100. That's $10,000 in order value. Using the published 2.9% plus 30-cent example, the processing fees would be approximately $320:

• Percentage-based fees: $290
• Fixed transaction fees: $30 across 100 transactions
• Total illustrative processing fees: $320

This example assumes every transaction is a successful domestic-card payment at that listed rate. It excludes refunds, disputes, other services, website development, software, taxes, delivery, and every other operating expense.

It also should not be treated as a direct like-for-like comparison with a marketplace service that includes customer discovery, delivery logistics, and support.

There is a further option worth considering: DoorDash offers an Online Ordering product for restaurant websites. Its published merchant information describes orders through that product as commission-free, while payment-processing fees still apply.

You can review the current terms in DoorDash's merchant FAQ.

So the sensible question isn't simply, "How do I eliminate every fee?" It is, "Which ordering setup gives my restaurant the best overall value after every relevant cost is considered?"

How I'd Approach the Technical Side

A direct-ordering system is more than a menu page with a checkout button. It is a small application with several parts that need to communicate reliably.

1. Build a clear customer-facing menu

The frontend should make categories, prices, descriptions, modifiers, and availability easy to understand. The layout should work properly on mobile devices because customers need to browse, select items, and check out without fighting the interface.

Depending on the requirements, this can be built with responsive HTML and CSS, JavaScript interactions, and a suitable backend.

2. Handle the order on the server

When a customer submits an order, the server should validate the submitted items, confirm their prices against the authoritative menu data, calculate the total, and create an order record.

The system should not blindly trust totals or prices sent by the browser. It also needs appropriate validation, protection against duplicate submissions, and clear handling for failed or abandoned payments.

3. Integrate the payment provider

Stripe is one possible payment provider for a US restaurant, subject to account eligibility, business requirements, and the selected payment integration.

The integration should use the provider's supported checkout or payment components and follow its security requirements. Sensitive card details should be handled through the appropriate payment-provider flow rather than stored casually in the restaurant's own application database.

After payment, the system must verify the authoritative payment status before treating an order as paid. This is where server-side verification and properly configured webhooks become important.

4. Send the order to the restaurant

Once an order has been accepted, the restaurant needs to receive it in a format the staff can actually use.

Depending on the existing setup, that might mean an order-management dashboard, a supported POS integration, a kitchen display, a notification, or a compatible printing workflow.

Sending orders directly to a kitchen printer or display is not automatic just because Stripe has processed a payment. It requires the appropriate software, integration, hardware compatibility, and testing.

I would also plan for failures. If a printer is disconnected or an external system is unavailable, the restaurant needs a way to identify the order and prevent it from silently disappearing.

5. Make payouts and order reconciliation clear

Payment acceptance and bank payouts are different stages. Stripe's payout schedule depends on the account, country, payment activity, and applicable settings. Restaurants should not assume that every payment reaches their bank account immediately.

The website and payment setup should make it possible to reconcile orders, payment statuses, refunds, and actual payouts.

Should Wichita Restaurants Abandon DoorDash?

Not necessarily. I would not tell a restaurant owner to abandon a channel that brings profitable new customers without first looking at the numbers.

A marketplace may be useful for discovery, particularly for customers who have never heard of the restaurant. Direct ordering can serve a different purpose by giving people who already know the restaurant another convenient option.

A sensible strategy may involve keeping the marketplace where it provides value while improving the direct ordering experience on the restaurant's own website.

Before making a decision, I would compare:

• The restaurant's actual marketplace commission rates.
• The number and value of orders from each channel.
• Payment-processing and ordering-platform costs.
• Delivery and fulfillment expenses.
• Marketing costs associated with bringing customers to direct ordering.
• The restaurant's ability to handle orders and customer support.

That analysis is more useful than assuming the highest advertised marketplace commission applies to every transaction.

Where Digital Menu Maker Fits In

My work on Digital Menu Maker is closely connected to the broader problem of making restaurant information and digital experiences easier to manage.

The platform focuses on hospitality technology, including QR code menus, digital menu boards, restaurant websites, and menu management.

Digital menus and ordering systems are not exactly the same thing. A menu helps customers explore what a restaurant offers. An ordering system must also handle item selection, pricing, payment, order acceptance, and the operational process behind fulfilling the order.

Some restaurants need only a better menu and a convenient link to their existing ordering provider. Others may benefit from a more integrated website and ordering workflow.

I would start by understanding the restaurant's needs, then choose the simplest arrangement that reliably supports them.