Uber tells restaurants using UberRush to switch to UberEats by May 8; spokeswoman says UberRush will focus on backend delivery logistics for merchants
Uber, Travis Kalanick's smartphone-based … Catherine Shu / TechCrunch : Report: UberRush will stop handling restaurant deliveries Tweets: Alison Griswold / @alisongriswold : A former employee told me Uber has had surge on UberX b/c too many drivers were delivering food for the dinner rush http://qz.com/... http://twitter.com/...
Context & Ripple Effects
UberRush began as an expansion bet: Uber launched the on-demand courier service in Chicago and San Francisco in October 2015, then opened the RUSH API to outside developers so any product could bolt on delivery. Eighteen months in, the consumer-facing version is being wound down for restaurants, with the service repositioned around backend logistics for merchants.
The move matters because it shows Uber pruning a side business rather than scaling it — and the corpus suggests the pruning continued: roughly a year later Uber announced it was shutting UberRUSH down entirely for items under 30 pounds.
First-order effects
- Restaurants currently relying on UberRush have until May 8 to migrate their delivery orders to Uber Eats or find another courier.
- Driver supply gets pulled back toward ride-hailing — per Alison Griswold's reporting, too many UberX drivers were delivering food during the dinner rush, forcing surge pricing on passenger trips.
Second-order effects
- Merchants who built ordering flows on the open RUSH API face platform risk: the developer-facing product they integrated against is being narrowed to backend logistics, and ultimately closed.
- Uber Eats absorbs the displaced restaurant demand, concentrating Uber's food-delivery business in one owned channel instead of two overlapping ones.
Third-order effects
- The pattern points to Uber running delivery as a portfolio of bets it closes when unit economics fail — the same logic behind the later shutdown of Uber Eats in Brazil as part of a global repositioning away from unprofitable operations.
- For third parties building on Uber infrastructure, each retrenchment reinforces that APIs and white-label services are contingent: integration decisions should price in the possibility of the surface disappearing.
The trend: Uber is consolidating its delivery ambitions around owned, dense marketplaces like Uber Eats while retiring standalone courier products that never reached scale.