Case Study: E-commerce Product Management

Helping small businesses manage products and inventory

I redesigned how store owners manage products, categories and stock, so it works properly on both desktop and mobile.

Role
Senior Product Designer
Company
Jimdo
Team
PM, EM, 1 frontend engineer, 1 backend engineer
Status
Shipped
The product list on desktop, showing status, inventory and stock for each product
The same product list on mobile

The product list on desktop, and on mobile

01. The problem

The existing product list did not work as stores grew

Product management lived inside a single panel in the website editor. That worked fine for a few products, but not for a real catalogue. As sellers added more, the panel got harder to use, especially on mobile. It wasn't a visual design problem. Product management needed its own structure, outside the website editor.

How could we give store owners a proper way to manage their products, instead of a panel that only worked for a handful of items?
The existing CMS flow: from the buried 'Products and categories' link in Edit Store, into the cramped side panel, to editing a single product

The old CMS flow: buried under "Products and categories," tucked into a side panel, one product at a time.

02. Research

What we learned from store owners

We spoke with people running real stores online, at different stages of their business, but with the same problem: managing products got harder as their catalogue grew.

Owners managing a growing product catalogue
People updating stock while away from their desk
Sellers who want clearer product and category organisation

We focused on the first group: people who already had several products online and were starting to feel the limits of a simple list.

03. What stood out

A few things stood out

01
Two different jobs

Editing a website and managing a product catalogue are different tasks. The old layout treated them as one.

02
Lists break down at scale

A short list works fine. A real catalogue needs categories. Scrolling alone doesn't cut it.

03
Mobile matters more than we assumed

Store owners often check stock or update products from their phone, away from their desk.

04
People expect familiar patterns

Store owners already use tools like Shopify. The system needed to feel familiar, not clever.

04. A clearer structure

Giving product management its own place

Instead of expanding the existing panel, we moved product management out of the website editor completely. It became its own section in the main navigation, with its own list and detail pages. That's a structural change, and it changes how the product can grow over time.

Before
Store Overview
Edit Store
↳ Products and categories
↳ Add new product
Orders
Business Profile
After
Store Overview
Edit Store
Orders
Products
Business Profile
The real flow we mapped for Peter, a store owner with 100 products, from Jimdo.com through to the new product list and detail pages

The actual flow we mapped out for Peter, a store with 100 products, from login through to the new Products section.

05. How we got there

Early brainstorming and discovery

I held an early brainstorming and discovery workshop with the PM, EM and both engineers. We mapped out every action Peter needed to take, and walked through his journey step by step, before sketching a single screen. Grouping those ideas together is what shaped the new IA.

Group Ideas, the affinity-mapping board from the team workshop, grouping ideas for product guidance, product management, left navigation, WYSIWYG editing and importing products

Group Ideas: clustering everything the team raised, from product guidance to importing products in bulk.

Journey map from the workshop, covering how Peter adds his first products and later manages a catalogue of a hundred

Peter's journey, mapped step by step: from adding his first products to managing a hundred of them.

06. Decisions

Key design decisions

A few decisions shaped the design, shown here in the real interface.

01
Separate list and detail pages
The product list and the product detail view became their own pages, not a pop-up. This gives the system room to grow, for variants, categories and stock.
02
Status shows what's actually happening
Draft, Published, In Stock, Out of Stock. Each one shows the real state of a product, something a store owner actually needs to act on.
03
Categories are part of the data, not just the display
Categories aren't a display trick. They're part of how each product record is structured.
04
Every row has clear actions
Each row in the list shows what you can do with that product: edit it, publish it, or view it live, without opening a separate page.
The product list: status, category management and row actions for every product

The list: status, category management and row actions, all at a glance.

The product detail page, its own screen with product fields, status and pricing, not a pop-up over the list

The detail page: its own screen, separate from the list.

07. Mobile

Managing products from a phone

Store owners often check stock or update a listing away from their desk. On mobile, they needed to be able to do everything they could on desktop.

The product list looks the same: status, stock and price at a glance
Every field on the product page is fully editable from the phone
Adding a new product works the same way it does on desktop
The full product list screen on mobile The full product detail and edit screen on mobile Pricing and inventory fields on the product detail screen, mobile
08. Testing

Testing the workflow with store owners

We tested the flow and the copy with real store owners, rather than only internal reviewers. Their feedback shaped some of the details in the design.

Notes from one of the usability testing sessions: participant background and a screen-by-screen walkthrough

Notes from one of the usability testing sessions: participant background on the left, the screen-by-screen walkthrough on the right.

No usage metrics are available for this project.

09. Reflection

What I learned

01

Moving something into the main navigation is a real decision. It's not a cosmetic change. The team has to support and maintain it going forward.

02

Good tools for running a business shouldn't draw attention to themselves. They should just work, even as the number of products grows.

03

Decisions like this work better when engineers are involved from the start, rather than brought in at review. This one worked because the PM, EM and both engineers helped shape it early on.

Designing for how small businesses actually work

Currently open to senior product design roles focused on practical, complex products.

Business Workspace Smart Forms × CRM Product Management APEX Lift
Get in touch →
← Smart Forms × CRM APEX Lift →