HOME
>
HUBBOX
HubBox Logo
TYPE
ECOMMERCE
YEAR
2025
ROLE
UX LEAD
Every shopper arrives at checkout with a default already in place: home delivery, which asks nothing of them. Pickup was visible, considered, and passed over anyway; shoppers weren't failing to notice it, they were weighing it and choosing something else. HubBox integrates local pickup into the e-commerce checkout, and treating that as a decision problem rather than a visibility one lifted take rate from 0.7% to 12% across 1,800+ retailers, driving tens of millions of parcels through out-of-home (OOH) networks.

TRANSFORMING LOCAL PICKUP

THE PROBLEM

THE LAUNCHEX

THE PROOF

THE WIDGET

TRANSFORMING LOCAL PICKUP

HOW UX STRATEGY DROVE MEASURABLE BUSINESS IMPACT
ACROSS 1,800+ RETAILERS

Transforming Local Pickup
IMPACT
0.7%→12%
Usage Rate
PEAK
Up to 28%
Usage in Key Markets
UI & UX
50+ new
Feature Improvements
STRATEGY
30,000+
Research Participants

Most teams treat low pickup adoption as a visibility problem: fix the tab, add a badge, write a better line of copy. The data said something more uncomfortable. Shoppers were not confused; they were making a rational decision under uncertainty, and pickup was not winning it. Once the problem is a decision rather than a display, the design job changes. It stops being about surfacing pickup and starts being about resolving the four things a shopper is actually weighing: cost, speed, proximity, certainty.

Pickup hadn't earned the switch
THE PROBLEM

Pickup hadn't earned the switch

Every shopper arrives at checkout with a default: home delivery. That default is powerful because it requires nothing from them. To move a shopper off it, pickup had to resolve a trade-off across all four axes simultaneously.

Cost, Speed, Proximity, Certainty

I owned the end-to-end UX of the shopper-facing pickup journey, from the checkout method step through location selection and confirmation, including research methodology, A/B testing infrastructure, and translation of findings into design & product direction.

UX LEAD LaunchEx, Widget, Confirmation state.
RESEARCH Methodology design, 30,000+ participants.
TESTING A/B infrastructure, reversion experiment design.
COMMERCIAL Activated by client success for retailer conversations.
RESEARCH

Three findings that changed the design direction

75%

Ranked free delivery top 3

Shoppers weren't anti-pickup on cost; they were opposed to uncertainty. Clarity between home delivery and pickup costs resolved this.

Make the saving absolute and present
70%

Ranked timing top 3

Shoppers needed less ambiguity towards timing. "Next day" outperforms "fast": factual language beats promotional claims.

Specific dates, not promotional language
95%

Proximity engagement in the Widget

Distance in metres keeps the journey abstract. "2 min walk" lets shoppers picture leaving, walking, arriving.

Walking time, not metres

The diagnosis: unresolved uncertainty accumulating across the decision. The design job was clarity and compression, not more information.

LAUNCHEX

A design argument in three stages

Before any of this, the pickup take rate sat at 0.7%.

LaunchEx static

Full shopper journey: LaunchEx → Widget selection → Confirmation

STAGE 01

Reframing the Decision Point

  • Replaced the tab-toggle with an explicit delivery comparison, presenting pickup as a full card, not a secondary option.
  • Courier branding, pricing tiers, and the value proposition visible without any interaction.
  • Widget opened directly on pickup selection, with no separate navigation step.
  • Hypothesis: if evaluating pickup costs more effort than accepting home delivery, home delivery wins regardless of the offer.
Reframing the Decision Point
STAGE 02

Embedding Selection Into the Checkout Step

  • Moved from a modal launch to inline selection within the checkout step.
  • Pickup pre-selected by default: not to force a choice, but to remove friction while keeping reversal easy.
  • List view prioritised: shoppers oriented via map but selected from the list.
  • List-first also eliminated a disproportionate API cost on every page load regardless of whether a purchase followed.
Embedding Selection Into the Checkout Step
STAGE 03

Specificity as the Mechanism

  • Savings signals consistently outperformed ambiguous costs: specificity resolves uncertainty.
  • Courier branding replaced an anonymous label; identity trust is a conversion signal.
  • Walking time replaced distance throughout: proximity you can picture, rather than proximity you have to calculate.
  • Remove any one element and performance degraded; the coupling was the mechanism.
Specificity as the Mechanism
THE PROOF

0.7% → 12% → 0.7% → 12%

The Proof: adoption rate chart

I removed the optimised version deliberately,
watched take rate drop back, then restored it. A designed experiment to prove mechanism.

Up to 28% in high-proximity markets Same pattern across Sandbanks, Glamify, and Oh Polly
THE WIDGET

Three decisions worth examining

At the LaunchEx, the job is persuading a shopper that pickup is worth considering at all. Inside the Widget, the job changes: make it easy to choose a specific location with confidence.

DECISION 01

The Map as Spatial Context

  • The instinct for a location-selection problem is to lead with the map, because spatial context feels obviously useful.
  • Research showed the map served a specific role: orienting shoppers to what was nearby, not helping them evaluate individual options.
  • 72% initially engaged with the map; evaluation and selection consistently happened in the list.
The Map as Spatial Context
DECISION 02

List View as the Primary Interface

  • 57% preferred the list for actually selecting a location.
  • Map-first failure mode: pin density described as "overwhelming". Evaluation needs side-by-side comparison, not spatial layout.
  • The list cuts through cognitive load. Name, distance, time, price, courier: all comparable at a glance.
  • Map stayed; hierarchy changed, and list became the primary selection surface.
List View as the Primary Interface
DECISION 03

Walking Time over Distance

  • Walking time converts abstraction into mental simulation: 95% of shoppers define "close" as within 10–15 minutes, not a set number of metres.
  • Distance formatting also fails: "1.500m" on a map pin was misread as "1500m" by a tested user.
  • The Widget shows both ("0.1mi / 2 min"), enabling objectivity and planning in the same field.
  • A typographic decision with a measurable behavioural consequence.
Walking Time over Distance

Pre-selected by Default

Pickup pre-selected by default redistributes effort: instead of requiring active selection to try pickup, it requires active selection to leave it.

One technical constraint had previously blocked this: the Widget needed to open on selection, which made a pre-selected state awkward. That constraint dissolved when I moved selection inline.

Something I'd known was high-performing finally became something the team could actually ship. The shopper remains free to choose home delivery throughout; the asymmetry is in effort, not in options.

REFLECTION

What This Changed

The most significant thing this project changed about how I work isn't visible in the product. Conversion problems are rarely purely design problems; they're organisational ones too.

Platform constraints shaped the work

Shopify introduced repeated friction between what research indicated was right and what was technically possible to ship. Navigating that without losing the design argument was a consistent challenge.

Client inertia had to be designed around

Any change to a live conversion page is treated with real caution. The design argument had to be made not just in design reviews but in sales calls and commercial conversations.

Handoff timing was a genuine tension

Involve engineers too early and the solution becomes engineering-led. Involve them too late and you're iterating against constraints that could have been surfaced months before.

Evidence is the permission

The mechanism that allowed us to move at all was the A/B testing infrastructure: not because it bypassed client concerns, but because it made the answer empirically available rather than rhetorically argued.

The most consistent pattern across this work is that the strongest design argument is results. Build the infrastructure to generate and prove, and design becomes a resource beyond visual.

MORE CASE STUDIES

PRISM・ECOMMERCE・DELIVERY APP

PRISM

WONDR・MEDICAL NETWORK・APP & WEB APP

ROOMS

WONDR・DESIGN SYSTEM

W_ DESIGN SYSTEM