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
✓ FINAL UI production-ready — build to this
All other screens are spec mocks (real-app design language + AC), not final UI.
✎ Revised · AI epics · 2026-08-17
The delivery work is now broken down under the AI Jira project. Five screens were reworked or added to match it:
AI-10 location configuration (one inline screen: method · radius · pickup · contact · fee statement);
AI-11 the Operations Console service toggle and menu eligibility + the Uber Direct attestation;
AI-12 the customer address book (My Addresses);
AI-13 Mobile and Online consolidated into one channel.
Every one of these mocks is live — the rules (gates, validation, Save blocking) actually run.
✎ Revised · PI-430 · 2026-07-22
Seven changes are folded in, with the old version kept visible (struck-through) on each page:
1) consumer flow is address-first (enter address → then in-range stores);
2) delivery address lives in Profile (add/edit/delete);
3) store area is radius-only (zip removed);
4) area + pickup + fee + compliance are one screen;
5) fee is a note, not a config;
6) Delivery is a Menu dining option that gates store config;
7) age-restricted / prohibited-item compliance confirmation on config-menu & config-delivery.
By AI epic · current Jira breakdown
The five screens the AI epics changed. Each is drawn in its real app's design language, and each runs its own rules — toggle, tick and type to see the gates fire.
AI-11
Uber — Merchant Enablement
Who may sell delivery: the merchant-level switch + which menus qualify
AI-10
Uber — Location Configuration
Everything a location must supply before a courier can be sent
AI-12
Uber — Customer Addresses
The customer address book — profile data, not order data
AI-13
Uber — Dining Option Consolidation
Mobile + Online become one channel; Kiosk adopts the same patterns
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 ConsoleGovern & enable
Feature flag per merchant, one central Uber connection, certify, monitor.
→
2 · Merchant ConsoleConfigure
Delivery as a dining option — one screen: fulfilment method, radius area, pickup & operational contact; gated by a Menu made visible for Delivery. Plus order tracker & report.
→
3 · MOOOOrder & track
Pick delivery, enter your address first, see the stores in range, 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 · earlier PI-430 breakdown
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-8969
Onboarding & Configuration
Turn delivery on (OC + MC) · central Uber connection · area / fee / pickup
SS-9032
Consumer Order Flow
Choose delivery up front → pay → track → notified · mobile + web
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).