Merchant Platform Ops

---
name: merchant-platform-ops
description: Operate the merchant side of a delivery platform — onboarding, menu management, order handling, payouts, and performance.
category: doordash
---

## Overview

Delivery platforms live or die on merchant success: restaurants and stores that receive orders smoothly, prepare them well, and grow through the platform. This skill covers merchant operations — onboarding, catalog/menu management, order handling tools, performance analytics, payouts, and support. General marketplace-operations guidance, platform-neutral.


Running the merchant side of a delivery platform — onboarding, menu management, tablet operations, payouts, and support — is where marketplace promises meet operational reality. Merchant satisfaction drives selection quality, which drives consumer retention. The skill is building merchant tooling and processes that scale across thousands of locations with wildly varying technical sophistication.
## When to use

- Onboarding merchants to a delivery platform
- Designing merchant dashboards and tools
- Reducing merchant churn
- Improving order accuracy and prep times
- Structuring merchant fees and payouts
- Building merchant support

- Onboarding merchants onto a delivery platform
- Reducing merchant-initiated cancellations
- Designing merchant payouts and fee structures
- Expanding to new merchant categories
- Reducing support ticket volume from merchants
- Designing merchant loyalty or incentive programs
## Core concepts

**Merchant lifecycle.** Acquire → onboard → activate (first orders flowing smoothly) → grow (marketing, optimization) → retain. Most churn happens in the first 30 days — onboarding quality predicts retention.

**Onboarding.** Menu/catalog setup, photo guidance, pricing and fee transparency, hardware/software setup (tablets, printers, POS integration), staff training, and test orders. Frictionless but complete — missing setup steps become support tickets later.

**Order management.** Tablet/app alerts, accept/confirm flows, prep-time setting (accurate prep times drive ETA accuracy), pause/unpause during rushes, item-level availability toggles (86'd items), and order history. Design for a chaotic kitchen — big buttons, loud alerts, minimal taps.

**Performance analytics.** For merchants: order volume trends, acceptance rate, prep time vs. quoted, customer ratings, top items, peak hours, and marketing ROI. Actionable insights ("your prep times spike 6–8pm — consider pausing during rush") beat raw data.

**Fee and payout structure.** Commission rates, delivery fee splits, marketing fees — transparent and predictable. Payout cadence (weekly/daily) and clear statements. Surprise deductions destroy trust; itemize everything.

**Merchant marketing.** Sponsored placement, promotions (merchant-funded or co-funded), loyalty integration, and new-customer offers. Give merchants levers to grow — platforms that only take orders don't retain merchants.


**The tablet problem.** Many merchants — especially independents — run your orders on a dedicated tablet alongside their POS, phone, and in-store chaos. Missed tablet alerts are the #1 cause of merchant-side cancellations. Design for glanceability (loud audio, persistent visual), confirm-by-default flows, and automatic escalation when orders go unacknowledged.

**Menu data quality.** Accurate menus, photos, modifiers, and availability are the product. Stale menus (wrong prices, unavailable items listed) cause refunds and bad reviews that blame the platform. Build self-serve menu tools simple enough for a busy restaurant manager, plus automated audits that flag anomalies.

**Payout trust.** Merchants live on cash flow: payout cadence, fee transparency, and dispute resolution directly affect retention. Weekly payouts with clear statements beat faster-but-opaque alternatives. Every fee should be explainable in one sentence.

**Merchant segmentation.** Enterprise chains (API integrations, dedicated support, custom contracts) → mid-market (self-serve tools + phone support) → independents (simplest tools, community support).
One-size-fits-all merchant ops underserves everyone — segment deliberately and staff accordingly.
**Menu engineering support.** Help merchants optimize: photo coverage (items with photos sell 2–3x more), description quality, price anchoring, bundle suggestions, and prep-time accuracy.
Merchants who sell more stay longer — their success is your retention strategy.
Offer this as a service for top merchants; productize the basics for everyone.
**Dispute resolution.** Order issues need fast, fair resolution: clear policies (who pays for what), empowered support agents (refund authority limits), and merchant appeal paths.
Perceived unfairness in disputes is a top merchant churn driver — audit dispute outcomes for bias quarterly.
## Practical workflow

1. **Design onboarding.** Checklist-driven flow: account → menu → photos → pricing → hardware → training → test order → go-live. Assign onboarding specialists for key accounts; self-serve for long tail.
2. **Build merchant tools.** Dashboard (today's orders, performance), menu manager (easy updates, bulk edits, scheduled availability), order app (kitchen-optimized), promotions manager, analytics, payout statements.
3. **Set performance standards.** Acceptance rate targets, prep-time accuracy, rating thresholds — with coaching before penalties. Publish the standards; enforce consistently.
4. **Enable growth.** Marketing playbook for merchants (photos, promotions, hours optimization), seasonal campaign toolkits, and success stories from top performers.
5. **Support merchants.** Dedicated merchant support (separate from customer support), proactive outreach to struggling merchants (declining ratings, long prep times), and a merchant community/forum for peer learning.
6. **Measure.** Merchant activation rate, 30/90-day retention, orders per merchant, average rating, support tickets per merchant, NPS. Segment by cohort and category.

**Onboarding checklist:** menu complete with photos, pricing verified, fees understood, hardware working, staff trained, test order successful, prep times set, hours correct, promotions considered.


**Merchant onboarding (5-day target):** day 1: contract + menu ingestion (assisted for independents, API for chains) → day 2: tablet/hardware setup + test orders → day 3: staff training (15-min video + quiz) → day 4: soft launch (limited hours, monitored) → day 5: full launch with launch-day support on standby. Measure time-to-first-order and 30-day retention by onboarding cohort.

**Cancellation root-cause program:** tag every merchant-cancelled order (prep overload, item unavailable, tablet missed, staffing) → weekly Pareto review → targeted interventions (prep-time recalibration, menu availability nudges, tablet alert audits). A 1-point reduction in merchant cancellation rate can move consumer retention measurably.

**Merchant health score:** order volume trend → cancellation rate → preparation time accuracy → rating trend → support ticket patterns → payout disputes.
Score weekly; trigger playbooks automatically (coaching for declining, recognition for improving).
**Seasonal readiness:** 6 weeks before peaks: capacity planning guidance → staffing recommendations → menu/promotion prep → support surge staffing → communication calendar.
Peak seasons make or break merchant annual revenue — proactive readiness beats reactive firefighting.
## Common pitfalls

- **Weak onboarding.** Merchants going live with broken menus and untrained staff. First impressions determine retention.
- **Opaque fees.** Hidden charges and confusing statements. Transparency is non-negotiable.
- **Tools designed for HQ, not kitchens.** Delicate UIs that fail during rush hour. Design for chaos.
- **No performance feedback.** Merchants never learning why ratings drop. Proactive, actionable insights.
- **One-sided economics.** Squeezing merchants until they leave. Sustainable partnerships retain supply.
- **Slow merchant support.** Merchants losing money while waiting on hold. Prioritize merchant support speed.
- **Ignoring the long tail.** All attention on top merchants while small ones churn silently. Scaled programs for everyone.
- **Designing for chains, forgetting independents.** Enterprise API integrations while the long tail struggles with tablets. The long tail is where selection breadth comes from — serve it deliberately.
- **Opaque fee changes.** Surprising merchants with new fees destroys trust instantly. Announce early, explain clearly, grandfather where possible.
- **Support only in platform language.** Merchant support in jargon or only via chatbots. Phone support during service hours for urgent issues (active orders) is table stakes.
- **Feature parity obsession.** Building every feature for every segment. Enterprise needs APIs; independents need simplicity — different roadmaps, honestly communicated.
- **Ignoring merchant feedback.** Product decisions made without merchant input. Advisory boards and regular surveys keep the roadmap grounded.