INFI · Initiative

Uber Direct Delivery — UI Documentation

One delivery capability across three product surfaces, organized by the five delivery epics. Every screen is drawn in its real app's design language and mapped to its acceptance criteria.

MOOO · customer griddle · 📱 Mobile + 🖥 Web Merchant Console ng-zorro #2a2bc0 Operation Console ng-zorro #1890ff

How it fits together

Delivery is governed top-down: INFI Operations turns it on and keeps the platform healthy → the Merchant configures it as a dining option → the Customer orders & tracks. Money and health flow back up.

1 · Operation Console

Govern & enable

Feature flag per merchant, one central Uber connection, certify, monitor.

2 · Merchant Console

Configure

Delivery as a dining option — area, pickup, customer-paid fee — plus order tracker & delivery report.

3 · MOOO

Order & track

Choose delivery up front, pay, follow it live, get notified — on mobile & web.

↺  Money flows back: the customer pays the delivery fee + courier tip on top of the order → INFI holds → remits to Uber; INFI covers Uber's charge by withholding that fee slice from the order total — no separate merchant bill.

By epic

The 17 stories across five functional epics. Each links to its UI doc (real-app mock + spec covering every AC). SS-9047 Research is an engineering spike — no UI.

SS-9033

Merchant

See & understand delivery — orders + spend
SS-9034

Money & Settlement

Collect fee+tip → INFI holds → remit to Uber · recover by withholding the fee from the order total
SS-9036

Production Readiness

Certify & launch · monitor & support
SS-9047

Research / Spike

Engineering findings & constraints
Engineering spike — no UI (findings feed certification & design).
17 stories · 5 epics · 3 surfaces (MOOO mobile+web · Merchant Console · Operation Console) · every screen mapped to its story & acceptance criteria · INFI location = Uber pickup (no store / no matching)