Tasty Bite - Refund Request

Tasty Bite - Refund Request

One refund flow instead of calls and emails

One refund flow instead of calls and emails

Category

F&B

Platform

Website

Collaboration

Product Owner, Business Analyst, Developers

Year

2025 - 2026

Overview

Overview

TastyBite previously handled refund requests through calls and emails. Parents had limited visibility into what was happening after requesting a refund, while operators had to manually coordinate information across different parts of the system.


We improved the refund experience across the Customer Portal and Back Office, turning a fragmented manual process into a structured workflow that both sides could track and manage.

A refund request didn't really have a product workflow

A refund request didn't really have a product workflow

The existing process started outside the product. A parent would contact the team to request a refund, while operators handled the request manually behind the scenes.


This created two connected problems:

For parents, there was no clear way to submit, track, or understand the status of a refund.

For operators, processing a refund required coordinating information across different modules and manually communicating updates.

The problem was therefore bigger than adding a “Request Refund” button.

We needed to define what happens from the moment a refund is requested until the money is successfully returned.

We treated refund as a lifecycle, not a single action

We treated refund as a lifecycle, not a single action

We mapped the refund process from both sides of the experience and identified the different states a request could move through.

We structured the experience around a lifecycle:

Requested → Reviewed → Approved → Processing → Completed

with additional states for cases such as rejection or processing failure.

This became the foundation for designing both the customer and operator experiences.

Every refund needs a clear state

Every refund needs a clear state

One of the most important decisions was making the status of a refund explicit.

A parent shouldn't have to contact support just to know whether their request was received or what was happening next.


I therefore designed the experience so that each request had a visible status and clear next step.

This created a shared source of truth between the Customer Portal and Back Office.


The customer could understand where the request was, while operators could see what action was required from them.

We designed the flow around reassurance, not just submission

We designed the flow around reassurance, not just submission

The customer experience needed to answer three questions:

Can I request a refund?
The flow guides parents through the information required to submit a request.

What happens after I submit it?
The request moves into a trackable status instead of disappearing into a support process.

What if something goes wrong?
Error and failure states communicate what happened and what the parent can do next.

This shifted the experience from a one-time form into a transparent service journey.

The back office needed to turn requests into actionable work

The back office needed to turn requests into actionable work

On the operator side, the challenge was different.


Instead of simply receiving refund information, operators needed to review requests, understand their context, and move them through the appropriate states.


We designed the workflow so operators could manage refund requests within the Back Office rather than coordinating information manually across different places.

The workflow also made the current state and next action explicit, reducing ambiguity around how each request should be handled.

A good refund flow needs to explain what happens when things fail

A good refund flow needs to explain what happens when things fail

Refunds involve money, so failure states cannot be treated as edge cases hidden behind the happy path.


We designed explicit states for situations where a refund could not be completed successfully.

For example, when processing fails, the experience communicates the failure and provides a clear Retry action rather than leaving the user in an ambiguous state.


This helped make the workflow more resilient and reduced the need for users or operators to guess what to do next.

The customer and operator experiences had to speak the same language

The customer and operator experiences had to speak the same language

A key challenge was keeping the Customer Portal and Back Office aligned.

If an operator sees a refund as “Processing” but the customer sees no meaningful update, the system still feels broken.

We treated the status model as a shared product logic rather than something designed independently for each interface.

The same underlying lifecycle drives both experiences, while each surface exposes only the information and actions relevant to its user.

The workflow had to fit the existing TastyBite ecosystem

The workflow had to fit the existing TastyBite ecosystem

I worked with Product, BA, and Engineering to define how the refund workflow should interact with existing modules such as Pre-Order Management and Wallet Management.


This required looking beyond individual screens and considering how refund requests, order information, wallet balances, and processing states connect together.


The collaboration helped validate the workflow against existing product constraints and ensured the final design could be implemented across both customer-facing and operational surfaces.

Refund became a product workflow instead of a manual support process

Refund became a product workflow instead of a manual support process

The redesigned refund workflow was rolled out across the Customer Portal and Back Office.


Parents can submit refund requests and track their status within the product, while operators can review and process requests through a structured workflow.


The process became more transparent and trackable for both sides, with explicit states and recovery paths for unsuccessful processing.


There is currently no feature-level quantitative data available, so I’m intentionally not claiming specific improvements in processing time or support volume.

The real design challenge was connecting the workflow, not designing the form

The real design challenge was connecting the workflow, not designing the form

At first glance, “refund request” sounds like a simple customer-facing feature. But the real problem existed across the entire lifecycle — from customer request to operator action to payment completion.


Designing both sides of that workflow helped me think beyond the interface and focus on states, responsibilities, dependencies, and recovery paths.

It reinforced an approach I now bring to product problems more broadly:

When a feature involves multiple users and systems, design the workflow first — then design the screens around it.

Design. Feedback. Can't sleep.

Available for work

Design. Feedback. Can't sleep.

Available for work

Design. Feedback. Can't sleep.

Available for work

Create a free website with Framer, the website builder loved by startups, designers and agencies.