Case studies / Practice case study · Retail

Moving a retailer's returns process online: the full requirements pack

Fernbridge Home’s online refunds took 12 days and a third of customer service calls were customers chasing them. I mapped the process, traced the delay to three root causes and wrote the requirements for a self-service returns journey, from the business case through to UAT.

Practice case study. Fernbridge Home is a fictional retailer and every figure is illustrative. I built this case to show how I run a requirements piece end to end. It is not client work.

12 → ~5days from return request to refund (estimated)
8 → 3pain points traced to three root causes
15 + 6business and non-functional requirements
45acceptance criteria across 15 user stories
Client
Fernbridge Home (fictional), 40 stores plus website
Sector
Retail
My role
Business Analyst, end to end
Delivery approach
Requirements baselined up front, built and tested in sprints
Tools
Markdown and Mermaid (BPMN-style maps), Excel/CSV for the RTM, Jira for UAT tracking

Executive summary

S
Situation

Fernbridge Home sells homeware through 40 stores and a website. Online sales have grown to about 35% of revenue, and online returns to around 1,800 a month.

C
Complication

Returns still run on email, phone calls and a shared spreadsheet. Refunds take an average of 12 days, about 33% of customer service calls are customers chasing a return, stores turn away online returns and nobody can say how much returned stock is waiting in the warehouse.

Q
Key question

What does the business need from a new returns process, and how will we know it works?

A
Answer

One return record in the order management system (OMS), status driven by events (label scans, inspection results) rather than emails, and more ways to send items back. That brings the refund time down to about 5 days. I wrote this up as a baselined BRD, 15 user stories with 45 acceptance criteria, a full RTM and a UAT plan.

1. The problem and the objectives

The returns process was designed when online sales were small. A customer has to email or phone to start a return, customer services log it in a spreadsheet, the warehouse updates that spreadsheet once a day and finance keys each refund by hand. I framed the problem with the sponsor (Director of Customer Operations) as a single problem statement, then agreed four measurable objectives before talking about solutions.

Problem statement

The problem of a manual, email-based returns process affects online customers, customer services, the returns warehouse and finance, and results in slow refunds, high call volumes and poor visibility of returned stock. A good solution would let customers start and track a return themselves, and pass each return between teams automatically.

IDObjectiveBaselineTarget (6 months after go-live)
OBJ-01Refund customers faster12 days average5 days or fewer
OBJ-02Reduce avoidable contact33% of calls about returns15% or less
OBJ-03Accept online returns in store0 of 40 stores40 of 40 stores
OBJ-04Know where every returned item isSpreadsheet only100% tracked in the OMS

Scope was agreed early to stop scope creep later: parcel-delivered online orders, self-service returns, prepaid labels, store returns, tracking and automatic refunds are in. Large furniture, exchanges, marketplace orders and changes to the 30-day policy are out, and exchanges are logged as phase 2.

2. Approach

I followed the standard requirements life cycle, with each document built from a template in my BA toolkit so the pack stays consistent.

  1. 01

    Frame

    Problem statement, objectives, scope, assumptions and early risks agreed with the sponsor.

  2. 02

    Engage

    Stakeholder register, power/interest map and a RACI so every decision has exactly one Accountable.

  3. 03

    Map the as-is

    Walk the current process with the people who run it, time each stage and log pain points with evidence.

  4. 04

    Design the to-be

    Design principles from the root causes, then the future process and a change summary.

  5. 05

    Specify

    BRD with MoSCoW priorities, then epics and user stories with Given/When/Then acceptance criteria.

  6. 06

    Trace and test

    An RTM from pain point to test case, and a UAT plan written from the acceptance criteria.

3. Stakeholders: who could stop this?

I listed 12 stakeholder groups and placed each on a power/interest grid. Three findings shaped the plan:

  • Store operations is the biggest risk. High influence and currently resistant, because in-store returns add work at the till. A two-store pilot and clear stock-handling rules come before any wider rollout.
  • The Data Protection Officer can stop go-live despite low day-to-day interest. Showing order details at the till needs DPIA screening early, not the week before launch.
  • Customers had not been asked. A short survey of recent returners tests the assumption that they want to track returns online.
Power interest grid placing the sponsor, ecommerce and customer service leads in Manage closely, store operations, retail IT and the DPO in Keep satisfied, and customers and store staff in Keep informed.
Figure 1. Power/interest grid for the 12 stakeholder groups. Select the image to open it full size.

A RACI then fixed decision rights: the product owner is accountable for the BRD and the backlog, finance for refund rules, the DPO for the DPIA, and the sponsor for the go-live decision.

4. As-is analysis: where the 12 days go

I mapped the as-is process as BPMN-style swimlanes (customer, customer services, warehouse, finance, store) and timed each stage against a sample of 200 returns.

As-is swimlane process map of online returns showing email requests, a shared spreadsheet, daily warehouse updates and manual refunds, with eight pain points marked.
Figure 2. As-is process map. ⚠ marks a pain point (P1 to P8). Select the image to open it full size.
StageAverage elapsed time
Request received → returns form sent1.5 days
Form sent → parcel arrives at warehouse4 days
Parcel arrives → inspected and spreadsheet updated3 days
Spreadsheet updated → refund requested from finance1.5 days
Refund requested → refund issued2 days
Total12 days

The key insight

Two-thirds of the delay (8 of 12 days) is internal handling and waiting between teams. Only the 4 days in the post are outside Fernbridge's control. A faster courier would not fix this; fixing the hand-offs would.

The eight pain points traced back to three root causes:

  1. No single record of a return. It lives in emails and a spreadsheet, so every team has to ask another team for its status (P2, P3, P6).
  2. Hand-offs by email. Each team passes work on by email or in daily batches, adding waiting time at every step (P1, P4, P6, P7).
  3. A process built around posting, not the customer. No label, no tracking and no store option (P1, P5, P8).

5. To-be design

For the to-be process, each root cause became a design principle: one record per return in the OMS; events, not emails, so status changes when a label is scanned or an item is inspected; more ways to send it back (prepaid QR label or any store); and people handle exceptions only, such as refunds over £250 or eligibility reviews.

To-be process map where the customer starts a return online, the order management system checks eligibility and issues a QR label, the warehouse scans on arrival and refunds are sent automatically.
Figure 3. To-be process map. ★ marks a new or changed step. Select the image to open it full size.
StageAs-is (days)To-be (days)Why
Request → label sent1.50Self-service; label issued straight away
In transit to warehouse43–4Unchanged (carrier); store returns refunded at the till
Arrival → inspection recorded31QR scan on arrival; inspection next day
Inspection → refund issued3.5under 1Automatic refund; finance approves exceptions only
Total (posted returns)12about 5Meets OBJ-01

The 1-day inspection assumes current warehouse staffing can keep up. That is flagged for testing with the warehouse manager.

6. Requirements: BRD, user stories and traceability

The BRD sets out 15 business requirements, each traced to a pain point or workshop and to an objective, plus 6 non-functional requirements covering availability, till performance (look-up within 3 seconds), data minimisation at the till, WCAG 2.2 AA, a 7-year audit trail and the 14-day legal refund limit.

Priority (MoSCoW)CountExamples
Must11Start a return online, automatic eligibility check, QR label or store, single return record, automatic refund
Should3Return reason capture, email/text notifications, returns report
Could0–
Won't (this phase)1Exchanges, deferred to phase 2

I broke the requirements into 6 epics and 15 user stories with 45 acceptance criteria in Given/When/Then form, so every story is testable. For example:

US-01 Start a return online (Must)

As a customer with a delivered online order I want to start a return from my account or with my order number and email so that I don't have to call or email customer services.

  • Given I enter an order number and email that don't match, when I submit, then I see “We can't find that order” and no order details are shown.
  • Given I select items and confirm, when the return is created, then I see a return number and the return is saved with status Requested.

The RTM links every requirement from its source (pain point or workshop) to its objective, user stories and UAT test cases. At baseline, no Must or Should requirement is left without a story or a test.

7. Testing: UAT plan

UAT is planned from the acceptance criteria: 18 test cases with full scripts for the 6 highest-risk ones (for example, a refund sent after approval, and a store refund to the original card). Testers are the people who will use the process: customer service advisers, store colleagues from the pilot stores, a warehouse operative and a finance analyst. Defects are tracked in Jira against the user stories.

Exit criterionTarget
Must test cases run / passed100% run, 95% or more passed
Open Critical or High defectsNone
Medium and Low defectsLogged with fix dates or agreed workarounds
Sign-offProduct owner, finance and store operations

8. Expected impact and next steps

  • Refund time falls from 12 days to about 5, meeting OBJ-01 and staying well inside the 14-day legal limit.
  • Avoidable calls should fall towards the 15% target, because customers can see status online and get updates.
  • Stores can accept online returns, starting with a two-store pilot before peak.
  • Operations gets a returns report: volumes, reasons, cycle time by stage and the inspection backlog.

Three open questions go to the right owners before build: refunding low-value returns at drop-off (finance), store refunds when the customer doesn't have their card (finance and retail IT), and who pays for the return label (sponsor).

What I'd do next on a real project

  • Validate the timings against live data rather than a sample before the business case is signed.
  • Run the customer survey early: it could change the priority of tracking and notifications.
  • Pair the store pilot with a short time-and-motion study at the till, since store operations is the main adoption risk.

Methods, deliverables and further reading

Every method and tool in this case study links to its page in my BA toolkit or glossary. Here they are in one place:

More case studies

Public data analysis · Healthcare

NHS A&E Waiting Times: Where Does the Pressure Build Up?

SQL and Python analysis of 30 months of NHS England A&E data, a live dashboard and five recommendations on where to focus improvement.

Read case study →

Practice case study · Social housing

Generative AI Adoption: Triage of Tenants' Repair Emails

An AI adoption assessment: options appraisal, requirements, UK GDPR and DPIA screening, a pilot plan and a Hugging Face prototype tested on synthetic emails.

Read case study →

Have a problem like this to work on?

I’d be glad to talk through how I’d approach it for your team.

Scroll to Top