How to Integrate DoorDash Drive and Uber Direct With Your WooCommerce Restaurant for Local Delivery

Why Third-Party Delivery Integration Matters for WooCommerce Restaurants

This is where DoorDash Drive and Uber Direct come in — and they’re fundamentally different from the DoorDash and Uber Eats marketplace apps most people know. Instead of listing your restaurant on a third-party marketplace (where you compete with hundreds of other restaurants, pay 15–30% commission per order, and lose control over your brand), these white-label services simply provide the driver. The order stays on your website. The customer interacts with your brand. You pay a flat per-delivery fee instead of a percentage of the order total.

For WooCommerce restaurant owners, this is a game-changer. You already own the customer relationship through your website. A plugin like FoodMaster handles the online menu, order management, and kitchen workflow. The missing piece is getting the food from your kitchen to the customer’s door without building infrastructure you can’t afford. DoorDash Drive and Uber Direct fill that gap.

The demand is real. According to the National Restaurant Association’s 2024 State of the Industry report, off-premises dining (delivery, takeout, and drive-through) now accounts for a significant and growing share of restaurant revenue, with delivery specifically continuing to climb year over year. Customers expect it, and restaurants that can’t offer it lose orders to competitors who can.

DoorDash Drive vs Uber Direct — Features, Pricing, and Coverage Compared

Before you start writing API calls, you need to understand what each platform offers and which one fits your operation. Here’s a practical breakdown:

Pricing Structure

DoorDash Drive charges a flat per-delivery fee that typically ranges from $6 to $10 depending on distance, market, and time of day. There are no monthly subscription fees or setup costs for most merchants. You can pass this fee to the customer, absorb it, or split it — that’s your call.

Uber Direct uses a similar per-delivery pricing model, generally in the $5 to $9 range. Uber also offers volume-based pricing tiers for high-volume merchants, which can bring per-delivery costs down. Like DoorDash Drive, there’s no commission on the order total.

Coverage and Availability

DoorDash Drive operates in all 50 U.S. states and has expanded into Canada and Australia. Their driver network is one of the largest, which means faster pickup times in most metro and suburban areas. Uber Direct is available across the U.S., Canada, and parts of Europe, Latin America, and Asia-Pacific. In dense urban markets, Uber often has faster driver assignment times due to the sheer number of active Uber drivers on the road.

API Access and Developer Experience

Both platforms offer REST APIs with solid documentation. DoorDash Drive’s API uses a straightforward delivery creation endpoint where you POST order details and receive a tracking URL. Uber Direct’s API is slightly more complex — it uses an OAuth 2.0 authentication flow and a two-step process (get a delivery quote first, then create the delivery). Both provide webhook callbacks for status updates like driver assigned, picked up, and delivered.

Real-Time Tracking

Both services generate a customer-facing tracking link that shows the driver’s real-time location on a map. You can embed this link in WooCommerce order confirmation emails or display it on the order-received page.

[IMAGE: Side-by-side comparison table showing DoorDash Drive vs Uber Direct features including pricing, coverage, API complexity, and tracking capabilities]

Which Should You Choose?

If you’re in a suburban area, DoorDash Drive often has better driver availability outside city centers. If you’re in a dense urban market and want the lowest possible per-delivery cost at volume, Uber Direct may edge ahead. The best strategy for many restaurants? Integrate both and use fallback logic so you’re never without a driver. We’ll cover exactly how to do that below.

Setting Up DoorDash Drive With WooCommerce Step by Step

DoorDash Drive doesn’t have a native WooCommerce plugin, so integration requires either a middleware tool or custom API work. Here’s the full process:

Step 1: Apply for a DoorDash Drive Merchant Account

Visit the DoorDash Drive portal and submit a merchant application. You’ll need your restaurant’s name, address, EIN or business ID, and estimated monthly delivery volume. Approval typically takes 3–5 business days. Once approved, you’ll receive access to the Drive Developer Portal.

Step 2: Obtain Your API Credentials

In the developer portal, generate your Developer ID, Key ID, and Signing Secret. DoorDash Drive uses JWT (JSON Web Token) authentication — you’ll sign each API request with these credentials. Store them securely; never expose them in client-side code.

Step 3: Build the Integration Bridge

You have three practical options for connecting WooCommerce orders to DoorDash Drive:

• Zapier or Make (Integromat): Set up a Zap that triggers when a WooCommerce order status changes to “ready for delivery” (or a custom status). The Zap sends a POST request to DoorDash Drive’s /v1/deliveries endpoint with the order data. This is the no-code option, though it adds a small per-task cost from Zapier.
• Custom WordPress Plugin or Functions: Hook into WooCommerce’s woocommerce_order_status_changed action. When the status transitions to your designated “ready” status, fire an HTTP request to DoorDash’s API using WordPress’s wp_remote_post() function.
• Third-Party Middleware: Services like Bbot or Deliverect can sit between WooCommerce and DoorDash Drive, handling the data mapping automatically. These add a monthly fee but reduce development time.

Step 4: Map Your Order Data

DoorDash Drive’s delivery creation endpoint requires specific fields: pickup address (your restaurant), dropoff address (customer’s delivery address from WooCommerce), order value, pickup time (when the food will be ready), and an external delivery ID (use the WooCommerce order number). You can also pass item descriptions, which help drivers verify the order.

Step 5: Handle Webhooks for Status Updates

Register a webhook URL in the DoorDash portal. DoorDash will POST status updates — driver_assigned, driver_arrived_at_pickup, picked_up, delivered, and cancelled — to your endpoint. Parse these and update the WooCommerce order status or add order notes so your staff and customers stay informed.

Setting Up Uber Direct With WooCommerce Step by Step

Uber Direct’s integration follows a similar pattern but with a few key differences in authentication and workflow.

Step 1: Create an Uber for Business Developer Account

Sign up at the Uber Developer portal and apply for Uber Direct access. You’ll need to provide business details and agree to Uber’s Direct API terms. Once approved, create a new application in the developer dashboard to get your Client ID and Client Secret.

Step 2: Generate OAuth 2.0 Tokens

Unlike DoorDash’s JWT approach, Uber Direct uses OAuth 2.0 client credentials flow. Your server sends a POST request to Uber’s token endpoint with your Client ID and Secret, and receives a bearer token valid for 30 days. Store this token and refresh it before expiration. All subsequent API calls include this token in the Authorization header.

Step 3: Implement the Quote-Then-Create Flow

Uber Direct uses a two-step process that’s actually beneficial for checkout UX:

1. Get a Delivery Quote: Send the pickup and dropoff addresses to Uber’s /v1/customers/{customer_id}/delivery_quotes endpoint. You’ll receive back an estimated delivery fee, estimated delivery time, and a quote ID.
2. Create the Delivery: When the order is confirmed and food is being prepared, POST to the delivery creation endpoint using the quote ID. This locks in the price and dispatches a driver.

The quote step is powerful because you can display the exact delivery fee to the customer before they place the order, right on the WooCommerce checkout page.

Step 4: Display Delivery Fees at Checkout

Use WooCommerce’s woocommerce_cart_calculate_fees hook to add the Uber Direct delivery fee as a line item when the customer enters their delivery address. Fire an AJAX request to your server, which calls Uber’s quote API, and return the fee to the checkout page. This gives customers full price transparency.

Step 5: Send Tracking Links to Customers

When the delivery is created, Uber Direct returns a tracking_url in the response. Append this to the WooCommerce order confirmation email by hooking into woocommerce_email_order_details. You can also display it on the WooCommerce “Order Received” (thank you) page. Customers see a live map with the driver’s location — branded under your restaurant, not Uber Eats.

[IMAGE: Screenshot example of a WooCommerce checkout page showing a dynamically calculated third-party delivery fee and estimated delivery time below the order summary]

Handling Delivery Fees, Zones, and Fallback Logic at Checkout

Getting the delivery fee onto the checkout page is only part of the equation. You also need to control where you deliver and what happens when a delivery service is unavailable.

Dynamic Fee Calculation Based on Distance

Both DoorDash Drive and Uber Direct calculate fees based on the actual distance between your restaurant and the customer. By calling their quote APIs at checkout time (triggered when the customer fills in their address), you display the real fee rather than a flat estimate. This prevents undercharging on long-distance deliveries and overcharging on nearby ones.

Setting Delivery Zone Boundaries

WooCommerce’s built-in Shipping Zones feature is surprisingly useful here. Create a shipping zone for your delivery radius — say, postcodes within 5 miles of your restaurant. Within that zone, add a shipping method called “Delivery” that triggers the third-party API quote. For addresses outside that zone, only display “Pickup” as an option. If you’re using FoodMaster for WooCommerce, you can leverage its built-in delivery zone management to define radius-based or postcode-based zones, which simplifies this setup significantly.

Implementing Fallback Logic

What happens if DoorDash Drive can’t find an available driver? Your customer shouldn’t see an error — they should still get their food. Here’s a practical fallback pattern:

1. Request a delivery quote from your primary service (e.g., DoorDash Drive).
2. If the quote request fails or returns no driver availability, automatically request a quote from your secondary service (e.g., Uber Direct).
3. If both fail, display a message offering pickup only or suggest the customer try again in a few minutes.

This logic lives in your server-side code (or Zapier/Make workflow). The customer never sees the behind-the-scenes switching. They just see a delivery fee and an estimated time.

Handling Surge and Peak Pricing

Both services may increase per-delivery fees during peak hours (Friday dinner rush, game days, severe weather). The quote API will reflect this. Decide in advance whether you’ll absorb the surge, pass it to the customer, or cap the delivery fee at a maximum amount and cover the difference. Transparency here builds customer trust — a brief note like “Delivery fees may vary during peak hours” on your checkout page goes a long way.

Real-World Tips for Managing Third-Party Delivery Alongside Pickup and Dine-In Orders

Integrating delivery APIs is the technical half. The operational half — managing delivery alongside your existing pickup and dine-in orders — is what separates restaurants that thrive from those that drown in chaos.

Sync Dispatch With Kitchen Prep Time

The biggest mistake restaurants make is dispatching a driver the moment an order comes in. The driver arrives in 8 minutes, but the food takes 20 minutes to prepare. Now you have a frustrated driver waiting, which can lead to cancellations or cold food if the driver leaves and returns.

The fix: pass an accurate pickup_time to the delivery API based on your actual kitchen prep time. If you’re using FoodMaster’s kitchen display and time slot features, you already have prep time estimates flowing through your system. Use those values when creating the delivery request. Tell DoorDash or Uber “the food will be ready at 7:42 PM,” and they’ll dispatch a driver accordingly.

Handle Failed and Cancelled Deliveries Gracefully

Deliveries fail. Drivers cancel. Addresses are wrong. Build these workflows in advance:

• Driver cancellation: Listen for the “cancelled” webhook. Automatically re-request a delivery (from the same or fallback service). Notify the customer that their delivery is slightly delayed.
• Wrong address: If the driver reports an address issue, have a staff member call the customer immediately. Most delivery APIs allow you to update the dropoff address mid-delivery.
• Food quality concerns: If a delivery takes too long due to driver issues, offer the customer a discount code for their next order. This is cheaper than a full refund and builds loyalty.

Refund Workflows

When a delivery goes wrong, who pays? Both DoorDash Drive and Uber Direct have merchant support channels for disputing delivery fees when the failure was on the driver’s side (e.g., food never delivered, excessive delays). Document every incident. For customer-facing refunds, process them through WooCommerce’s built-in refund system and track the reason so you can identify patterns.

Monitor Delivery Performance

Track these metrics weekly at minimum:

• Average delivery time (from dispatch to delivered)
• Delivery success rate (completed vs. cancelled)
• Average delivery cost per order
• Customer complaints related to delivery

Both DoorDash Drive and Uber Direct provide delivery data through their APIs and merchant dashboards. Export this data and compare it against your order revenue to ensure delivery remains profitable.

Scaling Across Multiple Locations

If you operate more than one restaurant location, each location needs its own pickup address registered with DoorDash Drive and Uber Direct. Your WooCommerce setup needs to route orders to the correct location’s API credentials based on which store the customer ordered from. Multi-location setups in WooCommerce can be managed through separate subsites in a WordPress multisite network, or through a single site with location-based logic — FoodMaster supports multi-location configurations that can simplify this routing.

Third-party delivery integration isn’t a set-it-and-forget-it project. It requires ongoing tuning — adjusting prep times, monitoring driver performance, tweaking delivery zones based on real order data. But the payoff is substantial: you keep customers on your own website, avoid marketplace commissions, and offer a delivery experience that rivals (or beats) the big platforms. Start with one service, nail the workflow, then add the second as a fallback. Your customers — and your margins — will thank you.