Back to all cases
Yandex Eats: New order history screen
Situation
When Yandex Eats, a restaurant food-delivery service, expanded into grocery ordering, support tickets spiked. Store inventory was often unreliable: items were frequently out of stock or substituted during picking. Yet the Order screen displayed only the original basket and total — without reflecting removals, substitutions, or price changes. As a result, customers couldn’t understand why products were missing or whether they had paid for items that were never delivered, leading them to contact support for clarification.
Task
Redesign the order screen to address the most frequent customer questions about grocery orders: clarifying missing items, substitutions, and charges; and in turn reduce the volume of support requests.
Actions
Together with my team, I conducted two rounds of research: analyzing support requests and interviewing customers who ordered groceries. This helped us identify the main problems and collect suggestions for a redesigned order screen.
Identified pain points:
Design process included:
Results
The launch of the new flow tripled takeaway orders — growing from 1% to 3% of all Yandex Eats orders within the first months after release.
Next case
Back to all cases
Yandex Eats: New order history screen
Situation
When Yandex Eats, a restaurant food-delivery service, expanded into grocery ordering, support tickets spiked. Store inventory was often unreliable: items were frequently out of stock or substituted during picking. Yet the Order screen displayed only the original basket and total — without reflecting removals, substitutions, or price changes. As a result, customers couldn’t understand why products were missing or whether they had paid for items that were never delivered, leading them to contact support for clarification.
Task
Redesign the order screen to address the most frequent customer questions about grocery orders: clarifying missing items, substitutions, and charges; and in turn reduce the volume of support requests.
Actions
Together with my team, I conducted two rounds of research: analyzing support requests and interviewing customers who ordered groceries. This helped us identify the main problems and collect suggestions for a redesigned order screen.
Identified pain points:
Design process included:
Results
The launch of the new flow tripled takeaway orders — growing from 1% to 3% of all Yandex Eats orders within the first months after release.
Next case
Back to all cases
Yandex Eats: New order history screen
Situation
When Yandex Eats, a restaurant food-delivery service, expanded into grocery ordering, support tickets spiked. Store inventory was often unreliable: items were frequently out of stock or substituted during picking. Yet the Order screen displayed only the original basket and total — without reflecting removals, substitutions, or price changes. As a result, customers couldn’t understand why products were missing or whether they had paid for items that were never delivered, leading them to contact support for clarification.
Task
Redesign the order screen to address the most frequent customer questions about grocery orders: clarifying missing items, substitutions, and charges; and in turn reduce the volume of support requests.
Actions
Together with my team, I conducted two rounds of research: analyzing support requests and interviewing customers who ordered groceries. This helped us identify the main problems and collect suggestions for a redesigned order screen.
Identified pain points:
Design process included:
Results
The redesigned order screen significantly improved clarity and transparency for users. As a result, support requests related to prices and order composition dropped by 24%, reducing the burden on the support team and increasing customer trust in the service.
Next case