Eatzy Management: Restaurants run their own menu
A portal for restaurant owners and managers on Eatzy. They update the menu, take sold-out dishes off and check their sales themselves, without calling an account manager.
- Role
- UI/UX Designer
- Users
- Restaurant owners and managers
- When
- 2017–2020
- Platforms
- Web app (in the browser)
The problem
Same power as the staff portal, for people new to software
The portal covers what the platform's local account managers could already do in their own portal: restaurant info, photos, item stock and analytics. But its users are restaurant owners and managers, mostly with little experience with tech.
What I did
One flow at a time, reviewed before UI
- Research, then flows and wireframes.
- A prototype for each flow, and a review before any visual design.
- UI once the flows were approved, then specs for developers.
- Analytics and heatmaps before launch, so real use could simplify it further.
The portal
Plain words, one job per screen
Revenue, income, average ticket and customers, split by delivery and takeout.
“86 it” takes an item, or a single option like a dressing, off the menu until it’s back.
Issue a refund and check payouts against card and POS records.
Restaurant info, photos and descriptions, kept up to date by the people who know them.
Result
Owners do it themselves
Restaurant owners and managers now update their info and media, manage stock, issue refunds and see how their restaurant performs, on their own. Analytics and heatmaps were in place from day one to keep simplifying it.
More from the same platform: dispatch, ordering and the kitchen tablet.
Tell me what you’re building and who it’s for. Thirty minutes is enough to see if I’m the right designer for it.
What happens next
- Pick a timeA 30-minute call, whenever suits you.
- Tell me about the productYour goals, the people using it and what’s in the way.
- Know if it’s a fitYou’ll leave knowing whether I’m the right designer for it.