HYPD · 2023 · Sole Designer · B2B + B2C

When the customer can't return and the ops team can't process, who fixes it?

35% fewer support tickets 25% faster processing 40% less manual work
MY ORDERS
What would you like to do?
Exchange item
Return item
CONFIRM EXCHANGE
Confirm
EXCHANGE CONFIRMED
Context

Creator commerce, built differently.

HYPD is a platform where creators sell directly to their audiences. Not a marketplace. Not a brand store. A creator-led shopping experience where trust between the influencer and their community is the product as much as anything in the cart.

That trust makes returns complicated. A bad return experience doesn't just lose a customer — it damages the creator's relationship with their audience. The stakes are higher than a standard e-commerce return.

Creator Audience Purchase Return / Exchange
The problem

HYPD didn't own its shipping.

That one fact broke everything else.

For customers

No process to follow. No status to track. No confidence anything was happening. They did the only thing that made sense — they contacted support. Every time.

For the ops team

Requests arriving from everywhere. No central system. No way to prioritise. COD returns handled case by case with no consistency. Everything manual. Everything slow.

Frustration on both ends and no single source of truth for anyone involved.

Role

Sole designer, both sides.

Scope B2B + B2C
Duration 2 months
Delivered Successfully shipped
Deliverables Research · Flows · Wireframes · Hi-fi · Handoff
The key insight

"The best e-commerce experiences with third-party shipping don't over-promise on tracking. They design for honesty instead."

That became the guiding principle for everything on the customer side.

How I approached it

Four steps. Both sides. In parallel.

01

Research both sides in parallel

Ops team workflow interviews and engineering constraints mapping. Running simultaneously, not sequentially. The constraint — HYPD didn't own its shipping — shaped every design decision that followed.

02

Competitive analysis

How do the best platforms handle third-party shipping limitations? The answer was consistent — design for honesty and clarity, not tracking promises you can't keep.

03

B2B first

Built the ops tool before touching the consumer flow. The ops team's ability to process requests was the dependency everything else sat on.

04

Iterative walkthroughs

Not a single handoff review at the end. Continuous loops with the ops team throughout the design phase. Every iteration validated against their real workflow.

The solution — customer side

A guided journey. No support contact needed.

A self-service mobile flow that walked customers through initiating a return or exchange step by step. Clear status communication at every point. Designed for honesty — no false promises about tracking that couldn't be kept given HYPD's shipping constraints.

Interactive flow · Mobile

Click any screen to preview

01
My Orders Order list with exchange and return CTAs
02
Order Detail Full order breakdown — address, payment, exchange window
03
Track Order Delivery timeline
04
Exchange or Return Choose between exchange or return & refund
05
Select Reason Pick a reason for the return
06
Select Size Choose the new size for exchange
07
Confirm Exchange Review details before confirming
08
Exchange Confirmed Success state with live timeline
09
Return Reason Reason selection for return flow
10
Return Confirmed Return success with refund timeline
The solution — ops side

Full visibility. Finally.

A structured order management tool that gave the operations team complete visibility and control over all incoming requests. A dedicated flow for handling COD returns that replaced case-by-case chaos with a consistent repeatable process.

Live dashboard · Order management · Ops team

Processing each request — five states.

Every exchange request moved through five states giving the ops team full control and a clear audit trail at every step.

5 states · Exchange request processing · Ops team

Impact

The numbers that came back.

35% Reduction in support tickets
25% Faster processing time
40% Less manual data entry for ops
15% Increase in post-transaction satisfaction
40% Improvement in COD return resolution
What I'd do differently

Two things I'd change.

1

Push earlier for a business decision on COD

Push earlier for a clear business decision on COD return handling before designing around it. We spent time iterating on design solutions for a problem that actually needed a business call first. Design can't solve a decision that hasn't been made.

2

Advocate for a phased launch

Advocate harder for a phased launch. The B2B ops tool alone would have delivered real value to the ops team immediately. Waiting for both sides to be complete delayed impact that didn't need to be delayed.