Making complex shop settings feel simple—and connecting them to a storefront that works.
A connected commerce experience
Shop builder · Backend settings · Storefront · Mobile checkout
ShopMaven / Backend settings and storefrontSelected interface explorations
ProjectShopMaven
FocusE-commerce · Product UX/UI
ScopeSettings & storefront experiences
Confidentiality note
Due to a Non-Disclosure Agreement associated with the original project, available information may be limited.
01 / Introduction
Simple to use. Powerful behind the scenes.
Design an online shop builder connected to a clear, structured backend settings system.
GOAL
Build the shop. Control the details.
Design a shop builder supported by clear, structured backend settings.
THE CHALLENGE
Complexity behind the scenes. Simplicity on the surface.
The project unfolded in phases, each introducing new challenges. The central design task was to make complex backend settings easy to understand and manage, while maintaining a seamless connection to the customer-facing storefront.
Key questions shaped the design process:
01
Designing for simplicity
What makes a settings interface intuitive and easy to navigate?
02
Optimizing visibility
Where should tags and chips appear without obscuring product information?
03
Deals & offers
How can discounted products be presented clearly?
04
Navigating languages
What makes language management and translation flows intuitive?
05
From cart to confirmation
How can checkout feel straightforward from start to finish?
02 / Use cases
Built for different ways of selling.
Different businesses, one flexible platform.
01 / Use case
E-commerce startups
Launch online stores with customizable templates and marketing tools.
02 / Use case
Retailers going online
Reach new customers while managing inventory in one place.
03 / Use case
Niche brands
Build distinctive storefronts with customizable themes and plugins.
04 / Use case
Global expansion
Support international customers with multiple currencies and languages.
03 / Design guidelines
Clarity as a design principle.
Three principles guided decisions throughout the project.
01
Ease of use
Help shop owners set up, customize, and manage their storefronts independently.
02
Accessibility
Make settings and storefront interactions easy to navigate across devices.
03
Efficiency
Keep common tasks efficient through clear, user-centered workflows.
04 / Process
Understand. Define. Ideate. Design.
From understanding the problem to designing the experience.
01 / PHASE
Understand
Research user needs, identify pain points, and understand the problem.
02 / PHASE
Define
Translate research findings into clear problem statements and project goals.
03 / PHASE
Ideate
Explore a range of ideas and potential solutions.
04 / PHASE
Design
Develop wireframes, mockups, and prototypes to test and communicate selected solutions.
05 / Screens
A closer look at the experience.
Examples from the backend settings and the storefront.
Each screen shows the problem, the thinking behind it, and the resulting solution.
Scope note
All features in this project, including those not shown here, were individual UX projects with their own research and design process.
Settings navigation overview
01 / 07
The problem
How might users navigate a wide range of shop settings without feeling overwhelmed?
The process
Research, competitor analysis, and user feedback pointed toward a familiar, straightforward navigation structure.
The solution
A scannable settings overview with distinct entry points and concise descriptions.
Settings page layout
02 / 07
The problem
How should individual settings pages organize information and controls for easy use?
The process
Research, competitor analysis, and testing informed a simple structure with clearly defined sections.
The solution
A centered layout with clear groupings and consistent spacing, making settings easier to scan.
Language management
03 / 07
The problem
How can users add languages, edit translations, and remove languages without unnecessary steps?
The process
Research, competitor analysis, and feedback supported editing translations directly in context.
The solution
A table-based interface with inline editing for managing languages and translations in one place.
Language management — table settings overlay
Product list view in the storefront
04 / 07
The problem
How can product tags be displayed without covering important product imagery?
The process
Research and surveys highlighted the need for a clear default view with flexibility to customize it. Competitor analysis informed the layout.
The solution
A flexible product grid that keeps imagery visible and places tags unobtrusively, using reduced opacity where appropriate.
Product offers in the storefront
05 / 07
The problem
How can shoppers recognize special offers and understand when they expire?
The process
Research, testing, and feedback informed a simple presentation with prominent timing cues.
The solution
Timers and progress indicators distinguish active offers and communicate when deals end or begin.
Product page in the storefront
06 / 07
The problem
How can shoppers explore product variants, including unavailable options?
The process
Research and feedback helped shape familiar ways to switch between colors, sizes, and availability states.
The solution
Clear selection controls—buttons, swatches, and image-based options—make variants easier to compare.
Bundle view in the storefront
07 / 07
The problem
How can shoppers understand what a bundle includes and how much they save?
The process
Research and testing emphasized visibility of each included item and direct access to its details.
The solution
A clear list of bundled items, supported by a prominent savings label.
06 / Bonus
A smoother path to checkout.
An additional exploration: mobile checkout.
A clear checkout flow helps shoppers complete their purchases with confidence. This exploration maps the key decisions and presents the mobile entry screen.
From cart to confirmation.
Mobile checkout user flow
Mobile checkout interface
07 / Project outcomes
Built to work better, together.
Project outcomes
The principles that guided the work and the improvements the redesign aimed to deliver.
Key takeaways
The key principles that kept usability at the center of design decisions.
Research-driven foundation
User interviews, feedback, competitor benchmarking, and input from internal experts grounded decisions in evidence rather than assumptions.
Modular UX planning across MVPs
Each MVP was scoped to deliver value while advancing a shared platform vision. Lessons from one release informed the next.
System-wide UX and UI consistency
Shared interaction patterns, components, spacing, hierarchy, and visual language created a more consistent and predictable experience.
Continuous stakeholder collaboration
Ongoing collaboration with product, engineering, support, and QA helped balance user needs, technical feasibility, and business goals.
Validation before scaling
Early prototypes and usability checks helped test assumptions, clarify interactions, and reduce the risk of rework.
Impact
How the new progressive web app (PWA) addressed limitations of the previous system and supported product goals.
Stronger product foundation
The new PWA replaced the previous LTS system with a foundation designed for greater speed, stability, and scalability.
Clearer merchant experience
Clearer flows and simpler decision points aimed to reduce friction during store setup and everyday management.
More efficient core tasks
Simplified onboarding, inventory handling, and order management made core workflows more straightforward.
Faster delivery across teams
Shared UX patterns and a unified UI language supported faster collaboration and greater consistency across MVP releases.
Reduced tech and design overhead
Reusable components and consolidated interaction logic made it easier to extend the product and maintain consistency over time.