Shoppers in an online store aren't there to admire the design. They're looking for the right product, comparing options, checking the price with shipping and deciding whether to trust the store. Every extra click, confusing filter or form field is a reason to close the tab and open the next store in the search results.
That's why ecommerce design is first and foremost about designing the shopper's journey, from the category page to the "Place order" button. Let's go step by step through what belongs in the catalog, the product page and the cart, where shoppers most often drop off, and what to check before launch.
The shopper journey: where ecommerce UX starts
Before drawing screens, map out the path of someone who came to buy. In a typical store it looks like this:
- Entry. The homepage, a category from the menu, a page from Google search, or an ad that goes straight to a product.
- Listing. The list of products in a category, where the shopper narrows the choice with filters and sorting.
- Product page. Photos, price, specs, shipping terms. This is where the decision is made.
- Cart. Checking what's in the order, the quantities and the total.
- Checkout. Contact details, shipping, payment and confirmation.
The key point is that people enter this chain at different places. Someone who searched for a specific model name lands straight on the product page, so every page has to work as an entry point: show people where they are and give them a way forward.
Test the journey against real scenarios. Buying a specific model, finding a product for a task, repeating a past order, comparing two options: each scenario has its own key screens and its own bottlenecks. Ecommerce conversion comes down to how many people get through each step, so look for the weak link along the whole chain, not just on the homepage.
Catalog design: navigation, filters and search
Catalog structure and menu
The catalog structure is built around how shoppers search, not how products are organized in the inventory system. Internal warehouse groups like "Misc-2" or a breakdown by supplier mean nothing to a shopper. Check category names against search queries: that makes the catalog clearer for people and gives you landing pages for SEO at the same time.
A large catalog needs a menu with subcategories, but no deeper than two or three levels. Breadcrumbs show people where they are and let them go up a level without returning to the homepage.
Filters in an online store
Filters are where a store either helps people choose or gets in their way. A good set of filters answers the question "what attributes do people use to narrow down this product?" For car batteries, it's capacity, polarity and dimensions; for clothing, size, color and price; for building materials, purpose and dimensions.
- each category has its own filters; a shared list "for the whole catalog" is almost always useless;
- the most important filters come first and are expanded, rare ones are collapsed;
- each value shows the number of products, and empty options are disabled;
- selected filters are gathered above the listing, and each can be removed with one tap;
- results update instantly or via a clear "Show N products" button.
Sorting and search
The default sort order determines what the shopper sees first. Usually that's "popular" or "recommended," followed by price and newest. Products that are out of stock are better pushed to the end of the list.
Site search should handle typos, SKUs and synonyms, and the suggestions in the search bar should show products and categories before the user hits Enter. The "no results" page deserves its own thought: instead of a dead end, it should offer similar queries, popular categories and contact details.
The listing: what to show in a product tile
A tile in the listing is a short version of the product page. It's how people decide whether to open a product, so it should contain what they use to compare items, and nothing more.
- a photo on a consistent background and at a consistent scale, so products can be compared at a glance;
- a name that distinguishes models rather than getting cut off halfway;
- the price, and with a discount, the old price next to it;
- availability or lead time;
- 2–4 key parameters, if that's how people choose in this category;
- an "Add to cart" button that doesn't take people away from the listing.
Ratings and review counts make sense when there really are a lot of reviews. "Bestseller" and "New" badges work as long as there are few of them: if every third product has one, the eye stops noticing. For large categories, a toggle between grid and list view, where more specs are visible, is useful.
Product page design
The product page is the most important page in the store. It's where shoppers should get answers to every question they would otherwise ask a salesperson in a physical store.
A good product page answers the shopper's questions before they think about calling.
- Photos. Several angles, details, the product in use, zoom on tap. For products where size matters, a photo with a clear sense of scale or a diagram with dimensions.
- Price and availability. Next to the name, in large type. If the price depends on a variant, such as color, volume or size, it updates when the variant is selected, without reloading the page.
- Buy button. One primary "Add to cart" button above the fold. After the tap, the shopper sees that the item was added and can go to the cart or keep shopping.
- Shipping and payment. Delivery times and costs for the shopper's location right on the product page, not only on a separate "Shipping" page.
- Specs. A table of parameters in a consistent format across the category, with the key ones higher up and the full list below.
- Description. What the product is for, who it suits, how it differs from neighboring models: everything the dry specs don't say.
- Compare and wishlist. Needed in categories where people choose between similar models by parameters: electronics, batteries, tools.
- Reviews and questions. With customer photos, sorting and the store's replies to criticism.
Below the main information, related products and alternatives are appropriate. They help when they're chosen with care: a charger for a battery, a stand for a Christmas tree, not random items from the same category.
Cart and checkout
At this step the person has already decided to buy, and the design's job is not to get in the way. An online store's cart should let people change quantities, remove an item and restore it, enter a promo code and immediately see how the total changed.
Fewer fields and guest checkout
Every form field is a reason to stop. An order usually needs only a name, phone, email and address if delivery is involved. Address entry works best with autocomplete, and the location should be detected automatically with an option to change it. Mandatory registration before purchase is an extra step: guest checkout should always be available, and an account can be offered afterward.
Shipping, payment and the final total
Shipping options are shown with delivery times and costs for the selected address, and pickup points appear on a map and as a list. Payment methods are listed before the person hits "Pay": card, digital wallets, cash on delivery, invoice for business customers if the store sells to companies.
The final total with shipping, discounts and fees is visible before the last step. A total that grows on the payment screen breeds distrust even when there's an honest reason. After the order, the shopper sees the order number, items, total, delivery method and what happens next: when they'll get a call, when a notification will arrive.
Trust and the mobile version of the store
What builds trust
Before a first purchase from an unfamiliar store, people check that there's a real company behind it and clear terms. For that, the site needs:
- the seller's company details, address, phone number and ways to get in touch;
- clear terms for shipping, payment, returns and warranty;
- reviews, including links to external review platforms;
- tidy product pages without empty fields or broken photos.
Search engines look at the same signals when they assess how trustworthy a store is, so work on trust also helps with SEO.
The mobile version of the store
The mobile version of a store isn't a shrunken desktop. Filters move to a separate panel with a "Show products" button, the buy button sticks to the bottom of the product page, and the cart is one tap away in the header. Form fields open the right keyboard, and payment supports fast methods that don't require typing in card details by hand.
Common mistakes in ecommerce design
Most mistakes appear when the design starts with the homepage and banners, and the catalog, product page and cart get whatever attention is left over.
- A slider instead of navigation. A homepage made of rotating banners that makes it hard to get to the categories.
- The same filters for every category. The shopper sees dozens of parameters when they need two.
- No states. Nobody thought through what an empty cart, a sold-out product, a payment error or an empty filter result looks like.
- Surprises at the end. The shipping cost or the minimum order value appears only at the last step.
- Pop-ups. A newsletter signup and a chat widget cover the buy button on mobile.
Checklist: ecommerce design before launch
Run through this list on a phone and a computer, placing several test orders in different ways.
- from any product page it's clear where you are, and you can go to the category;
- each category has its own filters, and selected filters are visible and removable with one tap;
- search finds products by SKU and with typos;
- listing tiles show the photo, price, availability and buy button;
- the product page shows price, availability, delivery time and cost, specs and reviews;
- adding to cart gives clear feedback;
- orders can be placed without registering, and the form has only the necessary fields;
- the final total with shipping is visible before moving to payment;
- empty states and errors are designed: empty cart, out of stock, payment failed;
- on mobile, the buy button and cart are always within reach, and filters open in a separate panel;
- analytics has a funnel set up: product page, cart, checkout, order.
As a web design and development agency, we design stores starting from the catalog and shopper scenarios: first we analyze the product range, competitors and the purchase path, then we design the key screens for mobile and desktop. Our projects, including online stores, are on our work page.
FAQ
How many pages need to be designed for an online store?
The minimum set is the homepage, a category page with the product listing, the product page, the cart, checkout, the order confirmation page, search and the customer account. Each key page is designed for mobile and desktop, plus states: empty cart, no results, out of stock, payment failed. Everything else is assembled from the same components.
Should customers have to register to place an order?
Mandatory registration is an extra step before purchase. It's better to let people check out as guests with a phone number or email, and offer to save their details and create an account in one click after the order. Returning customers will still find it useful.
How do we find where an online store is losing customers?
Set up a step-by-step funnel in analytics: listing views, product page views, add to cart, checkout started, order placed. The step where noticeably more people drop off than at the neighboring ones is the place to investigate. From there, session recordings and click maps of that page help, along with conversations with the sales team, who hear customers' questions.
Can a store be designed on a ready-made template?
For a start with a small catalog, yes, if the template covers the filters, attributes and shipping options you need. When products have complex parameters, compatibility-based search, wholesale pricing or custom logistics, the template starts getting in the way, and the design is built around the specific catalog and shopper scenarios.




