> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Build a Product Returns Process
- URL: https://blog.jestor.com/build-product-returns-process/
- Published: 2026-09-17T22:33:53.000Z
- Updated: 2026-09-17T22:33:53.000Z
- Author: Bruno Bannach

To **build a product returns process**, four things have to connect: the original order, the customer conversation, the physical inspection, and the stock movement that follows.

## Why returns are handled inconsistently

They arrive unpredictably and touch several teams, none of whom own the process.

- Requests arriving by message with no order reference
- Inspection results recorded informally
- Stock adjusted manually, or not at all
- The customer chasing for an update nobody can give

## The stages to define

| Stage             | What happens                                     |
| ----------------- | ------------------------------------------------ |
| **Request**       | Customer submits, referencing the original order |
| **Authorization** | The return is accepted or refused, with a reason |
| **Receipt**       | The item arrives and is logged                   |
| **Inspection**    | A checklist confirming condition                 |
| **Resolution**    | Stock movement, refund, or replacement           |

## How to build it in Jestor

1. Create a returns table in **Jestor**, connected to orders and clients.
2. Capture requests through a public form, or from a **WhatsApp** conversation as a card.
3. Add a checklist for the inspection, completed before the record advances.
4. Record the resulting stock movement with type, quantity, and date.
5. Notify the customer automatically at each status change, by email or template.

## Why choose Jestor for returns handling?

Because **Jestor** is relational, the return references the original order rather than repeating its details — so the team sees what was sold, when, and to whom, from the return itself.

**SLA** tracking per stage shows where returns actually wait, which is usually inspection rather than the parts customers complain about.

## Frequently Asked Questions

### Can a return reference the original order?

Yes, through a connected field. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can the customer be notified automatically?

Yes, on each status change.

### Can inspection be evidenced?

Yes, through a checklist on the record.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.