ReturnFlow — Order Return Application 

ReturnFlow is a ServiceNow application we built as a capstone project on the RiseUp with ServiceNow programme. The idea came from a very real frustration. Returning an item online should be simple. Instead, most customers end up on hold, talking to bots, repeating themselves to multiple agents, and still not knowing when their refund will arrive. We decided to fix that.

The Problem

Retail returns are a $890 billion global challenge. Nearly 17% of everything sold online gets returned, and 67% of customers say a bad return experience would stop them from shopping with that brand again. Most organisations still handle returns manually through phone calls, service desks, and overwhelmed frontline staff. Requests get lost. Customers lose patience. Businesses lose loyalty.

The Solution

ReturnFlow is a self-service portal where customers can submit a return request in minutes without calling anyone. They fill in a short form, the system validates their order instantly, and they receive a confirmation straight away with their return reference number and drop-off instructions. From that point, everything is automated. The warehouse team gets notified and assigned a task. Finance gets notified when a refund needs processing. The customer gets updates at every single stage. Managers can see everything happening across all returns on a live dashboard. No phone calls. No hold music. No chasing.

How It Works

A customer visits the ReturnFlow portal and clicks Submit a Return Request. They enter their order number, last name and email address. The system checks all three against the order record to confirm their identity, and also checks that the order was placed within the last 14 days. If anything does not match, the request is blocked before a record is ever created.

Once validated, a return record is created with a unique reference number. The customer receives an email telling them where to drop off the item. When the warehouse team receives and inspects it, they record their decision on their task. If the return is approved, the customer is notified, and finance receives a task to process the refund. If it is rejected, the customer is told why automatically, because the warehouse team's reason is pulled directly into the rejection email. 

Once finance processes the refund, the customer is notified, and the return is closed after a 7-day waiting period.

WHAT WE BUILT IT WITH

Everything in this application was built inside ServiceNow using the tools available on the platform. We did not use any third-party software or external code libraries. The full list of platform features we applied:

Scoped Application — a self-contained app that keeps ReturnFlow separate from everything else on the platform.

Tables and Forms — we designed custom tables for orders and order returns, and built the forms that customers and fulfillers interact with.

Record Producer — the customer facing return request form that sits on the service portal.

Business Rules — we wrote three JavaScript business rules that run server-side. One validates the return request before a record is created, one auto populates the order date field, and one copies the customer details across to the return record automatically.

Flow Designer — the automation engine behind the whole process. It creates tasks, sends emails, waits for fulfillers to complete their work, and moves the return through each stage without anyone having to manually trigger anything.

UI Policies — rules that show and hide fields on the form based on what the customer selects. For example, the attachment field only appears when the return reason is Broken or Faulty.

Roles and Access Controls — we set up permissions so customers can only see their own requests, while administrators and fulfillers have the access they need to manage and process returns.

Service Portal — the customer facing interface where the return form and knowledge base live.

Knowledge Base — a step-by-step guide on the portal explaining how to return an item, written for customers who want help before they start.

Notifications — automated emails that go out to both customers and fulfillers at every stage of the return journey.

Dashboard and Reports — a manager-facing view showing return volumes, approval and rejection rates, and reasons for return. All updated automatically in real time.

Source Control — we connected the application to GitHub using ServiceNow Studio, so the full codebase is version-controlled and publicly accessible.

Client Script — A client-side code that runs on the browser and responds dynamically to user inputs, making the form intelligent.

The Team

This project was built by a team of six as part of the RiseUp with ServiceNow programme.

Emeka Iwu — Project Lead

Abiodun Alao — Implementer

Lawrence Egwuonwu — Implementer

Michael Ayeni — System Administrator

Gauri Phapale — System Administrator

Fiyinfoluwa Adebola Oriade — System Administrator

View the full project on GitHub including all scripts, documentation and business rules.