What guardrail metrics should DoorDash track for Merchant Portal at global scale

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 operational hub where restaurants, grocers, and other local merchants manage their relationship with DoorDash: onboarding, menus/catalogs, pricing, hours, promotions, orders, payouts, performance insights, support, and account settings. At global scale, changes to the portal can improve merchant efficiency and marketplace outcomes, but they can also unintentionally harm merchant operations, consumer experience, Dasher utilization, or DoorDash economics.

In this metrics interview, you are being asked to identify the guardrail metrics DoorDash should track for Merchant Portal. Focus on how to detect negative side effects from portal changes across diverse merchant types, markets, languages, business sizes, and operational models. The question is not just about listing metrics; it is about defining what each guardrail protects, how it should be measured, and how it would inform product decisions.

Your answer should account for the fact that merchants use the portal for both high-frequency operational tasks and lower-frequency business management tasks. A global guardrail framework should distinguish between true product degradation, seasonal marketplace noise, regional differences, instrumentation gaps, and merchant behavior changes caused by pricing, demand, supply, or policy shifts outside the portal.

The experience should consider:

- Clear definitions of guardrail metrics, including numerator, denominator, time window, and directionality.

- Merchant cohorts such as SMB restaurants, enterprise chains, grocery/convenience merchants, new merchants, mature merchants, and region-specific segments.

- Portal workflows where degradation could create downstream marketplace harm, such as menu accuracy, order operations, store availability, promotions, payouts, and support.

- Instrumentation needs across web, mobile, API-integrated, and managed-account merchant experiences.

- Separation of leading indicators inside the portal from lagging business outcomes in orders, cancellations, refunds, merchant retention, and profitability.

- Guardrails that protect consumers, Dashers, merchants, and DoorDash unit economics rather than optimizing only for portal engagement.

- Alert thresholds, baselines, seasonality, experiment readouts, and how to interpret metric movement during global rollouts.

- Data quality risks, including missing events, duplicated actions, localization issues, third-party integrations, and inconsistent merchant identifiers.

The goal is to frame a robust guardrail measurement system that lets DoorDash ship Merchant Portal improvements confidently while quickly detecting unintended harm across the marketplace. Your response should show how the metrics would be actionable for product teams, reliable enough for experimentation and rollout decisions, and sensitive to the complexity of operating a global local-commerce platform.