Farshad Amiri
← All case studies

Case study 03 · NatureLand · Product card

From a card you look at to a card you shop from

  • Problem

    Every action on a product card needed a trip to the detail page, so carts held only 4 products on average.

  • Approach

    I walked through every task from the list, counted the steps, and compared three card concepts by how many shopper needs they covered.

  • Result

    One card with five states. Shoppers added almost three times as many products, without leaving the list.

Role
Senior Product Designer
Team
Product, Tech, QA
Surface
Product lists
Measure
SKUs added to cart
Reading
6 min
Visit NatureLand ↗
NatureLand product card, before and after: the old Vanilla milk card with an Out Of Stock label and no action, and the new card with a larger image, a clear heart and a + button next to the price.

4 → 11

SKUs added to cart, on average

Before and after the new card

+175%

more products per cart

Relative change, about 2.7×

1 tap

to add a product

Instead of a trip to the detail page and back

5 states

one card for every situation

Add, added, edit, notify, notified

01 · The problem, Context · Empathize · Define

A product card you could only look at

On Natureland, product lists are where shopping happens: dairy, bakery, fruit, household. The old card showed an image, a name and a price, and nothing else. To add a product, change the amount or ask to hear when it was back in stock, shoppers had to open the detail page.

0 actions

on the old card

Apart from opening the product

~4 steps

to add one product

Open it, add, go back, find your place

4 SKUs

added to cart on average

Before the new card

Before: shopping from a list

  1. Scans the list“Milk, yogurt, bread…”
  2. Opens the detail page“Just to add one thing.”Pain point
  3. Taps Add to cart“Done. Now back.”
  4. Goes back to the list“Where was I?”Pain point
  5. Finds a product out of stock“When will it be back?”Pain point
  6. Opens it again to get notified“Another detour.”Pain point

Every action cost a detour. The longer the shopping list, the more detours, so people stopped early.

Counting the cost of every action

Counting the cost of every action
TaskWhere it happened · stepsWhat shoppers need
Add a productDetail page only · ~4 stepsA fast add for familiar products
Change the amountDetail page or cart · 3–4 stepsEdit without leaving the list
Know what is in the cartCart only · 2 stepsSee it next to each product
Hear when it is backDetail page only · ~4 stepsAsk once, right where the product is
Save a favouriteCard, faint heart · 1 stepA clear saved state

What the walkthrough showed — four reasons carts stayed small

  • 01 · Familiar products don’t need a detail page

    Grocery shoppers rebuy the same things. For them the detail page added steps, not information.

  • 02 · Every detour breaks the flow

    Going back meant finding your place again, so each extra product felt like work.

  • 03 · The list hid what was in the cart

    Shoppers had to remember what they had added, or open the cart to check.

  • 04 · Out of stock was a dead end

    The card said “Out of stock” and stopped. Asking for an alert took another trip.

02 · The approach, Define · Ideate

Bring the action to where the decision happens

I traced each pattern to how people decide, then compared three card concepts by how many of the four shopper needs they covered: a fast add, editing the amount, seeing what is in the cart, and a next step when a product is out of stock.

  • HMW 1

    How might we let shoppers add, change and track products in one tap, without leaving the list?

  • HMW 2

    How might we turn an out-of-stock product from a dead end into a next step?

Why each pattern happened

Why each pattern happened
ObservedWhat was happeningPrinciple
Small cartsEvery add cost a detour, so the effort grew with each product.Interaction cost · Fogg Behaviour Model
Losing your placeLeaving the list broke the shopping flow.Context switching · Flow
Not knowing what’s in the cartThe list gave no feedback about added products.Visibility of status · Recognition over recall
Out of stock = stopThere was no next step, so the intent was lost.Dead end · Goal abandonment
Unclear saved stateA faint heart didn’t show whether a product was saved.Visibility of status

Three ways to bring the action to the list

  • Option A

    A better detail page

    A bigger Add to cart button on the detail page. Easy to build, but every action still needs a detour.

    Covers 0 of 4

  • Option B

    A stepper on every card

    Always show − 1 +. Fast, but it crowds every card and makes the list noisy before anyone adds anything.

    Covers 3 of 4

  • Option C

    One card, five states

    Start with a single +. After the first tap, show the count, and tap it to edit. Out of stock switches to Notify me.

    Chosen · covers 4 of 4

03 · What we did, Prototype

One card, five states

Each state answers one question a shopper has: can I add it, is it in my cart, how many, and what if it’s gone?

  • The old product card for Vanilla milk: a New Arrivals badge, a faint heart, an Out Of Stock label over the image, the name, the struck-through price with a 50% tag and the new price, and no action button.

    Before · the old card

    1. Display only: image, name and price
    2. “Out of stock” label with no next step
    3. Adding, quantity and alerts all happen on the detail page
  • The new product card for Vanilla milk: a larger image on a light background with variant thumbnails, a heart in a white circle, the name and size, the discounted price, and a + button next to the price.

    After · the new card

    1. + sits next to the price, so one tap adds the product
    2. A larger, cleaner image on a light background
    3. A clear heart in a white circle
    4. More white space between image, details and action

The state system — a shopper always has a next step

  • Product card in the Add state, with a + button next to the price.

    State 1

    Add

    + next to the price. One tap adds one item.

    Fitts’s law · Low effort

  • Product card in the Added state, with the button showing the count in the cart.

    State 2

    Added

    The button shows the count, so shoppers see what is in the cart from the list.

    Visibility of status

  • Product card in the Edit amount state, with a − 3 + stepper and a filled red heart.

    State 3

    Edit amount

    Tap the count to open − 3 +. A saved product shows a filled heart.

    Feedback · Reversible

  • Out-of-stock product card with no price and a Notify me button.

    State 4

    Out of stock

    Notify me replaces the dead end with a next step.

    No dead ends

  • Out-of-stock product card with the alert set and a Do not notify button.

    State 5

    Alert on

    The alert is set, and can be turned off from the same place.

    Progressive disclosure

Every change maps to a principle, and to a problem we saw

Every change maps to a principle, and to a problem we saw
ChangePrincipleFixes
+ on the cardFogg Behaviour Model · Fitts’s lawA detour to add
The count on the buttonVisibility of status · Recognition over recallNot knowing what’s in the cart
A stepper after the first addProgressive disclosure · FlowA detour to change the amount
Notify me on the cardNo dead ends · Zeigarnik effectOut of stock = stop
A clear heart and a cleaner imageVisibility of status · Aesthetic-usabilityAn unclear saved state, a busy card

Trade-offs we chose on purpose

Every speed gain moved something else.

Trade-offs we chose on purpose
DecisionGained · gave upHow we handled it
Add from the cardOne tap instead of a detour · fewer detail page visits, so less exposure to details, variants and subscriptionTapping the image or name still opens the detail page
+ first, stepper laterA calm, scannable list · changing the amount takes one extra tapThe count shows at once, and one tap opens the stepper
Fast addMore products per cart · a higher chance of adding by mistakeThe count gives instant feedback, and − undoes it on the spot
A bigger cardA clearer image and action · fewer products per screenTight white space and one action per state
No price when out of stockWorks within a technical limit · shoppers can’t check the price of a missing productNotify me is the main action, so there is no dead end
More SKUs per cartBigger baskets · more SKUs doesn’t always mean more revenueOrder value and checkout rate are tracked next

04 · The result, Test

Carts grew from 4 to 11 products

We compared the average number of SKUs added to cart before and after the new card.

SKUs added to cart

Average per cart · scale 0 to 12

  • Before4
  • After11

11

SKUs added to cart, on average

Up from 4 with the old card

+175%

relative change

About 2.7× more products per cart

1 tap

to add, edit or ask for an alert

All from the list, no detours

05 · What I learned, Reflection

Put the action where the decision is

Three lessons I carry into every project.

  • Put the action where the decision is

    Shoppers decide on the list, not on the detail page. Moving the action there changed behaviour more than any visual polish.

  • Every state needs a next step

    A card that ends in “Out of stock” loses the shopper. One button kept the intent alive.

  • Feedback builds momentum

    Seeing the count after each tap made adding the next product feel easy.