top of page
Passion Project · UX Case Study
images.jpeg

Amazon India —
Checkout, Redesigned

A comprehensive re-imagining of the checkout flow for Amazon India's mobile experience. This study tackles cognitive overload, fragmental address management, and payment friction to create a seamless journey from cart to confirmation.

Address
Bag
Payment
Confirmed

Role

UI/UX Designer (Solo)

Type

Passion Project

Timeline

Self-paced

Tools

Figma

Focus

Mobile-first checkout

Why This, Why Now

Why the checkout, and why Amazon

The checkout journey is the most critical juncture of any e-commerce experience. For Amazon India, this phase is uniquely complex, navigating a diverse user base with varying levels of digital literacy, fragmented address systems, and a high preference for localized payment methods. As the market evolves, the friction points within this flow become more apparent, risking conversion and user trust.

This case study explores how a strategic redesign can simplify the cognitive load of a feature-heavy interface. By prioritizing information hierarchy and streamlining address and payment selection, we can transform a functional necessity into a seamless, reassuring final step of the shopping journey. This isn't just about polishing the UI; it's about optimizing the conversion engine of a global leader for a regional audience.

The Problem

A flow that works, but never explains itself

Functionally, checkout on Amazon.in does its job — orders get placed, payments go through. But functioning isn't the same as feeling considered. Four problems show up consistently across the flow:

No sense of progress

The multi-step process feels like a black box. Users are often unsure how many steps remain or what milestones they've achieved, leading to checkout fatigue.

Outdated visual language

Legacy UI elements create a disconnect with the modern mobile ecosystem. The aesthetic friction makes the flow feel less trustworthy than more nimble competitors.

Flat emphasis

All information is given equal visual weight. Critical details like delivery windows and final totals compete with secondary alerts for user attention.

Reassurance, buried

Trust signals and security icons are often hidden at the bottom of long pages, failing to provide the mental peace required during high-value transactions.

70%

Average e-commerce cart abandonment rate across major online retailers.

Source: Baymard Institute

35%

Potential conversion lift from optimizing localized checkout experiences.

Source: Baymard Institute

Research & Audit
Five things the densest screen in the flow reveals

I ran a heuristic walkthrough of the full flow against six criteria, then went deeper on the screen carrying the most decisions at once: Payment & Order Review.

Visual Hierarchy

Moderate

Information density is high but grouping remains partially intact.

Emphasis & CTA Clarity

Weak

Secondary buttons often carry same weight as primary actions.

Information Grouping

Weak

Delivery slots and address details run into a single long list.

Visual Modernity

Weak

Legacy gradients and heavy borders date the experience.

Trust & Reassurance

Moderate

Security seals exist but are buried deep below the fold.

Error Prevention

Moderate

Inline validation works but lacks descriptive error recovery.

Current State

Current Screen Analysis

An actual screenshot of the Amazon.in product page — the real starting point, before a shopper even reaches the cart — marked up with what could be sharper.

amazon.jpg

Live screenshot, Amazon.in — captured for critique and reference purposes as part of this case study.

1

2

3

4

5

Header clutter

Prime Lite banner + stray "RAAKH" text compete with the core product focus

Weak trust signals

warranty/delivery/replacement info is plain wrapped text with no icons or grouping

Orphaned "Click to see full view" link

floats below thumbnails instead of being part of the main image interaction

Buried rating

4.3★ (51) is small and low-contrast for a flagship product

No breathing room

financial/promo complexity hits before the user has even processed the product itself

Who This Is For

Two shoppers, two different needs

QD

The Quick Decider

Mid-30s · Metro city · Orders weekly

Goal

Finish the transaction in under 60 seconds with zero visual distractions.

Frustration

Being forced to review address details she hasn't changed in three years.

CF

The Careful First-Timer

Early 20s · Tier-2 city · Orders occasionally

Goal

Seeing the final amount clearly and understanding when exactly the item will arrive.

Frustration

Ambiguous delivery dates and 'Order Total' lines that change at the very last step.

These two map onto two threads of the redesign: speed and minimal friction for the confident, and visible clarity and reassurance for the cautious. The same screens need to serve both without compromise.

The brainstorm, unfiltered

Behind The Scenes

Not everything makes it into a clean case study slide. Here's the actual mess — ideas I tried, killed, parked, or still haven't resolved.

KEPT

Moving delivery estimates to the very top. It’s the highest anxiety point for regional users waiting on logistics.

FLAGGING THIS

The Payment Review screen is still way too long on small devices. Need a collapsible summary.

KILLED

One-click voice buy.
Too many accidental purchases in noisy environments. The friction here is actually protective.

ASIDE

Why is the ‘Subscribe & Save’ CTA always yellow? Breaking common patterns for short-term gain might hurt trust.

INFORMED DIRECTION

Address verification via landmark rather than pin. It's how people give directions locally.

OPEN QUESTION

Should the address map be interactive? Might distract from the primary ‘Finish Order’ goal.

PARKED

Group-buy sharing feature. Interesting for Tier-2 cities but complicates the checkout hero path too much for V1.

FOR NEXT TIME

Gamifying the confirmed screen with regional badges. Too much for now, but a thought for loyalty.

Final Designs

High-fidelity screens
(coming soon)

01 Cart

02 Address & Delivery

03 Payment

04 Review & Confirm

Screens Currently under working, come back to view it.
bottom of page