← Home E-commerce · Dunelm · 2022

Fixing a cart
conversion crisis

After a cart redesign launched at the UK's largest homewares retailer, conversion from cart to checkout dropped by 22%. I used GA and ContentSquare to diagnose the problem, formed three hypotheses, and ran a series of multivariant tests that not only restored conversion but exceeded it.

Role
Lead Product Designer
Platform
Responsive web
Tools
GA, ContentSquare, UT.com, Lyssna
Team
Cart team, Engineering
Dunelm cart redesign
Situation

Conversion dropped 22% after a redesign

Dunelm operates over 170 stores across the UK and reported annual revenues of approximately £1.71 billion. As Lead Product Designer on the Cart team, I began analysing analytics data shortly after joining and discovered that cart to checkout conversion was significantly below the target benchmark.

After confirming with engineering that there were no code leaks or technical errors, it was clear the problem was a usability one.

Cart to checkout conversion rate
Goal
54%
Before
32%
After
68%
Funnel showing exit rates after redesign
Funnel showing redesign exit rates
Research

Reading the data before forming opinions

I pulled raw data from GA and ContentSquare to understand performance across the cart page. Once I confirmed the 22% conversion drop, I used ContentSquare to review heatmaps and session recordings of users navigating the cart, watching where attention went, where users hesitated, and where they left.

I also ran exit surveys on cart pages and conducted user interviews to understand intent and mental models around fulfilment and checkout.

Google Analytics ContentSquare Heatmaps Session recordings Exit surveys User interviews UT.com Lyssna
Hypotheses

Three reasons users were not converting

1
Fulfilment options disconnected from checkout

User interviews showed that customers expected fulfilment choices to directly progress them to checkout. The spatial separation was breaking that mental model.

2
Error messages too conversational

Users found the messaging confusing. It was unclear which items in the cart the message referred to, causing frustration and abandonment.

3
Mixed fulfilment options caused confusion

When a cart contained items requiring different fulfilment methods, the global fulfilment selector did not make it clear how each item would be handled.

Solutions

Testing each hypothesis independently

I validated each proposed solution individually using user testing on UT.com, surveys via Lyssna, and custom analytics funnels I built to isolate each variant. Running them separately ensured I could attribute any change in conversion to a specific intervention.

Solution 1 — fulfilment options above checkout button
Solution 1: fulfilment options moved above the checkout button
Solution 2 — item level error messaging
Solution 2: error messaging moved to item level
Solution 3 — fulfilment grouped at item level
Solution 3: fulfilment options grouped at item level
Result

Conversion restored and exceeded

I released the three variants into production for 50% of customers, split across three challengers at 33% each, measured over one month. I tracked conversion rate to checkout, time on page, average order value, revenue per visitor, bounce rate, pages per session, and return visit behaviour via multi-session cookies.

"I integrated multi-session cookies to track user behaviour across return visits, understanding where they entered the site before landing back on the cart page and where they went afterwards."

+3%
Checkout conversion lift above baseline
68%
Final cart to checkout rate
3
Variants rolled into production
Successful conversion design
Successful conversion design in production
Multivariant methodology

Each hypothesis was tested in isolation with dedicated analytics funnels to ensure clean attribution of any conversion movement.

Staged rollout

Variants were introduced sequentially into production to confirm they worked in combination, not just individually.

Return visit tracking

Multi-session cookies allowed behavioural tracking across visits, understanding the full journey not just the session.

Cross-team collaboration

Worked alongside engineering to confirm no technical root cause before beginning design investigation.

Want to chat more about this project?

This case study covers the core of the work. I am happy to discuss the user workshop process, team dynamics, design retrospectives, and the detailed research methodology in a conversation.

Send me an invite to chat