Peter Uzzi
Product + Design Leader
Expanding Clover’s reach to Enterprise
Background
Clover’s multi-location tools lagged behind competitors, forcing merchants to juggle two separate platforms and inconsistent workflows. This created frustration, errors, and wasted time—especially for franchises managing hundreds of locations. As Principal Product Designer, I led a year-long redesign of Clover’s web dashboard to simplify location management, unify workflows, and make everyday tasks like inventory and employee management seamless for businesses of any size.
Challenge & Task
The legacy multi-location platform architecture and its feature gaps risked losing high-value multi-location SMB accounts who were missing out on features available to single-location merchants on our core merchant dashboard.
I was tasked with transforming our core platform from supporting only single-location merchants to support both multi-location SMBs and enterprise franchises. This required:
Designing all new multi-location and franchise navigation.
Auditing and redesigning a number of core dashbaord features and workflows to scale with different user types and jobs.
Innovating a number of new design system components to handle new jobs, content, and scale.
Pain points for multi-location merchants on the legacy platform:
Multiple account juggling and platform switching.
Inconsistent UX patterns:
IA: core navigation and account management
Operational workflows: inventory and employees
Admin workflows: taxes and permissions
Content management workflows: search, filtering, and bulk editing.
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.
We first simplified and focused the navigation which included business nav (top) and content nav (left). The new architecture combined the two legacy 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.
Planning & Strategy
The initial plan I was asked to execute was to update the legacy platform with minimal, table-stakes features—keeping platforms separate. After leading discovery sprints and interviews with our users, it was clear that this would not solve the core problem our users faced. Partnering with Engineering and Product, I proposed an alternative solution:
Redesign Clover’s core web dashboard to streamline the Clover platform experience for all users, to
Retain high-value accounts.
Attract new enterprise franchises.
Reduce friction and increase conversions for merchants upgrading to multi-location accounts.
Reduce support costs.
Create a scalable, accessible, and cohesive location management experience (see final prototype). As a proof of concept, I
Leveraged our fledgling design system to demonstrate design velocity by extending existing components.
Partnered with our recently formed Design System team to help accelerate the development of core components and contributed new multi-location components and use cases.
My concept testing and validation aligned cross-functional teams around a shared architectural vision, utilizing the core platform along with new multi-location workflows, new design system components, and a new scalable navigation.
The merchant’s name is now the focus and users can perform bulk tasks for groups of locations. 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.
Before, entities like Items and Employees were flat and unrelatable. I helped design new relational entities and 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 and design system.
Execution
Systems & Architecture
Led design sprints with cross-functional stakeholders to define a new merchant account data model to support multiple locations per account.
Designed scalable navigation supporting nested location groups and advanced filtering.
This unified account architecture, navigation, content structures, and UI patterns into a single streamlined dashboard.
Replaced two disjointed apps, reducing cognitive load, minimizing errors, and enabling faster bulk actions.
Redesigned key workflows (Inventory, Employees, Settings) with new design system components.
Ensured A11y compliance for all navigation and content structures.
Cross-Functional Collaboration
Partnered with Inventory, Reporting, Employees, and Customer Management teams to scale content models for multi-location use cases.
Integrated with new merchant services (e.g., appointments for health/wellness verticals)—a concurrent project that I was leading.
Design Systems & Patterns
Partnered with the Design Systems team to create global components and interaction patterns, including:
A scalable modal drawer pattern for mobile and desktop, supporting both simple edits and complex workflows.
Built components as mobile-first atomic Figma assets with states, variations, and boolean properties for flexibility.
Merchants needed a way to inspect and manage new meta content without leaving their primary task workflow. 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 like assigning an item to a location or an appointment to an employee.
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 entities or their attributes across locations while preserving reporting integrity for admin users.
Solution & Impact
Merchants gained a centralized dashboard to manage locations, employees, and inventory, and more, reducing frustration and saving significant time.
Simplified navigation and bulk actions reduced errors and cognitive load, enabling faster training and onboarding.
Improved self-service capabilities empowered merchants, eliminating the need for costly white-glove support and custom workarounds.
Enterprise franchises can now manage complex hierarchies and reporting from one scalable platform, helping Clover expand into new markets.
The redesigned dashboard strengthened retention for high-value SMBs and received positive feedback from merchants for its clarity and ease of use.
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.
