What guardrail metrics should DoorDash track for Merchant Portal

Problem Statement Description

Product context: DoorDash is a local commerce and delivery platform; its products include restaurant delivery, DashPass, grocery and retail delivery, merchant tools, and dasher tools.

DoorDash’s Merchant Portal is the primary workspace where restaurant and retail partners manage their presence on the marketplace, including store hours, menus or catalogs, pricing, availability, promotions, order settings, payouts, performance insights, and support workflows. The question asks you to define guardrail metrics DoorDash should monitor to ensure changes to the Merchant Portal do not unintentionally harm merchants, consumers, Dashers, or marketplace economics.

Focus on the merchant user journey and the downstream marketplace impact of portal activity. A seemingly small portal issue—such as an incorrect menu update, confusing promotion setup, delayed payout visibility, or poor order-management configuration—can affect order accuracy, fulfillment reliability, merchant trust, consumer experience, Dasher efficiency, and DoorDash’s unit economics.

This is a metrics interview question, so the emphasis is not just naming metrics. You should explain what each guardrail is protecting, how it would be defined, what the denominator is, how it would be instrumented, which merchant cohorts it should be tracked for, and how DoorDash would use it to make product or launch decisions.

The metric framework should consider:

- The key Merchant Portal workflows being protected, such as onboarding, menu or inventory updates, store settings, order operations, promotions, analytics, payouts, and support.

- Clear metric definitions, including numerator, denominator, event source, time window, and whether the metric is merchant-level, store-level, order-level, or session-level.

- Segmentation by merchant type, size, tenure, geography, cuisine or retail category, integration status, and operational complexity.

- Marketplace guardrails that capture downstream effects on consumers, Dashers, merchants, and DoorDash economics without optimizing only for portal engagement.

- Instrumentation requirements, including portal clickstream events, configuration-change logs, order outcomes, support contacts, payout systems, and merchant feedback.

- Thresholds or alerting logic that distinguish normal variance from meaningful degradation, especially during launches, experiments, or seasonal demand spikes.

- Decision usefulness: how the guardrails would inform experiment readouts, rollout pacing, rollback decisions, merchant communication, and product prioritization.

The goal is to present a practical guardrail framework for Merchant Portal that helps DoorDash ship improvements confidently while preserving merchant ROI, operational reliability, marketplace balance, and trust across all sides of the platform.