Should Uber bundle Wallet with another product for restaurants at global scale

Problem Statement Description

Product context: Uber is a mobility and delivery platform; its products include rides, Uber Eats, grocery and retail delivery, freight, driver and courier tools, and marketplace pricing.

Uber is evaluating whether its Wallet offering for restaurants should be bundled with another restaurant-facing product and scaled globally. In this context, “restaurants” refers to merchant partners using Uber’s marketplace to receive orders, manage payouts, operate delivery workflows, and potentially access adjacent financial or growth tools. The strategic question is whether bundling Wallet can strengthen Uber’s restaurant ecosystem, improve retention or monetization, and create a defensible advantage versus delivery and local marketplace competitors.

You should frame the decision as a global product and go-to-market strategy, not just a feature packaging exercise. Consider the needs of different restaurant segments, from small independent merchants to enterprise chains, and how their pain points vary across markets, regulatory environments, payment rails, and competitive dynamics. The analysis should explore which adjacent product categories could plausibly be bundled with Wallet, what value the bundle would create, and whether Uber has the right to win.

The recommendation should account for strategic trade-offs: marketplace liquidity versus margin, restaurant adoption versus operational complexity, global consistency versus local customization, and short-term revenue versus long-term ecosystem lock-in. You are not expected to design the full Wallet product, but you should define the strategic logic, decision criteria, risks, and conditions under which Uber should or should not proceed.

The experience should consider:

- The restaurant workflows Wallet touches, including payouts, cash flow management, billing, incentives, refunds, ads spend, and reconciliation.

- Potential bundle candidates such as merchant ads, Uber Eats ordering tools, loyalty, capital/financing, analytics, POS integrations, or supply/procurement services.

- Restaurant segment differences by size, maturity, geography, delivery dependence, and financial sophistication.

- Competitive pressure from food delivery platforms, super-apps, payment providers, POS systems, and local merchant service providers.

- Strategic benefits Uber could seek, such as higher merchant retention, increased share of restaurant spend, improved payout reliability, better ad adoption, or stronger marketplace liquidity.

- Trade-offs around bundling complexity, pricing transparency, regulatory exposure, trust, support burden, and impact on restaurant unit economics.

- Global rollout considerations, including payment infrastructure, compliance, localization, sales enablement, and market-by-market readiness.

- Decision gates and success signals that would indicate whether bundling should scale, remain limited to select markets, or be deprioritized.

Your goal is to evaluate whether bundling Wallet with another restaurant product is strategically attractive for Uber at global scale, identify the most important options and risks, and articulate a clear decision framework for leadership without jumping directly to a product design or implementation plan.