Multi-Location Restaurant — White-Label Delivery Migration ROI

📊 Block 1 — Current Commission Bleed by Platform

▼

# Delivery revenue per location per platform platform_delivery_rev = (location_rev × delivery_%) × platform_share_% # Monthly commission paid to platform (money leaving the business) commission_bleed = platform_delivery_rev × commission_rate_% # Monthly delivery orders monthly_orders = platform_delivery_rev ÷ standard_AOV

✅ Block 2 — White-Label Migration Savings

▼

# For each migrated order: commission no longer paid, white-label flat fee paid instead migrated_orders = monthly_orders × migration_rate_% commission_saved = migrated_orders × AOV × commission_rate_% white_label_cost = migrated_orders × flat_fee_per_order net_saving_per_platform = commission_saved − white_label_cost # Key insight: flat fee is fixed regardless of order value → higher AOV = larger saving

💚 Block 3 — Net ROI vs Your Fees

▼

# The question: do client savings exceed what you charge? total_monthly_saving = sum of net_saving across all platforms × all locations net_client_gain = total_monthly_saving − your_monthly_fee payback_months = your_setup_fee ÷ net_client_gain # For this to make sense: net_client_gain must be POSITIVE and payback must be reasonable (<12 months)

📈 Block 4 — Economies of Scale (Migration Scenarios)

▼

Your monthly fee is a fixed cost. As migration % increases, savings grow linearly while your cost stays constant — this is the economies-of-scale argument you make to the client.

🎯 Block 5 — High-Value Order Nudging Analysis

▼

# White-label flat fee is FIXED regardless of order value # Commission is a %. So larger orders save more when migrated. saving_std_order = (commission_% × std_AOV) − flat_fee saving_hv_order = (commission_% × hv_AOV) − flat_fee extra_per_hv_order = saving_hv_order − saving_std_order # = commission_% × (hv_AOV − std_AOV) → entirely driven by order value difference

🤖 Block 6 — Nudging Strategies to Drive High-Value Direct Orders

▼

The flat fee structure means every extra dollar of order value saves proportionally more on migrated orders. These strategies are designed to engineer higher-value orders specifically through the direct/chatbot channel.

🍗 Group Box Exclusive

Offer "Party Box for 4" (≥CA$60) only via direct channel. Not listed on any platform. Chatbot promotes it by name during order flow.

+CA$27 vs std order on Uber Direct

💰 Direct-Only Discount Threshold

"Order CA$55+ on our website and save CA$5." Costs you CA$5 in discount, saves ~CA$8–10 in commission vs. Uber Marketplace. Net positive.

Net CA$3–5 saved after discount

⭐ Loyalty Points — Direct Only

Points only accumulate when ordering via chatbot/website. After 5 orders, free side. Drives repeat behaviour AND channel migration simultaneously.

Repeat order frequency ↑

📦 Catering & Pre-Orders via Chatbot

Corporate lunches, office orders, team meals. These are CA$80–150+ orders. Chatbot handles pre-order intake during lean window (1:30–5pm) — zero labour cost.

Highest ROI per order type

⏱ Priority Prep for Direct Orders

"Direct orders get a 5-minute head start on prep." Customers ordering for pickup or fast delivery are incentivised to go direct. No cost to implement.

Zero cost nudge

🎁 Add-On Upsell in Chatbot Flow

At checkout, chatbot suggests: "Add 6 wings for CA$9?" or "Upgrade to large combo for CA$4?" Platforms bury this. Your chatbot surfaces it. Raises AOV on every direct order.

AOV uplift on every order

📱 QR Code at Table & Packaging

In-store QR code on tables + printed on takeout bags: "Next delivery? Order direct. Same DoorDash driver. Lower price." Converts dine-in and pickup customers to direct.

Zero cost acquisition

🏢 Corporate Account Setup

Chatbot offers "Set up a corporate account for weekly orders." Creates recurring high-value direct orders. Manager 1 (Scarborough) handles Agincourt/Scarborough business corridor.

Recurring high-AOV stream

⚙️ Block 7 — Dispatch Automation Workflow

▼

When a customer places an order via the chatbot, the dispatch to DoorDash Drive / Uber Direct / SkipGo must happen automatically — no staff action required. Here is the technical flow and what you need to build in Make.com.

1

Customer Orders via Chatbot

Chatbot collects: items, qty, delivery address, payment. Sends structured order payload to POS via webhook.

Chatbot → Webhook

→

2

POS Receives & Confirms

POS fires a confirmation event. Make.com watches this trigger. Order is now in the kitchen queue.

POS Webhook OutMake.com Trigger

→

3

Make.com Creates Delivery Request

Scenario calls white-label API with: pickup address, dropoff address, order value, prep time estimate.

DoorDash Drive APIUber Direct APISkipGo API

→

4

Driver Assigned

Platform assigns nearest Dasher/driver. Returns tracking URL + ETA to Make.com.

Delivery ID + Tracking URL

→

5

Customer Gets Tracking

Make.com sends tracking link back to customer via chatbot / SMS. Full loop closed automatically.

SMS / Chatbot Message

What you need: API access to DoorDash Developer Platform (developer.doordash.com), Uber Direct API (developer.uber.com), SkipGo (via Skip merchant account). Each requires a merchant account already in place. Platform selection logic in Make.com can default to cheapest available option (Uber Direct CA$7.99) or match the platform the customer originally came from.

Multi-Location Restaurant — White-Label Migration ROI

⚙️ Assumptions

💰 Revenue

📱 Platform Mix (% of delivery revenue)

💸 Marketplace Commission Rates

⚡ White-Label Flat Fees (verified)

🧾 Order Values (pre-tax, from POS)

📈 Migration Rates & Operations