A smart default is a pre-selected option that represents the most common or most useful choice. The shopper can change it if they want, but most people accept the default and move on. In navigation and filtering, smart defaults reduce decision fatigue by removing one decision from the process entirely.
Every time a shopper opens a collection page, the store makes a default sort choice for them. Every time a filter panel opens, the store chooses which options are pre-expanded and which are collapsed. These defaults are invisible design decisions that shape the shopper’s experience more than most store owners realize.
Default sort order
When a shopper lands on a collection page, the products need to be in some order. The three most common defaults:
Best selling puts popular products first. This is a safe default because popular products have been validated by other customers — social proof in list form. The shopper sees the products most people buy, which reduces the effort of evaluating quality.
Recommended uses an algorithm (manual curation or automatic ranking) to surface the products the store wants to highlight. This gives the store control over what the shopper sees first — useful for promoting new arrivals, high-margin items, or seasonal picks.
Newest first works for stores where customers return frequently and want to see what’s changed. Fashion stores, home decor, and any store with regular new inventory benefit from this default.
Price: low to high is rarely a good default. It signals to the shopper that the store competes on price, and it pushes the store’s cheapest (often lowest-margin) products to the top. It’s a useful sort option, but not a helpful default.
The best default depends on the store and the collection. A “Best Sellers” page should default to best selling. A “New Arrivals” page should default to newest. A general collection like “Women’s Shoes” usually works best with “Best selling” or “Recommended.”
Pre-selected and pre-expanded filters
Filter panels on collection pages present another set of default decisions. Which filter groups are expanded (visible) and which are collapsed? Which options are pre-selected?
Pre-expanded filter groups should be the most commonly used. For a clothing store, Size and Color are almost always relevant. Showing these expanded by default saves the shopper a click — they see the options immediately and can start filtering. Less common filters (Brand, Material, Pattern) can start collapsed.
Pre-selected filters are more nuanced. In most cases, no filter should be pre-selected — the shopper arrives expecting to see all products in the collection, and pre-selecting a filter confuses them (“why am I only seeing blue products?”). The exception is when the store can infer the shopper’s preference: a logged-in customer who always buys size M could see size M pre-selected with a clear indication that it’s a personalized default.
“Selected for you” defaults walk the line between helpful and confusing. If the store shows a badge or label — “Showing your size (M) — show all” — the shopper understands why the filter is active and can remove it. Without that label, the pre-selected filter feels like a broken collection page.
Default views
Some stores offer different ways to view a collection: grid view (thumbnails), list view (details), or compact view. The default view shapes the shopper’s experience significantly.
Grid view is the standard default for visual products (clothing, furniture, art). Shoppers scan thumbnails quickly and rely on images to make decisions.
List view works better for information-heavy products (electronics, tools, B2B supplies) where specifications matter more than appearance. Each product gets more space for details.
Most stores default to grid view because it shows more products per screen, which works for the browsing behavior that most shoppers use. Offering a view toggle lets the shopper switch, but the default should match the most common behavior for that product category.
Nudging without forcing
Smart defaults are a form of nudging — gently steering the shopper toward a good decision without taking away their choice. The key is that the shopper can always change the default. A pre-selected sort can be changed to “Price: low to high.” A pre-expanded filter can be collapsed. A grid view can be switched to list view.
If the shopper can’t easily change the default, it’s not a default — it’s a restriction. And restrictions create frustration, not reduced fatigue.
The best smart defaults are invisible. The shopper doesn’t think “oh, this page is sorted by best selling” — they just see products in a sensible order and start browsing. The default did its job by removing a decision the shopper didn’t want to make.
This article is part of the larger guide on Too many choices: how navigation can reduce decision fatigue.