Self-Service Refunds

Service

An Iceland Foods case study

Three issues drive the vast majority of post-delivery contact at Iceland Foods: items that arrived defrosted, items that arrived damaged, and items that were missing from the order. All three end the same way — with a phone call, a queue, and a refund. We moved that entire interaction onto the order detail page, so customers can resolve issues in minutes and the contact centre can focus on the cases that actually need a human.

Project Info

ROLE:

UX Designer

COMPANY:

Iceland Foods

DATE:

[TODO]

TEAM:

[TODO: PM, engineers, etc.]

[TODO: Hero screenshot 1]

[TODO: Hero screenshot 2]

The Challenge

How might we let customers resolve the three most common post-delivery issues themselves — without opening the door to refund abuse?

Research & Discovery

Working with the contact-centre and operations teams, we mapped the top reasons customers called after a delivery. Three categories dominated the volume — and the calls themselves were short and structured, which made them a perfect fit for self-service.

The 3 reasons we set out to solve

Defrosted: Frozen items arrived thawed, often unusable, and the customer wants money back on the affected items.

Damaged: Packaging or contents were crushed, leaking, or otherwise unsellable on arrival.

Missing: Items were on the receipt but not in the delivery — picking, packing, or driver error.

For every one of these, the customer's intent was the same — refund the affected items and get on with their day. The contact centre call was just friction in the middle.

The Solution

We embedded the refund flow directly inside the order detail page in the customer account. Customers can pick the affected items, choose the reason (defrosted, damaged, missing), and submit a refund request on a per-order basis — without ever picking up the phone.

Per-order, per-item granularity: Refunds are scoped to the specific order, so the customer can flag exactly which items in a given delivery had a problem.
Three structured reasons: The flow asks for defrosted / damaged / missing — matching the three categories the contact centre was already trained to resolve.
Instant resolution for valid cases: Approved refunds are processed without an agent in the loop, cutting the customer's wait from a phone queue to a few taps.

Abuse safeguards

Letting customers self-serve refunds is only safe if the system can spot patterns that don't add up. We designed two layers of safeguarding into the flow:

Account history check: The system reads the customer's order and refund history. First-time refund requests follow one path; accounts with a heavy refund pattern get held for manual review.
Refund amount threshold: Above a defined value, the refund request is routed for human approval rather than auto-processed — so high-value claims still get the scrutiny they need.

Both thresholds are tunable by ops, so the team can tighten or loosen the gates as they learn from live data.

Design Process

Wireframes & Iterations

[TODO: Wireframe / iteration 1]

[TODO: Wireframe / iteration 2]

Usability Testing & Findings

[TODO: What you tested, with whom, and what changed because of it.]

Final Designs

[TODO: Final design 1]

[TODO: Final design 2]

The Impact

[TODO: Outcomes after launch — revenue, conversion, CSAT, contact-centre deflection, etc.]

[TODO: Headline metric]

XX%

More Iceland work

See Other Iceland Case Studies