Platform Control Threatens CloudKitchens Tenants

The core risk is that CloudKitchens does not control the customer tap. Its tenants rent kitchen space, but the orders usually arrive through DoorDash and Uber Eats, so the platforms decide ranking, promos, delivery fees, and customer membership perks. That gives the platforms two ways to squeeze tenant economics, by raising the cost to appear in the app, or by steering demand toward their own managed kitchen formats and preferred merchants.

• DoorDash already sells both marketplace demand and logistics as separate products. Restaurants can buy Drive for flat fee delivery through their own sites, while DoorDash also runs kitchen programs that place brands inside DoorDash operated facilities. That means the same platform can be supplier, landlord, and traffic controller at once.
  2 sacra 4 doordash 5 doordash
• The problem is sharper for delivery only brands because they are harder to discover off platform. Research on restaurant software shows many delivery marketplace orders carry roughly 30% commissions, while first party ordering stacks can land closer to 10%. If platform fees rise, a tenant with no dine in traffic or direct customer list can go unprofitable fast.
  3 sacra 4 doordash
• This pattern is not unique to DoorDash. Rappi built more than 300 dark kitchens to help restaurant partners expand and to make its own logistics network denser and more efficient. Once a delivery app owns demand and kitchen infrastructure together, it can decide which brands get the best locations, courier flow, and promotional exposure.
  6 uber 7 sacra

The next phase of the market favors kitchen operators that own more than boxes with stoves. The winners will be the ones that either generate direct consumer demand, or bundle software, procurement, labor, and fulfillment tightly enough that tenants make money even if marketplace rules change. Otherwise CloudKitchens remains exposed to platforms moving from partner to gatekeeper.