Farshad Amiri
← All case studies

Case study 02 · NatureLand · Checkout

From a long scroll to a checkout people finish

  • Problem

    81 of every 100 shoppers who reached checkout never tapped Pay.

  • Approach

    Pay-button events showed where they dropped. Session recordings showed why — so I rebuilt checkout around how people decide.

  • Result

    Almost twice as many shoppers reached Pay, and errors at Pay fell 78%.

Role
Senior Product Designer
Team
Product, Tech, QA
Platform
Mobile app
Data
Pay-button events, Microsoft Clarity
Reading
7 min
Visit NatureLand ↗
The new NatureLand checkout on three phones: Step 1 with the delivered address and a delivery method for each parcel, Step 2 with coupon code, rewards points, wallet and payment methods, and the Payment successful screen.

19 → 36

shoppers who tapped Pay

Per 100 shoppers at checkout, before and after release

+89%

more shoppers reached Pay

Relative change from 19 to 36 per 100

−78%

errors at Pay

Taps on Pay before the required details were complete

2 steps

instead of one long page

Delivery first, then payment

01 · The problem, Context · Empathize · Define

Shoppers reached checkout, then stalled

A Natureland order can split into several parcels, and each parcel has its own delivery options. The old checkout put everything on one long page: items, delivery for every parcel, summary, coupon and payment. The button at the bottom changed its label to whatever was still missing.

19 of 100

shoppers who reached checkout tapped Pay

Before the redesign

74%

of Pay taps ended in a successful payment

14 of 19

~3 screens

of scrolling before Pay

One long page

The checkout funnel, per 100 shoppers
  • 100reached checkout
  • 19tapped Pay
  • 14paid successfully

81 of every 100 shoppers who reached checkout never tapped Pay. That was the biggest loss, so that is where I looked first.

Before: the checkout journey

  1. Opens checkout“Let’s finish this.”
  2. Scrolls past the items“Where do I pick delivery?”
  3. Misses a parcel’s delivery“I thought I chose it.”Pain point
  4. Finds Knet already selected“Where is my card?”Pain point
  5. Looks for the coupon“I had a code…”Pain point
  6. Taps the button, details missing“Why didn’t it work?”Pain point

Steps 3 to 6 are where checkout broke: the page asked for decisions people could not see.

What the recordings showed — four patterns, again and again

  • 01 · Lost in the scroll

    People scrolled up and down the long page, looking for the next step.

  • 02 · Delivery went unnoticed

    Each parcel needed its own delivery choice. With two or more parcels, people picked one and thought they were done.

  • 03 · Searching for a payment method

    Knet was selected by default. Anyone paying another way had to hunt for the payment section at the bottom.

  • 04 · The coupon was hard to find

    A small “I have a coupon” link sat under the summary. People with a code had to look for it.

02 · The approach, Empathize · Define · Ideate

Events showed where people dropped, recordings showed why

I used two sources together. An event on the Pay button told us how many people tried to pay. Microsoft Clarity recordings and heatmaps showed what they did before that. Then I traced every pattern to the way people make decisions.

  • HMW 1

    How might we show only the decisions that matter at each moment, so no parcel is left without delivery?

  • HMW 2

    How might we make the payment method and savings easy to find and confirm, right before people pay?

Why each pattern happened

Why each pattern happened
ObservedWhat was happeningPrinciple
Lost in the scrollEvery decision sat on one surface, so people had to hold too much in mind at once.Cognitive load · Hick’s law
Delivery missed for a parcelThe options for a parcel were far from the next parcel and out of view.Proximity · Visibility of status
Searching for paymentA preselected Knet looked like a decision already made.Default effect · Status quo bias
Coupon not foundA small link at the end of a long page has very low salience.Salience · Serial position
Pay tapped too earlyThe button let people act before the order was ready.Error prevention

Fix the page, or split the journey?

I judged each option by how many of the four observed problems it solved.

  • Option A

    Polish the single page

    Clearer section titles and a sticky summary. Cheap, but the page stays long and parcel choices stay far apart.

    Solves 1 of 4

  • Option B

    Validate on Pay

    Scroll to the missing field when Pay is tapped. Catches errors, but only after people fail.

    Solves 1 of 4

  • Option C

    Two-step checkout

    Step 1: address and delivery for each parcel, with the cost so far. Step 2: coupon, points, wallet and payment method.

    Chosen · solves 4 of 4

03 · What we did, Prototype

Two focused steps instead of one long page

Same content, new order. Each screen asks for one kind of decision, and the button moves forward only when that decision is made.

  • The old one-page checkout: delivery address, then each parcel’s items with its own delivery options (Express, Regular, Scheduled) stacked in one long scroll.

    Before · One page

    about 3.2 screens of scroll

    1. Items come first. The first delivery choice starts below the fold.
    2. Each parcel has its own delivery list, far from the others.
    3. The coupon is a small link under the summary.
    4. Knet is preselected near the end of the page.
    5. The button label changes to whatever is missing.
  • New checkout, Step 1: the delivered address, Parcel 1 as a compact card of product thumbnails, and its delivery methods with Standard Delivery selected.

    After · Step 1 · Delivery

    about 2 screens

    1. Each parcel is a compact card: thumbnails and item count.
    2. Delivery options sit under their parcel, with price and a clear selected state.
    3. Subtotal and delivery fees before payment.
    4. Continue to pay moves on only when every parcel has delivery.
  • New checkout, Step 2: coupon code field with View Coupons at the top, rewards points and wallet balance in KD, and payment methods with Apple Pay selected.

    After · Step 2 · Payment

    about 1.9 screens

    1. The coupon field sits at the top, with View coupons next to it.
    2. Points and wallet balance are shown in KD, ready to apply.
    3. Every method is an equal card with its logo, including Cash on delivery.
    4. The summary updates with each saving; the button names the method.

In production Knet stays the default. Apple Pay is shown selected as a sample state for the development team.

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
Two steps: delivery, then paymentChunking · Goal gradientLost in the scroll
Delivery options under each parcel, with a selected stateProximity · Visibility of statusDelivery missed for a parcel
Continue to pay checks every parcel firstError preventionPay tapped too early
Payment methods as equal cards with logosRecognition over recall · Status quo biasSearching for payment
Coupon at the top of the payment stepSalience · Serial position effectCoupon not found
Fees, points and wallet in KD before PayAmbiguity aversion · Loss aversionUnclear final price

04 · The result, Test

Almost twice as many shoppers reached Pay

We compared the same measures before and after release: the event on the Pay button, and Clarity recordings.

  • Shoppers who tapped Pay

    Per 100 shoppers at checkout

    • Before release19
    • After release36
    Bar length on a 0–100 scale.
  • Errors at Pay

    Index, before = 100

    • Before release100
    • After release22
    Taps on Pay with required details missing.

36 of 100

shoppers tapped Pay after release

Up from 19 before, +89%

−78%

errors at Pay

Fewer taps on Pay with details missing

74%

of Pay taps succeeded before release

14 of 19 · success after release is the next measure

05 · What I learned, Reflection

The order of decisions did most of the work

Three lessons I carry into every project.

  • Events say where, recordings say why

    The Pay event showed the drop. Clarity showed the scrolling, the missed parcel and the search for a payment method.

  • Visible decisions get made

    People skipped what they could not see. Putting each choice next to what it affects did more than any warning.

  • Fix the order before the pixels

    The content barely changed. The order and grouping of decisions did most of the work.