Peter Uzzi
Product + Design Leader
Expanding Clover’s reach to Enterprise
Clover multi-location background
Clover’s legacy multi-location functionality trailed in the market and lacked feature parity with competitors. Merchants were using a separate application from their main Clover platform, making the experience frustrating and inefficient. Our goal was to streamline and integrate these capabilities into a single, scalable "One Dashboard" solution that works for businesses of any size. To achieve this, we developed a new franchise content architecture, improved navigation, and an upgraded content management system. The solution is now live.
Role: Design Lead
Contributions: Systems Design, UI Design, Prototyping, Product Strategy, UX Research, Executive Storytelling
Team: Senior Product Designer, Product Designer, UX Researcher, Product Manager, Engineering team
Timeline: 12 months
Milestones: Discovery, UX Research, UX Interviews, Design, Pilot launch, Validation testing
The Challenge
I led a year-long design effort to modernize these features, aiming to retain high-value SMBs, cut costs, and attract enterprise franchises. I addressed architectural constraints, bulk editing workflows, and content management across locations. A key challenge was eliminating redundancies like merchants managing multiple accounts and limitations to the data they could manage for multiple locations from a separate legacy tool. Another was aligning multiple product and design teams to solve system-wide issues. As a Principal Designer, I excel at uniting teams around a shared vision and maintaining a big-picture approach that delivers real value to users.
The legacy architecture forced merchants to use one web platform for their day-to-day business management, and another app for multi-location bulk actions that were limited to a sub-set of content.
Our solution introduced a scalable single merchant account and dashboard. The content management design used one UI for single-location merchants while growing with multi-location merchants.
Before, navigating to the multi-location dashboard opened a separate app in a new window. Merchant’s could only make bulk changes in this silo, with little transparency to how their changes cascaded to individual locations.
The new architecture combined the two apps into one scalable dashboard for all merchants. New location-specific and bulk editing actions appear contextually. Merchants can see the impact of their changes in real time as they edit object-level details for one location or many.
Execution
I led design sprints with product, engineering, and executive stakeholders to design a new hierarchical system that allowed merchants to manage multiple accounts from one dashboard. I then designed a scalable navigation system that supports both single-location businesses and large enterprise franchises with nested location groups. The new A11y accessible interface makes it easy to navigate, manage, and pivot between locations and groups—and to powerfully filter the content within each.
The merchant’s name is now the focus and users can perform bulk tasks for groups of locations called Chains. The new navigation scales for all merchant types and admins. Clear signifiers indicate when multiple locations are selected.
A hierarchical organization navigation solved the problem of redundant accounts.
Merchants can view locations relationally and pivot between them in the same session.
Beyond navigation, merchants needed more robust content management tools. I collaborated with product and design teams across platform, inventory, reporting, employees, and customer management to audit and scale our content model—ensuring it supported location management while integrating with parallel initiatives that were expanding our services (e.g., adding appointments for new merchant verticals such as Health and Wellness).
As a Principal Product Designer, I approach platform design with a systems mindset, working horizontally across product verticals to align teams, maintain architectural cohesion, and deliver a unified user experience.
This project highlights how I led cross-functional design efforts, working closely with engineering architects and content designers to develop scalable content structures that accommodated both new services and location management complexities.
Before, objects like Items and Employees were flat and unrelatable. I helped design new relational object classes that extended our platform to support merchants in new business verticals beyond our core of Restaurants, like Retail and Services. In this case, we were adding Appointments and Services for the first time. I helped to reconcile new content design patterns across our platform.
Merchants needed a way to inspect new meta content and assign relatable objects to one another. I designed a new global interaction pattern that supported all merchant verticals, content types, and location use cases. Merchants can invoke one familiar UI across use cases and content types to explore secondary tasks, whether assigning an item to a location or an appointment to an employee.
Collaborating with our Design Systems team, I created new global components and interaction patterns for desktop and mobile to support our new content types, services, and location architecture. This modal drawer interaction pattern became ubiquitous across content types, locations, and merchant vertical use cases, scaling from less complicated use cases like the one above to more complex multi-step workflows and “side-journeys” (click for prototype) like the example below. From a design system perspective, I built this pattern as a mobile-first, Atomic, Figma component that extends the navigation location-switching modal above, using Figma component variations, states, and boolean properties.
Between new merchant account architecture, navigation, content architecture, and interaction patterns, we replaced two separate, limited applications (each using disparate content and UI patterns) with one unified dashboard and common patterns. This more straightforward and transparent system reduced the cognitive load for our users, made bulk actions easier, increased transparency, reduced errors, and saved merchants time while giving them more self-service options.
The modal workflow can be invoked contextually and unobtrusively. It works across all content types like inventory, appointments, employees, customers, settings, and more. In this example, admins can modify default or item-specific taxes from location to location, share employees, or limit employee permissions by location.
Corporate admins and individual locations can manage differences such as assigning ”variations” for objects or their properties across locations while preserving reporting integrity for admin users.
Solution and Impact
With over 750,000 merchants—10% managing multiple locations—this solution helps tens of thousands streamline operations. Merchants now have a centralized admin interface to organize locations, access both aggregate and individual reports, and simplify tasks like managing shared inventory and employees. This allows them to scale efficiently while meeting their unique business needs. We delivered the project on time, enabling Clover to:
Improve retention of key accounts and improved merchant satisfaction by simplifying these operations and freeing merchants to focus more on their businesses.
Reduce support costs by eliminating duplicate accounts and enabling more self-service tasks for merchants that eliminated the white-glove customizations that Clover was offering as workarounds for many merchants.
Expand into the enterprise market by supporting complex franchise use cases.
Our solution received positive feedback from merchants, solidifying Clover’s position as a scalable and user-friendly point of sale and business management platform for businesses of all sizes.
I approached all solutions with a Mobile-first and responsive strategy. All designs went through our component-driven design system process, leveraging component variants and auto-layout.
